PRACTICAL SAAS LAB | LEAD FOLLOW-UP WORKSHEET
Version 1.0 | 2026-09-30 | Free editable template
Guide: https://practicalsaaslab.com/lead-follow-up-process-small-service-team/

START HERE
Copy the blank record for each enquiry into your shared document or CRM.
Use a record ID; keep personal contact details in your approved customer system.
Agree a response deadline and stop rule before assigning records.
Example below is fictional, not a measured customer result.

BLANK ENQUIRY RECORD
Record ID:
Request / service needed:
Stage and evidence supporting it:
Named owner (one person):
Next action (verb + outcome):
Due date and time (include time zone):
Last contact / outcome:
Backup owner:
Pause / stop reason and review date:
Link to approved customer record:

FICTIONAL EXAMPLE
Record ID: DEMO-001
Request: Email migration for a small consultancy
Stage and evidence: Qualified; scope call completed and decision contact confirmed
Owner: Alex
Next action: Send a proposal covering the agreed scope
Due: 2026-10-02 15:00 Europe/London
Last contact: 2026-09-30; buyer requested a phased proposal
Backup: Morgan
Pause / stop: Not paused; review after the agreed follow-up date
Customer record: [internal link]

DAILY QUEUE REVIEW
[ ] Every open record has one owner, next action and due time.
[ ] Overdue work is completed, reassigned or rescheduled with a reason.
[ ] Paused work has an owner and review date.
[ ] Duplicate enquiries do not trigger conflicting outreach.
[ ] Declines and requests to stop are respected.

WEEKLY REVIEW RECORD
Review date:
Open records reviewed:
Unassigned records:
Overdue next actions:
Records paused without review date:
What failed / one change to test:
Change owner and next review:

USE NOTES
A due date says when to act; a stage says what evidence exists.
Choose your own response cadence. This template does not prescribe repeated
contact after a request to stop. Do not paste passwords or payment details.
You may copy and adapt this template for your own business workflows.
