How we scale
Big-4 scale. Boutique standard. By design.
The objection to a boutique on a large programme is bench depth. Here is the direct answer: large programmes are won by design, QA and governance — not by the size of a standing bench. Our delivery model puts scale exactly where scale belongs and judgement exactly where judgement belongs.
Reflect on why large programmes fail and the cause is almost never "not enough people." It is flat effort that ignores risk, standard drift that doubles rework, MI that cannot evidence risk reduction, and QA that marks its own homework. Every one of those is a design and judgement failure — and every one gets worse, not better, when you scale headcount without scaling the design discipline underneath.
So we separate the work into layers and match each layer to who is best placed to do it.
Specialist core — CCL
Leads the judgement-intensive workDiagnosis, risk-tiering, file-standard design, decision logic, regulatory strategy, governance and Board-level MI. The layer that determines whether the programme is defensible.
Independent QA
Holds the standardConflict-free second-line challenge sitting outside delivery — testing that the volume produced actually meets the standard, on a documented risk-weighted sampling methodology.
Vetted delivery partners & client teams
Execute at volumeHigh-throughput file completion performed by vetted delivery resource and the institution's own teams, integrated under CCL's design and one quality framework.
One MI spine
Connects everythingA single governance structure and MI spine gives the Board and the regulator a coherent, real-time view of risk reduction across every party executing beneath it.
Layered this way, the model delivers Big-4-scale throughput while keeping the standard a specialist sets. CCL is the brain and the assurance; the partners and client teams are the scalable hands; QA and MI are the connective tissue.
Illustrative multi-party delivery
A 150,000-customer remediation, one standard
A worked illustration of how the layers operate together on a typical large programme. Figures are illustrative of the model, not a single named engagement.
- Weeks 1–4 — CCL leads. Population baseline and file-quality diagnostic; risk-tiering of all 150,000 customers; standardised file templates, decision logic and quality gates designed once; the MI spine stood up. Nothing is mass-executed yet — the design is locked first.
- Weeks 3–6 — delivery mobilises. Vetted delivery partners and the bank's own analysts are onboarded against CCL's standard and trained on the workflow. High-risk and EDD-eligible tiers are triaged first.
- Ongoing — independent QA. A separate CCL-led QA function samples completed files on a risk-weighted basis, testing whether risk was correctly identified and addressed — not just whether files look complete. Error themes feed back into the standard.
- Weekly — one MI pack. ExCo and the MLRO receive a single, coherent MI pack across all parties: completion by risk tier, EDD escalations, SAR triggers, ageing and QA error rates. The regulator sees one story, not three vendors' dashboards.
- At close — BAU handover. CCL hands back a perpetual-KYC operating model so the backlog cannot silently rebuild. The delivery partners stand down; the standard stays.
Three or more parties executed. One design. One standard. One MI spine. That is how a specialist practice runs a programme at a scale its own bench could never staff — without the standard drift that flat staffing produces.
Why CCL vs the alternatives
The same scale, sharper judgement, leaner cost
| Dimension | Cognitive Compliance | Big-4 firm | Generic contractor model |
|---|---|---|---|
| Who does the thinking | The senior specialist who worked the problem inside a Tier 1 institution | Partner at steering committee; junior staff do the work | No design layer — contractors work whatever standard exists |
| How scale is achieved | Vetted delivery partners + client teams under one standard | Large standing bench, premium-priced across the pyramid | Raw headcount, hired directly, minimal scaffolding |
| Standard consistency | Held by independent QA outside delivery | Variable; QA often inside the delivery team | Drifts — ten analysts, ten interpretations |
| Cost shape | Specialist rates for judgement; scaled rates for volume | Specialist rates across the whole pyramid | Cheap per head, expensive in rework and findings |
| Regulator-readiness | MI built for the supervisory question from day one | Strong, but brand premium attached | Throughput metrics that cannot evidence risk reduction |
Read the longer argument in how a boutique scales, or see the umbrella programme this model enables: end-to-end financial crime transformation.
Speak to the practice
Have a programme too large for your bench and too important to get wrong?
That is exactly what this model is built for. A short call to scope how specialist-led, partner-enabled delivery would work for your programme.