How do you make sure we launch on time?

Written by

Contic

Read time

2 minutes

A large clock hanging under the roof of a railway station.

By fixing the scope in Discovery, fixing the price and running the build on change control. We don’t publish a success-rate percentage, and you should be wary of anyone who quotes you a perfect one. LaunchPad runs 2, 3 or 4 months depending on tier.

Why there’s no single “3 months”

Each tier has its own window. Starter (£25k) launches in 2 months, Growth (£60k) in 3 and Scale (£100k) in 4. Prices exclude VAT.

The window covers the whole job: Discover, Design, Build and Launch. It isn’t three months of coding after a long planning phase. Our answer on what happens during a LaunchPad build walks through each step.

What protects the date

Software projects slip for familiar reasons. The scope was vague, it kept growing, or nobody owned the timeline. LaunchPad is built to close each of those gaps.

What slips a projectWhat we do about it
A vague scopeDiscovery sets the exact scope within your tier, in writing, before the build
Building the wrong thingEvery tier includes an interactive prototype to test before build
Scope that keeps growingOne-in, one-out during the build, so additions need a swap
A supplier with no reason to finishA fixed price, so extra time on agreed work is our cost, not yours
Paying for work you can’t seeStaged payments, with each phase invoiced in advance

That fourth row matters most. On a time and materials contract, a late project earns the supplier more. On a fixed price, it costs us. Nothing focuses a team like paying for its own overrun.

Where AI fits

We use AI throughout the build, and it makes us faster. Speed from tools only helps a date if someone experienced checks the output. Senior engineers review all of it, and they own what ships.

What you can do to keep it on track

Some of the risk sits on your side, and it’s fair to say so plainly.

  • Answer questions quickly. Slow decisions are the most common reason any project runs late.
  • Make big changes before the build. Discovery and Design are the cheap places to change your mind.
  • Park new ideas. Mid-build ideas go on the post-launch roadmap, or are swapped one-in, one-out.
  • Start account paperwork early. Company developer accounts can need a business ID, which takes days.

Our answer on what happens if you’re slow with feedback covers the other side of this.

What’s outside anyone’s control

App store review is the main one. Apple and Google both review apps before launch, and a rejection can add days. Third-party services can also change or fail without warning. We plan for both, but we won’t pretend they don’t exist.

If the plan itself is wrong

The worst way to miss a date is to build confidently towards the wrong thing. That’s why there’s a checkpoint after Discovery, before the build starts. If the plan doesn’t convince you there, you get back what you’ve paid.

How to check us

Don’t take a supplier’s word on delivery, including ours. Ask to see live products and what they took to launch. Our answer on seeing past work shows where to start.

If you need a date sooner than your tier allows, see whether you can launch sooner. For why a fixed price changes who carries the risk of lateness, read fixed price vs time and materials.

Thinking about building something?

We design, build and launch digital products at a fixed price, with a money-back guarantee after Discovery. Tell us what you have in mind.