M&A Readiness No. 01 · Maps · Teel & Company®

SYNOPSIS

Each Map renders one structural condition the Series argument develops—the stakeholders looking at the enterprise, the failure catalog diligence writes when capabilities are not built, the dashboard-versus-structure contrast, the cost-of-delay trajectory across preparation horizons, the capability compounding that cannot be shortcut, the founder-to-enterprise translation, and the surface area each operating model occupies inside the enterprise. Read alongside the Fieldwork Slides edition and Field Notes.

Map · No. 01-A · The Stakeholder Lens

Teel & Company Map · No. 01-A Issued · May 2026

Stakeholder perspectives

The same enterprise, five lenses

Five stakeholders looking at the same enterprise see five different enterprises. The contrast is the diligence gap—what the leader sees as growth, the buyer sees as risk; what feels coherent inside is read as fragile under examination.

The contrast is the insight

An enterprise has no single vantage. What gets discounted at diligence is the gap between how leadership reads its own institution and how buyers, boards, and senior employees read it.

Lens 1

Founder

What the founder sees inside their own enterprise.

• Revenue and margin moving in the right direction

• Team performing; key customers stable

• Personal relationships are the firm's strength

• Operational decisions handled in real time

“We're approaching milestone. The growth story is intact.”

Lens 2

CFO & finance

What the senior finance officer sees in the close cycle.

• Month-end discipline still inconsistent

• Revenue recognition treatment unsettled in places

• Customer concentration showing in the numbers

• Reporting infrastructure two upgrades behind

“We need two more years of clean reporting before anyone audits this.”

Lens 3

Board

What the Board sees in oversight materials and meetings.

• Trajectory directionally right; verification thin

• Founder concentration is the named risk

• Succession architecture not visible

• Strategic options being scoped—readiness uncertain

“How ready, structurally, are we—really?”

Lens 4

Buyer

What the acquirer sees during diligence examination.

• Single point of failure: the founder

• Customer relationships not transferable

• Reporting inconsistencies surface quickly

• Talent retention through transition unverified

“What survives without the founder?”

Lens 5

Senior employees

What the second-tier leadership sees from inside operations.

• Critical decisions still escalated to founder

• Authority boundaries informal and shifting

• Customer relationships belong to founder

• Process documentation thin or absent

“We work hard. The founder still drives the calls that matter.”

See Fieldwork Slides Part One · See Field Note No. 01-A

Map · No. 01-B · The Inversion Map

Teel & Company Map · No. 01-B Issued · May 2026

Inversion—the failure catalog

What “not building” specifically looks like

The deck argues for building. This Map inverts: when each horizon's capabilities are not built, these specific failures surface at diligence. The catalog is not theoretical—each item is what a buyer's diligence team writes in the report.

Foundation absent

When the institution is not designed

No organizational architecture, no financial systems, no decision framework.

Diligence finds

Org chart with one node. Founder is operationally everywhere; no second tier with real authority.

Chart of accounts that cannot reconcile. Reporting changes month to month; comparability across years impossible.

Decision rights undefined. Every material decision escalates; bottleneck is structural.

Strategic posture inconsistent. Public narrative and operating reality diverge under questioning.

“There is no enterprise to acquire—only the founder.”

Maturity absent

When systems do not yet operate

Foundation in place, but reporting cadence, audit history, and second-tier capacity not built.

Diligence finds

Monthly reporting unreliable. Numbers change after the fact; close discipline absent.

No audit history. Three years of audited statements unavailable; comfort level low.

Process integration thin. Functions operate in silos; cross-functional coordination is founder-mediated.

Talent depth missing. Function leaders cannot run their functions independently.

“The institution exists but does not operate institutionally.”

Diligence prep absent

When the structure has not been examined

Capabilities partly in place, but never tested under examination conditions.

Diligence finds

Records not audit-ready. Documentation gaps surface across financial, customer, and operational records.

Customer concentration unmeasured. Concentration risk known to leadership but never analyzed or disclosed.

Controls undocumented. Internal controls exist informally; cannot demonstrate to a third party.

Management retention unaddressed. Key talent flight risk through transaction not mitigated.

“Preparation is a project the institution did not start.”

Transaction posture absent

When the close is approached unprepared

Diligence prep capabilities partly in place, but transaction execution not coordinated.

Diligence finds

Data room incomplete. Information requests met with delays; trust degrades during examination period.

Q-of-E surprises. Quality-of-earnings analysis surfaces adjustments leadership did not anticipate.

