An executive LinkedIn series, and a podcast episode adapted into an article

Format sample, added 7 Nov 2026. Written to cover the two formats the other samples do not: executive LinkedIn posts, and content adapted from an interview or podcast.

The portfolio already had the two long formats (articles, an investment-committee memo). It did not have these two: a short-form executive LinkedIn series and a podcast-to-article adaptation. This file supplies both, plus the production system that makes a 26-episode season of the second one survivable.

Provenance, before anything else

The executive in Part A and the speaker in Part B are fictional, and the firm, the portfolio and the track record are invented to demonstrate voice and format. Nothing here describes a real fund, a real executive, a real podcast or a real transaction. No client names, no attributable quotes, no borrowed statistics. Where a real number appears it is public and correct; nothing is dressed up as proprietary data.

This is how I would work a real engagement: the principal's own words, their own numbers, their own review before anything publishes. Nothing goes out under a name it does not belong to.

Part A: executive LinkedIn series

Client situation this is written for: a fund principal who has an opinion about deal discipline and no time to write. Four posts, published over six weeks, each able to stand alone in a feed and each advancing one argument. Cadence matters more than length: four posts a quarter beats one essay a year, because the feed rewards consistency and the principal's network reads in fragments.

Voice notes held throughout: first person, no jargon where a plain word exists, one idea per post, a specific number or instance in the first three lines, and the last line lands rather than summarises. No hashtag stacks, no "thoughts?", no engagement bait.

Post 1 — the one that sets the position

We looked at sixteen AI data-centre opportunities in eighteen months and committed to two.

Our investment committee asks me the same question every quarter, in a slightly different tone each time: are we being disciplined, or are we being slow?

Both, probably in that order. I am not neutral on the subject.

The short version of why fourteen of them are not in the portfolio: we stopped underwriting a contract and started underwriting a counterparty. A fifteen-year take-or-pay agreement with a customer whose balance sheet is smaller than the contract is not revenue. It is an option the customer holds and we have paid for.

That single change in how we read a term sheet cost us deals. It also kept us out of three I would have had to explain.

Post 2 — the operational one

I have never seen a data-centre deal go late because the building was late. I have seen several go late because the utility was late.

This is the part of the asset class that everyone claims to understand and almost nobody prices. Construction is a contract with a party you have leverage over. Energisation is a queue you are standing in behind strangers.

So when a developer shows me a schedule, I ask one question: what happens to debt service if power arrives two quarters after the building is ready?

If the answer requires the borrower to fund a gap it has no liquidity for, we are out, and we are out early rather than at the end of diligence. The cheapest thing we do all year is decline in week two.

Post 3 — the one that invites a conversation

An acceptance test is the only place in these documents where an engineering claim becomes money.

Throughput, sustained performance, error rate, burn-in duration, who witnesses it, and what happens when it fails. That is the whole game, and it is usually four pages of an appendix that nobody reads until something goes wrong.

Twice now I have read acceptance schedules that could not fail. Once because the vendor's own engineering team wrote it. Once because it tested a configuration nobody would run in production. Both times the borrower said it would never be enforced that way.

If the milestone cannot convert a failed test into a payment holiday, it is decoration. I have started asking to see the test script before I read the model, which is not how anyone else runs a first meeting.

Post 4 — the concession that earns credibility

We are going to lose the next two deals to people who underwrite inference pricing more confidently than we do.

Contracted capacity is a business. Uncontracted capacity is a bet on a price with almost no reliable history, and every model I have seen assumes that price declines gently. Almost none of them test what happens if it declines faster than the debt amortises, or if utilisation plateaus while the power bill stays fixed.

I do not know where inference pricing lands. I am confident that limited partners did not hire us to find out with their capital.

So we size to the contracted revenue and treat the rest as upside we do not need. That makes our bids lower. I have made my peace with it, and I would rather explain a lost deal than a covenant breach.

