Most teams inherit a codebase they are afraid to touch. We write the kind you can hand to someone else.
01 — Practice
We began in 2019 on a booking system that had already been rewritten twice. Both attempts collapsed for the same reason. Nobody had written down what the thing was meant to do. The third attempt started with a fortnight of questions and a document, and it is still running.
That fortnight is now the first two weeks of every project here. It is the least exciting part of the work and the only part that decides the rest.
Nine of us, one floor above Southerton Road. We hold four projects at a time. When a fifth arrives we give a start date, not a yes. We do not take fixed-price builds under £8,000, and we turn down rescue work we cannot scope inside two weeks — a rescue quoted blind is a second failure with our name on it.
The industry bills for velocity. We would rather be judged on the number of things you never have to fix.
We ship fewer things, later than you would like, and they hold.
02 — The work
Every figure below is a starting point for a London engagement. The number that matters comes out of discovery, in writing.
Two weeks of questions, a written specification, and an architecture you can argue with. Ends in a fixed quote.
A typed backend under a modern front end. Tests written alongside each feature rather than promised for later.
One codebase, both stores, native modules only where they earn their place.
Getting your CRM, your billing and your warehouse to agree on what a customer is.
Infrastructure as code, one-command releases, and a rollback path that has actually been rehearsed.
Dependencies patched, alerts triaged, and a named engineer who already knows your system.
Hiring, architecture review, and telling a board what is genuinely achievable this quarter.
Prices exclude VAT and are a guide only. No build begins without a written scope and a fixed quote agreed first.
03 — Method
Scope
A fortnight of questions, ending in a document you can hold us to.
Build
Two-week cycles. At the end of each one you see the thing running, not a slide about it.
Harden
Load, security and the dull failure cases. Before launch, while there is still time.
Hand over
Documentation, runbooks, and thirty days where we are still the ones on call.
Scope. Build. Maintain.
Tell us what breaks, or what does not exist yet. We will tell you what it takes and what it costs, in writing, before anyone opens an editor.
04 — Enquiries
- [email protected]
- Telephone
- +44 7480 251 242
- Studio & registered office
-
5 Southerton Road
London W6 0PJ
Open in Maps ↗ - Legal entity
- Rentlens Technologies Ltd
Company No. 17361889 - Hours
- Monday to Friday, 09:00–18:00
