See how the pieces connect. Follow one fictional client, explore any chapter, and try the handoff for yourself.
Meet HarborLock, a fictional account-takeover response firm. Its expertise, evidence and voice give every next step a foundation.
Account-takeover response · Midsize employers
Leah Ortiz, response lead. Account recovery, help-desk verification and anonymized incident timelines.
HarborLock’s own April–June case review. Not an industry estimate.
Plainspoken. Journalist-first. Specific evidence.
One low-friction ask. No inflated claims.
Capture expertise, spokesperson knowledge and the facts your client can support.
Explore a chapter, or press play. No sound needed.
This interactive tour simplifies the workflow, rather than recreating every product screen.
Chapter 1: Client contextThese are captures of shipped RunPR components with the same fictional HarborLock scenario. Captured September 16, 2026; current layouts may evolve.
A captioned, sound-off video of the same story for your next conversation.
Meet HarborLock, a fictional account-takeover response firm. Its expertise, evidence and voice give every next step a foundation.
Capture expertise, spokesperson knowledge and the facts your client can support.
Keep the scope: 18 of 60 incidents in HarborLock’s own casework, not an industry estimate.
The voice helps draft, but you bring the strategy and relationships.
Connect relevant reporting with client expertise. Prepare for selected upcoming events and the public milestones you add.
A news story about help-desk impersonation matches HarborLock’s account-recovery expertise.
RunPR flags opportunities, you determine if they’re worth pitching
Upcoming events such as earnings, events and holidays help you plan coverage
Research a reporter’s recent coverage and the connection to your client. A match is a lead, not permission to send.
Maya Chen’s reporting focuses on enterprise identity and incident response.
RunPR helps you determine what’s useful, and what’s just inbox noise
Your team checks the fit and decides whether to pitch. There’s no way to automate judgment.
The source, client facts and voice come together in an editable pitch. Review the writing and its factual support.
The draft connects the reporter’s beat or recent coverage to a specific client contribution. It answers the basic question “why are you pitching this to me now?”
Pitch Check reviews the writing and double-checks factual support. It helps surface gaps, but you make the final call.
Try editing the copy here. This demo stays in your browser, and nothing is saved or sent.
Just as you’d do with a pitch drafted by a junior account executive, you review the copy, resolve feedback and make final edits. Review, approval and sending are distinct steps.
Nothing goes out without manual approval. Hold a draft, scratch it, or approve it when the story is ready.
In this workflow, approving a draft does not send it. Sending is a separate, deliberate action.
After live outreach, RunPR tracks delivery and captured replies. This demo sends no live messages.
RunPR brings outreach, captured replies, coverage and AI visibility trends into reporting designed not to showcase as many metrics as possible, but to explain what PR success looks like to clients.
This separate sample month contains 24 sends and 8 captured replies. It is not the result of the September pitch.
Review 3 fictional source-supported placements separately from replies. Add your interpretation and next steps.
AI visibility shows comparable sampled answers, not causal proof. Review the report before exporting; nothing is shared automatically.
Enter a client’s website and inspect the research preview before choosing a plan. Your team brings the strategy, relationships and final judgment.