You own everything, and you can leave

The code, the accounts, the hosting and the documentation for your system stay in your organisation's name while we look after it. Support runs month to month, and if you decide to move on we hand the system over in a state another team can run. Being easy to leave is how we earn the right to stay.

What stays yours

Everything another team would need to run the system without us.

  • The source code and its history

    You have access to the repository at all times, with every change, who made it and why, and it is moved into your organisation's own account whenever you ask. For a system we take over, the code was yours already; for new work, ownership passes to you when the work is paid for.

  • Accounts, hosting and domains in your name

    Servers, cloud subscriptions, domains, certificates and third-party services are registered to your organisation, not to us or to one of our engineers. We use named accounts that you can see and remove.

  • A record of who has access

    A written list of every system, account and person with access, kept current. When someone joins or leaves, it is updated, so access never outlives the need for it.

  • Documentation another team could use

    How to build the system, how a change is released, what it connects to, how it is monitored and where the risks are. It is kept current as part of the work, not written at the end.

  • Monitoring and history

    Where practical, monitoring and logging accounts are in your name too, so the history of errors and performance stays with the system.

  • No minimum term

    Support plans run month to month. You can leave with 30 days' notice, and the notice period is for an orderly handover, not a penalty.

If you decide to leave

The exit is planned from the start, so it is routine when it comes.

The transition plan we work to
  1. You give notice

    30 days, in writing. Nothing else is needed and no reason is required.

  2. We agree a handover plan

    Who is taking over, what they need and in what order, using the same checklist we use when we take a system on ourselves.

  3. We hand over everything

    The repository, the release process, the documentation, the access record and the list of open faults and planned work. Our own access is removed, or transferred to the incoming team, as you direct.

  4. We answer the incoming team's questions

    During the notice period, so they can build and release the system themselves before we step away.

Low risk to try

  • First month refunded

    If you are not satisfied in the first 30 days of a support plan, tell us and we refund that month's fee.

  • 30 days' notice

    Support plans run month to month. Change plan or leave with 30 days' notice, with no minimum term.

  • Priced before we start

    Every piece of work is quoted in writing before any chargeable work starts. Nothing is added to the bill without your agreement.

  • You own everything

    The code, the accounts, the hosting and the documentation are in your name, and kept so another team could take over.

    What that means in practice

Questions

What if we never had the source code in the first place?

Then getting it, and proving it builds into the system you run, is the first job of any takeover. Our answer on who owns the source code of bespoke software explains where you stand.

Will you use our code for other clients?

No. Your code and data are used only to support your system, and are covered by a confidentiality agreement if you want one.

Can we bring the work back in-house later?

Yes. The documentation and the handover plan are written so that an in-house developer or another supplier can take the system on.

Tell us about your system

Say what it does, what it is built on and what is worrying you. We will reply with what we would look at first and whether we are the right people to help.

Tell us about your system 0800 433 7990 Monday to Friday, 9am to 5pm. A first 20-minute call is free, and we reply to every enquiry within one working day. What happens after you get in touch