Workflow
Follow-up sequencer
The follow-up happens on schedule whether or not anyone remembered.
- By
- Caleb and Ryan, the founders
- Updated
- September 2, 2026
- Version
- 0.1, in the library
- n8n
- Make
After a call, a proposal, or a quiet week, the right follow-up gets drafted from the actual history of the deal and queued for the owner to send. Timing rules are yours; the drafts sound like you because they are built from your own prior messages.
Built, documented, running.
Part of the working library we deploy from on every engagement.
Bring this into a project- Complete and documented: the same files we run ourselves.
- Deployed and tuned to your stack as part of an engagement.
The file
Draft excerpt# Timing after call: next morning, recap plus the agreed stepafter proposal: day 3 if silent, day 7 with a new anglealways: the owner sends; the system drafts and waitsstop: any reply, or the owner says stop
What is inside
3 items. Includes deployment guide.
flow.jsonTriggers, timing rules, draft queuetiming-rules.mdWhen each follow-up fires, and when it stopsguide.mdKeeping the human on send
Who it is for
- Deals go cold in the week after a good call.
- Follow-up quality depends on how busy the rep was that day.
- Proposals go out and enter a silence nobody manages.
Requirements
- CRM with deal activity
- An outbound channel (email, connected)
Where this sits
This system
Follow-up sequencer
In the library, running.
In your stack
The audit finds which system earns its place first; we install and tune it around how you work.
Changelog
- September 2, 2026In the library. Version 0.1 runs in our own operation.
Related
- Featured
Workflow
Speed-to-lead pack
A form fill becomes a booked call in under a minute
Works with n8n, Make.
Built and running Agent pack
Post-call brief to CRM
The call ends and the CRM is already done
Works with Claude Code, n8n.
Built and runningWorkflow
Lead intake router
Every lead from every door lands in one queue, deduped and routed in seconds
Works with n8n, Make.
Built and running