Can we pause the project partway through?

Yes, and the cleanest place to pause is between phases: after Discover, after Design or before Launch. Each phase is invoiced in advance, so pausing at a boundary means you haven’t paid for work that hasn’t started. Pausing in the middle of a phase is possible, but how it’s handled depends on where you are.

This article is about timing: stopping for a while and coming back. If you want to stop for good, see what if I want to cancel midway. For the money-back guarantee, see is there a refund policy.

Why the end of a phase is the natural place

Each of the four steps ends with something whole. You can put it down, and pick it up again later without losing much:

Pausing halfway through a step is messier. A half-finished design or a half-built feature goes stale while it waits, like a half-painted room. The people holding it in their heads move on, and that context takes time to rebuild.

So if you can see a pause coming, tell us early. We’ll aim to finish the current phase cleanly rather than stop mid-stride.

What you keep while you’re paused

Everything produced so far is yours. The code and IP belong to you, and so do the designs and the plan.

During the build, accounts sit with us or with you, whichever you chose at the start. They become yours at launch either way. If you’re pausing before launch and want them in your name, raise it when you pause.

Coming back

If your direction is the same when you return, we pick up from the last finished phase. Expect a short restart while the team gets back up to speed. We can’t promise the same people will be free the day you return, so give us notice of your restart date.

If the direction has changed, we revisit the plan before carrying on. That might mean rerunning part of Discovery and re-scoping the rest. Building the old plan for a new direction wastes your money. The price stays tied to a fixed scope, so a new direction means a fresh look at what fits your tier.

Pause, or stop?

Sometimes a pause is really a decision not to continue. Better to say so out loud, to yourself and to us, than to let a project drift.

The clearest exit is the end of Discovery, when you can walk away with your money back if the plan doesn’t convince you. Beyond that point, the cancellation article covers what happens.

If the pause is because new ideas have arrived, you may not need to stop at all. What if I want to add more features midway explains the options.

If you already know you’ll need a break

Some pauses are predictable: a funding round, a busy season or a long holiday. In those cases, start later rather than start now and stop.

Tell us before you sign, and we’ll plan the timeline around it. A project that runs straight through keeps its momentum. It also keeps the same team, and it reaches launch sooner.

If it’s your availability that’s the worry, rather than a full stop, read what happens if I’m slow with feedback. A lighter-touch few weeks may be enough without pausing.

For how every account and asset should move to you cleanly, paused or not, the non-technical founder’s build playbook has a full checklist.