
AV coverage runs asymmetric: a single incident gets treated as a referendum on the entire technology, while thousands of clean miles get no coverage at all. We build press strategy around a verifiable safety record and a pre-written incident response plan, so the day something goes wrong in public, you're not drafting a statement from scratch.
One incident gets covered as if it indicts the whole fleet
A vehicle stalling in an intersection, blocking a fire truck, or being involved in a minor collision gets national pickup within hours, while the millions of miles driven without incident never make the news because clean operation isn't a story. Companies without a response plan built for this asymmetry either go silent, which reads as guilt, or issue a defensive statement that gets picked apart, and either way the news cycle sets the narrative instead of the company.
Regulatory filings become press events you don't control the timing of
NHTSA investigations, DMV disengagement reports, and state DOT filings are public record, which means a reporter can build a story off your own regulatory disclosures before you've decided how to talk about them. Companies that treat these filings as a compliance-only exercise get blindsided when a beat reporter covering the agency turns a routine disengagement report into a headline about safety, and there's no time to build a response once the story is already running.
Local coverage and national trade press require completely different playbooks
A city council hearing about robotaxi pickup zones or a neighborhood complaint about vehicles idling on a residential street gets covered by local reporters who don't care about your funding round or your disengagement rate – they care about the intersection down the street. Companies that only staff national tech and transportation press miss the local stories that actually shape whether a city renews an operating permit, and by the time it's a national story, the local narrative is already set.
Founder commentary skews futurist instead of safety-credible
Founder interviews in AV often drift toward when full autonomy arrives or how the technology will reshape cities, because that's a more comfortable conversation than defending a specific safety record under skeptical questioning. That positioning gets founders quoted in trend pieces but does nothing to build credibility with the transportation and safety reporters who actually drive public and regulatory perception, and it leaves the founder unprepared the first time a reporter asks about a specific incident instead of the future.
Assessment starts with an audit of what's actually on the public record about your safety and operating history – disengagement reports, any incidents already covered, open regulatory inquiries – cross-referenced against what your team currently says publicly. Most AV companies have a defensible safety story buried under generic innovation language, and the gap between the two is exactly what a skeptical reporter or a city council member finds first.
Strategy work builds two things in parallel: a proactive press narrative grounded in verifiable operating data, aimed at the specific transportation, safety, and local beat reporters who cover AV seriously, and an incident response plan tiered by severity – a stalled vehicle is not the same story as an injury, and the plan needs a different statement and escalation path for each. We also build the plan for coordinating public statements with whatever your legal and regulatory teams are filing, so a press response never contradicts a NHTSA disclosure filed the same week.
Execution runs pitching tied to real operating milestones and safety data to the narrower list of reporters who take the category seriously, while running local press and city-relations outreach separately – a different set of contacts, a different tone, built for the audience that actually influences permit renewals and public trust in the markets where vehicles operate. The incident response plan gets drafted before any pitching starts, with pre-approved statement templates for the most likely scenarios and a clear internal chain for who talks to press within the first hour.
Media training runs with founders and operators before any interviews, focused specifically on the safety-record and incident questions reporters increasingly lead with rather than the future-of-mobility questions founders are used to. A founder who handles "what happened in the incident last month" credibly earns more trust in one interview than a dozen pieces about where the industry is headed.
Measurement tracks whether coverage reflects your actual safety record rather than a generic AV-hype or AV-fear framing, whether the incident plan gets used within its response-time window if triggered, and whether local coverage in operating markets trends toward trust rather than complaint volume. This work runs alongside our broader crisis and brand strategy support, since PR for an AV company only holds up if the incident plan behind it has actually been rehearsed, not just written.
The AV companies with the least press damage after an incident aren't the ones with the cleanest driving record – they're the ones who had a statement ready before the vehicle stalled.
Our 90-day PR sprint starts with the safety-record audit and the incident response plan, because pitching before either exists just adds more unverified claims to a category the press already treats skeptically. The first 30 days pull every public disengagement report, past incident, and open regulatory inquiry, and draft the tiered incident response plan against the most likely real scenarios for your specific operating footprint.
Days 30 to 60 build the two reporter lists – national transportation and safety press, and local beat reporters in each operating market – and run the first proactive pitches tied to real safety data and operating milestones, alongside media training that stress-tests founders on incident questions before a reporter asks them live.
Days 60 to 90 run a tabletop exercise on the incident plan with whoever owns the first-hour response, review which pitches landed with which reporters, and tighten the local outreach based on actual city or community reaction. By day 90 the incident plan has been rehearsed at least once, not just filed away, and the press narrative is built on operating data that survives a fact-check.
Engagements typically run 4-6 months. The first 30 days run heaviest, 2-3 days a week, building the safety audit, the incident plan, and both reporter lists. After that, cadence settles to 1-2 days a week for ongoing pitching, local outreach, and plan maintenance as operating markets expand or regulatory status changes.
We work directly with founders, whoever owns communications or regulatory affairs internally, and safety or operations leadership for fact verification on the audit and the incident plan. You provide access to disengagement data, incident history, and founder time for media training.
Weekly sessions track active pitches, upcoming regulatory filings, and any incidents that need the response plan activated. Monthly reviews assess coverage tone against your actual safety record and check the incident plan against any changes in your operating footprint or fleet.
Most engagements run 3-6 months as an initial phase, with an option to extend into ongoing support as the company adds operating markets or regulatory scrutiny shifts.
If your autonomous vehicles company needs public relations leadership, we should talk.

Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Engagements typically run $12K to $30K per month depending on how many operating markets need local press coverage and how much of the incident plan needs to be built from scratch. Companies already carrying open regulatory inquiries tend toward the higher end during the first month or two while the audit and plan get built.
The safety audit and tiered incident plan take the first 30 days and are the priority before any proactive pitching starts. By day 30 you have pre-approved statement templates and a clear escalation chain, and by day 90 the plan has been rehearsed through a tabletop exercise rather than sitting untested.
The incident plan is built in coordination with whoever handles NHTSA, DMV, or DOT filings, so a public statement never contradicts a regulatory disclosure filed the same week. We need access to disengagement reports and any open inquiries during the audit phase, and an ongoing sync point with legal before any incident-related statement goes out.
Most agencies pitch AV clients the same way they'd pitch any tech company – future-of-mobility narrative first, crisis planning as an afterthought if at all. We build the incident response plan before pitching starts, run separate local and national press tracks, and coordinate every public statement against what's actually being filed with regulators.
We track whether coverage reflects your verifiable safety record instead of generic hype or fear framing, whether the incident plan performs within its response window if activated, and whether local sentiment in operating markets trends toward trust. Raw press mention volume isn't the metric, because volume during a bad incident week is the opposite of a win.
Companies at Series A through growth stage, roughly $5M to $100M ARR, already operating vehicles in at least one real-world market with data to audit and a founder available for media training. The best fit is a team that has a genuine operating safety record to point to but no plan yet for the day an incident makes local or national news.
Tuesday, October 20, 2026
Frank Growth – Episode 242 – Why AI Slop Backfires with Nicole Cassese
Tuesday, June 16, 2026
Frank Growth – Episode 224 – The Bootstrapper’s Revenge with Alex Roy
Tuesday, October 13, 2026
Frank Growth – Episode 241 – What AI Still Can’t Do with Will Sartorius
Tuesday, October 6, 2026
Frank Growth – Episode 240 – Commerce for Weirdos with Bryan House
Ready to unlock your growth?
Book Free Call