Growth outran the tooling
You hired quickly and the build system did not get the memo. Onboarding takes weeks and nobody can say exactly why.
About us
Somebody has to care about the boring middle
Product teams get roadmaps. Infrastructure gets budget. The ground in between — the build, the environments, the path from a laptop to production — usually gets whoever has time. That is the ground DevForm works on.
Why we exist
Almost every engineering organisation past about thirty people arrives at the same problem. The work of building software has quietly become the work of waiting for software: waiting for a build, waiting for an environment, waiting for someone in another team to approve a thing they do not have context on.
Nobody decided this. It accumulated. And because it accumulated, no single team owns it, which is exactly why it does not get fixed. Each individual delay is defensible. Added up across forty engineers and fifty weeks, those delays cost as much as a whole team.
DevForm exists to make that cost visible and then remove it. We come in, measure honestly, agree a fixed scope, build it with your team rather than beside them, and leave. If we have done the job properly you should not need us again for the same thing.
What we are not
We do not sell a platform product with our name on it that you would have to keep paying for. We will not recommend a migration because it is fashionable.
We will also tell you when the answer is that you do not need consultants. It happens more often than you would think, and saying so is cheaper than the alternative.
The short version
An independent UK platform engineering consultancy. We measure developer friction, agree fixed scope, build in your repositories, and hand it back with the documentation to run it.
- Registered name DevForm LTD
- Company number 17407475
- Registered office 167-169 Great Portland Street, 5th Floor, London, W1W 5PF
- Founded 2026
- Working hours 09:00–17:30 UK, Monday to Friday
How we work
Five commitments we will hold to in writing
These are not values on a wall. Each one shows up as a clause in the engagement letter, and you are entitled to hold us to every one of them.
-
Measure before we sell
We will not propose a platform until we can show you what not having one is costing, in hours and in money, from your own systems. If the number is small, we will say so.
-
Your repositories, your licence
Everything we write is committed to your version control under your ownership as it is written. There is no DevForm runtime, no hosted component you must keep paying for, and no part of the result that only works while we are engaged.
-
Embedded with your team
We work inside your standups and your review process, because a platform built in isolation gets abandoned the week after handover.
-
Boring where it counts
We choose the tool your team can still operate in eighteen months, not the one that makes the best conference talk. Novelty is a cost that lands on whoever is on call.
-
Fixed scope, and a real change process
Scope is agreed and priced before work begins. When it needs to change — and on interesting projects it usually does — it changes through a written change request with a costed impact assessment, not through an invoice you were not expecting.
Who we work with
Usually somewhere between thirty and three hundred engineers
Big enough that the friction is expensive, small enough that one focused engagement can change the shape of it.
Two people and a mandate
You have just created a platform team. They need direction, a roadmap, and someone who has done it before to argue with.
Compliance eating velocity
Controls are non-negotiable, but they should be built into the paved path rather than enforced by a queue of manual approvals.
Thirty minutes, one annoying workflow
Bring the thing your team complains about most. We will tell you what we would measure first and whether it is worth paying anyone to fix.