Plan and build against the same records the business sees.
Build lanes, a roadmap with real definitions of done, and an AI-assisted document workspace — your product's record living next to the rest of the operation.
Build lanes
Your build as a measured lane — what's shipping, what's stuck.
Every shippable thing is a lane with a status, an owner, and a progress read. The board doesn't just hold cards — it counts them, so a blocked lane raises its hand instead of hiding in a column.
Done = verified
A roadmap where a goal is done only when the work is verified.
Every goal carries an outcome and a definition of done. It doesn't close because someone dragged it — it closes only when every issue linked to it (tasks.goal_id) is terminal with at least one done. And because each of those issues already passed the ship/verify gate, closing the goal is transitively verified — nobody signed off their own work to get there.
AI docs
Write the spec next to the tasks and leads it drives.
Specs, briefs, and notes get an AI editor to draft and revise them — and they live on the same board as the build lanes, one tab over. The doc that defines a lane sits beside the lane, in the same database, not in a separate app you have to keep in sync.
Docs your agents cite
The agent working the task reads the spec — and cites it.
Because a doc is a row, not a walled-off wiki page, an agent that claims a task can open the governing spec, quote the clause it's acting on, and link it back into the work — no copy-paste, no 'which version is current.'
$ excellent-mcp task_update 1042 --status in_progress✓ #1042 claimed · shipper claude-8df093$ excellent-mcp urn_resolve "spec:onboarding-rewrite"Onboarding rewrite · Product ▸ Docs · §2 first-run < 3 min$ excellent-mcp note_add --task 1042 --body "per spec §2 — first-run < 3 min"✓ note on #1042 cites spec:onboarding-rewrite (same DB, no copy-paste)Docs your agents can actually read and cite.
Reference material is part of the data layer, not a walled-off wiki — so an agent working a task can read the spec, cite it, and act on it.
Explore the rest of the product.
Every surface reads from the one database you own — pick the next one.
Work
The human queue and the agent queue on one board.
Customers
Leads, pipelines, and one timeline per relationship.
Operations
The directory, money, and back office on one layer.
Hiring
A local-first ATS — candidates are people.
Agents
A team that claims, does, and verifies real work.
Integrations
Sync your stack into the one database. No broker.
Ownership
One database, on your disk. Local-first, exportable.
Bring your whole business home.
Download Excellent and run your whole business on your own machine.