Why this series works as a unit (for the client, not the feed): post 1 states a position a reader can disagree with, which is what makes a first post travel. Posts 2 and 3 are the evidence, so the position reads as earned rather than contrarian. Post 4 concedes something real, which is the only reliable way to make a principal sound like a person instead of a pitch. Each one is under 260 words so it survives a phone screen.

Part B: podcast episode adapted into a LinkedIn article

The client's stated need is 26 episodes in 2027 turned into LinkedIn articles. The work is not transcription and it is not summarising. It is deciding which forty seconds of a forty-minute conversation is the argument, then rebuilding it so it reads as writing rather than as speech.

B1. The raw material (as a transcript arrives)

Reconstruction of a spoken extract, written for this demonstration. Filler, false starts and repetition are kept because that is what real transcripts look like.

"So the thing that I keep coming back to, and I've said this to a few people and they sort of nod politely, is that we were underwriting the wrong document. For two years. We were underwriting the contract. And the contract looks great, it's fifteen years, it's take or pay, the coverage ratio is fine, you can put it in a slide. But the contract is a promise from a company. And the question is not what the company promised, it's what the company can do if it has a bad year. That's the actual question, and we weren't asking it, because the contract answered a different question really well. So, and I think this is true across the sector, not just for us, you have a whole industry pricing paper and calling it credit. I don't mean that as an insult to anyone, I mean it structurally, the term sheet is designed to be underwritable, that's its job, and the thing that actually determines whether you get paid is not in the term sheet. It's in the customer's liquidity and in whether the obligation survives the customer's insolvency. And nobody puts that on slide four."

What is in there: one argument (underwrite the counterparty, not the contract), one diagnostic (the term sheet is designed to be underwritable, which is why it hides the risk), one missing piece (the obligation surviving insolvency), and a line worth keeping verbatim ("pricing paper and calling it credit"). Also, roughly 180 words of throat-clearing.

B2. The article as published

What a fifteen-year contract actually promises

By [principal name], [title]

For two years we underwrote the wrong document.

The contract was not the problem. It was excellent: fifteen years, take-or-pay, coverage that looked comfortable on a slide. The problem was that we were treating a promise as a fact. A contract is a statement about what a company intends to do. The question underneath it is what that company can do in a bad year, and in most of the deals we saw, nobody had answered it, because nobody had been asked.

I do not think this is specific to us. It is structural. A term sheet is designed to be underwritable; that is its job, and it is good at it. It puts the negotiable things where a credit committee can see them: tenor, coverage, covenants, cure periods. The thing that actually decides whether you get paid is not in that document at all. It sits in the customer's liquidity, and in whether the obligation survives the customer's own insolvency.

Which means the honest summary of a lot of infrastructure credit is that we are pricing paper and calling it credit.

Two questions do most of the work once you start asking them. The first is whether the commitment is larger than the counterparty can honour. If it is, the long tenor is not protection, it is an option the customer holds and the lender has paid for. The second is what the obligation looks like after a restructuring: who the guarantor is, what the cure periods actually permit, and whose claims sit ahead of ours when the customer's own lenders arrive.

Neither question appears on the term sheet. Both change the answer.

[Principal name] is [title] at [firm]. This piece is adapted from an episode of [podcast], available [where].

B3. What the adaptation actually did

Time budget per episode: 45 minutes to read and mark the transcript, 60 minutes to draft, 20 minutes of edits after the principal's review. About two hours per piece once the voice map exists, which is why a 26-episode season is a scheduled pipeline rather than a series of favours.

Part C: how a 26-episode season runs

The reason this is a system and not a writing exercise: at 26 episodes, the constraint is not talent, it is turnaround and consistency. What the client supplies, and what comes back.

Two things that decide whether the season survives contact with a busy executive: the voice map is done once and reused, so the principal is not re-teaching their voice every fortnight, and the review is one pass in one place, so it costs them twelve minutes rather than an afternoon.

What this sample is, and is not

It is a demonstration of format and process: short-form executive voice, the transcript-to-article move, and the operating rhythm behind a content season. It is not a portfolio of published clips, and I would not present it as one.

The long-form equivalents (byline, analyst piece, investment-committee memo) are samples one to four on this site.