Before you build anything, do five things in order: write the idea down in one page, talk to twenty people who have the problem, check who already solves it, decide what the smallest version must prove, and only then work out what it costs and who should build it. Talking to developers and designing screens come after those steps, not before.
Most founders arrive at the same moment: the idea is clear in their head, it has been for weeks, and the obvious next step feels like finding someone to build it. That instinct is understandable and it is usually the most expensive mistake in the whole journey. This post gives you the order of operations we recommend to every founder who contacts us with an idea and no product yet.
Step 1: Write the idea down in one page
Not a pitch deck and not a feature list. One page that answers five questions in plain language:
- Who has the problem? Be specific. "Small restaurant owners who take phone bookings" is a person. "Businesses" is not.
- What is the problem, in their words, and what does it cost them today in time, money or stress?
- What do they do about it now? Spreadsheets, WhatsApp groups, a competitor, nothing?
- What would your product do differently, in one sentence?
- How would you make money from it?
If you cannot answer one of these, that is your first task. Everything downstream depends on it, and it is far cheaper to discover a gap here than in week six of development.
Step 2: Talk to twenty people who have the problem
Not friends, and not people who might be interested one day. Twenty people who match the description in question one. Ask them how they handle the problem today, what they have tried, and what they would pay to make it go away. Do not pitch. Listen for the words they use, because those words become your marketing and your first screens.
Founders often resist this step because it feels slow. It takes about two weeks and it changes the product more than any other activity you will do. Our post on validating an idea before writing code walks through how to run these conversations.
Step 3: Find out who already solves it
Someone does, even if badly. Search the app stores, search the web in the words your interviewees used, and ask them directly what they have tried. Competitors are not a reason to stop. They are evidence that people pay for a solution, and their reviews are a free list of what to do better. What you are looking for is the gap: the segment they ignore, the workflow they get wrong, the price point they miss.
Step 4: Decide what the smallest version must prove
Your product will eventually do many things. The first version needs to do one thing well enough that a real user gets value and you learn whether they come back. Write down that one thing, and the single number that will tell you it worked: sign-ups that complete a first booking, users who return in week two, customers who pay. This is your minimum viable product. Our guide to what an MVP should leave out goes deeper.
Step 5: Now work out cost, timeline and who builds it
With a one-page description, twenty conversations and a defined first version, you can get a realistic quote and a realistic timeline. Without them, every quote is a guess, and the cheapest guess wins for the wrong reasons. Read what an app costs in 2026 and how agencies, freelancers and in-house teams compare before you take the first call.
The two things to do last
- Designing screens. Founders love this step, and it locks in assumptions before they are tested. Sketch by all means, but keep the sketches disposable until step four is done.
- Talking to developers. A good developer will ask you the five questions from step one. A bad one will quote you before you can answer them. Arrive with the answers and you will get a better partner and a better price.
A note on secrecy
Founders often hesitate to talk about the idea for fear of it being stolen. In practice, ideas are cheap and execution is everything. The risk of building the wrong product in silence is far greater than the risk of someone copying a conversation. Use a simple non-disclosure agreement with vendors if it makes you comfortable, then talk freely.
Where 7L fits in
We are glad to be the first call, but we are more useful as the sixth. When you have done the steps above, our discovery phase turns your one page into a scoped first release with a fixed budget and timeline. If you are earlier than that, the Startupper Program exists precisely for founders who want a partner through validation as well as through the build. Either way, tell us where you are and we will tell you what to do next.
Frequently asked questions
Do I need a business plan before building an app?
Not a formal one. You need the one-page answers described above and evidence from real conversations. Investors and partners will ask for those before they ask for a forty-page plan.
Should I patent or trademark my app idea first?
Software ideas are rarely patentable and the process is slow and expensive. A trademark for your brand name is cheap and worth doing once you have chosen it. Spend the early money on validation instead.
How do I find twenty people to interview?
Start where your target users already gather: industry groups, online communities, trade associations, LinkedIn, or simply walking into businesses. Offer nothing but a short conversation. Most people enjoy talking about their problems.
What if my idea needs the full product to be useful?
That is rarely true and always worth challenging. A marketplace can start as a spreadsheet and a WhatsApp group. A booking app can start as a form. Find the manual version that proves demand before you automate it.
When should I contact a development company?
When you can describe who the product is for, what the first version must do and what you will measure. That is typically two to four weeks of work for a focused founder, and it makes the first conversation with any vendor far more productive.