CDD Engagement Kick-Off

Every strong diligence starts the same way: with a sharp question and a disciplined plan to answer it fast. The kick‑off phase sets the tone for everything that follows—what you believe, what you must prove, and how you’ll get there within a compressed window. Done well, you establish a shared thesis, a prioritized learning agenda, clean‑team boundaries, access protocols, and a governance cadence that keeps decisions moving. Done poorly, teams chase interesting data instead of value‑critical proof and run out of time.

Use this chapter to engineer a rigorous start. We translate the investment thesis into testable hypotheses, define scope and boundaries, set roles and decision rights, and design the first wave of research and analysis. You’ll leave the kick‑off with a crisp issue tree, a ranked set of “would‑have‑to‑be‑true” statements, a data and access plan, and a calendar locked to the deal timeline. Above all, you’ll know what you are trying to disprove first—because finding the break point early is the most reliable way to protect time, fees, and judgment.

2.1 Initial Hypotheses Development

The first job of a CDD is to turn an investment narrative into testable propositions. Hypotheses are not guesses; they are concise statements about how the market works, why the target wins, and what conditions must hold for the deal to create value. Strong hypotheses do three things: they focus the team on the few drivers that swing valuation, they dictate the evidence you need (and what you can safely ignore), and they create a common language for trade‑offs as new facts arrive.

Start by extracting the thesis in plain English. Strip out marketing language and restate the logic as cause‑and‑effect: “Because X market is expanding and competitors are fragmented, the target can raise price Y% and grow share Z% while maintaining churn below A%.” If you can’t express the thesis in that form, you don’t have one yet. Next, decompose the statement into a small set of driver hypotheses—market size and growth, pricing power, customer retention and expansion, competitive response, sales capacity and productivity, unit economics, and (if relevant) revenue synergies. Each driver needs a target value, a rationale, and a path to independent verification.

Build an issue tree that mirrors those drivers. Under market size, specify definitional boundaries (what’s in/out), reachable segments, and the mix shifts implied by the plan. Under pricing, define the architecture (list vs. realized, discounts, rebates), sources of power (differentiation, switching costs, channel leverage), and the pressure tests that matter (promo intensity, new entrants, procurement tactics). For retention, anchor on cohort behavior and the causes of churn—voluntary vs. involuntary, competitive vs. value‑for‑money—and specify what expansion must look like to hit net revenue retention targets. This tree is your backbone for day‑to‑day decisions and for the story you will eventually tell.

Write each hypothesis as a “would‑have‑to‑be‑true” (WHTBT) statement. Make it binary and measurable so it can be proved or disproved. Examples:

“Serviceable market in core geographies is ≥ $1.2B today, growing ≥ 7% CAGR through 20XX, with >60% of growth in segments where the target participates.”
“Average realized price can increase 2–4% annually for three years without materially elevating churn in the top three segments.”
“NRR stays ≥ 110% with gross churn ≤ 8% and upsell from feature bundle B delivering ≥ 3 points.”
“Two largest competitors lack distribution coverage in Tier‑2 channels and are unlikely to expand there within 24 months.”

For each WHTBT, document the minimum viable evidence you’ll accept and the disconfirming tests you’ll run. Minimum evidence might include triangulated market sizing (top‑down using reputable industry series and bottom‑up using buyer counts and replacement cycles), 12–20 targeted customer interviews with decision‑makers and recent churned accounts, and transaction‑level price‑realization analysis if access allows. Disconfirming tests could include win/loss analysis with procurement, competitor mystery shopping, elasticity checks in comparable categories, and back‑solving the plan to see if implied conversion or ramp times violate historical base rates.

Quantify stakes and set thresholds before you collect data. If a hypothesis failing would move enterprise value by more than your materiality threshold, label it “killer variable” and test it first. Don’t bury killer variables in a long research plan—resolve them in week one. Use base‑rate thinking to keep ambition honest: what is the historical distribution of growth, pricing, or NRR for companies with similar ACVs, sales cycles, and channel mix? If your target sits in the top decile of that distribution, you will need top‑decile proof.

Treat hypotheses as living objects and require owners, dates, and decision points. Each hypothesis should have a named owner, a due date aligned to governance gates, a list of sources to be tapped, and a pre‑commitment on how you will update beliefs as evidence arrives (Bayesian in spirit, practical in execution). When facts conflict, don’t average; rate confidence explicitly and prefer revealed behavior (contracts, invoices, win/loss decisions) over stated preferences.

