Product Update

From exercises to an operation that runs

We started as the complete exercise platform. We've become something larger — a place where your whole preparedness operation lives, learns, and works on its own. Here's what we have now, and what's coming next.

Preparedness has always been treated as a series of projects. An exercise this quarter. A plan refresh next year. A THIRA when it's due. Each one starts from a blank page, or at best a document to jump off from, ends in a document, and the document goes in a drawer. The next project starts cold.

We built Preppr because that model wastes the most valuable thing an emergency manager produces: what they learn. Every exercise surfaces gaps. Every after-action names fixes. Every plan encodes hard-won judgment. And almost none of it carries forward. Your readiness, in effect, resets to zero the moment the report is filed.

So we set out to change the unit of work — from the project to the operation. Not a faster way to write documents, but a system that captures the complexity of what you actually run, and compounds it.

Preparedness isn't a project with an end date. It's a continuous operation. Software should treat it that way.

Where we are now

A preparedness operations platform

What began as exercise design has grown into a connected system. The exercise is still there — and it's still the best in the category — but it's now one motion inside a platform that holds the whole lifecycle. Three properties define it.

01 · Connected — One operation, not ten tools. Assess, gather intel, engage stakeholders, design, exercise, improve — every stage in one workspace, sharing one memory. The work stops living in scattered files and disconnected apps.

02 · Compounding — Readiness that builds on itself. Every exercise, finding, and decision flows back into one living knowledge base. The next question starts smarter than the last. Nothing resets to zero.

03 · Grounded — Built on what you're held to. Hundreds of rules across every sector you operate in, plus your own plans and patterns. Every output cites the requirement it meets — defensible, not generic.

~1,500Rules from federal doctrine & regulation
14+Sectors covered out of the box
5Lifecycle stages, one connected system
∞Findings that compound, never reset

On top of that foundation sit the capabilities people use every day. Ask Preppr reasons across your knowledge base to develop plans and answer hard questions. Collaborate brings external stakeholders into the work with real roles. The Exercise Designer turns design from a content problem into an agentic build — it plans the work, reasons across your doctrine and history, and hands back a defensible exercise. Preppr Exercise then takes it live — delivering and facilitating the exercise itself, and feeding what surfaces straight back into the record. And the Knowledge Base ties it all together, linking plans, exercises, findings, and rules into a single graph.

The shift

From a tool you use to an operation that runs

The biggest change isn't a feature. It's a change in posture. Most preparedness software is a place you go — you open it, you do work, you leave. Preppr is increasingly an operation that runs.

This is worth being precise about, because the words for it have been worn smooth. "Connected" has come to mean a vendor's software can reach into your tools — an integration, a plumbing claim. We mean the opposite. You never come to Preppr. You stay in your inbox, your Slack, your meeting, and the same operation runs whether you typed it, said it, or forwarded it from your phone. Not we can call your tools — you never have to leave where you already work. That's a different axis entirely, and it's the one that matters when the work competes with a full calendar.

"Agent" has been worn smoother still. For most software it means a chatbot reading over your documents — it answers questions about your plan. Preppr does something a chatbot structurally cannot: it pressure-tests the plan. Hand it a tabletop and it doesn't summarize your doctrine back to you — it builds the exercise, runs it dozens of ways, finds where it breaks, and hardens it before you ever see a draft. Answering questions is retrieval. Doing the analysis you couldn't run by hand is labor. Only one of them changes how ready you are.

You direct it however you already work: by typing or clicks, by voice, by handing it a goal over email or Slack, or by driving it from your own tools. It does the multi-step work in the background and reports back where you asked. The most reliable member of your team — one you delegate to, not one you operate.

And there's a hard line we hold: autonomy on the labor, never on the decisions. Preppr does the building and the analysis a person could never do by hand — but it pauses before anything goes outward, and nothing reaches your leadership until you say yes. You keep the judgment. It takes the work. And because the analysis runs out of sight, you can always look in: the full fleet of work behind a recommendation is open to you, including what it tried and set aside, not just the answer it landed on.

You supply the intent and the judgment. Preppr supplies the plan and the labor. The line between them never blurs without your say-so.

What's soon possible

Where this goes next

Everything above is live or arriving. What makes us most optimistic is what the foundation now makes possible — because once the operation is connected, compounding, and grounded, entirely new capabilities become straightforward.

→ Autopilot, end to end. Hand Preppr an outcome — "draft a hurricane tabletop for the EOC and schedule it next month" — and it designs, validates, asks only what it can't infer, pauses for your approval, then finishes and reports back. It confirms the request really came from you, works in the background, and you never open the app unless you want to look in.

→ Simulate at scale. Before a design ever reaches you, Preppr fans out a cohort of concurrent agentic simulations — each a full multi-cell tabletop in miniature, grounded by a deterministic physics engine and a cognitive model so every agent reasons like a different person under pressure. A Red cell drives the threat, a White cell adjudicates, a Blue cell of section chiefs deliberates — and they disagree, because each seat carries its own expertise, risk appetite, and priorities. Preppr reads across the whole fleet and hardens the exercise before a human sees it. It's a depth of analysis a chatbot over your documents can't reach, and a person could never run by hand.

→ Intelligence that informs every decision. The point was never just to produce preparedness intelligence — it's to put it to work. As the knowledge base deepens, Preppr surfaces what matters across the whole cycle, so every decision is better-informed than the last, not just the documents faster.

→ Work anywhere. Talk to it. Email it. Message it. Or let it run. Preppr meets you in the channels and tools you already use, so the operation keeps moving whether or not you're sitting in front of it. Not connected to your tools — running from inside the way you already work.

★ Anticipatory readiness — Preppr watches, then acts. This is where it all converges. Preppr monitors the threats and trends you named in your THIRA, HVA, and risk assessment. When one moves, it doesn't wait to be asked — it reads your knowledge base, sees what you've worked on and where the gaps still are, and acts: a heads-up by email or Teams, a plan offered before you'd have thought to build it, and recommendations grounded in what Simulate already learned about how that scenario plays out against your operation. The work shifts from reacting to a calendar to staying ahead of the risk itself.

The throughline is simple. You describe the outcome. Preppr does the work — grounded in your reality, compounding with every cycle, and always stopping at the decisions that are yours. The result is the thing every emergency manager is actually trying to be:

The most prepared person in the room — and getting more so every cycle, without the busywork that used to be the job.