axelerant.
← The play
Workstream two

Organic posts

Three posts from Sachin's handle, drawn from the language of the two POV pieces rather than written separately. The audience attending is corporate development and CEOs, so the posts run on the deal-side argument: the estate as an unpriced liability, not a systems project.

WED 15 OCTBOOST THIS ONE

Post 1 · the deal model

Straight from the deal-side POV. The argument a corp dev person can check against their last deal

Copy

Your deal model counts revenue, headcount, EBITDA and the synergies you expect to realize.

It does not count the estate.

Every company you acquire arrives with a second set of everything. Another website on another platform, another content system, another commerce stack, another set of customer records, another set of reporting definitions. None of it appears in the LOI. All of it arrives on day one.

Most of it gets treated as an IT matter, handled after close, by people who were not in the deal. That framing is the expensive part, because it moves a priceable cost into the one period where nobody is looking for it.

I'm at M&A East in Philadelphia next week. If you're acquiring at pace and this keeps landing in month four rather than diligence, find me.

Why it works

Opens inside their vocabulary, not ours. "It does not count the estate" is the line people will quote back. Target A1 and A2 for the boost.

FRI 17 OCTNO BOOST

Post 2 · the seven questions

The takeaway artifact from the deal-side POV, used as the invitation

Copy

Philadelphia next week for M&A East.

Seven questions I'd ask about a target's digital estate before signing, none of which the data room answers and none of which need a technologist to ask:

How many content platforms, and who maintains each?
What happens to their domains and search equity if the brand is retired?
How many storefronts, catalogues and pricing structures?
Has a CRM implementation been attempted here before, and what happened to it?
Is the ERP staying, and for how long?
Do their reporting definitions match ours?
What vendor contracts transfer, and when do they renew?

The fourth one is the one I'd put first. A clean answer means the integration is an engineering exercise. A messy one means you're buying a trust problem as well as a technical one.

Oct 20 and 21. Happy to walk through any of these for twenty minutes, no pitch.

Why it works

Gives the whole artifact away. Saveable, forwardable, and it qualifies anyone who replies about a specific question.

FRI 24 OCTBOOST THIS ONE

Post 3 · the synthesis

Highest-value post of the three, and the one most people skip

Skeleton

Two days in Philadelphia asking operators and sponsors the same question: you bought the companies, what are you running them on?

[Pattern 1, with the specific detail that makes it credible.]
[Pattern 2.]
[Pattern 3, ideally something that contradicted what I expected.]

The thing nobody said, which I found interesting: [the absence].

Write-up in the comments if useful.

Why it works

Material nobody else has, written after the feed has cleared. Target A3 plus A1. The third pattern should genuinely surprise, or leave it out.

Where the language comes from

The posts deliberately reuse phrases from the drafts so the whole play sounds like one argument.

"A second set of everything"

Opens both POV pieces and post 1. The most portable phrase we have.

"It does not count the estate"

The deal-side POV's opening move, and the line post 1 turns on.

The seven questions

The diligence checklist from the deal-side POV, given away whole in post 2.

What we dropped

An earlier post ran on vocabulary and definitions. Good argument, wrong audience: it speaks to people who own reporting, and the room is corp dev and CEOs. Keep it for the operator track.