We take responsibility for software that has to keep working.
Kedgeworks is a UK software consultancy. A principal leads every engagement and works in the code until handover.
Most of our work starts in one of four places.
You have a platform to build from nothing
A brief, a deadline, and no codebase yet. We design it, build it, and hand it to a team that can run it.
Product delivery→Your team is short of senior engineers
The plan is fine. The roadmap is slipping because there are not enough hands at the level it needs.
Engineering capacity→Your system costs more to change every quarter
It still works. It just gets slower and more expensive to touch, and nobody wants to be the one who breaks it.
Rescue and re-platforming→Somebody else started it and stopped
A half-finished project, an agency that left, or a codebase nobody remaining understands. We pick those up.
Rescue and re-platforming→The job underneath is the same one every time. Take responsibility for software that has to work, and hand it back in better shape than we found it.
Platform rescue & re-platforming
Modernise a live, critical system without taking it offline.
Rescue & re-platforming →02Senior engineering capacity
Senior engineers embedded in your team, productive in week one.
Engineering capacity →03End-to-end product delivery
Take a brief and ship the product. Greenfield, or picking up where another team stopped.
Product delivery →How engagements are shaped
Rates are set per engagement.You need to know how bad it is before committing.
A live platform that needs stabilising and modernising.
You have the plan and need senior hands.
A defined product to design, build and hand over.
Most engagements run three to nine months. We take on a small number at a time, and we are usually booked several weeks ahead.
A legacy Ruby forex system moving onto Express and Next.js after the Visa acquisition, so it could scale and its processes could be modernised.
Read →Low61M+High-traffic free-to-play gaming platforms holding sub-200ms responses through match-window peaks.
Read →Diageo190Tooling for several teams of developers to move 190 Diageo brand sites off assorted CMS platforms, with Guinness.com built first as the test project.
Read →- 01
Discovery A call, then the code. We read the system before we form opinions about it.
- 02
Assessment A written view of what is wrong, what is fine, and what to do in what order. Yours to keep either way.
- 03
Delivery Incremental, in production, visible in your tools. You see progress in the repo rather than in a slide.
- 04
Handover Planned from day one. Your engineers get time in the new system while we are still there, and the documentation is written as the work happens.
Every engagement is led by a principal, and that principal works in the codebase until handover. Nobody is ever billed at a level above the work they are doing.
“A valuable asset to our team in the time he worked with us, he proved himself to be dependable, a hard-worker, and brought an impressive level of expertise to the team. I was always impressed by Grant’s ability to quickly understand complex requirements, and deliver elegant solutions quickly and at a very high quality.”
You're a CTO with a platform problem
You need architecture detail and evidence we've done this on systems like yours. Start with the case studies.
The work →You're running a programme
You need a supplier who won't fail visibly. Regulated-sector track record, process, and how engagements run.
Our approach →You're an agency needing capacity
We work white-label behind your brand, and we never approach your clients. Most of our work arrives this way.
For agencies →Tell us what you’re working on.
Forty-five minutes with the principal who would run the engagement. It costs nothing and it is not a sales call. We’ll tell you if you don’t need us.