Skip to content

Fixed-scope offer

API integration in 2 to 4 weeks

Price
From £3,500Most single integrations land between £3,500 and £6,000; middleware joining several systems from £12,000.
Time
2 to 4 weeks
Payment
50% deposit to book, balance on launch; monthly plans billed in advance.

Two systems you already use connected properly: the records that should move, moving on their own, with retries, idempotency and an alert when something stops. A fixed price for an agreed scope, in two to four weeks.

We reply within one working day.

What happens after you get in touch

We reply within one working day.

  1. Step 1

    We reply within one working day

    We read what you sent and come back with questions, a rough view of cost, or a time to talk.

  2. Step 2

    A 20-minute call

    We talk through what you need and tell you honestly whether we're the right team. No charge and no obligation.

  3. Step 3

    A written, fixed-price proposal

    Scope, price and timeline in writing. Nothing starts until you've signed it off.

Who it's for

Businesses whose team copies data between systems by hand, or whose Zapier flow or old script keeps breaking, and who want one named integration done properly rather than a day rate and a shrug.

What you get: A working integration in your own repository and cloud account, a mapping document, a runbook, and monitoring that tells you when it stops.

What's included

  • A discovery call and a one-page scope: which systems, which records, which direction, how often, and a fixed price and start date.
  • Access checks on every API before we quote: keys, OAuth apps, sandbox accounts and any approval queues, so the surprises come first rather than last.
  • A written field mapping covering duplicates, partial records, refunds, cancellations and time zones, signed off before the build.
  • The integration itself, with an idempotency key on every incoming event, retries with backoff on every outgoing call, respect for the provider's rate limits, and logs detailed enough to replay a failure.
  • A staging environment pointed at the providers' sandboxes, so you test with realistic data before anything touches a live account.
  • Monitoring and an alert when a queue backs up, a token expires or a provider is down.
  • Handover: the code in your repository, accounts in your name, the mapping document, a runbook for the failures we expect, and a walkthrough with whoever will look after it.

Not included

  • Subscriptions to the systems themselves, and any provider's API or transaction fees. Those are paid by you to the provider so the accounts are yours.
  • A new web or mobile app on either end. If one of the systems is a product that doesn't exist yet, that is a separate project and we quote it as one.
  • Data cleaning in the source systems. We map and move what is there; if the records need tidying first, we scope that separately.
  • Changes a provider makes to its API after handover. On the Ongoing development plan we track and make those updates; otherwise the runbook tells you where to look.

What each budget buys

From £3,500; most single integrations land between £3,500 and £6,000; middleware joining several systems from £12,000. Three honest examples of scope, so you can place your own idea before we talk. 50% deposit to book, balance on launch; monthly plans billed in advance.

  1. About £3,500

    One direction, one record type

    Events from one system create or update records in another: Stripe payments raised as Xero invoices, website bookings pushed to HubSpot as deals, Shopify orders sent to a courier for labels. Webhook or scheduled, with retries, idempotency, logging and an alert.

  2. About £6,000

    Two-way sync with history

    Records that live in both systems and change in both, kept in step with clear rules for conflicts, plus a one-off backfill of existing records. Typical for CRM to app customer sync, or stock between a shop and a warehouse.

  3. About £12,000

    A middleware layer for several systems

    Three or more systems sharing one set of records and rules through a small service you own: orders, payments, accounting and shipping all reading from the same source of truth, with a dashboard of what moved and what failed. Six to ten weeks.

How it runs

  1. Week 1Discovery and mapping: the scope, access to every API, and the field mapping document, signed off by you. The mapping sets the price and whether the build takes two weeks or four.
  2. Weeks 2 to 3Build against the providers' sandboxes, with a working staging integration you can watch and a short review call each week.
  3. Final weekBackfill if needed, switch to live accounts, monitoring on, then handover: code, accounts, runbook and walkthrough.

Why trust us with it

We run our own business on integrations we built this way: an anonymous usage-data service on Google Cloud Run and BigQuery that our apps report to, App Store Connect API automation that publishes our listings in nine languages and feeds our sales dashboard, Stripe webhooks that record payments on this site, and a client portal on Firestore. We have no client integration case study yet, and we won't invent one.

After launch

Keep it working after launch

Websites and apps need looking after once they're live. Ongoing development is the plan most people choose after this, at from £1,500 a month.

Already have an app or site that needs looking after?

Questions we get asked

One integration between two named systems, in one direction, for one kind of record: for example Stripe payments raised as Xero invoices, or website bookings pushed into HubSpot. That includes discovery, the mapping document, the build with retries and monitoring, a staging environment and handover. Two-way sync, backfilling history or more record types move it towards £6,000, and we tell you which in the scope before you commit.

Other ways to start

Start with a 20-minute call with our team.

Tell us where you are and what you need. We'll tell you honestly whether this offer fits, or what would. We reply within one working day.