Blue for Process Management
Codify your approval flow process.
Run it forever.
Three primitives — event-driven, conditional, and scheduled — give you enough to codify any process. Approvals, onboarding, incident response, vendor reviews, RFP cycles. Build it once; the system runs it for the next decade.
Drag a record. It's the real product.
Below is what a process looks like in Blue — records moving through stages, with custom fields, owners, and the same automation engine you'll wire up yourself.
Teams running their processes on Blue
What a process runs on Blue.
Four moving parts that show up in every codified process: how work enters, how it branches, who gets pinged, and what runs on its own.
Forms as the front door
Public or internal forms create records the moment they're submitted. Map fields, route by selection, and kick off the rest of the process automatically.
Conditional branching
When a record transitions into a state — overdue, approved, escalated — fire the next step. Different branches for different outcomes.
Notifications & nudges
Email the right person, comment on the record, post to Slack — without anyone manually following up.
Scheduled rollups
Daily, weekly, monthly — scheduled automations sweep matching records and ship reports, reminders, or status digests.
01 · Event-driven
When something happens.
A field changes. A status updates. A record gets created. Each event fans out to the actions you've wired — emails, comments, status moves, webhooks.
02 · Conditional
When the record crosses a line.
Watch a filter — overdue, approved, over budget, escalated. When a record transitions into the condition, fire one branch. When it transitions out, fire the other. Same engine that powers SLA timers, escalations, and gate reviews.
Deal · Acme Corp
priority = 'high'ANDstage = 'open'03 · Scheduled
Every Monday at 9am.
Daily standups, weekly status PDFs, monthly invoice runs, quarterly board packs. Cron-style schedules sweep the records that match a filter and fan actions across the whole batch at once.
status = 'overdue'- Report · Q4 Launch
- Task · Ship v2
- Ticket · Billing bug
- Deal · Renewals Q1
- Task · Review design
04 · Permissions
Right step. Right person.
Steps in a process belong to specific roles. Workspace-, record-, and field-level permissions enforce who can see what, who can move it forward, and who's just along for the ride.
One price. Pay once. Forever.
Build the process once and run it for years — pay once for your tier, no recurring per-seat fees.
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
Build it once.
Run forever.
Codify the messy process you're tired of doing by hand.
Watch it run by itself for the next ten years.