Why did your project fail or slip?

Enter a troubled project — its tasks, notes, milestones and red flags — and six specialist agents will investigate it in parallel, then deliver a ranked root-cause report with a preventive action plan.

Demo case study

📉 CRM rollout that slipped 6 months

Enterprise software project — scope creep, attrition, silos, cut QA budget. 10 tasks, 10 notes, 5 milestones, 14 red flags.

Demo case study

🏢 Office relocation that went over budget

Facilities move — permit surprises, sponsor drift, no owner. 6 tasks, 6 notes, 3 milestones, 8 red flags.

1

Document the projectBasic profile: what it was, planned vs actual dates, how it ended.

2

Enter the evidenceTasks with dates, meeting notes, milestone slippage, red flags.

3

Get the autopsySix agents investigate; you get ranked root causes + fixes.

1 · Project profile

The basics. Everything here feeds the analysis — especially the dates and the "what went wrong" brief.

Project name *

Project type

Industry (optional)

How did it end?

Methodology

Team size (people)

Planned start

Planned end

Actual end (if it ever finished)

Complexity / difficulty

Moderate (3)

What went wrong? (brief — this is mined as evidence)

2 · Evidence

The more real evidence you add, the sharper the diagnosis. Need inspiration? load software-case sample or ops-case sample.

📋 Tasks 0

🗒️ Notes 0

🏁 Milestones 0

🚩 Red flags 0

Add tasks with planned & actual end dates — the engine computes lateness, slip and compounding delays from these.

Task	Owner	Status	Planned end	Actual end

Paste meeting notes, emails, retrospective quotes. The engine reads these for signals of scope creep, silos, burnout, etc.

Milestones with planned vs actual dates show whether slippage compounded over time.

Milestone	Planned date	Actual date	Met?

Tick the red flags that applied. These are the classic early-warning signs from project-management post-mortems.

Agents investigating…

Six specialist agents review the evidence in parallel, each from its own discipline.