Public demo · Read only
[Demo] Postmortem Blame Router
This pre-generated demo belongs to no visitor account and consumes no credits.
How to read this report
Start with the verdict and what can kill it, confirm whose problem this is, inspect the business case and counter-evidence, then run only the seven-day tests. Expand supporting research as needed.
- 01Verdict
- 02User
- 03Business
- 04Counterproof
- 05Action
01 · Decision brief
Blame avoidance in postmortems is a real problem, but satirical packaging is more likely to drive virality than stable revenue.
What to do now
Biggest unknown
Riskiest assumption · viability
Engineering leads will hand over sensitive postmortem materials to a new tool and pay for the generated formal output.
Without material authorization, automation is impossible; without real payment, this is just content, not a business.
Current evidence: Only public articles, templates, and transaction signals from adjacent incident management tools; no user interviews, upload behavior, or payment records for this product.
Experiment 01 below tests this assumption directly
Evidence ladder · L2
Public help requests, complaints, and alternative evidence exist, but no target user behavior or payment.
Next level L5: Collect at least 3 prepayments of $49 and confirm at least 2 outputs were actually sent to teams.
Step 1 · Identify whose problem this is and how they solve it today
02 · Whose problem is this
Target user and payer
When it happens
Pain intensity
03 · How they solve it today
Current alternatives and doing nothing
- Using incident management tools like Rootly, incident.io, FireHydrant for technical postmortems
- Using free templates in Notion, Confluence, Asana, or spreadsheets
- PM manually compiles timeline, responsibility boundaries, and action items
- Skipping formal postmortems, relying on verbal consensus and accepting recurring issues
Help and complaint signals
Alternative and transaction signals
- Platforms like Asana and Notion offer free postmortem templates, showing low-cost alternatives for structured documentation.↗
- Enterprises pay for incident management platforms, but no public evidence shows buyers would separately purchase a satirical blame routing tool.
Step 2 · Test the conclusion across eight business dimensions
04 · Eight-dimension judgment
Step 3 · Expand market, business, and execution when you need the detail
▶Market, timing & competition
Market & Timing
Bottom-up math
TAM
All tech organizations needing cross-team incident, project, and roadmap postmortems.
SAM
English-speaking tech companies with 50-500 people, formal postmortem processes but weak action item closure.
SOM
100 teams in first two years, ~$58.8K ARR at $49/month.
Assumptions
- Buyers willing to let third-party tool read anonymized postmortem materials
- Product reduces single postmortem compilation time by at least 30 minutes
- Satire mode can be disabled; formal mode passes internal procurement review
Why now
- Remote collaboration scatters incident context across meetings, chats, and task systems, raising manual compilation costs
- LLMs can already extract timelines, role-based rewrites, and action item summaries
- Companies increasingly value psychological safety and blameless postmortems, but lack lightweight tools to turn principles into daily practice
Competition & Moat
Direct competitors
| Competitor | Positioning | Pricing | Strengths | Weaknesses |
|---|---|---|---|---|
| Rootly / incident.io / FireHydrant | Full incident response and postmortem platform | Enterprise quote or per-team subscription | Existing incident data, integrations, and enterprise procurement relationships | Primarily serve technical incidents; weaker on cross-department project failures and communication politics |
Indirect competitors
| Competitor | Positioning | Pricing | Strengths | Weaknesses |
|---|---|---|---|---|
| Notion / Confluence / Asana templates | General postmortem documentation and collaboration | Free templates or included in existing subscriptions | Zero additional procurement, team familiarity, fully customizable | Relies on manual compilation; cannot proactively detect responsibility drift or unclaimed action items |
Substitutes
- PM manually writes postmortem notes
- Using generic AI prompts to rewrite incident descriptions
- Hiring organizational development or agile consultants to facilitate postmortems
Whitespace
Possible moats
- Workflow data — Only after long-term accumulation of anonymized failure patterns, action item completion rates, and rewrite effectiveness can a stronger evaluation baseline than generic prompts be built.
- Embedded integrations — If deeply embedded in Slack, Jira, Notion, and incident platforms, switching costs rise; MVP stage has no such barrier.
▶Business model & cold start
Monetization Path
Recommended model
One-time service validates real materials, delivery quality, and willingness to pay without building complex integrations; subscription only works if customers use it monthly.
Suggested pricing
Pricing anchors
- Free templates anchor pure document generation at zero, so charging must come from saving facilitation time, reducing political risk, and tracking action items.↗
Unit economics
- Gross margin >80%
- Monthly churn <4%
- Sales and acquisition costs recovered within 6 months
Willingness-to-pay evidence
- Adjacent incident management platforms have enterprise budgets, but no prepayments, letters of intent, or actual checkout evidence for this product.
Cold Start & Seed Users
Matched strategies
- Anonymized postmortem transformation — Invite engineering leads to submit de-identified materials, show before/after comparison for free, build credibility with real delivery.
- Service before software — First 20 orders manually reviewed; record time saved, revision count, and willingness to pay again for each order.
Seed-user communities
- SRE, DevOps, and engineering management communities — Publish anonymized incident postmortem breakdowns; invite leads who experienced high-pressure postmortems to paid trials.
- Product Hunt, Hacker News, and engineering lead communities — Attract attention with satirical concept, but landing page highlights formal output and action item closure.
Channels (impact/confidence/ease)
▶Execution feasibility
Technical, operational & regulatory
Technical
Operational
Regulatory
Dependencies
Timeline
MVP & Execution
Must-have features
- Import a de-identified postmortem material and extract event timeline
- Distinguish facts, speculation, blame expressions, and system conditions
- Generate internal formal version, management summary, and action item list
- Action items must include owner, deadline, and review condition
- Provide satire mode toggle; default to formal blameless expression
Build / buy / partner
- buy LLM extraction and rewriting — Start with mature models; do not train own model.
- build Postmortem evidence structure and responsibility boundary rules — This is core to product judgment and long-term data moat.
- partner Slack, Jira, Notion integrations — MVP starts with text upload; build costly integrations only after payment is validated.
Effort estimate
Biggest tech risk
Step 4 · Seek counter-evidence and stop signals
Counter-evidence & failure conditions
Free postmortem templates are already widespread.
Without significant time savings, conflict reduction, or action item completion improvement, standalone charging has no basis.
Existing incident platforms already have customers, data, and integrations.
Standalone AI rewrite features are easily copied; must carve a narrower niche from non-technical failures or cross-team responsibility closure.
Kill Risks
No one pays: free templates and generic AI are sufficient.
If the product only offers one-time rewrites, buyers struggle to create a new budget for it.
Cheap test: Deliver 10 manual services using the same real postmortem materials, collect $49 before delivery; stop development if fewer than 3 pay.
Satirical packaging undermines credibility; legal and HR teams veto outright.
Incident materials may affect performance reviews, labor disputes, and litigation; joking responsibility assignment amplifies organizational risk.
Cheap test: Have 5 engineering leads and 2 labor lawyers review product copy and output samples; record unacceptable boundaries.
Permission barriers to read Slack, Jira, email, and meeting content are too high.
Without integrations, automation is hard; with integrations, security reviews and compliance costs are triggered.
Cheap test: Start by accepting only user-uploaded anonymized materials; test if 10 teams are willing to upload and repurchase.
Existing incident management platforms quickly replicate blame analysis features.
They already have data, workflows, and customers; adding an AI rewrite layer has low marginal cost.
Cheap test: Track competitor updates for 90 consecutive days; simultaneously verify if non-technical project postmortems form a sufficiently independent entry point.
Expected objections
- This is just a joke; I can't send it to management.
- We already have incident.io and Notion templates.
- Legal won't allow the system to automatically assign responsibility.
- Too risky to hand internal communication data to a small company.
- Generic AI plus a prompt can do the same thing.
Step 5 · Replace guessing with seven days of action
Next Actions
01
Recruit 10 leads who recently experienced incidents or project failures; complete one 'postmortem detox' using human + AI; require real payment before delivery.
Hypothesis: Engineering leads who experienced high-pressure postmortems are willing to pay at least $49 for a safer, sendable formal postmortem.
Engineering management communities, SRE communities, and targeted LinkedIn DMs
- Create landing page with formal and satire mode toggle
- Screen 10 people who facilitated a postmortem in the last 90 days
- Sign de-identification agreement and collect $49
- Deliver postmortem summary, action items, and risk notes within 24 hours
- Record revision count, willingness to send, and repurchase intent within 30 days
$300 recruitment and tooling cost, plus 30 hours manual delivery
Success criteria: At least 3 pay, at least 2 willing to send formal version to team, at least 1 repurchases within 30 days.
Failure criteria: Fewer than 2 pay, or most only want to see satire content but refuse to submit real materials.
▶Unit economics and seven-day execution
Unit economics gates
CAC
LTV
Gate
Data to collect first
Seven-day action calendar
Four-question pricing survey
Only ask those who facilitated a postmortem in the last 90 days and are willing to submit de-identified materials.
- 01Below what price would you doubt this postmortem's credibility?
- 02What price feels like a great deal and you'd try immediately?
- 03What price starts to feel expensive but you might still buy?
- 04Above what price would you definitely not buy?
Complete 20-30 qualified buyer interviews before deciding subscription price.
Interview question list
Mom Test rule: ask about past behavior and actual spend, never whether they would use it.
- 01Who facilitated that postmortem, and how long did it take from gathering materials to issuing conclusions?
- 02What defensive statements, silences, or blame shifts occurred during the meeting? How were they handled?
- 03What template or tool did you use? Which step was still the most labor-intensive?
- 04How many final action items were completed on time? Who tracked them?
- 05Have you ever paid for an external consultant, incident platform, or postmortem tool? Amount and reason?
- 06What data must never be handed to a third-party tool? Who has approval authority?
- 07If someone could deliver a sendable postmortem package within 24 hours, how much would you pay to try it once?
Evidence Gaps
- No real payments, prepayments, or letters of intent for this product.
- No behavioral data on target users submitting sensitive postmortem materials.
- No conversion rate comparison between satire and formal landing pages.
- No formal review opinions from corporate legal, security, or HR teams.
- Market size and unit economics are bottom-up assumptions, not calibrated with sales data.
▶Evidence ledger (5)
Only reviewable public sources belong here. Desktop research caps at L2 and cannot replace behavior or payment evidence.