Lead Follow-Up SOP Template
Fortunes Fortuna

Purpose
Use this SOP when inbound requests arrive, but replies depend on memory, shared inbox habits, or one person checking at the right time.

Daily Review
1. Open the lead queue once each workday before starting delivery work.
2. Filter to leads with next action due today or overdue.
3. Assign one owner before any reply is drafted.
4. Move each lead to the next clear status before closing the review.

Required Fields
- Received date
- Source
- Contact name
- Company or project
- Reply channel
- Status
- Owner
- Next action
- Next-action date
- Last reply date
- Quote value when known
- Close reason when known

Suggested Statuses
- New: request arrived and needs first human review.
- Needs info: clarification reply is required before scope or price can be discussed.
- Qualified: request fits the offer and has enough context for a scoped proposal.
- Proposal sent: owner approved and sent a specific scope for customer review.
- Won: customer accepted and payment path is active.
- Delivery: work has started.
- Delivered: handoff is complete.
- Lost: lead declined or is not a fit.
- Archived: no current action pending.

First Reply Rule
Reply personally to real inbound requests only. Ask for missing workflow facts before quoting.

Clarification Questions
1. Where does the lead or request arrive today?
2. What should happen after it arrives?
3. What tool, spreadsheet, or inbox already tracks it?
4. Who owns the next action?
5. What deadline or urgency applies?

Follow-Up Rule
Every active lead must have one owner, one next action, and one next-action date. If any of those are missing, the lead is not under control.

Boundary
- Do not add contacts to unrelated campaigns.
- Do not use scraped lists, fake leads, or bulk unsolicited messages.
- Do not store passwords, wallet seed phrases, private keys, exchange credentials, or customer secrets.
- Do not add contract, invoice, BTC, or payment instructions without owner approval.

Build Trigger
If this SOP requires copying between inboxes, spreadsheets, invoices, and delivery notes, a small workflow build is usually safer than relying on memory.

Related resources:
- https://fortunesfortuna.com/resources/lead-response-risk-calculator.html
- https://fortunesfortuna.com/resources/revenue-workflow-scope-builder.html
- https://fortunesfortuna.com/demos/lead-follow-up-board.html