Negotiation positioning weak. Without preparation, leadership negotiates from incomplete information.

Execution coordination ad hoc. Bankers, lawyers, and management not aligned; deal velocity slow, errors compound.

“The transaction reveals the work that was not done.”

See Fieldwork Slides Part One · See Field Note No. 01-A

Map · No. 01-C · Visible / Invisible Architecture

Teel & Company Map · No. 01-C Issued · May 2026

Visible / invisible architecture

What you see—and what diligence sees

Operational visibility and diligence visibility are not the same. The leader's dashboard renders confidence; diligence renders structure. The same enterprise reads as healthy from above and fragile from below.

What leadership sees daily

The operational dashboard

Revenue

+24% YoY

Top line growing on plan; Q4 targets in reach.

EBITDA margin

18.2%

Margin holding through expansion phase.

Customer count

142 +18

New logos added;
net retention strong.

Headcount

87 +12

Hiring on plan;
key roles filled.

Cash position

$8.4M

Runway healthy; no near-term financing needed.

The dashboard renders the enterprise from above—diligence reads it from below.

What diligence surfaces

The structural reading

Founder
concentration

Single point of failure

Operating decisions, customer relationships, and institutional memory all run through one person. The growth metric is the founder's signature, not the enterprise's.

Customer
concentration

Top three = 47% of revenue

Behind the customer count number, three relationships carry the firm. Each is held in the founder. None has been tested for survival of transition.

Reporting
depth

Margin not reproducible at audit

EBITDA presented monthly does not reconcile to year-end financials. Adjustments are personal judgment, not documented method. Q-of-E will compress the number.

Talent
fragility

Second tier underbuilt

Headcount counts heads. The structural question is which heads can decide, which can run a function alone, which the institution would survive losing. Most cannot.

Cash
quality

Working capital under-managed

Cash position reflects timing, not structure. Days-sales-outstanding lengthening; receivables concentration mirrors customer concentration; the runway number is fragile to working capital normalization.

See Fieldwork Slides Part Four · See Field Note No. 01-C

Simulated midmarket enterprise case data used for demonstration purposes.

Map · No. 01-D · The Cost-of-Delay Trajectory

Teel & Company Map · No. 01-D Issued · May 2026

Cost-of-delay trajectory

The compound cost of waiting

Three preparation postures, three valuation outcomes. The discount at transaction is not what the leader paid in months before the close—it is what the leader did not build in the years before that.

Posture A
Build throughout

Foundation begun 5+ years before transaction

With capabilities placed at each horizon over years, diligence finds an enterprise that holds together; transaction posture sits as a thin overlay on coherent build, and valuation reflects what was built.

Posture B
Build 2–3 years before

Foundation begun late; Maturity capabilities accelerated

With institutional architecture partly in place but multi-year reporting history thin, diligence finds partial coherence—and valuation reflects what was built, with discounts for what was not.

Posture C
Prepare 12 months before

Foundation absent; Maturity skipped; preparation activities only

Where the institutional architecture was never built, diligence finds the absence: the data room is organized but the underlying structure is not, and compression of valuation is severe and structural.

Schematic; not to scale.

See Fieldwork Slides Part Five · See Field Note No. 01-D

Map · No. 01-E · The Capability Compounding Tree

Teel & Company Map · No. 01-E Issued · May 2026

Capability dependencies

What enables what—the capability compounding tree

Capabilities at each horizon enable the capabilities at the next. The dependencies cannot be shortcut: late preparation cannot succeed because the chain must be built in order.

→ Time progresses; capabilities compound. →

Heavy red lines mark the critical path. Foundation gaps surface as Diligence-stage failures four to five years later.

See Fieldwork Slides Part Five · See Field Note No. 01-D

Map · No. 01-F · The Founder-to-Enterprise Translation

Teel & Company Map · No. 01-F Issued · May 2026

The translation

From founder to enterprise—the translation map

The structural project of building toward liquidity is the translation of what is held in the founder into what is held in the enterprise. Some translations are mechanical; some require years of deliberate construction. The difficulty rating is the structural project.

Held in the founder

Carried in one person's accumulated capacity

Translation

Held in the enterprise

Carried in systems, roles, and documented standards

Operating standards

“How we do things here” lives in the founder's accumulated judgment and direct example.

Mechanical

Documented operating systems

Process documentation, SOPs, training materials, decision rights matrices.

Financial control

Founder approves the close, signs the major checks, holds the cash judgment.

