Free self-check
Just raised? Check your build plan.
Ten questions for founders who just closed a round. One minute. See whether your plan will turn the money into a product your investors can see working, and what to fix before you spend.
- A scoreOut of 100, with what it means for you.
- Your checklistWhat is in place, what is partly there, what is missing.
- What to doA fix for each gap, with steps to check it yourself.
- A report to shareBy email if you want it, ready to forward to your team.
Your result
0/100
Ready to build
Your plan has what it takes to turn funding into a working product. The risk now is speed: who can build it, well, in the weeks you have.
Gaps to close first
The plan is promising, but the gaps below tend to cost months once spending starts. They are listed by impact: close them before the clock runs.
High risk to the runway
Several basics are missing, so money can be spent without a product investors can see working. Start with the first item below: scope and milestones decide everything after them.
What to close first
- Is your first release defined as a short list of things a user can do?
Cut the first release down to what a user can do end to end. A short, testable scope ships in weeks; a wishlist ships in quarters.
- Do you have a 90-day plan with dated milestones you could show your investors?
Write the 90-day plan with dates. Investors fund milestones, and the plan is also how you will know in week four whether you are on track.
- Do you know who builds it in the next 30 days, with senior people involved?
Settle who builds the first version before you start hiring. A senior team can ship the first version while you recruit, so the clock doesn't stop for hiring.
Read: Senior team or first hires? The first 90 days after a round
- Will the code, cloud, domains and data live in accounts your company owns?
Put everything in your company's own accounts from day one. Moving it later costs time, and investors' due diligence will ask.
- Will product analytics be in place from the first user?
Instrument before you accelerate. The first users are the ones that tell you what works, and data you didn't collect can't be recovered.
- If AI is part of the product, have you decided how you'll measure whether it's right?
Decide how you'll measure AI quality before you build it: real examples, a pass mark and a review loop. Without it, "the AI works" is an opinion.
Read: How to trust an AI score
- Are automated tests and a release process planned from the start?
Plan tests and releases from the first week. They are what lets a small team ship every week without breaking what already works.
- If you'll hold several customers' data, is keeping it apart designed and tested?
Design and test customer data separation from the start. It's far cheaper than retrofitting it, and it's the first thing an enterprise buyer will ask about.
Read: One system, many customers: proving their data stays apart
- Will your team and investors get a written progress report every week?
Report in writing every week: what shipped, what's next, what's blocked. It keeps investors confident and catches drift while it's still cheap.
- Is your budget tied to milestones, so you know what each month of runway buys?
Tie spending to milestones and agree in advance what success looks like for each one. Runway is measured in what it buys, not in months.
No gaps on this list. You are ready to move fast.
Want an engineer to review your plan?
Send your result to an engineer and get a reply with how we would approach your first 90 days. Free, with no obligation.
Built from real projects
Every question comes from what we have seen go right, and wrong, on real work. See it in practice:
AI Sales-Coaching Product, Working in 8 Weeks →Questions
- Is it really free?
- Yes. The result appears on the page, and nothing is asked of you to see it.
- What happens to my answers?
- They are scored in your browser. We only receive them if you choose to send them to an engineer or ask for the report by email. See our privacy policy.
- Will you add me to a newsletter?
- No. If you ask for the report, we send that one email. We only write again if you reply.
- Who is behind it?
- EVDevs: experienced engineers working with AI on revenue, data and AI systems. About us.