01
Write the problem in one sentence.
Not "I want to build an app for X." Write the problem your future user has. If you can't write it in one clear sentence, you don't understand it yet. Example: "Small medical practices lose revenue because they don't follow up on denied insurance claims."
02
Find 5 real people with the problem. Talk to them.
Not surveys. Not polls. Call or meet 5 people who might have this problem and ask: "How do you handle this today? How much is it costing you?" If you can't find 5 people willing to talk about the problem, the problem isn't real enough yet.
03
Define the minimum version that proves the idea works.
Not the full vision. The smallest possible version that proves one person will pay (or use) it. A Google Form and a spreadsheet often proves the concept before any code is needed.
04
Calculate the unit economics before you build.
If you charge ₹500/month and it costs you 2 hours/customer to support, you make ₹250/hour. Is that worth it? What's the maximum number of customers you can handle alone? What changes when you hire one person?
05
Build the landing page before the product.
Write the page that explains the product as if it exists. If you can't write a clear, convincing page, you don't understand the value proposition yet. The page also becomes your first acquisition channel the moment you launch.
06
Get one person to say "I would pay for this."
Not "that's a great idea." One real person saying "I want this, here's how much I'd pay" — ideally with a small upfront payment. Pre-sales beat market research every time.
07
Now build. Start with the one feature that delivers the core value.
Everything else is a distraction until step 6 is done. In Build45, we enforce this: you don't build feature 2 until feature 1 is shipped and tested by a real user.