On this page
- Define the first 90 days with a venture builder
- Days 1 to 15: build the baseline before building features
- Days 16 to 30: test the commercial thesis in the market
- Days 31 to 60: build only what the test requires
- Days 61 to 75: turn learning into a go-to-market motion
- Days 76 to 90: prepare the company for the next decision
- Sources
Your first 90 days with a venture builder should end with evidence, not a thicker slide deck. By day 90, you should know which customer problem you are pursuing, what product you can credibly ship next, how your unit economics behave, and what milestones make a funding conversation worth having.
Define the first 90 days with a venture builder
The first 90 days with a venture builder are a working contract between you and the people building alongside you. It should state the business outcome, the decisions required to reach it, the operating cadence, and the evidence needed to decide whether to continue, change direction, or stop. “Build an MVP” is not a 90-day outcome. “Validate that a defined customer segment will pay for a solution to a stated workflow problem” is closer.
Strong plans separate founder-owned work from venture-builder-owned work. You remain responsible for conviction, customer access, domain context, and hard decisions. Your venture builder should take ownership alongside you across validation, product, fundraising, and go-to-market, with named deliverables and deadlines.
A 90-day plan also needs mutual commitments. A March 2026 interview with Sequoia’s George Robson describes its new-company 90-day plan as a two-way contract: founders may commit to pricing clarity, design customers, or critical hires, while the investor commits to defined support.Source The principle applies to any serious build relationship: both sides need observable commitments.
Start with one outcome: At day 90, an informed outsider should be able to see what you learned, what you built, what customers did, and what decision follows from that evidence.
Days 1 to 15: build the baseline before building features
The opening two weeks are for reducing ambiguity. Founders often arrive with a broad market, a product idea, and a list of features. That is raw material, not a plan. Your first job is to turn it into a narrow initial thesis: one customer type, one painful job, one current alternative, and one reason that alternative fails.
Document the baseline before anyone starts making product decisions. What do you know because you have seen it happen repeatedly? What do you believe but have not tested? What would make the opportunity materially smaller? This prevents the team from treating founder intuition as validated demand.
At Nebula, our operating system moves through Idea, Market, Product, Team, Fit, Validate, Funding, and Scale. The early work should make the first four stages explicit rather than allowing them to blur into a rushed product build. You can review the full venture-building process before agreeing on the work plan.
- Customer definition: Specify the buyer, user, sector, location, company stage, and trigger event.
- Problem statement: Describe the costly or frequent workflow failure in the customer’s language.
- Competitive reality: List what customers do today, including spreadsheets, staff, agencies, or no action.
- Evidence inventory: Separate interviews, revenue, pilots, usage, and assumptions into different buckets.
- Decision log: Record the decisions made, the evidence behind them, and what could reverse them.
Do not spend these days debating a brand identity or polishing a pitch. If you cannot describe the customer and problem with precision, every downstream activity becomes expensive guesswork.
Days 16 to 30: test the commercial thesis in the market
The next phase is customer discovery with a commercial purpose. The goal is not to collect compliments about your idea. The goal is to learn whether a defined group has a problem severe enough to change behaviour, spend money, share data, introduce you internally, or commit time to a pilot.
Run interviews around real past behaviour. Ask what happened the last time the problem appeared, what it cost, who felt the pain, what was tried, and why the current process remains in place. Ask for artefacts where possible: invoices, screenshots, workflows, procurement steps, support tickets, or reports. These details expose whether the problem is urgent or merely interesting.
By day 30, convert the research into a commercial thesis. You should be able to state the customer segment, the job being solved, the buyer, the buying trigger, the initial price hypothesis, and the path to acquiring the first users. If you cannot, keep researching. A product team cannot compensate for a vague buyer.
| Weak discovery output | Useful discovery output |
|---|---|
| “People liked the concept.” | “A defined buyer described a repeated workflow cost and agreed to evaluate a paid pilot.” |
| “Our market is large.” | “We can identify and reach a specific first customer segment through named channels.” |
| “Customers want more features.” | “Customers will switch if we remove this measurable bottleneck.” |
This is also the right moment to agree on what would invalidate the thesis. A venture builder should not protect the original idea from evidence. It should help you act on the evidence quickly.
Need an operator-led partner to turn customer evidence into a build plan? Build with us.
Days 31 to 60: build only what the test requires
Once the commercial thesis is clear enough, product work begins with restraint. The first version should prove a specific customer behaviour, not imitate the finished company you imagine five years from now. Every feature must have a stated user, a stated job, and a stated learning goal.
Nebula’s Venture Validation phase runs from Months 0 to 4, while Product Development begins during Months 3 to 9. That overlap matters. Validation does not end when product work starts. Product work should create sharper validation, and customer feedback should continue to change product priorities.
Use a weekly product rhythm. Review what shipped, what users did, where they dropped off, what support questions appeared, and what decision that evidence changes. If a feature does not alter a business decision or user behaviour, it is likely not the next priority.
Do not confuse activity with progress. A polished prototype without user action is a design asset. A rough workflow that earns repeated use, pilot commitment, or payment gives you a basis for product investment.
During this period, define the operating metrics that matter at your stage. For a B2B company, that could mean qualified conversations, pilot conversion, active users within an account, time to first value, and renewal intent. For a consumer business, it may mean acquisition source, activation, repeat use, and contribution after direct delivery costs. Choose a small set; a dashboard with too many metrics hides weak signals.
Make the technical plan match the test. Your architecture, tools, and hiring choices should support the next evidence milestone. Premature engineering creates cost before you have proof that customers need the capability.
Days 61 to 75: turn learning into a go-to-market motion
A working product is not a go-to-market plan. By this point, you need a repeatable account of how a prospect moves from first contact to value. Start with one primary acquisition path rather than trying content, partnerships, paid media, outbound, communities, and referrals at the same time.
Map the path in operational terms. Where do the first prospects come from? Who contacts them? What message earns a response? What happens in the first meeting? What must the customer see before they agree to a pilot or purchase? Where does delivery break? Each answer should create an owner and a measurable weekly action.
For early-stage founders in India, pricing deserves direct attention. Do not defer it because your product is unfinished. A price conversation tells you who controls the budget, which alternative you are replacing, how procurement works, and whether the problem carries economic weight. Free usage can be useful when it tests activation or retention, but free access is not evidence of willingness to pay.
- Choose a narrow beachhead: Begin with the segment where pain, access, and speed of learning are strongest.
- Write one sales narrative: Lead with the customer’s costly problem and the specific outcome you can produce.
- Set qualification rules: Define what makes a prospect worth founder time.
- Track the funnel weekly: Review outreach, meetings, proposals, pilots, conversion, and reasons for loss.
- Capture objections: Turn repeated objections into product, positioning, or pricing decisions.
Go-to-market and Scale begins from Month 9+ in our operating model, but the foundations start far earlier. You cannot wait for scale to learn how customers buy.
Days 76 to 90: prepare the company for the next decision
The final 15 days should produce a decision package, not a ceremonial demo day. Put the customer evidence, product learning, commercial results, financial assumptions, and unresolved risks in one place. Then decide what the next 90 days are for: deeper validation, product expansion, revenue conversion, a key hire, or fundraising preparation.
Fundraising comes after you can explain what capital will change. Investors will ask what you know about the customer, why this team can execute, how the product creates value, what traction means in your model, and what the money funds. Your deck should be a compressed version of your operating evidence, not a collection of market claims.
At Nebula, we work from prototype to scale-up through Venture Building, Fractional Leadership, and Startup School. Venture Building is the deepest engagement, with institutional co-founders across product, fundraising, and go-to-market. Fractional Leadership places senior operators part-time, while Startup School is an 8-week cohort with 16+ live sessions designed to make founders investor-ready. See the engagement models to judge which level of involvement fits your stage.
Your 90-day review should answer five questions:
- What did customers do that changed our view of the problem?
- What product behaviour proved or weakened our thesis?
- What commercial motion showed promise?
- Which assumptions remain untested and materially risky?
- What single outcome matters most in the next 90 days?
A good plan creates momentum without trapping you in it. The output is not certainty. It is a company that learns faster, makes cleaner decisions, and earns the right to commit more time and capital.
Sources
- Sequoia's George Robson: An Inside Look at Sequoia and What it Takes to Build Generational Companies
Your first 90 days should leave you with proof, priorities, and an accountable plan for the next stage. If you want a venture builder that works alongside you across validation, product, fundraising, and go-to-market, Build with us.
Enjoyed this? Get the next one in your inbox.
Fundraising guides and validation frameworks, every two weeks. No spam.
Frequently asked questions
What should founders achieve in their first 90 days with a venture builder?
Founders should leave with a defined customer segment, evidence of problem severity, a focused product test, an early go-to-market motion, and a clear decision on the next 90 days.
Should fundraising be a priority in the first 90 days?
Fundraising should follow evidence. Use the first 90 days to clarify what customer, product, and commercial proof will make a funding conversation credible.
Ready to build your startup?
We work with a small number of founders each year — mentorship, fundraising support, and a co-founder network included.
Start a conversation
Talk to the founder directly. We reply within two working days.
Applying to Nebula 1.0? Apply here →