Platform engineering & developer experience — United Kingdom
DevForm is a platform engineering consultancy. We find where your engineers lose their days — CI queues, ticket-driven infrastructure, three-week onboarding — and we build the thing that removes it.
Unformed — how it usually starts
Formed — what we are hired to reach
Illustrative, not a promise. The left column is what we most often measure on day one; the right is what we scope against. Your baseline gets measured before anything is agreed.
What we form
Most teams do not need a bigger platform. They need the six places their people get stuck to stop being places they get stuck.
A paved route from empty repository to production, with the defaults already correct. Built so the easy way is also the compliant way. Where it helps, a catalogue-grounded assistant and agent-safe self-service sit on that same path.
Pipeline archaeology, then surgery. We attack the wait — caching, test sharding, parallelism, and the flaky tests everyone has learned to re-run.
Infrastructure as code that your team can read, plus ephemeral preview environments per pull request so review stops being imagination.
Service objectives tied to something a customer would notice, alerts pruned to the ones worth waking for, and runbooks written by the people who will use them.
Pipeline telemetry, structured interviews and a survey your engineers will finish — then a baseline specific enough to argue with. Most clients start here.
Roadmap, real users, adoption measured rather than assumed, and the nerve to deprecate things properly. Coaching for a first-time platform lead included.
How an engagement runs
In that order, every time. You can stop after any stage and keep everything produced up to that point.
We instrument your pipelines, sit in on your standups, and interview the people doing the work. You get a written baseline: where the time goes, what it costs, and the three changes with the best return. It is yours whether or not you continue.
Every deliverable named, with acceptance criteria you can hold us to, and a price against it. Nothing starts until it is signed. If the work needs to change after that, it changes through a change request — never through a surprise invoice.
Embedded with your engineers, in your repositories, under your licence. Weekly demo of working software rather than a status deck. Your team reviews every pull request, because they are the ones keeping it.
Runbooks, architecture notes, a recorded walkthrough and a named owner on your side who has already done the job with us watching. We come back after 30 days to see what actually stuck.
For clients already working with us
Scope changes. That is normal, and it is planned for. The client desk is where you log a change to signed work, report something broken, or ask for access — on a form that captures what we need the first time.
Every submission gets a reference number on screen and lands in our CRM against your account. Change requests are acknowledged within one working day and answered with a cost and schedule impact within three.
A conversation is 30 minutes and free. Bring one workflow that annoys your team and we will tell you honestly whether it is worth paying anyone to fix.