Find your next move
One question about where you are, one optional question about what’s in the way, and a straight answer about what to do next, including when the answer is that you don’t need to hire anyone yet.
Step 1 of 3
Where are you right now?
Pick whichever sentence sounds most like your situation. There is no wrong answer and nothing to fill in.
Step 2 of 3 (optional)
What’s actually in the way?
This adjusts the answer below. Skip it and the answer still stands.
Step 3 of 3
Your next move
Where you are
This is the most expensive place to guess. Every decision you make now (scope, stack, what’s in the first version) sets the cost of everything after it. It’s also the place where a small amount of paid thinking saves the most money.
You also said: I don’t know what to build
That’s the Discovery Sprint’s whole job. It exists because this is the most common blocker and the most expensive one to leave unsolved.
What matters now
- Separate must-have from nice-to-have, in writing, with someone who’ll argue with you
- A realistic build order and cost range before you commit to a budget
- A tech stack decision with a reason attached to it
What can wait
- Building anything
- Hiring a team
- Scale, performance, and infrastructure planning
- The features you’ll want in year two
Common risk at this point
Going straight to a developer with a feature list. You’ll get a quote for the list, not for the product, and the list is almost always too long.
What I’d suggest
A Technical Discovery Sprint ($1,200, 1–2 weeks). You get an MVP Scope and Roadmap Document: features prioritised, stack chosen with reasoning, build order, cost estimate, risks. You can hand it to any developer. You don’t have to hire me to build it.
One next action
Book a 30-minute call. If the scope is already clear enough that you don’t need the sprint, I’ll say so.
Think this is close?
This is a general answer built from one sentence about your situation. Thirty minutes gets you a specific one.