Bias is the enemy of good hypotheses. Counter it deliberately. Start every sprint with a short pre‑mortem: “Six weeks from now this deal failed because…” Capture the three most plausible failure modes and ensure at least one hypothesis actively looks for each. Build a contrarian bundle—two or three hypotheses that, if true, would invalidate the deal or materially cut the price (e.g., “Price increases are driving silent churn; NRR is being propped up by temporary expansion” or “Distributor consolidation will compress gross‑to‑net by 300–500 bps”). Assign a senior reviewer to champion the contrarian view and safeguard it through synthesis.

Translate hypotheses into a ranked learning agenda. You are not trying to learn everything; you are trying to learn the few things that matter in time to act. A practical first‑week agenda often includes: (1) dual‑method market sizing to bracket headroom, (2) 8–12 expert calls to map channels and competitor moves, (3) 10–15 customer interviews split between loyalists and churned accounts, (4) price‑architecture reconstruction from contracts, rate cards, and invoices if accessible, and (5) a funnel reality check using anonymized pipeline data or external proxies. In auctions with limited access, heavier weight shifts to outside‑in sources, channel checks, and secondary datasets; in bilaterals, take advantage of access to test commercial capabilities, not just collect more documents.

Document your hypotheses in a simple, reusable artifact—one page per hypothesis—so the team and sponsors stay aligned. A good “Hypothesis Card” includes:

Statement (the WHTBT in one sentence)
Why it matters (value at stake and which decision it affects)
Evidence to prove/disprove (exact sources and sample sizes)
Disconfirming tests (the fastest way to break it)
Current belief and confidence (high/medium/low, with date)
Owner and due date (tied to governance gates)

Close the loop with stakeholders early. Share the hypothesis set within 24–48 hours of kick‑off, insist on ranked priorities, and confirm what you will not do. Push sponsors to mark where they would change price, structure, or go/no‑go if a hypothesis flips from true to false. That discipline prevents “decision drift” and forces useful escalation when access or data quality threatens to leave a killer variable untested.

Common pitfalls in hypothesis development are well known and avoidable. Teams overfit to management’s narrative, phrase hypotheses in ways that are unfalsifiable (“market is attractive”), skip base‑rate comparisons, or design research that can only confirm. Others boil the ocean by turning hypotheses into wish lists. Keep your list short, measurable, and anchored in value at stake. When in doubt, ask: “If this were true or false, would we act differently?” If the answer is no, drop it.

Initial hypotheses checklist (use on Day 0–2):

Investment thesis restated as causal, testable statements.
Issue tree covering market, customer, competition, pricing, GTM, unit economics, and (if relevant) synergies.
6–12 WHTBTs written as binary, measurable conditions with thresholds.
Value‑at‑stake quantification and a short list of killer variables to test first.
Minimum viable evidence and explicit disconfirming tests for each hypothesis.
Base‑rate benchmarks identified for growth, pricing, retention, and productivity.
Owners, due dates, and governance gates assigned; confidence ratings initialized.
Clean‑team and MNPI constraints mapped to the learning agenda; access plan confirmed.
Stakeholder alignment on priorities and on what will not be done within the timeline.

Start here, and you will give the rest of the diligence a clear edge: a small set of sharp questions, a practical plan to answer them, and a bias toward breaking bad news early—when it is still useful.

2.2 Stakeholder Alignment Workshop – Step-by-Step Guide

The alignment workshop is how you turn a fast‑moving deal into a focused, disciplined sprint. In a single working session—90 to 120 minutes—you lock the thesis, the “would‑have‑to‑be‑true” statements, the not‑doing list, clean‑team boundaries, and the cadence that will govern the next few weeks. The point is not ceremony; it’s commitment. Everyone should leave the room knowing exactly what must be proved, by when, and what will happen if access is thinner than expected or facts break the thesis.

Before you gather people, set the pre‑conditions. Circulate a pre‑read 24 hours in advance that includes the one‑page thesis, initial hypotheses (with owners), value at stake for the top three variables, the draft workplan, and the proposed governance calendar. If you expect clean‑team constraints or limited access in an auction, include them up front so the research design is realistic. Ask invitees to mark the single assumption that, if false, would change price, structure, or go/no‑go. That simple discipline forces sharper discussion when you convene.

