Plays
Write the motion once. Run it on every account.
A play is a named motion — rescue, expansion, onboarding, renewal — with a trigger, steps, and a channel. Quivly starts it when the signal hits.
Book a demo
Expansion playbooks
Start when expansion signals match
Supabase
Expansion QBR + pricing bands
Vercel
New seats: approval loop
Railway
API tier — upgrade nudge
Slack: #expansion — Supabase QBR sent for review
Automated
Vercel: 12 seats — finance approval draft
Needs approval
In-app: Railway “upgrade API tier” nudge
Automated
Rescue
A churn signal starts a save play, with the reason attached, before renewal.
Expansion
Usage and buying signals route an expansion play to the person who owns the account.
Onboarding and renewal
A stall triggers a nudge, a check-in, or an escalation. Renewals get a 90, 60, and 30 day cadence.
FAQ
Frequently asked questions
The play is the motion you name and reuse. Workflow automation is the graph underneath it: the trigger, the account lookup, and the action.
The play is the recipe. Actions Feed is today’s list of runs waiting on a person, with the draft already written.
Yes. Drafts stay in review unless you have allowed an AI Agent to send that step.