Most people who write to me open with an apology. They say they are not technical, they only have an idea, and they assume that is not enough to talk to a developer. It is enough. It is where nearly every app that exists started, and the work of turning it into something buildable is a conversation, not a document.
What follows is the order I would actually take you through, and you can do the first four steps without paying anyone.
1. Write the one sentence
Not a pitch. One plain sentence with three parts: who it is for, what they can do, and when they would open it. "A booking app for my three hair salons so clients can rebook themselves instead of calling during the day."
If you cannot write that sentence, the idea is not ready for a developer yet, and no amount of money fixes that. If you can, you have just saved yourself weeks. Every decision later gets tested against it.
2. Decide what counts as version one
This is where most budgets are lost. The idea in your head contains everything the app will ever do. Version one should contain the smallest thing that is still useful to a real person.
A test that works: imagine one specific person using the app once, successfully, and list only what had to exist for that to happen. Notifications, profiles, settings screens, admin dashboards and social features almost never make that list, and each one of them is real money.
From experience: in nearly every first call, the app gets smaller. Not because I am trying to do less work, but because the version the client described would take four months and the version they actually need takes four weeks, and the four-week one teaches them what to build next.
3. Work out whether money changes hands inside the app
This single question moves the price and the timeline more than anything else, including the number of screens.
- Nothing is sold in the app. Simplest and cheapest. The app is a tool, and you charge for something else, or not at all.
- You sell something digital, like a subscription or unlocking features. Apple and Google require you to use their payment systems and take a cut, and the plumbing around restoring purchases and handling refunds is genuinely fiddly.
- You sell something physical or a real-world service, like a haircut, a delivery or a class. Then you can use ordinary card payments, keep the store cut, and the rules are easier.
People routinely get this wrong in both directions, and it changes the business, not just the code.
4. Check whether your category has extra rules
Both stores have categories that carry additional requirements or outright rejections. Lending and financial services, health and medical claims, anything aimed at children, and anything that handles identity documents. If your idea sits in one of those, find out before you build, not after.
You can read Apple's App Review Guidelines yourself, and it is worth an hour. The section on business models is the one that surprises people.
5. Only now decide who builds it
With the sentence written, version one defined, and the money question answered, you can have a useful conversation with anybody: an agency, a freelancer, a no-code consultant, or an AI tool. Without those, every quote you get will be a guess, and quotes that are guesses come back as change requests later.
Roughly, the options look like this.
| Route | Typical cost | Best when |
|---|---|---|
| You build it yourself with no-code or AI tools | $0–500 | Simple, no payments, you enjoy the process and have the time |
| One experienced developer | $4,500–15,000 | A real first version that has to survive actual users |
| An agency | $30,000+ | Several platforms, a big team, ongoing contract |
I have written separately about what an app actually costs and about how far you can get without coding, both with real numbers.
What you do not need yet
A company. A designer. A patent or a non-disclosure agreement, and I say that as someone who signs them happily when asked. Ideas are not protectable in any practical sense, and the protection you actually want comes from building the thing and having customers, not from paperwork.
You also do not need to know which technology it should be built with. If a developer asks you that question, that is their job, not yours.
Want the version that applies to your idea?
A free thirty-minute call, and you leave with a written plan: what to build first, what it costs, how long it takes. Yours to keep whether you hire me or not.
Book a free 30-minute call