Who should attend. Keep it lean enough to decide and broad enough to avoid re‑litigation later. Typical attendees: deal lead and one investment professional, operating partner or corporate sponsor lead, CDD lead partner and manager, QofE lead, legal counsel, tech/ops diligence leads as needed, and a PMO or chief of staff to run governance. If a clean team is required, separate “clean” and “non‑clean” attendees in the invite and agenda.

What you must leave with. A ranked list of hypotheses with thresholds, a not‑doing list, a locked research plan and access protocol, a governance calendar with gates, and a 72‑hour action plan with named owners. Anything less invites thrash.

Step‑by‑step facilitation plan (90–120 minutes).

Frame the decision and timeline.
Open with the decision you must enable and by when: price, structure, and conditions for the Investment Committee. Put the IC date and key intermediary gates on a single slide. Anchor materiality: define what “moves value” in dollars, not adjectives. This sets the bar for what qualifies as a killer variable.
Restate the thesis in causal terms.
Have the sponsor state the investment logic in one minute, then the CDD lead re‑states it as cause‑and‑effect. Write it in “because/therefore” form. If you can’t say it crisply, pause. Ambiguity now becomes confusion later.
Review and refine hypotheses (WHTBTs).
Walk through the 6–12 “would‑have‑to‑be‑true” statements prepared in 2.1. For each, confirm the threshold (e.g., “NRR ≥ 110%”), why it matters (value at stake), and the minimum evidence you’ll accept. Assign an owner. Mark two or three as killer variables to be tested first. If attendees propose new hypotheses, ask the price‑change test: “If true or false, will we act differently?” If not, park it.
Confirm definitions and scope boundaries.
Agree on market definitions, product and segment taxonomies, and geographies. Decide where the line is for a serviceable market and reachable share. Clarify in/out items for analysis. This step prevents late‑stage rework caused by definitional drift.
Set the not‑doing list.
Explicitly list the analyses you will not perform within the sprint. Common examples: long‑tail micro‑segment sizing, extensive competitor profiles with no value impact, or speculative synergy quantifications that cannot be validated pre‑close. This saves days.
Lock the access and clean‑team protocol.
Confirm what management access, data room quality, and customer contact are realistically available. If operating under clean‑team rules, specify who is “clean,” what datasets they can see, how anonymization will work, and what can be shared with non‑clean members. Note MNPI and anti‑trust boundaries for primary research and competitive information. If access is uncertain, set a date to escalate; don’t assume it will resolve itself.
Design the research plan.
For each hypothesis, confirm the evidence path: secondary sources, expert calls, customer and channel interviews, surveys, and outside‑in datasets. Agree on the cohorts you need (e.g., top accounts, churned customers, procurement leaders, distributors), the sample sizes, and the order in which you’ll contact them. Where access is thin, pre‑authorize substitutes (e.g., channel partner checks instead of end customer).
Agree on analytical methods and triangulation.
Commit to dual‑method market sizing (top‑down and bottom‑up), price architecture reconstruction, cohort retention analysis, and unit‑economics diagnostics where relevant. Decide where you’ll run sensitivity and scenario work, and what ranges are decisions‑useful. Name the “second method” you’ll use to cross‑check each killer variable.
Set governance and decision rights.
Lock the cadence: daily stand‑up or thrice‑weekly, mid‑sprint gate for killer variables, and pre‑IC synthesis. Assign decision rights: who can change scope, who approves new data purchases, who escalates access issues, and who can call a stop or price change if a killer variable breaks.
Define interfaces with other streams.
Map the handoffs to QofE, legal, tech, ops, tax, and ESG. For each material assumption, mark who validates what and by when. Example: “Renewal rates—CDD shapes cohorts and drivers; QofE validates ledger consistency; legal reviews termination and assignment clauses.”
Surface risks and pre‑mortem.
Run a five‑minute pre‑mortem: “It’s four weeks later, and we got the decision wrong because…” Capture the top three failure modes. Make sure each has a corresponding hypothesis or disconfirming test. Assign a senior “contrarian” to protect alternate explanations during synthesis.
Confirm artifacts and the single source of truth.
Agree on the templates and where they live: hypothesis cards, risk ledger, issues log, workstream charters, interview guides, source register, and compliance memo. Name the document owner and the file path. Version control matters under time pressure.
Close with a 72‑hour action plan.
Leave with a punch‑list, owners, and dates. The first 72 hours set the tone; make sure the killer variables are at the top.

