Handing over an app? We'll look after your client.

Plenty of good developers reach a point where an app they built no longer fits. Maybe you've moved on to other work, or you'd rather not be on call the next time Apple rejects an update. We take apps over from freelancers, small studios, agencies and no-code builders, and we do it in a way that leaves you looking good to the client you're passing on.

Talk to us about a partnership

If you're handing over an app you built

You introduce us to your client on an email that copies all three of us. We have a short call together, then we look at the code and send our notes to you before anyone else sees them. Your client gets a plan for the first month, a shared Slack or Teams channel, and a clear answer to "who do we call if something breaks?"

You can stay as involved as you like. Some developers want one handover session and a clean break. Others keep the website or the backend and hand us only the app. Either works, and the work that's yours stays yours. We pay you for the handover hours at your normal rate, through the client's first statement of work, and most handovers then move onto App Care, our maintenance retainer, from £675 a month.

If you're an agency without a mobile team

We build and maintain iOS and Android apps for agencies whose clients need one, usually alongside the agency's own CRM, design or web work. There are three ways to work with us:

  • Introduce. Your client contracts with us for the app and keeps you for everything else. We pay you 20% of what they pay us in their first year.
  • White-label. We work under your brand at our normal price, you set your own price to the client, and we never need to meet them.
  • Co-deliver. You run your part, we run ours, and each of us invoices the client.

Most agencies choose to introduce, because a fixed client budget leaves little room for a markup and nobody wants to pay a supplier before the client has paid them. Whichever you pick, we agree a named technical contact on your side, and we won't offer your client anything you already sell them. If a tender needs an app team, we're happy to be named as your technical delivery partner.

If you build with Lovable, Bubble, Base44 or FlutterFlow

Some no-code projects outgrow the platform, usually when the client needs the App Store and Google Play, push notifications, in-app payments or data that works offline. When that happens, send them to us. We treat the prototype as the specification, because it already shows what the app needs to do, and we rebuild the parts that need it with tests behind them. Founders who come to us too early for a production build get sent back to you.

How a handover works

  1. Introduction: one email that copies you, your client and us.
  2. First call: the three of us, 30 minutes, to agree what the client needs first.
  3. Access: the code repository, App Store Connect and Google Play Console, signing keys, hosting and any error logging. We send a checklist so nothing turns up missing three months later.
  4. Private review: our notes on the code go to you first.
  5. Plan and price: the client gets a fixed price for any stabilisation work and an App Care proposal.
  6. Handover session: you walk us through the parts only you know, including how to switch things off in an emergency.

What's in it for you

  • 20% of what the client pays us in their first 12 months, paid each time they pay us.
  • Paid handover hours at your rate, if you're passing on an app you built.
  • We won't sell your client anything you already provide, and we'll send work like that back to you.
  • No exclusivity. Refer as often or as rarely as you like.

It's all in a one-page partner letter, which we'll send you before any introduction.

Questions partners ask

Will you criticise my code to my client?

No. Every codebase has things its author would do differently with more time, and the client doesn't need a report card. We send our review to you, and the client gets a plan.

Will you try to take my other work with that client?

No. If you do their website, CRM, design or backend, it stays with you. That's written into the partner letter, and it works both ways.

How does the referral fee work?

We pay you 20% of what the client pays us in the 12 months from their first invoice, excluding VAT and third-party costs we pass on at cost. You're paid within 14 days of each payment we receive. White-label work doesn't carry a fee, because you set your own margin.

What if the code is in a poor state?

We'll tell you privately and price the work to fix it before the client commits to anything.

What do you need from me?

Access to the repository and the App Store Connect and Google Play Console accounts (or a transfer of the app into the client's own accounts), signing keys and passwords, hosting and backend access, and an hour or two of your time for the handover session.

Which technologies do you take on?

Flutter, React Native, native iOS (Swift) and native Android (Kotlin) apps, and the backends behind them. For no-code apps, we work from the Lovable, Bubble, Base44 or FlutterFlow project and its export.