How to Write a Press Release in 60 Minutes: The Solo Founder's Five-Block Scaffold

A first-time solo founder can write a press release that journalists will quote and AI engines will cite in 60 minutes by following a fixed five-block scaffold: a 5W lede, three supporting facts, one real quote, a schema-aware boilerplate, and a short distribution list. The trick is not better prose. It is a hard timebox that forces you to skip the parts no reporter reads and no language model surfaces.

The 60-minute timebox: what to write, what to drop

A first release does not need to be perfect. It needs to be quotable. A timebox forces that.

Five blocks every release needs, and nothing more:

1. The lede — a 30-40 word 5W paragraph stating the news.
2. Three facts — a number, a comparison, a customer name.
3. One quote — one named spokesperson, written from spoken voice.
4. The boilerplate — a short company description that maps onto structured data.
5. The contact — one human's email, not "press@".

What to consciously cut on a first release: marketing copy, founder biography, product roadmap, vision statement, and the "we are excited" preamble. None of these get quoted. None of these get cited. They cost you minutes you do not have.

The deliverable at the end of the hour is one document a reporter can quote and an AI engine can extract. Treat it as a structured artifact, not an essay.

Minute 0-15: the 5W lede that doubles as an AI citation snippet

The first paragraph carries 80% of the work. The AP Stylebook — the formatting baseline reporters at AP, Reuters, and Bloomberg work from — defines the lede as a single sentence answering who, what, when, where, and why. Compress that into 30-40 words and you get a snippet that doubles as the answer-text Perplexity, ChatGPT, and Google AI Overviews extract.

Answer-first construction is not a stylistic preference. Generative search engines pull the first informational sentence as the citation. If the first sentence is "We are thrilled to announce," that is what gets surfaced — and that is what gets discarded.

Before: "We are excited to announce that our company has reached an important milestone in our journey to transform the way teams work."

After: "Acme Robotics, a Boston-based seed-stage startup, on April 30 launched Acme Pilot, a $99/month service that lets warehouse operators deploy autonomous forklifts in under 48 hours, with five paying pilots already live."

Thirty-six words. It tells a reporter the headline. It tells an AI engine the entities, dates, dollar values, and verifiable claims.

Headline rule: state the news, not the emotion. "Acme Robotics launches 48-hour forklift deployment service" beats "Acme Robotics is thrilled to revolutionize warehouse automation."

Minute 15-30: three supporting facts and one quote that sounds like a person

Three concrete data points beat ten generic claims. Reporters skim. Journalists report rejecting outreach that exceeds about 200 words, so density matters more than length.

Pick three facts that fit this template:

• One number. "Five paying pilots" or "$1.2M ARR" or "200 warehouses across three states." Specific. Verifiable.
• One comparison. "Cuts deployment from six weeks to 48 hours." Reporters need the so-what.
• One customer name. Real. Public. With permission. "Pilot customer DHL Northeast" earns more credibility than "a Fortune 500 logistics company."

Then write one quote. One. From one named person. Use spoken voice — say it out loud first.

Press-release-speak (do not write this): "We are excited to leverage our innovative platform to empower the next generation of warehouse automation at scale."

Spoken voice (write this): "We built Pilot because every warehouse operator we talked to said the same thing: the robots work, the deployment doesn't. We fixed the deployment."

A solo founder writing their own quote should not sound self-promotional, because a real founder talking about a real problem does not sound self-promotional. They sound like someone explaining why they built the thing.

Reporters and AI engines need overlapping but not identical things from this block. Reporters need a quotable sentence. AI engines need attributable claims with named entities. The three-fact-plus-quote structure satisfies both.

Minute 30-45: the boilerplate as structured data, not a paragraph

The boilerplate is the part everyone copies from the last release and forgets to update. It should not be prose first. It should be structured data first, written out as prose second.

Every boilerplate field maps one-to-one onto schema.org Organization properties: name, foundingDate, founder, headquarters (mapped to address), url, and numberOfEmployees. The schema.org PressRelease type is a dedicated subtype of NewsArticle, telling crawlers that a document is official corporate communication. Google's structured data guidance for Article and NewsArticle spells out the exact properties — headline, datePublished, author, publisher, image — that determine whether a release is eligible for AI Overviews and rich result surfaces.

Princeton's GEO research found that adding citations, quotations, and statistics to source content raises the likelihood of being cited by generative search engines by roughly 30 to 40 percent. Structured data is the machine-readable version of that same signal.

Sample prose boilerplate:

Acme Robotics, founded in 2024, builds autonomous forklift deployment software for mid-market warehouses. The company is headquartered in Boston and was founded by Jane Doe and John Roe. More at acme.example.

Same content as JSON-LD twin, embedded in the release page <head>:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Robotics",
  "foundingDate": "2024",
  "founder": [
    {"@type": "Person", "name": "Jane Doe"},
    {"@type": "Person", "name": "John Roe"}
  ],
  "address": {"@type": "PostalAddress", "addressLocality": "Boston"},
  "url": "https://acme.example"
}

Both versions live on the page. The prose version is for the reporter who copies it. The JSON-LD is for the LLM crawler that resolves the entity.

Minute 45-60: the solo-founder distribution starter list

Skip the paid wire on a first release. A founder without a comms budget gets more out of five named journalists who cover the beat than out of a $400 syndication.

Self-host the release first. The canonical version lives on a URL you control — acme.example/press/pilot-launch. That is the page AI crawlers resolve to and cite. If the release exists only on a third-party wire, you have given up the canonical record.

Five free channels worth using on a first release: your own newsroom URL on your domain, your founder LinkedIn (with the canonical URL linked), one niche industry aggregator (Hacker News, IndieHackers, a vertical Substack), direct email to five named reporters who cover the beat, and a single post linking to the canonical URL.

A 5-name distribution starter list, scoped to a B2B SaaS founder pitching enterprise reporters:

1. The TechCrunch reporter who wrote about your closest comparable startup last quarter.
2. The Axios Pro newsletter writer in your vertical.
3. A senior writer at The Information covering your category.
4. A trade-publication reporter in the industry your customers operate in.
5. An independent newsletter writer (Substack, Beehiiv) with 5,000+ engaged subscribers in your niche.

Each name should come with a one-sentence rationale: "X wrote the warehouse-automation roundup last month." The note is for you, but it also forces honesty — if you cannot write the rationale, the name does not belong on the list.

Skip the rest. Paid wires, embargo strategy, multi-region distribution: all of these matter at release ten, not release one.

After minute 60: three checks before you hit send

Three checks before you publish. Each takes under 60 seconds.

1. Read the lede aloud. If it does not stand alone as a tweet, rewrite it. The lede is the only part 80% of readers — and 100% of AI engines — will read.
2. Verify every number and every link. A broken citation kills credibility for both the reporter who quotes it and the AI engine that crawls it.
3. Cross-check the boilerplate against your live website. LLMs cross-reference. If your release says "founded 2024" and your About page says "founded 2023," neither version gets cited.

Sixty minutes. Five blocks. One canonical URL. That is enough for a first release.

If you want a tool that scaffolds the 5W lede and writes the schema.org Organization JSON-LD for you, start a release — or walk through the founder onboarding flow for a worked example before drafting your own.