Inputs to prepare before the workshop.

One‑page thesis with a value bridge and hold‑period logic.
Draft list of WHTBT hypotheses with thresholds and value at stake.
Proposed workplan, milestones, and governance calendar.
Access assumptions and clean‑team proposals.
Initial data and research budget with pre‑approved vendors.
Risks and open questions you already know about.

Outputs you must have at the end.

Finalized and ranked hypothesis list, with killer variables flagged.
Not‑doing lists to protect speed and focus.
Approved research plan with cohorts, sample sizes, and sequencing.
Access and clean‑team protocol documented and blessed by counsel.
Governance cadence, decision rights, and escalation paths.
Cross‑stream handoffs with owners and due dates.
72‑hour action plan with named owners and calendar holds.

Sample 90‑minute agenda you can lift and run.

Minute 0–10: Decision, timeline, and materiality bar.
Minute 10–25: Thesis restatement and value logic.
Minute 25–50: Hypotheses review and killer variables.
Minute 50–60: Definitions, scope, and not‑doing list.
Minute 60–70: Access plan and clean‑team rules.
Minute 70–80: Research and analytics plan.
Minute 80–85: Governance, decision rights, and interfaces.
Minute 85–90: Risks, pre‑mortem, and 72‑hour actions.

Facilitation tips that keep it sharp.

Start with the price‑change question to focus on value, not trivia.
Write thresholds as numbers, not adjectives (“≥ 7% CAGR,” not “strong growth”).
Time‑box debate; when evidence is missing, capture the test, not opinions.
Use a parking lot for interesting but non‑critical topics; review only if time remains.
Avoid consensus‑by‑averaging; record confidence levels and assign owners to resolve.
Keep slides light; use a live tracker for hypotheses, owners, and dates.

Clean‑team and compliance guardrails to state explicitly.

Who is on the clean team and what they can see or share.
What constitutes MNPI in this process; how primary research will avoid it.
What cannot be discussed pre‑close (pricing coordination, customer allocation).
How anonymization and aggregation will work for sensitive datasets.
Who to call when in doubt, and the turnaround time for counsel sign‑off.

72‑hour action plan template (fill this before you adjourn).

Killer variable 1: owner, evidence path, sources, decision date.
Killer variable 2: owner, evidence path, sources, decision date.
Market sizing: owner, top‑down series to pull, bottom‑up build approach, date.
Primary research: owner, cohorts, target counts, screener approved, start date.
Price architecture: owner, artifacts to collect (contracts, invoices), outside‑in proxies.
Competitor response: owner, expert list, scenarios to test, date.
Interfaces: owners in QofE/legal/tech, specific questions, hand‑off date.
Governance: calendar invites sent, stand‑up cadence locked, issues log live.

Common failure modes and how to disarm them early.

Ambiguous thesis: rewrite it in cause‑and‑effect form and test for price impact.
Kitchen‑sink scope: enforce the not‑doing list and the price‑change test.
Access optimism: set an escalation date and a plan B source list on day one.
Definition drift: publish a glossary and lock market and segment definitions.
Confirmation bias: assign a contrarian lead and require disconfirming tests.
Tool sprawl: declare a single source of truth and a single owner for every artifact.

Quick checklist to keep on the room’s whiteboard.

Decision and date are clear.
Hypotheses ranked; killer variables first.
Not‑doing list agreed.
Access and clean‑team rules locked.
Research plan and cohorts set.
Governance and decision rights assigned.
Interfaces and owners named.
72‑hour actions committed.

Run this workshop with discipline and you’ll compress weeks of drift into one decisive session. The payoff is a team aligned on the few things that truly move value, a plan grounded in reality, and the mechanisms to adapt quickly as facts arrive.

2.3 Scope Definition Checklist

Scope is strategy under time pressure. In a diligence sprint, you win by deciding what not to do just as decisively as what to do. A tight scope anchors everyone on the decision you must enable, the variables that truly move value, and the minimum evidence required to be credible. It also locks the boundaries—markets, segments, time horizons, access rules, and handoffs to other streams—so the team can move fast without re‑litigating definitions.

