- Business website and service area.
- One lead source: web form, call log, marketplace lead, email thread, or old estimate list.
- 10-25 redacted rows, screenshots, or exported lines.
- A note on the main problem: missed calls, stale estimates, unclear owner, bad source, or risky draft replies.
Safe first-scan packet
Send enough evidence to diagnose the leak, without sharing private access.
Use this packet before the $197 AI Leak Scan. It keeps the first step small: up to 25 redacted lead records, one lead source, the business website, and a plain note about what feels stuck.
- Customer names, phone numbers, emails, street addresses, payment notes, and private job details.
- Anything that is not needed to understand status, timing, source, owner, or next action.
- Recordings or full CRM exports unless George asks for a safer alternative later.
- Passwords, one-time codes, payment cards, customer lists, admin logins, or full private exports.
- Requests to contact customers automatically.
- Promises you need George to make about job outcomes, recovered revenue, rankings, or customer responses.
What a useful redacted row looks like
Source
Google form, website chat, LSA call, old estimate, marketplace lead, or referral.
Timing
Received date, first reply date if known, and whether the lead is still recent enough to handle carefully.
Current status
Quoted, no answer, duplicate, wrong service, waiting on photo, do-not-contact, or owner unclear.
The first scan is a diagnostic. It is meant to show which rows are safe to handle, which need context, and which should not be contacted.