Route5 · product
Product overview
What is in production, what is on the roadmap, and how to work with us for pilots, security review, and rollout.
North star
Enterprise AI execution layer — sits above Slack, Notion, email, and project tools without replacing them.
Decisions happen in meetings, Slack, and documents, but they are rarely owned, tracked, or executed. Work gets summarized; accountability does not.
Persistent accountability state: what was decided, who owns it, deadlines, and whether it happened—with risk surfaced before failure.
Built to close the loop from decision to done: a dedicated execution workspace alongside chat, email, and your existing project tools.
B2B SaaS for C-suite and COOs at mid-market companies (often 50–500 employees) in finance, law, consulting, and operations-heavy businesses.
01 — Who we built for first
Execution layer. Primary buyers: C-suite and COOs who own operational outcomes; Mid-market companies (~50–500 employees) where execution breakdown costs money; Finance, law, consulting, and operations-heavy teams.
Route5 converts decisions into owned, tracked commitments—persistent accountability state so leadership always knows what was decided, who owns it, and whether it is happening.
02 — The problem Route5 targets
Execution breaks after decisions are made. Companies decide things in meetings, Slack, Notion, and email — but those decisions are rarely turned into owned, tracked work. Nobody stays accountable; tools require someone to remember to log work; summarizers capture what was said, not what must happen next. The gap is persistent accountability state, not another dashboard.
Route5 converts communication into owned commitments you can track to completion: capture and structure decisions, assign ownership, monitor risk and staleness on Overview, and integrate with existing tools where configured — starting with paste and API-backed paths today.
03 — Route5 vs. a chat tab
A chat tab is fine for thinking out loud. It is a weak place to ship operational work: threads mix topics, checkboxes do not roll into metrics, and nothing stays tied to a project in your database. Route5 is built for that job — its own surface, not a wrapper around a chat model.
| Area | General chat | Route5 |
|---|---|---|
| Where the work lives | Scrollback mixes threads; hard to audit “what we decided last Tuesday.” | Per-project capture history — timestamps, duplicates, and exports from your database. |
| Structure you can execute | Free-form replies; you copy bullets into Jira or a doc by hand. | Problem + path forward + open questions + snapshot, then decisions and checkable actions per commitment — metrics from completions. |
| Follow-through in the UI | No workspace-wide queue of open commitments across projects. | Desk is the primary execution surface; Feed surfaces commitments org-wide; Capture processes raw text; Overview shows execution health and what still needs an owner. |
| Connectors (when configured) | You paste URLs or exports yourself. | Linear & GitHub import paths documented per screen — live lists only with tokens on your deployment. |
04 — In production
Route5 is a signed-in workspace: projects, Desk processes, structured fields, and action checklists — backed by your tenant data store. A system of record for ownership and deadlines: who owes what, when it is due, and how load and risk read from the same data your team updates.
- Authentication. Clerk sign-in (SSO if you configure it).
- Projects. Projects hold captured decisions, commitments, action checklists, and history.
- Webhook input. Optional POST /api/ingest/webhook with ROUTE5_INGEST_SECRET — push text into a project as commitments (Zapier, scripts, Slack outgoing).
- Decision capture. Paste raw text. With AI enabled: structured fields (problem, path forward, open questions, summary, decisions, actions). Without AI: a fast pattern-based process with the same fields, clearly labeled on each capture.
- Linear. Settings → Connections → Linear: browse, import by link when API access is configured.
- GitHub. Settings → Connections → GitHub: samples and import by URL when a token is configured.
- Actions. Check off action items; saved per capture; completion rolls into workspace metrics.
- Limits & data. 100k chars per capture. Supabase or local SQLite per user.
05 — Roadmap
These themes describe where we are investing. Capabilities are committed when they are available in the product and documented here—not before.
- Automatic ingestion: Slack, email, Notion, meeting transcripts (connectors)
- Agents: monitor progress, surface blockers, escalation before deadlines slip
- Executive and org-wide execution health views
- Deeper two-way sync with Linear and GitHub
- Team roles, shared workspaces, audit posture
- On-premise and bring-your-own models where required
06 — Why teams talk to us
- · Clarity: one workspace, one capture flow, traceable history.
- · Clear scope: in-product and documentation stay aligned on what is available today.
- · Governance: human review of outputs before they drive operational decisions.
07 — Using model-assisted capture responsibly
Language models can miss context. Route5 surfaces structured drafts; your subject-matter experts and owners remain accountable for what ships. That expectation is reflected in product copy and in our terms.
08 — The ask
If the fit is interesting: we'll walk your team through the workspace, align on security / data questions, and agree a concrete next step — pilot scope, technical deep-dive, or introduction to the right owner on your side.