Start with the decision, not the workplan. In one sentence, state the Investment Committee decision you must support and the date. Translate that decision into a handful of “would‑have‑to‑be‑true” statements (killer variables first), then design the scope to break or prove those statements quickly. If a task doesn’t change price, structure, or go/no‑go, it probably doesn’t belong in scope.

Be explicit about market and product boundaries. The fastest way to waste days is to let definitions drift. Write down the market taxonomy (what’s in and out), the geographies that matter, the customer segments you’ll analyze, and the product or SKU families you’ll cover. Tie revenue types to those definitions (recurring vs. transactional, license vs. usage vs. services), and confirm the base year, currency, and hold‑period horizon you’ll model. If adjacencies are part of the thesis, treat them as options with their own evidence thresholds rather than default inclusions.

Calibrate scope to access. Auction processes with thin management time and tight data rooms push you toward outside‑in sources, expert calls, channel checks, and clean‑team protocols. Bilaterals often allow deeper access; use it to test commercial capabilities (price realization, funnel health, renewal mechanics), not to collect more documents. Decide up front what customer and channel outreach you will do, the minimum sample sizes, and the rules for avoiding material nonpublic information.

Guard against false precision. Commit to dual‑method triangulation on the few things that matter (e.g., bottom‑up and top‑down market sizing; invoice‑based and interview‑based price realization). Identify a “second method” for each killer variable before work starts. Where evidence is thin, set explicit confidence levels and ranges; do not round a directional answer into a spurious point estimate.

Define interfaces and handoffs. CDD does not validate ledgers, interpret contracts, or certify compliance. For every material assumption—renewal rates, rebates, exclusivities, data‑use rights, roadmap feasibility—assign a validation owner in QofE, legal, tax, tech, ops, or ESG, and put a date on it. Keep a shared risk ledger so no assumption dies in email.

Below is a practical checklist you can copy into your kickoff and complete in 30–45 minutes. Use plain numbers, avoid nested sub‑lists, and fill every line.

Decision to enable and date (price, structure, conditions).
Materiality threshold in dollars; what “moves value” here.
Ranked hypotheses with explicit thresholds; killer variables flagged.
Market definition: taxonomy, inclusions and exclusions, competitive set.
Geography and segment scope; which micro‑segments you will actually size.
Product and revenue scope: SKUs or modules, recurring vs. transactional, services.
Time horizon: base year, seasonality treatment, hold period, exit year.
Currency and FX policy; inflation and pricing index assumptions.
TAM/SAM/SOM definitions and exact methodology you will use.
Scenarios required: base, downside, upside; triggers and monitoring indicators.
Primary research plan: cohorts, target counts, screening, and fieldwork start date.
Secondary sources and datasets: named vendors, budget cap, and approvals.
Access assumptions: management time, data room quality, customer contact rules.
Clean‑team, MNPI, and antitrust guardrails; who is “clean” and what they can view.
Analytical methods: second‑method cross‑checks for each killer variable.
Pricing scope: price architecture to reconstruct and evidence required for realization.
Demand and retention scope: cohort definitions, NRR/GRR math, churn taxonomy.
Go‑to‑market scope: funnel stages, productivity metrics, channel economics to test.
Unit economics scope: contribution margins, cost‑to‑serve cuts, CAC/payback/LTV.
Externalities: regulatory, reimbursement, platform dependencies, supply constraints.
Interfaces to other streams: specific questions and owners in QofE, legal, tech, ops, tax, ESG.
Deliverables: deck outline, data book contents, and appendix artifacts to produce.
Governance: stand‑up cadence, mid‑sprint gate, pre‑IC synthesis date.
Not‑doing list: analyses explicitly out of scope for this sprint.
Risk ledger: open issues, owner, due date, confidence rating.
Budget and staffing: hours by workstream, external spend cap, vendor PO process.
Quality bar: triangulation standard, citation style, and replication requirement.
Escalation triggers: what forces a price/structure change or a stop.
Contingencies: plan B if access is thin; proxies you will use.
Definition of done: what must be true to call the scope complete.

Use the not‑doing list to protect speed. Write it as firmly as the in‑scope list. Typical candidates include exhaustive competitor profiles that do not change the story, long‑tail micro‑segment sizing when the thesis rides on the top five segments, speculative synergy estimates without a path to validate pre‑close, and deep operational diagnostics that belong with ops diligence. Review the not‑doing list at every governance gate; add to it as new red herrings appear.

