The VCP — Value Creation Protocol

The methodology that carries the intelligence.
Not the people.

The VCP is Denacom’s engagement methodology and the software application that runs it. Five phases — configured to the gap profile the Readout surfaces. Focused engagements run in 90 days. Complex situations run longer. The scope, the team, and the timeline are defined before the contract is signed. The diagnostic intelligence is encoded in the system — any trained engagement lead can deliver it at quality, without founder involvement in every decision.

Five phases.
Scoped to your situation.

The phase framework is a proven diagnostic and delivery structure — not a fixed pipeline every engagement runs through identically. The Readout defines which phases apply, in what depth, and over what timeline. Focused engagements with a contained gap profile run in approximately 90 days. Complex situations — broader scope, deeper system dependencies, multiple entities — run longer. What does not change is the rigor: phases overlap by design, build begins before design is finalized, and the scope is defined before anything is signed.

Day ranges shown reflect a focused engagement baseline. Complex engagements extend the timeline proportionally — the phase structure and overlap logic remain the same.

0
Trigger — Engagement Configuration
Activation is not a sales process. The engagement lead is assigned within 24 hours. NDA and SOW are executed within 72. The value creation thesis is reviewed. Initial access is secured. The kickoff session is a pre-diagnosis briefing — not a discovery call.
OutputSigned scope document with success metrics tied to the value creation plan — not Denacom’s metrics.
Days 0–7
1
Diagnosis — Operational Baseline
Three simultaneous tracks: Commercial & Financial (revenue quality, EBITDA bridge, working capital), Operational (C-suite structured interviews, process mapping, capacity audit), and Data & Systems (what data exists, where it lives, whether it is trustworthy). The goal is an honest operational baseline — before anyone designs a solution.
OutputThe Operational Gap Register — every material gap catalogued by area, severity (EBITDA impact), effort to close, and owner. No internal vs. external version. The PE firm sees it. Management sees it.
Days 1–21
2
Design — Build Specification
The Gap Register becomes a build plan. For each priority gap: the target operating model, the process change required, the operational infrastructure configuration that supports it, and the KPI that proves it is working. Maximum 12 KPIs per engagement. Every KPI traces to EBITDA or growth trajectory. No vanity metrics.
OutputThe Operational Design Document — a build specification, not a recommendation deck. First data connections go live during Diagnosis, so design is validated against real data before the document is final.
Days 14–45
3
Build — Operational Infrastructure
Four sequential layers, each used by management as it goes live. No big reveal at the end. Layer 1: data connections — source systems connected, management sees their numbers in one place. Layer 2: process workflows — new workflows live, not documentation of old ones. Layer 3: performance dashboards — KPIs live, baseline vs. current visible. Layer 4: alerting and cadence — automated flags, weekly operational rhythm embedded.
OutputFunctioning operational infrastructure, deployed in layers, in active use by management throughout.
Days 35–75
4
Stabilize — Clean Exit
Denacom exits cleanly. The operational infrastructure runs without us. Management operates independently for a minimum of two weeks with Denacom in standby before formal exit. The Exit Memo is not a victory lap — it is an honest accounting of what moved, what did not, and what the management team needs to execute next.
OutputExit Memo: EBITDA impact vs. baseline, Gap Register closure status, infrastructure operational status, open items with named owners.
Days 66–90

The intelligence
is in the system.

In a traditional consulting firm, diagnostic quality depends on the seniority of the person in the room. The VCP eliminates this dependency by encoding the methodology — the questions, the branching logic, the contradiction detection, the gap weighting — in the application itself. A trained engagement lead runs the VCP. The system tells them what to ask, what the answers mean, what gaps to prioritize, and what to build.

Traditional consulting
Knowing what question to ask next
Adaptive branching logic — the AI probes vague answers, extends strong ones, and flags contradictions in real time
Traditional consulting
Recognizing contradictions across domains
Cross-domain contradiction detection — a COO who reports efficiency while the CFO’s working capital data shows the opposite. Flagged automatically.
Traditional consulting
Understanding what a gap means for EBITDA
Gap weighting with impact scoring, corroborating signals across domains, and industry benchmarks from the engagement repository
Traditional consulting
Briefing the execution team
The Operational Design Document — every signal, gap, evidence chain, and design decision in the system. The execution team does not rely on a verbal briefing.
Traditional consulting
Knowing when to flex the team
Team sizing triggers tied to gap profile from the Readout — gap type, count, severity, and system complexity determine configuration
Traditional consulting
Knowing what to build and leave behind
The build specification is derived entirely from diagnosis. No assumptions. No fixed product. What gets built is what the gaps require.

One team.
Dynamic composition.

The VCP team is not a fixed headcount. It is a configuration that changes as the engagement moves from discovery to execution. From the customer’s perspective: one continuous relationship, one unbroken process. Internally, the skill composition rotates based on what each phase demands. The engagement lead stays throughout. That is the continuity anchor. Everything else flexes.

Readout
Senior engagement lead
AI interview review, gap presentation, scope definition, contract
Phases 1–2
Engagement lead + 1–2 analysts or operational designers + light engineering
Diagnostic validation, design document, first data connections
Phases 3–4
Engagement lead (oversight) + 2–4 engineers + QA and PM
Infrastructure build, workflow deployment, testing, handover
“A trained engagement lead doesn’t need to be Carlos. They need to be able to run the VCP.”

What stays
behind.

Every VCP engagement leaves behind a functioning operational infrastructure. What that infrastructure is — its components, its integrations, its interfaces — is determined entirely by what the VCP diagnosed and designed for that specific company. It is not a product. It is not a platform. It is the answer to the specific operational gaps found in that engagement.

An ERP for one portco. A revenue operations layer for another. A data integration and reporting system for a third. The deliverable has no fixed name because it is a different thing every time. What is consistent across every engagement is not what gets built — it is how it gets built.

Data connectivity
Connects to the portco’s existing source systems — ERP, CRM, HRIS, financial systems. Does not replace them.
Operational baseline
Captures and stores baseline metrics at Day 1. Every improvement is measured against it.
Gap Register integration
Structured issue tracking tied to process areas with status workflow that reflects real closure — not checkbox compliance.
KPI framework
Custom KPI definition with owner, target, cadence, and measurement method — derived from Phase 2 design, not imposed externally.
PE reporting layer
Executive summary view with EBITDA and growth trajectory metrics front and center. Separate from management detail.
Post-exit operability
Self-service enough to run without Denacom present. Owned and operated by the portco management team from exit onward.

What you leave
the engagement with

The Operational Gap Register — closed
Every gap identified at Day 1 has a status: resolved, in progress, or deferred with rationale. No open items without a named owner and a next step.
Functioning operational infrastructure
Built, deployed in layers, in active use by management before Denacom exits. Not handed over at exit — already running.
KPIs live with baseline vs. current visible
Up to 12 KPIs, each with a baseline from the Diagnosis phase, a scoped target, and a measurement method. Movement is visible. Attribution is traceable.
The Exit Memo
An honest accounting of what moved, what did not, and what the management team needs to execute next. EBITDA impact vs. baseline. Not a victory lap.
Two weeks of independent operation before exit
Management operates the infrastructure independently — with Denacom in standby — for a minimum of two weeks before formal exit. The handover is not a handover. It is a confirmation that the system runs without us.
Start the Readout Contact us