The recurring work, mapped first
Every repeated step around the play, with who does it, how often and what it costs in hours.
How we work · What we build · Step 03
The weekly busywork, running itself
Research, routing, enrichment and reporting on a schedule or a trigger, so skilled people stop doing it by hand. We automate a step once the play it serves has worked.
Book a call30 min · no prep needed
What you're after
01
Hours back for skilled people
Your RevOps lead and reps stop pulling lists and pasting fields, and spend the time on buyers.
02
Work that happens when someone's out
New leads researched and routed at 2am on a holiday.
03
Automations you can see
Every run has a history and every failure alerts its owner. Nothing fragile that nobody remembers building.
Three stages before a step runs on its own
A step moves down only when the stage above shows it works. Buyer-facing steps keep the approvals in Agents at every stage.
| Stage | Who does the work | What tells you it's ready for the next stage |
|---|---|---|
| Run by hand | A person, using a skill in the AI workspace | The play is new. We're still learning what good looks like. |
| Drafted by an agent | An agent drafts, a named person approves | Approval edits get small and the argument holds. |
| Automated | A workflow on a schedule or trigger. Internal steps run alone. Anything a buyer sees still waits for its approval. | The read against comparison accounts says keep the play. |
Workflows a play might need
Illustrative: Northwind's play for new VPs of Operations. Companies, people and numbers are fictional.
| Workflow | Runs when | Where the result lands |
|---|---|---|
| New-hire signal | A target account names a new VP Operations | The owning SDR's Slack queue, with an account brief |
| Pricing-page alert | An account visits the pricing page twice in a week | The account owner's queue |
| Contact and phone coverage | A new target account is added | CRM contacts, sourced across several providers |
| Account tier refresh | Every Monday | Tiers in the CRM, from fit plus back-tested signals |
| Call summary to CRM | A recorded call ends | The opportunity record, plus the next task |
| Play read | Every Friday | A Slack post for the SDR manager: touches, replies and meetings, against comparison accounts |
Why most automations break quietly
The usual approach
- Zaps built one at a time by whoever had a spare hour
- Built before anyone knows the play works
- No owner, so it breaks silently when a field changes
Play first, then automate
- Mapped against where hours and pipeline are lost
- Automated after the play earns it, then read against accounts that didn't get it
- Documented, monitored and owned by someone on your team
How we keep them honest
Tools that fit
Clay, Zapier, n8n or your CRM's own workflows where they fit. Code where they don't.
AI steps only where they help
Research an account or summarize a call inside an otherwise fixed sequence.
Retired with the play
When a play is retired, its workflows are switched off too, so nothing keeps spending credits for a play nobody runs.
What workflows do at each step
- Step 011
Connect your data
Move tool data into your warehouse and keep it fresh.
- Step 022
Prioritize by revenue impact
Automate the steps around your costliest buyer decision first.
- Step 033
Ship into the tools your team uses
Land results in your CRM, sequencer or Slack, where people already look.
- Step 044
Keep improving
Get reviewed with the play each week, and go when the play goes.
Where to start
Implementation
Implementation takes a play that works to production, including the workflows it needs. Managed Agents keeps them running.
Before you book
How is this different from Zapier or our CRM's workflows?
We use those where they fit and write code where they don't: AI steps, your full data, logic they handle badly. If you already run a dozen, we start by asking which ones change who gets worked or what they hear.
Will you run the automation for us, like an agency?
Not like an agency. We build it in your accounts with the people who'll use it and train its owner. If you'd rather we run it, that's Managed Agents, and you still own everything.
Workflow or agent?
If the steps are always the same, a workflow. If the path depends on what it finds, an agent. Workflows cost less and behave more predictably.
What happens when one breaks?
It alerts the owner, and the run history in the tool shows where it stopped.
Where's your line stuck?
Find the hours you're losing
30 minutes. Bring the work your team repeats every week. We'll tell you what's ready to automate and what isn't.
Book a call