How to use this guide

Use this handbook to decide what your startup needs to communicate, which stakeholders matter, how to run the work, and who should own it. It supports founder-led, in-house, freelance, fractional, agency, and hybrid programs. Start with the decision in front of you, then follow the linked pages as the work develops.

Start with the business problem

PR begins with a business condition that communication may be able to change. Examples include low awareness among a defined buyer group, confusion about a new category, employee uncertainty during a transition, or scrutiny after an incident.

Use this sequence to build a program:

Define the business condition and the decision the company needs to support.
Map the stakeholders who affect or experience that condition.
Research what those stakeholders know, believe, need, and do.
Set a measurable communication objective and choose a strategy.
Develop messages and proof, then select the appropriate paid, earned, shared, and owned channels.
Assign an owner, execute the work, measure audience response and outcomes, and revise the plan.

The pages on what PR is and what PR can and cannot do provide the foundation for that sequence.

Choose the path that matches your current decision

Build the foundation. Start with PR's role in reputation and stakeholder relationships, its relationship to marketing and advertising, stakeholder mapping, research, strategy, ethics, and measurement. This path helps a team write a useful brief before choosing tactics or vendors.

Prepare a story pipeline. Use the pages on newsworthiness, building a story engine, messaging and positioning, the PR calendar, the press kit, and media training. These pages explain the source material the company must maintain even when an outside practitioner runs execution.

Run a specific program. Go to the relevant playbook for media relations, a funding announcement, a product launch, thought leadership, analyst relations, international work, or crisis communication. Each program should inherit the same stakeholder, evidence, approval, and measurement decisions from the foundation.

Choose an operating model. Start with whether you need an active PR program yet and the comparison of agencies, freelancers, fractional leaders, and in-house teams. Then use the service, pricing, scope, contract, and vetting pages if outside support fits the work.

Manage outside help. Use the onboarding, responsibility, approval, reporting, measurement, troubleshooting, and offboarding sections throughout the relationship. A vendor can supply capacity and specialized judgment. The company still owns its objectives, facts, stakeholder obligations, approvals, and institutional knowledge.

Keep five working documents

A small program can run from five maintained documents:

Situation brief. The business context, research findings, risks, and constraints.
Stakeholder map. The people affected, their current relationship with the company, and the desired change.
PR strategy. The objective, insight, approach, messages, channels, resources, and measures.
Story pipeline. Candidate stories, evidence, permissions, timing, owners, and status.
Measurement record. Activity, outputs, audience response, outcomes, business impact, and lessons.

The Tools and Reference section turns these decisions into briefs, scorecards, reports, and checklists. Keep the underlying facts and decisions in company-controlled files so they remain available when a team member or vendor changes.

Apply specialist review to high-risk communication

This handbook provides an operating framework. It does not replace legal, regulatory, financial, security, safety, HR, or incident-response expertise. Route claims and events in those areas to the appropriate specialist before publication. During an active incident, the communication lead should work inside the cross-functional response rather than run a separate process.

PressFriendly publishes this handbook and sells PR services

Pages that cite PressFriendly prices, service terms, or activity data should label that information as company-specific. Treat those examples as one vendor's evidence, then compare them with your requirements and other available options.