How Solo Founders Can Do PR Without an Agency

Solo founders can do useful PR without an agency, but only if they stop treating PR as a burst of inspiration before launch day.

The work needs a small operating system. One defensible hook. A short list of reporters who are current on the subject. A pitch that a founder can stand behind. A follow-up rhythm that respects the inbox. A simple record of what happened.

RunPR publishes this guide, so it is vendor-owned advice. We build software for monitoring, journalist matching, drafting, approvals, outreach, and coverage tracking. The process below also works manually if you are not ready for a tool. The point is to give a founder a repeatable way to work, not to pretend software creates news.

Start With One Defensible Hook

Most founder-led PR fails before the first email because the founder starts with the company instead of the story.

"We launched a new product" is usually not enough. "We raised money" can be news, but only for a narrow set of outlets and only if the funding, investors, market timing, or company evidence makes it relevant. "We have a better way to do X" needs proof before it becomes a pitch.

A defensible hook has three parts:

1. a real change that happened or is happening now
2. a specific group of people affected by the change
3. evidence that your company can speak credibly about it

Examples of the shape, not fabricated case studies:

• a new regulation changes how small businesses handle a compliance task, and your product serves those operators
• a platform policy shift creates a measurable cost for teams in your category, and your data shows the pattern
• a competitor move reveals a market tension, and your founder can explain what buyers are missing
• a customer behavior shift appears across your usage data, and you can share the aggregate pattern without exposing private data

If you cannot name the change, the affected reader, and the evidence, pause. You may have marketing copy, but you do not yet have a PR hook.

Build a Small Reporter Cohort

A solo founder does not need a list of 300 journalists. That list will become a guilt document. You need a cohort of five to fifteen people whose recent work shows a reason to care.

Start with the story neighborhood. Write down the subjects that overlap with the hook. A hiring software founder might list labor market data, HR technology, recruiting operations, workplace regulation, and startup productivity. Each subject produces different reporters and different angles.

Then search recent coverage. Use publication sites, Google News, trade newsletters, podcast episode pages, and competitor coverage. Start from bylines, not database labels. For every promising journalist, open their author page and read several recent pieces.

Keep only reporters with visible evidence of current fit:

• Primary fit: they have covered the exact topic or a very close neighbor in the past 90 days
• Adjacent fit: they cover the audience or consequence, but not the exact angle
• Relationship fit: you have a legitimate prior interaction and the story fits their current lane

Everyone else waits. A founder's advantage is not volume. It is proximity to the facts and the ability to explain why this story matters right now.

For a deeper version of this research process, use the beat-mapping approach in how to find journalists covering your industry. If you are starting from zero tools, the manual approach in how to pitch a journalist without a media list pairs well with this system.

Research Recent Bylines Before Writing

Do not personalize from a bio alone. A bio can lag the real beat by months. Recent bylines show what the journalist is actually doing.

For each reporter in the cohort, capture a short fit note:

• current outlet and author page
• two recent articles that support the fit
• the pattern you see in their coverage
• the sentence that connects your hook to their readers
• any public pitching preference
• the date you checked it

The fit note should be plain enough that you can judge it the next morning. "Covers fintech" is weak. "Has written three recent pieces about how payroll, tax, and compliance work are moving from back-office software into founder workflows" is useful.

This note also protects you from forcing the pitch. If the bridge sounds strained in your own document, it will sound worse in the journalist's inbox.

Draft the Pitch in Three Moves

A founder pitch should sound like a person who knows the work, not a press release pretending to be an email.

Use three moves:

1. The hook: one or two sentences naming the current change and why it matters to the reporter's readers.
2. The proof: one short paragraph with the evidence, product context, data point, or operator view that makes you credible.
3. The ask: one clear next step, such as offering a short conversation, a data point, a source comment, or early access to a relevant report.

Keep the first send short. Avoid attachments unless the reporter asked for them or the format requires them. If you have a press release, link it only when it helps. The email still has to earn attention on its own.

Write one base pitch, then adapt it by cohort. The business reporter may care about market timing. The trade reporter may care about the operational pain. The technical reporter may care about what changed in the system. Those are different pitches, not synonyms.

Approve Your Own Work Like an Operator

Solo founders still need approval. The reviewer may be you, but the step matters because it creates a pause between excitement and sending.

Before any pitch goes out, run this check:

• Is the hook true without adjectives?
• Can I show the evidence if the reporter asks?
• Does the first sentence explain why this matters now?
• Does the pitch reflect the reporter's recent work?
• Is the ask specific and low-friction?
• Would I be comfortable seeing this quoted back to me?
• Have I removed claims that depend on private customer information or unapproved results?

