Crisis intelligence and response

Crisis Comms Built for Tech Companies

Distributism is crisis intelligence and response for technology companies. When an outage, a breach, an AI controversy, a social media backlash, a round of layoffs, or a business crisis puts your company in the public eye, I give your leadership a clear picture of what's happening and the words to act on it.

Deploy Distributism

Retainer clients hear back within 15 minutes. At any hour.

Run by JA Westenberg
tech writer and journalist

The first hour usually goes like this

Sound familiar?

  • The incident channel has 140 people in it, and nobody owns the words.
  • Legal wants to say nothing. Engineering wants to explain everything.
  • The holding statement is on its ninth revision in a shared doc.
  • A reporter wants comment by 5pm. It's 4:40.
  • Someone on a forum has a theory about what happened, and it's getting upvoted.
  • Customers are reading your status page next to a screenshot of a Discord thread. They trust the screenshot.

None of these are engineering problems, but they shape what customers, staff, and reporters remember about the incident.

What changes when I'm in the room

Without Distributism

  • Everyone reacts to whoever is loudest
  • Statements are written by committee
  • Nobody says anything, because nobody has worked out what silence will cost
  • Communications stop when the fix ships

With Distributism

  • One operating picture of every audience
  • One author, checked by counsel, approved by you
  • Staying quiet is an option, with its costs set out next to the others
  • Communications continue until customers, staff, and press move on

What I handle

Technical incidents are only part of the work. I also handle crises that start with an AI product, a social media post, a layoff, or a business decision.

  • Outages and breaches

    Service failures, security incidents, and vulnerability disclosures. I write the status updates, customer notices, and advisories, and check each one with your engineers and counsel.

    • Multi-region outages
    • Data breaches
    • Zero-day disclosures
  • AI backlash and incidents

    Model failures, harmful or wrong outputs, disputes over training data and privacy, and public objections to how you build or use AI. I explain what happened and what you're changing in terms your users and critics can check.

    • Model incidents
    • Training data disputes
    • AI policy changes
  • Social media backlash

    Pile-ons, viral complaints, boycotts, and coordinated campaigns. I track where the complaints are spreading, tell you which ones need a response, and write that response for the platforms where people are talking.

    • Viral complaints
    • Boycott campaigns
    • Community backlash
  • Layoffs and restructuring

    I plan announcement day and write the messages for affected employees, the remaining team, customers, and the press, so people hear the news from you first.

    • Layoffs
    • Reorganizations
    • Office closures
  • Business crises

    Crises with no technical cause: executive misconduct or departures, pricing changes, failed launches, funding or acquisition fallout, lawsuits, and regulatory inquiries.

    • Executive departures
    • Pricing backlash
    • Regulatory inquiries
    • M&A fallout

The public environment is part of the incident

Once an incident is public, customers, employees, markets, media, regulators, investors, and online communities all start working the story at once, each with different information and different incentives.

I pull those audiences into a single view, then tell you what's changing, what matters, and where you can still alter the outcome.

Narrative intelligence

See what people are saying as it happens.

My monitoring tracks public sentiment, emerging claims, influential voices, media movement, and community response, so you see what people are saying as it happens, not days later in a report.

Readout · 14:20 UTC
“Customer data exposed”
Spreading · unverified
Developer forums
Hostile, levelling off
Trade press
2 inbound, 1 deadline
Status page traffic
12× baseline
This one needs an answer inside the hour.

Response engineering

Every word, ready to ship.

I write and execute your most critical communications. Every message is precise, technically authenticated, and ready to deploy.

Holding statement · draft 2
What happened
At 09:12 UTC we identified…
Who is affected
Customers in one region
What we're doing
Service restored 11:40 UTC
Next update
16:00 UTC, on this page
Every sentence checked against the incident log.

Executive command

Know what each move costs.

I map the public risk and outline your strategic options. Before you make a move, I forecast the consequences of taking action, and the true cost of staying silent.

Decision memo · options
A · Publish now
Own the timeline
B · Wait for forensics
Story sets without you
C · Say nothing
Costed, not assumed
Recommendation
A, with a 16:00 follow-up
You decide. I show you the price of each option.

Reputation recovery

I stay on after the fix ships.

Public recovery usually takes longer than technical recovery. I stay on the public side until customers, staff, and press stop treating you as the story.

Recovery · two clocks
Fix shipped
Day 1
Post-incident report
Day 6
Customer check-ins close
Day 14
Press stops calling
Day 19
Public attention usually outlasts the technical fix.

Built for high-consequence technology

If a bad day at your company makes the news, you're who I work for.

Artificial intelligenceAgentic platformsCloud infrastructureCybersecurityDeveloper toolingFintechCritical softwareNetworked products

…when any of these happen:

  • Outages
  • Breaches
  • Vulnerability disclosures
  • AI backlash
  • AI model incidents
  • Social media outrage
  • Coordinated campaigns
  • Layoffs and restructuring
  • Product failures
  • Pricing backlash
  • Executive exposure
  • Regulatory attention
  • Market-moving events

I work inside your response team

My model is closer to forward-deployed engineering than to account service.

I work alongside your engineers, your executives, and your counsel. I'm a senior operator who can enter a complex situation quickly and own the narrative.

Before anything happens

Forward positioned

On retainer, I stay close to your company, your systems, your leadership, and the people who talk about you in public, so when pressure arrives, I already have the context.

Right now

Incident deployment

For a live situation, I deploy straight into the response and stay through public recovery.

Before the first alert

Readiness systems

I build the communications infrastructure, the intelligence baselines, and the executive capability you'll need when it sounds.

Built on AI agents, run by a person

“The agents handle monitoring and analysis. I check their work, make the calls, and answer for them.”

I build Distributism around agentic systems. They extend my reach, provide around-the-clock coverage, and deliver sentiment analysis at speed and scale.

I review and approve every external communication myself, and before I act on any material reading of public sentiment, I test it against what I know about your company, the incident, and the limits of the data.

Private by default

I treat everything you share during an incident as confidential.

I work over encrypted communications and encrypted document exchange, keep the circle to the people who need to be in it, and open a secure channel from your first message.

A note before you go

Distributism is me. When you send a brief, I read it. When you're on the call at 3am, I'm on the call.

Agents do the watching. Every statement that leaves with your name on it has been through my hands first.

You work with one senior person, who is responsible for every statement from the first alert until people stop asking about the incident.

Deploy Distributism

For ongoing coverage, readiness, or an active incident.

Open a secure briefing

Retainer clients receive a response within 15 minutes, at any hour.

Live incident right now? Skip the form and email activate@distributism.ai.