Make deliverables decision‑ready. Define on day one what the Investment Committee will see: a one‑page thesis and value bridge, a market sizing section with method and sources, customer insights with direct quotes (anonymized), a pricing and unit economics section that ties to realized margins, a competitive response section with explicit scenarios, and a driver‑based model with sensitivities. Decide which exhibits must be replicable by a third party and how you will footnote every material claim. The “data book” should include source registers, interview guides, anonymized notes, and model documentation.

Lock the research footprint. For primary research, set quotas by cohort (top customers, churned accounts, procurement leaders, distributors). Name the first ten targets and the screener questions. For secondary, list the exact series you will pull and who will own each. If you plan to purchase datasets, pre‑approve vendors and the ceiling spend to avoid delays. Where outreach is constrained, pre‑authorize channel checks and expert calls as substitutes.

Treat risk and compliance as scope, not footnotes. If the target and buyer are competitors, write down the clean‑team roster, the anonymization rules, and what can be shared with non‑clean team members. State what you will not ask in interviews, how you’ll describe the study’s purpose, and the approval path for any sensitive requests. Include a short compliance memo in the data book.

Put guardrails on modeling. Declare the model’s structure (driver‑based, transparent formulas, version‑controlled), the naming conventions, and the sensitivity suite you will run. Fix the base‑rate comparisons you will use to sanity‑check plan assumptions (e.g., NRR distributions for peers with similar ACVs and sales cycles). Decide how you will handle seasonality, one‑offs, and normalization. Require a model integrity check before any number hits a deck.

Define “done” before you start. A scope is complete when each killer variable has been tested with two methods or independent sources; the market is sized with both a bottom‑up and top‑down approach; NRR/GRR and pricing realization have been validated or bounded with clear ranges; downside scenarios are quantified with triggers; and all critical handoffs to other streams have named owners and dates. Anything less is progress, not completion.

Finally, time‑box the first 72 hours. By the end of day three you should have locked definitions, launched primary research, pulled top‑down series, started the bottom‑up build, collected initial contracts or invoices for pricing reconstruction (or confirmed proxies), and scheduled cross‑stream handoffs. If a killer variable is blocked by access, escalate immediately and execute the contingency path you already scoped.

When you use this checklist with discipline, scoping stops being a kickoff ritual and becomes a force multiplier: fewer surprises, faster decisions, and a diligence product that holds up under scrutiny.

2.4 Workstream Charter Template

A workstream charter is your contract with time. It tells the team exactly what must be proved, how it will be proved, and when decisions get made. In a compressed diligence window, a clear charter prevents drift, stops scope creep, and accelerates the few analyses that actually move value. Treat it as both a planning document and a live control mechanism: you will use it to assign owners, lock definitions, track confidence, and trigger escalation when evidence is late or thin.

What “good” looks like is simple. The charter ties every activity back to a decision the Investment Committee must make. It sets measurable “would‑have‑to‑be‑true” thresholds, pre‑commits to triangulation methods, and spells out the minimum viable evidence you will accept. It also draws firm boundaries: what is out of scope, which risks belong to other diligence streams, and which clean‑team or compliance rules gate access. Finished charters read like checklists you can execute against, not essays.

Design each charter to be short, sharp, and replicable across workstreams—market sizing, pricing and unit economics, customer and retention, competitive dynamics, go‑to‑market, technology implications, and (where relevant) revenue synergies. Use consistent field names and keep one living version in your single source of truth. Update confidence ratings as evidence lands; do not bury changes in email threads.

Below is a copy‑paste template you can drop into your project workspace and complete in under an hour. Use numbers, not adjectives. If a field does not change price, structure, or go/no‑go, drop it.

Workstream Charter Template (copy, fill, and publish)

