Skip to content
Abhiram Chandramohan
MVP and launch

The first ninety days decide whether an idea becomes a company

Abhiram Chandramohan · 2 min read

In short

The first ninety days decide whether an idea becomes a company or an expensive lesson. Use them to validate the problem, map the customer journey and launch a lean MVP with evidence.

The first ninety days decide whether an idea becomes a company or an expensive lesson. That is the stretch I work on with founders, and it rewards a very particular kind of discipline.

Days 1 to 30: what problem are we really solving?

Map the problem space and the people who feel the pain most. Frame one sharp problem statement and the riskiest assumption behind it. Resist the urge to open a design tool.

Days 31 to 60: what is the cheapest way to be proven wrong?

Design the smallest experiment that can disprove your riskiest assumption: a landing page with a real price, a concierge version run by hand, a clickable prototype in front of ten customers. Map the customer journey alongside it: how people find, choose and stay.

Days 61 to 90: ship something real

Build the MVP or prototype, AI-assisted, in days rather than months. Then read the evidence and commit: scale it, pivot it or kill it.

What makes the ninety days work?

  • Small shipments, short cycles. Weekly sprints with something real to show at the end of each one.
  • Validated learning over opinions. Every feature starts as an assumption and earns its place with evidence.
  • Customers at the centre. Talk to users every sprint, not once before launch.
  • Inspect and adapt. Retrospectives turn every miss into the next experiment.

At the end you should have a validated problem, a launched MVP and evidence you can take to customers and investors.

  • #MVP
  • #Startups
  • #Agile

FAQ

Questions on this topic

Still unsure? Send a note with your idea and I'll tell you honestly whether I can help.

Ask me directly

With a validated problem and a tight scope, an MVP or prototype can be built in days to a few weeks, especially with AI-assisted development. If it is taking months, the scope is probably too big.

Keep reading

AI adoption

AI adoption · 2 min read

Where AI actually pays off for early-stage founders

AI makes small teams faster when it is used in research, building and operations with a clear problem in mind. It does not replace talking to customers or deciding what to build.

Read article

Idea discovery

Idea discovery · 2 min read

Fall in love with the problem, not your solution

Most startups fail by building the wrong thing, not by building it badly. Founders who start from a sharp problem statement and its riskiest assumption reach a go, pivot or kill decision before they spend their savings.

Read article

Let's talk

If you are at zero, I am your first call.

Tell me about the idea, the customer and where you are stuck. I will tell you honestly whether I can help, and what the first ninety days should look like.

  • A validated problem, not a guess
  • A launched MVP, faster and cheaper
  • Evidence for customers and investors

Your details are only used to reply to you.