| name | getting-started-with-venture-capital-in-strawberry |
| description | Help a venture investor use Strawberry across market intelligence, deal sourcing, company research, pipeline review, meetings, diligence, investment memos, introductions, and portfolio monitoring. Use when someone wants a useful first investing workflow or a connected way to run venture work over time. |
Get Started with Venture Capital in Strawberry
Help the user see how their companion can support the whole investment process, then complete one
useful piece of work. Do not require a full firm setup or force every investor through the same
funnel.
Paint the investing system
Explain briefly that Strawberry can work across visible browser tabs, logged-in research tools,
email, calendar, meetings, CRM records, data rooms, files, approved apps, and the public web. It can
keep sources beside claims, remember how the firm interprets its thesis, and continue from research
into meeting briefs, diligence, memos, introductions, or reviewed record changes.
Show four connected parts of venture work:
- Develop the investment view: understand markets, startup ecosystems, and how relevant
investors are deploying capital.
- Build and manage deal flow: source companies, research and qualify opportunities, use the
network thoughtfully, and keep the pipeline useful.
- Evaluate and decide: prepare for founder conversations, test the important questions, and
build a traceable memo or decision record.
- Support and monitor the portfolio: notice material company changes, make useful connections,
and carry current context into firm and portfolio work.
The central deal-flow path often runs source → research and qualify → meet → diligence → memo and
decision, but users may enter anywhere. Keep the system visible without treating it as a required
sequence.
Find a useful first win
Start with the live investment work in front of the user. If they are unsure, use approved thesis,
pipeline, calendar, tabs, files, memory, and connected context to suggest a small set of relevant
options and explain why they fit. Useful starting moments include:
- researching one company before deciding whether to spend more time on it;
- mapping a market or startup ecosystem around an investment question;
- sourcing a calibrated set of companies against the firm's thesis;
- preparing for an upcoming founder or partner meeting;
- reviewing active opportunities and deciding what needs attention; or
- checking what has materially changed at a portfolio company.
Suggest another app only when it would materially improve the chosen result. Continue from visible
tabs, files, or details the user provides when those are enough.
Develop the investment view
- Map a startup ecosystem: read
strawberry/venture-capital/map-startup-ecosystem for the
companies, investors, accelerators, relationships, and investment activity shaping a startup
market.
- Map a broader market: read
strawberry/research-analysis/map-a-market when the decision
depends on category boundaries, value chains, experts, associations, or established companies
beyond the startup ecosystem.
Build and manage deal flow
- Source thesis-matched companies: read
strawberry/venture-capital/source-investment-opportunities. Begin with a varied sample so the
investor can correct the interpretation before the search expands.
- Research one opportunity: read
strawberry/venture-capital/research-an-investment-opportunity for a source-linked company view,
preliminary thesis fit, contradictions, and the questions worth resolving next.
- Review the active pipeline: read
strawberry/venture-capital/review-investment-pipeline to identify priorities, stale assumptions,
missing evidence, and useful next actions.
- Find a network path and prepare an introduction: read
strawberry/operations/make-a-warm-introduction. Never imply a current relationship without
evidence or send before the people, context, and destination are approved.
- Apply approved CRM changes: read
strawberry/sales/keep-crm-updated. Follow the investment
team's actual objects, stages, fields, and source-of-truth rules rather than importing sales
semantics.
Evaluate and decide
- Prepare for a founder, partner, or expert conversation: read
strawberry/operations/prepare-for-meetings.
- Turn a completed conversation into evidence and follow-through: read
strawberry/operations/debrief-a-meeting.
- Test the material underwriting questions: read
strawberry/venture-capital/conduct-investment-due-diligence.
- Build the investment case and decision record: read
strawberry/venture-capital/write-an-investment-memo.
Keep company claims, independent evidence, calculations, internal context, interpretation, and
unresolved questions distinct. Preliminary fit is not proof of investment quality, and the
companion does not autonomously approve, reject, or communicate an investment decision.
Support and monitor the portfolio
- Review material company changes: read
strawberry/venture-capital/monitor-a-portfolio-company for current news, financing, leadership,
hiring, product, customer, regulatory, and market signals that match the accepted monitoring bar.
- Prepare a firm or portfolio update: read
strawberry/operations/prepare-a-status-update.
- Find commitments or ownership gaps: read
strawberry/operations/close-open-loops.
- Make a useful connection: read
strawberry/operations/make-a-warm-introduction and preserve
private relationship context until sharing is approved.
Improve the process through real work
Use feedback on actual results to learn the firm's thesis interpretation, trusted sources,
qualification bar, memo structure, writing style, materiality rules, and review preferences. Save a
custom or team skill only after those choices prove durable.
Suggest a Routine only when the trigger and signal rules are clear—for example, a weekly pipeline
review or a portfolio monitor that checks agreed sources and drafts a digest when a material change
appears. Define the systems, output, destination, approval behavior, and stop conditions. Do not
automate introductions, investment decisions, data-room access, CRM writes, or external messages
without sufficient scoped permission.
The guide has done its job when the user understands the larger system, completes one useful piece
of investment work, and can see the most relevant next step.
