Skip to content
Spark
Writing

How we work

Owning your system: if you part ways with your builder, you keep everything

If you stop working with the people who built your system, you should keep the code, the data and the documentation, and be able to hand them to someone else. That belongs in the contract from day one. Here’s what to ask for.

By Seb Lawson · 3 November 2026 · 5 min read

If you stop working with the people who built your system, you should walk away with everything: the code, your data, and documentation good enough for another team to pick it up. That shouldn’t depend on goodwill at the end. It should be written into the agreement before any building starts. That’s how we work, and we think you should ask for it from anyone who builds for you.

Leaving matters more with bespoke than with bought software

With off-the-shelf software, leaving is painful but well understood. You export what the vendor lets you export and move to another product. With a bespoke system there’s no other product to move to. If you can’t get the code, the system is gone. If you have the code but nobody else can understand it, you’re tied to one builder whether you like it or not.

Nobody plans to leave. But businesses get sold, people retire, priorities change and working relationships sometimes go wrong. Planning for that costs almost nothing at the start and is very hard to fix later.

You should own the code and the accounts it runs on

The code written for your business should be yours, and you should be able to get to a copy without asking anyone. In practice that means three things.

  • The agreement says you own it. Everything written specifically for you belongs to you. Where a builder reuses its own standard building blocks, you should get a permanent right to keep using them in your system, so nothing can be switched off later. The tools underneath, such as Xero or Microsoft 365, stay under their own licences, which is normal.
  • The code sits somewhere you can reach. That might be a code repository in your business’s name on a service like GitHub, or one you can take over in a few clicks.
  • The accounts are in your name. Hosting, domain names and subscriptions for connected services should belong to your business, with the builder given access, and not the other way round.

That last point catches people out. If the hosting account is in the builder’s name and the relationship ends badly, owning the code doesn’t help much on Monday morning.

You should be able to export all your data, at any time

Your data is the part you can’t replace. Every client, job, quote, invoice and record your team has created belongs to you, and you should be able to take a full copy whenever you like, including while you’re still working together.

Ask for three things:

  • A full export in standard formats, such as spreadsheet files or a copy of the database, that another system can read.
  • The history as well as the current state, including audit trails and attachments, so you keep the record of who did what and when.
  • A test export early on. Run one in the first few months and check it opens properly. Any problem is much easier to fix then.

Because a good system joins up tools you already own, much of your data already lives in places that are yours: your Xero file, your SharePoint or Google Drive, your HubSpot account. That’s one reason we build around your existing tools instead of replacing them.

The documentation should let another team take over

Code without documentation is only half handed over. A capable new team can read code, but working out why it was built the way it was takes them far longer.

Good documentation covers what the system does and for whom, how the parts connect, where it runs and how a change gets made, which outside services it relies on and the accounts behind them, and the decisions that weren’t obvious at the time. It should be written in plain English as the system is built, and updated each time it changes.

The test we use is simple: could another competent team pick this up and run it without ringing us? If not, the documentation isn’t finished.

Agree the hand-over before you need it

Even with everything owned and documented, a clean exit takes a little time. The agreement should say what happens if either side ends the arrangement:

  • how much notice is needed
  • what the builder does during that notice, such as walking the new team through the system and answering their questions
  • how admin access to every account passes to you, and when the builder’s own logins are removed
  • what the hand-over costs, if anything, agreed now so there’s nothing to negotiate later

It’s easy to agree at the start and hard at the end

The reason to settle all this up front is simple. At the start, everyone wants the project to work and nobody minds writing down what happens if it doesn’t. At the end, if things have gone wrong, every point becomes a negotiation.

So before you sign with any builder, ask:

  1. Will we own the code, and where will it be kept?
  2. Whose name will the hosting and service accounts be in?
  3. Can we export all our data, at any time, in a standard format?
  4. What documentation will we get, and when?
  5. What happens, step by step, if we stop working together?

If the answers are vague, or come with a fee for things that should be yours anyway, take that seriously.

We’d rather you stayed because you want to

It might seem odd for a builder to explain how to leave them. We see it the other way round. If you can leave easily and still choose to stay, it’s because the system works and we keep making it better. That’s the relationship we want with every client, and knowing you could leave keeps us working for it.

If you’d like to see how we handle ownership and hand-over, or talk through a system someone else built for you, book a review. It’s a free 30-minute call with Mark or me. You can also read the security questions to ask any builder, which cover the access side of leaving.

Let’s map how your business works

A free 30-minute call with Seb or Mark. Bring the spreadsheet you hate most and we’ll tell you honestly whether a system would fix it.