Mechanical

CFO function & controls

Independent close discipline, audit-ready records, documented controls, treasury function.

Decision flow

Critical decisions escalate to the founder—the bottleneck and the assurance both.

Structural

Distributed decision architecture

Decision rights documented; second-tier authority real; the founder in strategic decisions only.

Enterprise memory

The founder remembers why decisions were made, which customers matter, where the bodies are buried.

Structural

Documented enterprise record

Decision logs, customer histories, enterprise retrospectives, codified strategic rationale.

Talent leverage

The team performs because the founder leads and corrects in real time.

Years of work

Second-tier enterprise capacity

Function leaders who can run their function without founder intervention; decision capacity at the second tier.

Customer relationships

The founder is the relationship. Customers stay because of trust in the person.

Years of work

Enterprise-held customer relationships

Customers know multiple firm contacts; trust transferred to the enterprise; relationships survive transition.

See Fieldwork Slides Part Seven · See Field Note No. 01-E

Map · No. 01-G · Operating Model Surface Area

Teel & Company Map · No. 01-G Issued · May 2026

Operating models

Where the advisor operates—the surface area

Four operating models, four structural relationships to the enterprise. The distinction is not value or fee—it is the surface area of the advisor's presence inside the enterprise.

Model 1

Advisor

Periodic counsel from outside the organization.

Touchpoints from outside

PositionExternal to organization

CadenceEvent-driven; on request

AuthorityCounsel only; no operational role

SurfaceDiscrete touchpoints

Model 2

Consultant

Project-based engagement on defined scope.

Defined scope, bounded duration

PositionAdjacent; project-based

CadenceTime-bounded engagement

AuthorityWithin scope; deliverable-defined

SurfaceOne function, one engagement window

Model 3

Fractional executive

Part-time leadership of a
single function.

One function, fractional time

PositionInside one function

CadenceRecurring; part-time

AuthorityFunctional; no cross-function role

SurfaceOne function only; partial presence

Model 4

Operational accountability

Continuous interior leadership and operational presence across function categories.

Full interior; minimum twelve months

PositionInside the organization, continuously

CadenceDaily; continuous

AuthorityOperational; corporate-focused scope

SurfaceFinance, HR, Operations, Administration

See Fieldwork Slides Part Seven · See Field Note No. 01-F

M&A READINESS NO. 1: BUILDING THE ENTERPRISE THAT PASSES DILIGENCE

Building the Enterprise That Passes Diligence

Series 01 of the M&A Readiness Topic. Twelve Fieldwork Slides, seven Maps, and six Field Notes developing the structural conditions diligence reads.

M&A READINESS NO. 1 →

M&A READINESS NO. 1: BUILDING THE ENTERPRISE THAT PASSES DILIGENCE

Fieldwork Slides No. 01

Twelve slides developing the Series argument from the reader and the moment through the seat at the principal’s table.

FIELDWORK SLIDES NO.1 →

M&A READINESS NO. 1: BUILDING THE ENTERPRISE THAT PASSES DILIGENCE

Field Notes No. 01

Six concentrated structural arguments that extend Fieldwork Slides No. 1, examining enterprise value building processes.

FIELD NOTES →

INTRODUCTION

For enterprise leaders who recognize these structural conditions in their own enterprise, an introduction is the way in.

The firm does not respond to general inquiries. The introduction process is structured: a written exchange that establishes whether an operating relationship fits before any conversation occurs.

BEGIN AN INTRODUCTION

EST. 2017 · CHICAGO, ILLINOIS

Maps

The same enterprise, five lenses

Founder

CFO & finance

Board

Buyer

Senior employees

What “not building” specifically looks like

When the institution is not designed

When systems do not yet operate

When the structure has not been examined

When the close is approached unprepared

What you see—and what diligence sees

Single point of failure

Top three = 47% of revenue

Margin not reproducible at audit

Second tier underbuilt

Working capital under-managed

The compound cost of waiting

Foundation begun 5+ years before transaction

Foundation begun late; Maturity capabilities accelerated

Foundation absent; Maturity skipped; preparation activities only

What enables what—the capability compounding tree

From founder to enterprise—the translation map

Where the advisor operates—the surface area

Advisor

Consultant

Fractional executive

Operational accountability

Other places to read

Building the Enterprise That Passes Diligence

Fieldwork Slides No. 01

Field Notes No. 01

For enterprise leaders who recognize these structural conditions in their own enterprise, an introduction is the way in.