The CRM is a read-intensive reporting and opportunity intelligence layer placed on top of existing business outreach processes. Businesses are already imported, batched, messaged, moved through pipeline statuses, and sent outbound communications. The CRM does not manage pipeline movement — it reads the data produced by existing processes and provides reporting, comparison, opportunity detection, and performance insight to improve future batches.
Core responsibility: Segregate batches · Report pipeline status per batch · Compute response % · Identify opportunities from response data · Compare batches and messages · Surface performance levers · Drive improvement in future cycles.
Click any node for its detailed plan. Lanes marked Existing are handled by existing processes — the CRM reads from this data but does not manage it.
Lane 1 — Existing Processes (data sources)
Actor: existing systems · CRM reads from these, does not manage them
Actor: CRM · scans response data to surface commercial opportunities
→→→→
Lane 4 — Response Comparison
Actor: CRM · compare batches, messages, and time periods to find what works
→→→
Lane 5 — Performance Metrics & Improvement Levers
Actor: CRM · surface metrics and what to change to improve the next batch
→→→→
What the CRM does
Reads existing data and reports on it: Segregate businesses into batch views · Report pipeline status per batch · Compute response % per batch · Drill into individual business history · Compare batches, messages, time periods, channels · Identify warm leads, stalled businesses, preview-needed, activation-ready, upgrade candidates · Compute performance metrics · Model what-if improvements · Recommend changes for next batch.
Does NOT do: Move businesses through pipeline statuses (already handled) · Create or send outbound messages (already handled) · Create or manage batches (already handled) · Generate websites or process payments (EP044/EP047).
Statuses the CRM reports on
The CRM does not manage these — it reports on them as a read-only view of pipeline data from existing processes.
Active pipeline: Identified → Ready for outreach → Email sent → Awaiting response → Responded (positive) → Responded (interested) → Follow-up required → Listing claim started → Listing claimed → Website preview sent → Website preview viewed → Activation pending → Website activated → Social lead service offered → Converted
Terminal: Not interested · No response · Follow up later · Disqualified
What-If modelling concept
The CRM should allow tuning key variables and seeing the projected impact on downstream outcomes:
Response rate slider: "If we improve response rate from 12% to 18%, how many more claims would we get from a batch of 25?"
Positive rate slider: "If we improve positive rate from 40% of responses to 55%, how many more activations?"
Conversion rate slider: "If we improve preview→activation conversion from 30% to 45%?"
Batch size tuner: "If we increase batch size from 25 to 50?"
Display: Projected claims, activated sites, revenue per batch and cumulative
Key metrics definitions
Per batch
Emails sent · Responses received · Response rate (%) · Positive responses · Positive rate (%) · Claims → Preview viewed → Activated → Converted · Per-status counts · Revenue generated · Avg days in pipeline · Time to first response
Per message version
Sent · Response rate · Positive rate · Claim rate · Activation rate · Revenue · Rank vs other versions
Pipeline health
Count per status · Avg dwell time per status · Stage drop-off rate · Stalled businesses · Bottleneck stages · Total pipeline time