If you have a cofounder, advisor, or communications contractor, route the pitch to them for a fast review. If you do not, sleep on anything high-stakes. A pitch sent one day later is usually better than a sloppy pitch sent while the founder is charged up.

Follow Up Without Turning Into Noise

A founder can follow up. The mistake is treating silence as permission to keep nudging.

Wait three to five business days after the first email. Send one short follow-up that either adds useful context or cleanly restates the reason the story may fit. If there is a genuine update, include it. If there is not, do not invent one.

One more follow-up after another week is enough for most founder-led outreach. After that, stop the thread and move the learning back into the system:

• Was the hook too company-centered?
• Was the cohort too broad?
• Did the reporter's recent work support the pitch?
• Did the subject line make the news clear?
• Was the timing wrong?

The goal is not to win every inbox. It is to improve the next cohort and preserve the relationship for a better story.

Track Coverage and Non-Coverage

Coverage tracking is not just a victory folder. It is how a founder learns what the market is willing to repeat.

Use a simple sheet or product record with:

• story hook
• reporter and outlet
• source bylines used for fit
• pitch date
• follow-up dates
• reply status
• coverage URL if it lands
• message that appeared in the coverage
• next action

Also track useful non-coverage. A polite pass, a correction about the beat, a referral to another reporter, or a request to come back with data is valuable. Those signals tell you how to adjust the story before the next cycle.

For reporting and coverage classification, the framework in software to track media coverage and press mentions helps separate strategic coverage from clip counting.

A 30-Day Founder PR Cadence

This cadence assumes the founder can spend three to five focused hours per week. If you have less time, shrink the cohort rather than skipping research.

Days 1 to 3: Choose the hook

Write three possible hooks. For each one, name the current change, affected reader, and evidence. Pick the one with the clearest proof and most timely reason to exist.

Output: one-sentence story, three proof points, and a list of source material you can share or summarize.

Days 4 to 7: Build the cohort

Search recent coverage and build a list of ten to twenty possible journalists. Read recent bylines and reduce it to five to fifteen credible targets. Group them by angle.

Output: reporter cohort with fit notes, source URLs, and confidence level.

Days 8 to 10: Draft and review

Write the base pitch and one version for each cohort. Run the approval checklist. Remove vague claims, unsupported adjectives, and anything you could not defend on a call.

Output: final pitch variants and one approved ask.

Days 11 to 14: Send the first cohort

Send to the strongest five targets first. Space the sends if you need time to handle replies well. Record each send immediately.

Output: sent record with pitch, target, and reason for fit.

Days 15 to 20: Follow up and listen

Follow up once where appropriate. Watch replies, opens if you track them, and any signal that the angle is landing or missing. Do not expand the campaign until you have reviewed the first cohort.

Output: reply notes, follow-up record, and angle adjustments.

Days 21 to 25: Expand or revise

If the first cohort showed promise, send the next group with a refined angle. If it did not, revise the hook or wait for a stronger proof point.

Output: second cohort decision and updated pitch.

Days 26 to 30: Report and decide

Summarize what happened. Include coverage, replies, useful passes, stale contacts, and what the next story should be. Decide whether this system is sustainable for another month.

Output: one-page PR operating review.

The Decision Framework

At the end of the month, make a direct decision.

Keep doing PR yourself if you can identify one credible hook per month, build a small current cohort, write without overclaiming, and respond to journalists quickly.

Use software if the work is sound but too manual. The right tool should reduce the time spent monitoring, checking bylines, drafting, routing approval, sending, and tracking outcomes. It should not pressure you into larger sends.

Hire a specialist contractor if the story is strong but you need sharper positioning, launch planning, or experienced review before high-stakes outreach.

Hire an agency if PR has become a continuous program, the company has multiple storylines, executives need media prep, crisis risk is real, or you need relationships and strategy beyond what a founder can operate in a few hours a week.

Do not pitch yet if you cannot defend the hook, cannot show evidence, or need customer proof you do not have permission to use.

Where RunPR Fits

RunPR helps when the founder has real stories but lacks the workflow to run them consistently. The product monitors for relevant signals, matches reporters using beat and recent byline context, drafts pitches, holds them for human approval, sends from a verified domain, and tracks delivery, opens, bounces, coverage, and AI visibility.

It is not a substitute for having something worth saying. It is also not the right first purchase if you only need a broad enterprise media database or a full-service agency to create the PR strategy for you.

For a founder-led team, the useful question is simple: can you operate the 30-day cadence above without dropping research, approval, or follow-up? If yes, keep it lightweight. If the workflow is what breaks, RunPR can give the system a place to live. For tool evaluation, read the journalist database and outreach buyer's guide, or compare broader categories in the startup PR software guide.