On this page7 chapters
"How long will it take?" usually comes straight after "how much will it cost?", and the two are linked: time is most of what you pay for. The good news is that most of what decides the timeline is in your hands before a line of code is written.
The short answer
- A small proof of concept: about 8 weeks.
- An MVP: about 12 weeks.
- A full system, with a database, sign-in and the rest: 12 weeks or more.
These are our own timelines, and they cover the whole journey: exploring the idea, discovery, design and the build. They're set once the scope is agreed, so you know your launch date before the build begins.
Where the time goes
Exploring the idea
What it is, who it's for, and what has to be true for it to work. It's the shortest phase and the most important: every decision skipped here comes back later, when it costs more to make.
Discovery
Finding the version with the best chance of success: the core job, the flows that carry it, the data it needs, and what can wait. It ends with a plan for what gets built first.
Design
Every screen designed, from scratch or on your existing design system, so it looks and feels like a real product from the first click.
Build and hand over
The longest phase. We build features one at a time, each working end to end, with a live preview link for every change, so you can click through it and give feedback as it's built. AI tooling speeds this up, and everything it produces is reviewed and refined by hand. Then QA, deployment and a walkthrough of the codebase, so your team can take it forward.
What makes it take longer
- More types of user. Every role needs its own screens, permissions and flows.
- Integrations. Payments, calendars, CRMs and third-party APIs each need building, testing, and handling for when the other service fails.
- Complex logic. An app that calculates, schedules or matches takes longer than one that stores and displays.
- Web and mobile at once. Two platforms mean more screens to design, build and test.
- Slow feedback. Waiting on sign-off, or on several people to agree, is usually the biggest variable, and the easiest to fix.
Web or mobile: does it change the timeline?
A web app is usually the fastest route: one build, no app store review, and updates that go live instantly. A mobile app adds app store setup and review before launch. Most of what we build are web apps; when a product needs a mobile app, we build it in React Native, which ships to iOS and Android from one codebase, so going mobile doesn't mean building everything twice. Many products start on the web and add mobile once the core is proven. We compare the ways to build a mobile app in React Native vs Flutter vs native.
How to reach launch sooner
- Prototype first. A clickable prototype answers "will people understand this?" before the build budget is committed. It comes with our app design work.
- Cut to the core job. An MVP should do one thing well for one kind of user. Here's how to scope one.
- Use managed services. Sign-in, databases, file storage and email are solved problems. Building them from scratch is slow and rarely better.
- Name one decision-maker. One person who signs off keeps feedback rounds short.
- Have content ready. The copy, images and data you'll need at launch shouldn't wait for the end.
After launch
Launch is a milestone, not the finish line. Most products change quickly once real users arrive, so plan for a stretch of fixes and small features straight after it. An optional retainer covers that: ours typically run R 2,500 to R 10,000 a month.
See how we work on our MVP development page, or tell us what you're building, and you'll have a scope and price within 48 hours.
Questions we get asked
Can you build an app in a month?
Usually not. With us, even a small proof of concept takes about 8 weeks, because it covers exploring the idea, discovery and design as well as the build. The quickest projects have one core job, one type of user and one person signing off.
Does a mobile app take longer than a web app?
Usually, yes: there's app store setup and review before launch. Building in React Native keeps iOS and Android on one codebase, so it doesn't double the work.
When is the timeline set?
Once the scope is agreed. From then on you know the launch date.
How long does a proof of concept take?
About 8 weeks with us, including exploring the idea, discovery and design. Here's how it works.
What slows app projects down the most?
Scope that keeps growing, and slow feedback. Agree the core job up front, keep a "later" list, and name one person to sign off.