Latest edition: 12 August 2026London — published continuously since 2026Free forever
The Founder Gazette
Startup news, held to newspaper standards
Founder comms

Answer one question and you have a comms strategy

A ghostwriter who has drafted for founders says most of them freeze at the same point: they think they need to be vulnerable or contrarian, when all they need is a reason they started.

By The Gazette desk12 August 202666

Kristen Lowe writes for founders for a living. She says the most common reason they hire her is not that they hate writing.

It is that, in her words, "I have no idea what to say."

Lowe is an executive ghostwriter and narrative strategist, the incoming Director of Founder & Editorial Communications at Scribe, and a former Director of Operations at Hinge. Her argument, published in Lenny's Newsletter, is that founder communications need one input: an answer to why you started the company.

She sorts those answers into three archetypes. The Problem founder solved a problem that was hurting them personally. The Insight founder saw a problem others had missed. The Vision founder imagined a different world.

The point of the sorting is not the label. It is that each archetype produces a different feeling in the audience: I identify with you, I trust you, I'd follow you. Lowe says the story makes the content interesting, but the archetype decides which of those three you are actually building.

From there, she says, four decisions follow: the goal of the content, the voice, the subjects you return to, and how you will know it is working.

She is blunt about what the archetype does not answer. Posting frequency does not matter much, on her account: the best comms routine is the one you will keep, and audience segmentation, attribution and the earned-versus-organic split can wait until there is a body of work to optimise.

The Problem founder gets the fullest treatment. Lowe cites Sara Blakely cutting the feet off her pantyhose and starting Spanx, and Tobi L\u00fctke building Shopify after the existing software frustrated his snowboard business.

The framing instruction is specific. A Problem founder's origin story cannot sound like "existing options weren't working for me"; it has to sound like "I was crying in my car during lunch." Scene-level detail, repeated across channels, is what makes a stranger feel recognised.

She names three ways it goes wrong. Overgeneralising the problem until anyone could claim it. Sliding into CEO voice, talking about market gaps and competitor shortcomings instead of your own experience. And oversharing past the story, which spends your privacy without bringing anyone nearer the business.

On channels, Lowe puts Problem founders on social media, podcasts and profile pieces, and suggests securing one conversation-style speaking slot long enough to tell the story properly, then cutting it up for everything else. X, she says, is usually not the place for the storytelling.

Her test for whether it is working is worth stealing whatever your archetype. Not follower counts: whether customers reply with their own version of the problem instead of writing "great post!"

For a founder with no budget and no press contacts, the practical read is that the expensive part of this is not distribution. It is sitting down and answering, in scene-level detail, what the worst day with your problem actually looked like.

I have no idea what to say.
The most common reason founders hire her, according to ghostwriter Kristen Lowe