Workflow automation
Triggers, sequences, and approvals — the busywork runs itself, no code.
Domain events — lead won, payment failed, booking made, event attended — trigger workflows you compose in the dashboard: send the message, create the task, wait, branch, ask for approval. The engine is durable: runs survive restarts and dead-letter loudly instead of vanishing.
How it helps you
Follow-ups that never depend on memory
The quote follow-up, the review ask, the win-back — define once, runs forever.
Approvals with an audit trail
Human-in-the-loop steps pause the run until someone signs off — recorded, not Slack-lost.
Failures surface, never vanish
A failed run dead-letters and notifies the built-in coach — silence is not an option.
The walkthrough
Pick a trigger
Any domain event — CRM, money, events, bookings.
Compose the steps
Messages, tasks, waits, branches, approvals — visual, no code.
Watch runs live
Every run is inspectable: what fired, what sent, what is waiting on whom.
Projects, plans and tasks
Winning the job is the easy half. This is the part that decides whether you deliver it well.
A plan per job
A won deal becomes a delivery plan — phases, tasks, owners, dates — without anyone retyping the scope that was already quoted.
Tasks that know their order
Tasks depend on other tasks, so “this cannot start until that finishes” is enforced by the plan rather than remembered by a person.
A board and a personal list
Managers work the board; everyone else opens “my tasks” and sees only what is theirs, in priority order.
Reusable blueprints
The way you run a wedding, an install, or an onboarding becomes a template you start from — so quality does not depend on who set it up.
Locked plans and change requests
Once a plan is agreed it can be locked, and changes arrive as requests with a decision trail — not silent edits nobody can reconstruct later.
The part your customer sees
The difference between a client who trusts you and a client who keeps calling is whether they can see progress without asking.
Their own delivery view
Customers watch their project move — what is done, what is next — in your branded portal, with no phone call required.
Change requests from their side
They ask for a change where the work lives instead of in an email thread, and it lands in your queue with the plan attached.
Good, better, best — built by them
Share one private link and your client browses the services you offer, each with a good / better / best option, and assembles what they actually want. It arrives as a request list you price — so the first call is a quote, not an interview. This is exactly how one live events company on the platform runs their bookings.
No login required to shape the job
That builder link needs no account, and you can rotate or revoke it at any time — so sharing it costs you nothing.
Shipped features behind this
From the same machine-readable catalog we publish at /features.json — what your AI reads to learn the platform.
Automation runs & approvals
The other half of Automations: run history per lifecycle state with cancel, plus the approvals queue — the human gate an automation pauses on before any money-moving or irreversible step (approve releases the dispatch; reject routes to the failure path).
Coach — act feedback + signal periods
Closes the Coach's feedback loop: 'I acted on this' on every insight (the engine learns which advice lands) alongside Dismiss, and the signal view gets a working 7d/30d/90d period selector over the live signals endpoint instead of a fixed 30-day pill.
Common questions
What happens if a workflow fails mid-run?
The run records the failure, retries where safe, and dead-letters loudly if it cannot proceed — the failure watchdog turns it into a coach observation so a human sees it.
See it, then build on it
This whole site runs on the same platform — fork the template, or point a front end you built with Lovable, v0, Bolt, Claude, or Cursor at the backend.