Market Intel: M&A — v1 Build ✎

Gantt

Task table

System map — Market Intel: M&A

Status snapshot of every subsystem. Done = shipped, Partial = scaffolded with stubs, Todo = planned, Blocked = waiting on external. Click a ticket in the Gantt to drill into details.

Business logic flow — Market Intel: M&A

The recurring intel cycle this project builds toward. Once launched (M4), this loop runs weekly — each step below maps to the subsystems in the system map.

Step 1 — Collect

Run the weekly sweep across all connected sources — deal databases, trade press, filings, and broker conversations — using the sweep checklist. Every signal (announcement, rumor, listing, financing event) gets captured.

Step 2 — Log

Normalize each signal into the deal tracker against the fixed schema: buyer, seller, date, value / multiple where known, geography, rationale, and source link. One row per deal, updated as it moves.

Step 3 — Profile

Update the buyer watchlist and target universe with what the week surfaced — new acquirers entering the market, appetite shifts, targets changing hands or falling out of scope.

Step 4 — Analyze

Refresh the valuation benchmarks and target scores. Closed deals feed the comps set; pipeline moves and profile changes re-rank the target list.

Step 5 — Report

Produce the intel report from the template: new deals, pipeline moves, benchmark shifts, and target callouts. Deliver on the locked cadence to the locked distribution list.

Step 6 — Act

Decisions made off the report — outreach, deeper diligence, watchlist changes — feed back into the tracker and watchlists, so next week's cycle starts smarter than this one.

Latest statuses — ORION trackers

Per-project latest update, blockers, and next steps, fetched on demand from the fleet RAG service over Tailscale. Read-only here — update trackers via /project-update, the HUD, or the phone.

RAID register

Risks, Assumptions, Issues, and Dependencies. Link entries to tickets by ID — chips open the ticket. Everything here persists with the board and flows through Download edits / auto-sync.

RACI matrix

Rows are activities/deliverables; columns are this board's users (Users button to manage). Click a cell to cycle blank → R → A → C → I. Each row wants exactly one A — the count badge goes red otherwise.

Scrum board — kanban by assignee

One lane per user, kanban columns by status with Blocked leading. Each card shows how many days since the ticket was last touched (green ≤2d, amber 3-5d, red 6d+). Cards open the ticket. Owner/status/phase/epic filters above apply here too.

Computed live from the board: flow (cycle time, throughput, WIP, aging), predictability (burndown, schedule variance, projected finish), risk (blockers + downstream impact, RAID), and quality (rework, acceptance coverage). "Copy status report" puts a ready-to-paste markdown standup summary on the clipboard.