In short
Building an app takes nine steps: goal, users, feature list, data model, first version, weekly iterations, testing, launch and ongoing development. With AI-assisted development, a focused first version is ready in weeks. Most projects do not slip during coding, they slip at the start, when nobody has decided what the first version must do.
1. The goal: what problem does the app solve?
Do not start with features, start with one sentence: “With this app, [who] can do [what] [how much faster or better].” For example: “Our customers request a quote for a used machine in 2 minutes, with photos, without a phone call.”
That sentence is also your yardstick: it is what you measure after launch.
2. Users and roles
Who logs in, and who can see what? A typical business app has three roles: admin (sees everything), staff (sees their own tasks) and client (sees only their own data). Write the permissions down now, because changing them later is the most expensive kind of rework.
3. The feature list, and what stays out
Write down everything you can think of, then split it into three groups:
- Essential: without it, the app does not reach the goal.
- Nice to have: can come in the second round.
- Later: only if users ask for it.
Only the first group goes into the first version. That is the MVP, and we wrote a separate article about it.
4. The data model
What data does the app store, and how does it connect? For example: a client has several orders, and an order has several items and a status. This step is invisible, but it decides whether the app can grow later.
One of the biggest lessons from our own product, DogDietLab, was exactly this: splitting one large “dog” table into dog, daily log, diet recommendation, owner and expert review is what made the app maintainable.
5. The first working version
We do not start with drawings and weeks of design, but with a working first version you can click through, on a real database. You see early whether it is going in the right direction, instead of judging from a picture.
With AI-assisted development this is fast: DogDietLab's first working version took about two weeks.
6. Weekly iterations on a live preview
From here, work moves in small, tested steps. Every week there is something to try on a live preview, and your feedback decides the next step. When a new idea comes up, we price it and schedule it, instead of slipping it in.
7. Testing
Before launch we check:
- Permissions: every role sees only what it should.
- Forms and emails: every form saves, every notification arrives.
- On phones: the main flows work on mobile.
- Bad input: what happens when someone enters the wrong format or skips a field.
- Logic by hand: we check every calculation manually. AI can write code that looks right and still counts the wrong field.
8. Launch
Domain, analytics (so you see how many people use it and how), backups, privacy texts, and if there are public pages, a structure Google can read. Agrider, for example, went live in 5 languages with 2,463 URLs in its sitemap.
9. After launch
The first weeks teach you the most: what people use, where they get stuck, what they ask for. Plan an agreed support period and a budget for further development.
How long does each step take?
| Step | Typical time for an MVP |
|---|---|
| Goal, users, feature list | 1–3 days, with one or two calls |
| Data model | 1–2 days |
| First working version | 1–3 weeks |
| Iterations and testing | 1–3 weeks |
| Launch | a few days |
These are guidelines. A larger system takes longer, but there too a working part is ready to try in the first weeks.
Where do projects go wrong?
- Nobody decided what stays out. Every new idea goes into the current round, and the first version never ships.
- There is no single decision-maker. If three people say different things, development stalls.
- The data model changes late. This is the most expensive change, so we spend time on it up front.
- No testing with real users before launch.
Started on your own and got stuck?
Many people now start with an AI app builder, and that is a good starting point. The trouble usually begins when real users, permissions and live data arrive. In that case we start with a short review (data model, logic, security) and give you a fixed price to fix and finish it.
Frequently asked questions
Do I need a specification to start?
No. From a 30-minute call, the goal and a rough feature list, we put together the itemised quote and the scope of the first version.
How much of my time does the project need?
About an hour a week to try the live preview and give feedback, plus quick answers when a question comes up.
Further reading
- How much does app development cost in 2026?
- MVP development: a working first version in weeks
- Mobile app or web app: which one does your business need?
- Custom software or off-the-shelf?
If you have an idea, see our custom app development services.