Blue for Case Management
Every case.
Every step. Recorded.
Legal matters, support escalations, patient files, compliance investigations — every case as a record, with full audit history, role-scoped access, and the documents and conversations that produced the outcome.
Open a case. Run a real workspace.
Below is the actual product, shaped like a case file. Custom fields, checklists, comments, and the audit history — the same surface your team gets on day one.
What case work looks like on Blue.
Four moving parts: the case file, the work it requires, who can see it, and the deadlines that matter.
Case files as records
Every case is a record with custom fields for status, assigned counsel, jurisdiction, deadlines, and the dozens of attributes a real case carries.
Case tasks & checklists
Break a case into the discrete steps it requires. Subtasks, dependencies, due dates, and assignees — visible to the case team and no one else.
Role-scoped access
Privileged information stays scoped to the people who need it. Field-level controls keep names, financials, or PHI hidden from anyone outside the case.
Statute & SLA timers
Conditional automations watch deadlines and escalate before they slip — statute of limitations, response SLAs, regulatory windows.
01 · The case record
Who did what. When. And why.
Auditable history, threaded discussion, and case-team knowledge — all attached to the case record itself.
Every change, recorded.
The audit trail logs who created the case, who modified each field, who closed it, and when. Exportable for review.
Opposing counsel proposed a settlement window — recommend we counter at 1.2x.
Agreed. Draft the response, I'll review before we send it.
Decisions in context.
Comments and threaded discussion attach to the case itself. The rationale travels with the work, not with someone's inbox.
Intake & Conflict Check
Procedures linked to the work.
Intake checklists, escalation procedures, and case-type SOPs — written once, referenced from every case that uses them.
02 · Permissions
Privileged. By default.
Case data is private to the case team. Field-level controls keep names, financials, and PHI hidden from anyone outside it. Counsel sees the matter. Operations sees the calendar. Clients see only their own case.
03 · Deadlines
When the clock crosses a line.
Statute of limitations, regulatory response windows, SLA timers — Blue's conditional automations watch the boundary and escalate before it slips. Different actions for "approaching" and "missed."
Deal · Acme Corp
priority = 'high'ANDstage = 'open'One price. Pay once. Forever.
Pay once for your tier — no recurring per-seat fees. Size the tier to your team and move up only when you outgrow it.
Starter
For freelancers & small teams
One-time payment
- 5 users
- 5 workspaces
- 2,000 records per workspace
- 5,000 records per org
- 10GB storage
- 250 automations / month
- 3 webhooks
- 3 dashboards
- 1 custom role
- 20 req/s API rate limit
- Community support
Growth
For growing teams
One-time payment
- 30 users
- 25 workspaces
- 2,000 records per workspace
- 25,000 records per org
- 100GB storage
- 1,000 automations / month
- 10 webhooks
- 10 dashboards
- 3 custom roles
- 50 req/s API rate limit
- Email support
Scale
For large organizations
One-time payment
- 150 users
- 100 workspaces
- 2,000 records per workspace
- 100,000 records per org
- 500GB storage
- 5,000 automations / month
- 50 webhooks
- 25 dashboards
- 5 custom roles
- 200 req/s API rate limit
- Email support
Every case.
On the record.
Stop running case work in shared inboxes and labelled folders. Start with one case workspace and let the audit history take care of itself.