Case study: how [client] launched in 14 weeks (with real numbers)

People ask us how long an app really takes, and the honest answer is that it depends on what you are willing to leave out. This is the story of one build that went from a signed brief to a live launch in fourteen weeks, which is fast for us, and I want to walk through how it actually happened rather than the tidy version you would put on a sales page. The client has agreed to let us share the details, and where there are numbers, they are the real ones, not rounded up to look impressive.

[VERIFY: confirm written client permission to publish this case study, and confirm the client is happy to be named or wants to stay anonymous. Do not publish until this is in writing.]

Who this was and what they needed

[VERIFY: client name or agreed anonymised descriptor, sector, and the one-line problem the app solved. Replace this paragraph with the real context once confirmed.] The short version is that a founder came to us with a clear problem, a defined first user group, and a deadline that mattered for a reason outside their control. That last part is what made fourteen weeks possible. A real deadline forces real decisions.

What they did not have was a long list of features. They had one job the app needed to do well, and the discipline to leave everything else for later. If you have read our piece on how to write a brief for your app developer, this was close to the ideal version: a problem described clearly, the people who have it named specifically, and a willingness to cut.

The timeline, week by week

Here is roughly how the fourteen weeks broke down. The exact split shifts with every project, but the shape is typical of a fast, focused build.

[VERIFY: confirm the real week-by-week breakdown against the project tracker. The phases below are the standard shape; adjust the week counts to match what actually happened.]

The thing that kept it moving was not speed for its own sake. It was that we agreed, in week one, what we were not going to build. Every request that arrived later got measured against the deadline, and most of them were parked rather than refused. We kept a written list of everything we said no to, which made those conversations calm instead of tense. That habit comes straight out of our checklist for scoping an app project.

What we cut, and why it worked

The features that did not make v1 are as much a part of this story as the ones that did. [VERIFY: list the 3 to 5 specific features that were deferred to a later version, and confirm the founder agrees with how they are described.] None of them were bad ideas. They were simply not the one job the app had to do to be useful on day one.

Cutting is uncomfortable because every deferred feature feels like a promise broken to yourself. But a smaller app that ships is worth more than a complete one that slips. The launched version did the core job well, real people started using it, and the deferred features got built later with the benefit of actual usage data telling us which ones still mattered. [VERIFY: confirm which deferred features were later built, and whether usage data changed the priority order.]

The real numbers

This is the part people actually want, so here it is without varnish.

[VERIFY: every figure in this section must be checked against the real project record and the client’s agreement before publishing. Do not invent or estimate. If a number cannot be confirmed, cut the line rather than guess.]

• Total cost: [VERIFY: real project cost in GBP]
• Time from signed brief to live: 14 weeks
• Team size: [VERIFY: real number of people and roles]
• Users in the first [VERIFY: period]: [VERIFY: real number]
• What the founder spent their own time on: [VERIFY: real description]

I am deliberately not dressing these up. Some of them are better than average and some are ordinary. The point of sharing real numbers is that a founder reading this can hold them next to their own situation and decide whether a fast, focused build is the right shape for them, or whether they are better off with more time and a wider scope.

What we would do differently

No launch is clean, and this one had its rough edges. [VERIFY: confirm with the team the one or two genuine things that went wrong or would be done differently, described honestly but without throwing anyone under the bus.] The honest reflection matters more than the highlight reel, because the rough edges are where the actual lessons live.

If there is one thing to take from this, it is that fourteen weeks was not the result of working faster. It was the result of deciding sooner. The clarity came first, the speed followed. That is the order it always goes in.

If you have a real deadline and the discipline to build one thing well before building everything, that is exactly the kind of project we move quickly on. Tell us what you are trying to launch and we will tell you, honestly, whether your timeline is realistic.