Skip to content
Kedgeworks

How the work runs.

Four phases, whatever the engagement shape. No methodology branding, no ceremony for its own sake.

01

Discovery

A call, then the code. We read the system before we form opinions about it.

02

Assessment

A written view of what's wrong, what's 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, not in a slide.

04

Handover

Documentation, upskilling, and a codebase your team can run without us. Planned from day one.

What we refuse to do

We don't sell strategy decks. We write code.

We don't staff engagements with juniors and bill them as seniors.

We're not the cheapest. If cost is the deciding factor, we're the wrong call.

We won't tell you to rewrite it from scratch unless that is the right answer, which it usually is not.

The practical answers

The things procurement asks. Answered here so nobody spends a meeting on them.

Contracting
[Founder input] Contracting model and IR35 position, stated plainly.
Insurance
[Founder input] Professional indemnity, public liability, and Cyber Essentials status.
Working hours
UK-based, UK hours. On-site where the work needs it; remote-first where it doesn't.
Security
We've worked inside the compliance perimeters of Visa, Sky Betting & Gaming and a DSPT/CQC-regulated clinical service. Your security review will not surprise us.
Handover
Documentation and upskilling are in the plan from the start. The measure of a good engagement is that you don't need another one.

Sounds like how you'd want it run?