What if I want to cancel midway through the project?

You can stop. Past Discovery, the phase you’ve paid for isn’t refunded, but you keep the code, the IP and everything built so far, and the accounts move to you. This page covers leaving for good; the refund policy covers the Discovery guarantee, and pausing covers a break.

Priorities change. Funding moves, a market shifts or a cofounder decides they’d rather open a bakery. Stopping a project shouldn’t mean losing what you’ve already paid for, so here’s what happens.

What it costs you to stop

Each LaunchPad phase is invoiced before it starts: Discover, Design, Build, Launch. Your tier price, set out in how much a LaunchPad build costs, is split across them. So you’ve only ever paid for the phase you’re in, never the whole build.

If you stop partway through a phase, the payment for that phase isn’t refunded. The team is booked and the work is under way.

What you keep

You own the code and IP, and that doesn’t depend on finishing. You keep everything we’ve produced up to that point. Depending on the phase, that might be:

• the Discovery plan and agreed scope
• wireframes, interface designs and the clickable prototype
• the source code, in a GitHub repository
• the hosting and infrastructure it runs on
• any app store listings already set up

How the accounts move to you

During the build, accounts, hosting and code sit with us or with you, whichever you prefer. If they’re already in your name, there’s nothing to move.

If they’re with us, they can be transferred:

• Hosting. An AWS setup is a whole AWS account, run under our AWS Control Tower. Control Tower is how we manage many AWS accounts safely, and an account can move out to you complete.
• Code. GitHub repositories can be transferred to your own GitHub account.
• Apps. App Store and Google Play apps can be transferred between developer accounts.

That matters, because ownership on paper isn’t much use without the keys. Our guide to who owns your code explains what to check at any handover.

Can another team carry on?

Yes. That’s the point of owning the code. A new team will review it before they quote, because quality varies across the industry. We’ll walk the new team through it, so they aren’t starting from guesswork.

Our answer on taking over an app another agency built covers what a good handover looks like.

Before you cancel

Stopping is sometimes right. But if the reason is scope, cost or a feature you now want, talk to us first. There’s often a cheaper fix:

• A feature you now need. Our one-in, one-out rule swaps it for something less important, so the price holds.
• Money is tight. Pausing between phases spreads the cost without losing the work.
• The plan feels wrong. Say so early. It’s cheaper to change direction in Design than in Build.

Our answer on adding features mid-way explains how changes work.