What You’re Actually Buying
You’re not buying hours. You’re buying commercial clarity at the moment it matters — before small leaks stack up into rework, delay, dispute, and cashflow pain.
Scope stays locked
Deliverables, exclusions, assumptions, and interfaces are made explicit.
Change gets controlled
Variation triggers are defined, priced, and decided deliberately.
Decisions happen early
We stop “we’ll sort it later” becoming your margin problem.
The Engagement Models
Project Delivery Review
(Best place to start)
A structured, independent review of one project to expose where margin is leaking and exactly what needs tightening to regain control.
Project Rescue Sprint
(When a project is drifting)
A short, fixed-scope intervention to stabilise a live project before small issues become unavoidable margin loss.
Retained Delivery Oversight
(Ongoing protection)
Monthly independent oversight across live projects to keep scope controlled, decisions timed, and risk visible — without adding admin.
The EPD Method (How Control Actually Gets Built In)
Step 1: Baseline the Truth (What was sold vs what’s being delivered)
We pull the project back to first principles:
- deliverables and boundaries
- assumptions (spoken and unspoken)
- responsibilities and interfaces (who owns what)
Output: a simple baseline summary — what’s solid, what’s exposed, what needs deciding.
Step 2: Identify the Quiet Leaks (Where margin disappears)
We look for the common failure modes that quietly kill projects:
- scope written like a brochure
- acceptance criteria missing
- “promise creep” during bid pressure
- change control not enforceable
- lead times assumed
- handover gaps between sales and delivery
Step 3: Install Practical Controls (Without bureaucracy)
Controls are lightweight, but non-negotiable:
- clear assumptions schedule
- interface/RACI clarity
- programme hold points
- variation triggers + decision path
- stage-gates where they matter (e.g., design freeze before procurement)
Step 4: Force Better Decisions Sooner (The real value)
Most teams don’t need more process. They need:
- the right decisions made earlier
- owners named
- deadlines set
- and the confidence to hold the line commercially
What You Get (Deliverables)
After a review, you’ll leave with:
- A clear view of current exposure (scope, variations, interfaces, programme risk)
- A list of specific decisions required, with owners and dates
- A defensible position on what is / isn’t included
- Practical next steps: tighten scope, reset change control, or escalate into a sprint/retainer
What We Need From You (So the work stays fast)
Minimum inputs (kept simple)
- Quote / contract / order acknowledgement
- Scope / spec / drawings (latest revision)
- Programme + key dates
- Variation log (even if informal)
- Known risks / constraints
Note: If documentation is messy — that’s data. We don’t need perfection, we need the truth.
Frequently asked questions
Good. This doesn’t replace them.
This protects them (and the business) from carrying commercial risk that was never theirs to own.
No — it slows down bad decisions.
Most delays come from unclear scope, late changes, and unresolved interfaces. Tightening those early speeds everything up downstream.
No. It’s fewer, sharper controls in the places projects actually fail:
quote → handover → design freeze → procurement → install readiness → acceptance.
Then we stop pretending. That’s when a Project Rescue Sprint makes sense — to stop further damage and reset control
Who This Works Best For
Ready to Regain Control?
Start with a single project. Get clarity fast. Then decide whether you want a one-off intervention or ongoing oversight.