Workstream name and owner
Objective in one sentence (decision this enables and by when)
Key hypotheses (WHTBT statements with numeric thresholds)
Value at stake (estimate in dollars if hypothesis passes vs. fails)
In‑scope items (markets, segments, products, geographies, period)
Out‑of‑scope items (explicit not‑doing list)
Methods and triangulation plan (first method and second method for each killer variable)
Minimum viable evidence (sources, sample sizes, artifacts you must obtain)
Primary research plan (cohorts, quotas, screeners, timing)
Secondary sources and datasets (named vendors, series, budget cap)
Access assumptions and constraints (management time, data room, customer contact rules)
Clean‑team and compliance rules (who is “clean,” what can be viewed or shared, MNPI and antitrust guardrails)
Analytical steps (calculations and models you will run, with owner for each)
Model specification (driver definitions, version name, sensitivity suite, base‑rate comparisons)
Interfaces and dependencies (QofE, legal, tech, ops, tax, ESG—what each must validate and by when)
Deliverables and acceptance criteria (exhibits, model outputs, data book artifacts; what makes them “done”)
Milestones and gates (dates for first read‑out, mid‑sprint gate, pre‑IC synthesis; stop/price‑change triggers)
Risks and assumptions (confidence rating, evidence gaps, contingency paths)
Staffing and hours (roles, time allocation, backup coverage)
External spend (approved vendors, PO status, ceiling)
Communications cadence (stand‑ups, stakeholder updates, decision rights)
Version control and citations (location of source register, footnote standard, replication requirement)
Data security and retention (storage location, access controls, retention/destruction date)
Definition of done (binary checklist you will use to sign off)
Approvals (names and date stamps for owner, CDD lead, sponsor)

Use the charter to align language and lock definitions. For market work, write the taxonomy and inclusions in the charter, not in slide notes. For pricing work, specify which price you mean—list, net, realized—and exactly how you will compute it from available artifacts. For retention, define cohorts, GRR/NRR formulas, and the treatment of upgrades and downgrades. For go‑to‑market, define funnel stages and conversion math. Precision now prevents rework later.

Commit to your second method before you start. If your first method for market sizing is a top‑down triangulation using industry series, your second method should be a bottom‑up build from buyer counts, penetration, and replacement cycles. If your first method for pricing is contract analysis, your second is transaction‑level netting or customer interviews with procurement. Writing this in the charter forces rigor and speed review.

Keep acceptance criteria crisp and binary. “Done” means the exhibit or model can be replicated by a third party, every material claim is footnoted to a verifiable source, and ranges are shown where confidence is less than high. A charter without acceptance criteria is an invitation to iterate indefinitely.

Escalation rules belong in the charter. Declare what triggers a scope change, a price change, or a stop: for example, failure to obtain customer access by a named date, discovery that the competitive set is misdefined, or evidence that a killer variable has broken (e.g., realized price is 300 bps lower than modeled). Name who can make the call.

Interfaces should be explicit, not implied. If the charter depends on QofE to validate ARR definitions or on legal interpretation of MFNs and termination rights, write the exact questions and the due dates. Create one shared risk ledger across streams and link it in the charter. The goal is to avoid unowned assumptions at synthesis.

Resource realistically. Use the charter to assign hours where impact is highest. If a killer variable sits in pricing power, put your strongest analyst there and pre‑approve spend for invoice pulls or external datasets. If access is thin, shift effort to expert calls and channel checks and record the confidence downgrade in the charter.

Below is a concise, fill‑ready example of a “Definition of Done” you can insert at the end of any charter.

Definition of Done (insert at section 24 of every charter)

Each killer variable tested with two independent methods or sources.
Market sized with both bottom‑up and top‑down methods, variance reconciled.
Pricing realization reconstructed or bounded within a justified range.
Retention math (GRR/NRR) verified against defined cohorts and formulas.
Competitive share estimated with at least two triangulations.
Driver‑based model updated; sensitivity ranges shown and footnoted.
Interfaces cleared; QofE/legal/tech/ops answers received or flagged with owner and date.
All exhibits footnoted; data book updated with sources, interview guides, and model documentation.
Clean‑team and MNPI rules followed; compliance memo attached.
Workstream owner and CDD lead have signed off.

Common pitfalls are predictable. Charters that read like to‑do lists rather than decision tools, vague hypotheses that cannot be falsified, undefined second methods, or missing acceptance criteria all slow you down. Resist the urge to be comprehensive; be decisive. If a field does not help you prove or break the thesis, leave it out.

Finally, treat charters as living documents. Update confidence weekly, record what changed and why, and roll those updates into your synthesis. A strong charter turns a complex diligence into a sequence of clear promises kept: the right questions, answered the right way, at the right time.

Commercial Due Diligence Playbook >