Book a consultation
The studio What we build Case notes Contact Book a consultation
Abstract illustration of cloud infrastructure — layered glass forms rising out of coloured cloud
Product & platform studio · Saffron Walden · working UK-wide

Software that gets finished.

Most internal software stalls at eighty per cent. The demo works, the budget runs out, and the thing never quite lands on anyone's desk. Ramden Labs builds web platforms, internal tools and the cloud underneath them, and hands them over working.

Two-week discovery first. Fixed price after that, or you walk away with the plan.

The studio

Nobody opened the dashboard.

It had taken two agencies, eleven months and somewhere near forty thousand pounds. By the time it went live, the operations manager who commissioned it had moved on, and the depot team had gone back to the spreadsheet they trusted.

Adam Kelsey, principal engineer and technical lead at Ramden Labs
  • TeamThree engineers, one designer
  • StackTypeScript, Postgres, boring infrastructure
  • ReviewEvery change read by a second engineer
  • AccessibilityWCAG 2.2 AA on customer-facing work

That project in Harlow is the reason this company exists. We were brought in to rescue the reporting side of it and had a working replacement in five weeks. Not because we are quicker typists. Because we spent the first fortnight sitting with the four people who would use it, instead of with the person paying for it.

Ramden Labs works in two-week blocks. Every block ends with something you can open in a browser, not a status report. Discovery comes first and always produces the same three things: a map of the workflow as it actually runs, a scoped build plan, and a fixed price. Take that plan to another studio if you like — plenty of clients have asked, and the document is yours either way.

We won't quote a build we haven't scoped, and we won't put a developer on your payroll and call it a partnership. If you need bodies rather than a finished thing, we're the wrong studio.

The other thing we do differently: we start with the ugliest screen. Most studios open with a design system and a brand workshop. We open with whatever your operations team stares at for six hours a day, because that is where the money leaks. The pretty parts are easier once the plumbing is honest.

Four builds shipped in the last eleven months, all in the East of England and London, all still running. There is no account manager to go through — you email the person who wrote the code.

Abstract illustration — a cluster of glass towers wrapped in coloured cloud
How the work runs

Two weeks of questions before a line of code.

Discovery is where a build gets cheap or expensive, and it happens before anyone opens an editor. We interview the people who will use the thing, watch them work, and write down the steps they've stopped noticing. Then we price it. Nothing after that is an estimate.

The work

Five things we take on, and the money each one starts at.

Every engagement begins with discovery. The figures below are the honest starting point for a project of average shape; the number in your proposal is fixed, and it comes out of the sprint rather than out of the air.

2 weeksFixed feeDeliverable, not a meeting

We sit with the people doing the job, map the workflow as it really runs, and hand back a scoped build plan with a fixed price and a delivery date. Credited in full against the build if you go ahead. Yours to take elsewhere if you don't.

8–14 weeksFixed priceHandover included

Customer-facing systems: accounts, quoting, bookings, document flows, billing hooked into whatever you already run on. Built as a web application your customers log into, tested on real devices, handed over with the source and the deployment pipeline.

4–9 weeksReplaces spreadsheets

The scheduling sheet three people edit at once. The inbox someone triages by hand every morning. The report that takes a Friday afternoon. We replace those with something boring and reliable, and we keep the exports your accountant already expects.

3–8 weeksUK/EU hostingNo downtime on the switch

Moving a system off the machine under someone's desk, or off a host nobody has logged into since 2019. Migration, backups that get restored and tested rather than merely configured, monitoring that pages a human, and a written runbook so it isn't only in our heads.

Rolling monthlyCancel with 30 days3-hour first reply

Patching, dependency updates, uptime monitoring and a budget of development hours for the small changes that keep arriving. You email the developer directly. We publish what we did each month, including the months where the answer is very little.

Prices exclude VAT and are a guide until discovery is done. After that the figure is fixed in writing: no hourly billing, no change-request fees for things we should have spotted in the sprint.

Case notes

Four recent builds, and what changed for the people using them.

Logistics · Harlow

A reporting dashboard two agencies had already abandoned

We kept the database and threw away the interface. Depot supervisors now open it at the start of a shift instead of exporting to a spreadsheet, and the daily figures reconcile with the finance system without anyone retyping them.

5 weeksfrom first meeting to daily use by 34 depot staff
Abstract brand illustration — a flowing translucent ribbon in blue and pink
Abstract brand illustration — a glass structure holding coloured cloud and trees
Legal services · Cambridge

Six spreadsheets became one intake tool

Client onboarding ran across six files and an email folder. It now runs as a single form with the conflict checks built in, and the paralegals get their afternoons back.

40 → 6 minaverage time to open a new matter
Manufacturing · Braintree

A twelve-year-old order system, moved off a server under a desk

Same software, new home, proper backups, and a runbook that someone other than us can follow. The changeover ran over a weekend and the Monday shift noticed nothing.

0 minutesof downtime across the migration weekend
Abstract brand illustration — a connected grid of coloured tiles and nodes
Health SaaS · London

A founder's prototype, turned into a product

Rebuilt for multi-tenancy, audit logging and NHS-grade access control, without pausing the people already using it. The founder kept shipping features throughout; we worked underneath.

417 clinicianslogging in each week at handover

Bring us the process that annoys you most.

A first call takes half an hour and costs nothing. If we're not the right studio, we'll say so on that call.

Call +44 7882 775 527
Get in touch
  • Email[email protected]
  • Telephone+44 7882 775 527
  • Registered office30a Victoria Avenue, Saffron Walden, Essex, CB11 3AE
  • HoursMonday to Friday, 8.30am–6pm. Support tickets are read outside those hours.

The map is a Google embed, which sets its own cookies. We only load it if you ask.

What are you looking at? (optional)