01
Working record and daily queue
Keep the lead record where the team already works. Due and overdue items form a daily queue with an owner, date, and reason for attention.
Current active product
Lead Follow-Up Control
A controlled follow-up workflow for founder-led service teams whose opportunities still depend on memory, scattered context, or an unreliable to-do list.
It works around your existing spreadsheet, Notion database, or CRM. The source stays familiar while the daily queue, human review, send record, and next action become clear.
Workflow
From lead record to evidence-backed next action
Lead The source record
Follow-up due Visible in the daily queue
Draft Prepared from known context
Human review Edit, approve, or block
Manual send External action stays human-controlled
Send logged Evidence records what happened
Next action A dated step keeps the loop alive
Approval ≠ sent. The record moves to sent only after the operator completes the external action and logs it. A dated next action then keeps the loop moving.
02
Drafting and human review
Drafts use recorded context. A person edits, approves, or blocks them. Approval means the content is ready; it does not claim the message has been sent.
03
Manual send and next action
The operator sends through the right channel and records what happened. Every open lead then receives a dated next step.
04
Exceptions
Missing context, conflicting records, stale dates, and duplicate candidates pause for attention with the reason shown.
Lifecycle states
A visible state model prevents false completion
OpenA live opportunity exists in the source of truth.
DueThe dated next action has arrived.
Draft readyA follow-up draft is available for review.
ApprovedThe operator has approved the content; it has not yet been sent.
SentManual send evidence has been recorded.
WaitingThe lead is awaiting a response with a dated next check.
ExceptionMissing context, conflict, or another blocker needs attention.
Changes
Fragile coordination
- Memory becomes a dated queue
- Disconnected reminders become one working record
- “Done” becomes a specific recorded event
- Activity history stays available for review
Keeps
Your relationship systems
- Your CRM, Notion database, or spreadsheet
- Human judgement over relationship context
- The person who reviews and sends messages
- Your chosen email, LinkedIn, or messaging channel
Internal implementation evidence
A reconciled baseline using real operating records
In September 2026, the internal working set reconciled across the queue and next-action record. This demonstrates the workflow controls rather than a customer result.
- 15 / 15
- real prospects with one scheduled follow-up task
- 15 / 15
- prospects with a dated next action
- 0
- missing next actions or duplicate tasks
- 0
- automated messages sent
Fit enquiry
Bring the current process, not a perfect specification.
Describe where leads live today, who follows up, and where the process becomes unreliable. We will assess whether this workflow fits.
Start a fit enquiry