Real workflows. Lasting capability.
These case studies come from our own internal workflows and early client engagements. We dogfooded the methodology before taking it to market.
Built from the inside.
Before we took the methodology to clients, we ran it on our own work. Each card below is a Claude skill file we built for ourselves and still use every week.
Management papers (formal briefing documents prepared for steering committees and project control groups) took roughly a week to draft, review, and finalise. Built a Claude skill that captures the template and reasoning logic, turning raw project inputs into a complete first draft.
Monthly progress claims and variation directions repeat every month, every project, with the same structure. Built a reusable Claude skill file for progress claim automation, encoding commercial logic, formatting standards, and sign-off expectations.
Consultant briefs (scope-of-works documents for engineering consultants) are high-value and high-judgement, but share structural DNA across projects. Built a skill that ingests project context and produces a structured first-draft brief. Proven across two live engagements with very different scopes.
Weekly and monthly progress reports are the most repetitive deliverable on the calendar. Built a Claude skill that ingests raw period inputs (progress notes, programme updates, RFI logs, cost movements, risk changes) and produces a structured, client-ready report matching each client's template.
Want a case study with your name on it?
Every engagement starts with a conversation about your workflows. We'll show you where Claude earns its place.