From Free Scan to $1,200 Client in 11 Days — A Walkthrough

Eleven days, one cold email, zero calls until day 6. This is a realistic (hypothetical, composited from how this plays out in practice) walkthrough of turning a free scan into paid work: the exact sequence, not the highlight reel.

Day 1: Picking the target

The niche is boutique dental practices in a mid-size city, 20 sites pulled from Google Maps and a local directory. Most run on generic templated platforms with almost no blog content, which is exactly the profile that scores worst on AI visibility.

Day 1: Running the scan

A Litmus scan on the first practice's homepage takes a few minutes. The results: composite score 41/100. The worst dimensions: blog visibility (practice has zero blog posts, just service pages), content freshness (last updated over a year ago, no visible dates anywhere), and technical access (the site's robots.txt blocks GPTBot entirely, probably from a template default nobody touched).

Day 1: The email

Subject line: "ChatGPT can't recommend [Practice Name] right now"

Three sentences. The robots.txt finding, a screenshot of the score, an offer to send the fix list free. Sent at 9am.

Day 3: No reply. Follow-up sent

A short follow-up naming the second issue (content freshness) with one added line: most competitors in the same city scored better on this exact check, without naming which competitor. Curiosity plus mild competitive pressure works better than the technical detail alone did in email one.

Day 6: Reply, first call

The practice owner replies asking what "AI visibility" actually means for a dental office. The honest answer: increasingly, patients ask ChatGPT or Google's AI Overview things like "best dentist near me for [specific procedure]," and if the site isn't structured to be readable and citable by those systems, it doesn't show up in that answer even if it ranks fine on classic Google search. A 15-minute call, no pitch deck, just walking through the exported PDF report screen-share, dimension by dimension.

Day 6: The offer

A fixed-scope proposal, not a retainer: fix the top 4 issues (robots.txt, add publish/update dates to service pages, add FAQ structured data to the two highest-traffic service pages, publish 3 starter blog posts answering real patient questions) in 10 business days, re-scan, show the delta. Price: $1,200, half upfront.

Day 7: Signed and paid deposit

No negotiation on price. The scope was concrete enough that there wasn't much to argue about. Deposit paid via a simple invoice link.

Days 8-16: The actual fix work

The robots.txt fix takes 20 minutes. Adding dates and basic schema to two pages takes an afternoon with Claude or Cursor doing the JSON-LD generation and copy edits, reviewed and adjusted by hand. This is the part where AI coding tools make the fulfillment side genuinely fast, not just the pitch side. The three blog posts (each answering a specific, real patient question in answer-first format: direct answer in the first two sentences, detail after) take roughly half a day each including research and a review pass.

Day 17: Re-scan and delivery

Composite score moves from 41 to 68. Blog visibility alone jumps the most: going from zero posts to three well-structured ones is the single highest-leverage change available on a site like this. The before/after PDF, screen-shared on a 15-minute call, is the whole "close."

Day 17: The retainer pitch

With the score movement as proof, the follow-on offer: $400/month for one new blog post plus a quarterly re-scan and a freshness pass on existing pages. Accepted on the same call. It's a much easier sell after the number already moved once.

What made this work

Nothing about this required deep SEO expertise. It required running a scan, reading a report that's already organized by severity, and using AI tools to execute the fixes efficiently. The entire cycle (cold email to signed retainer) ran 17 days with maybe 6-8 hours of actual work spread across it. It's the same audit-first sequence AiViREX ran on its own client sites before packaging Litmus as a standalone tool.

Where this breaks down

Not every prospect replies, and not every reply converts. This walkthrough is a "it worked" case, not the average case. Expect to run this sequence against 15-20 prospects to land one client like this. The mechanics don't change; what changes is how many times you have to repeat them before one lands.

Q: Is this a real client story or a composite?

A: It's a realistic hypothetical built from how these engagements actually unfold in practice, not one specific real transcript. The numbers and sequence are representative, not a verified case study.

Q: Could the blog posts really be written that fast?

A: With AI tools handling first drafts and research pulls, and a human doing fact-checking and voice editing, three solid 800-word posts in 1.5 days per practitioner is realistic for someone who's done this a few times.

Q: What if the client asks for a bigger discount before signing?

A: Hold the price, adjust the scope instead: fewer blog posts or a longer timeline rather than a lower number. Discounting the price trains the client to expect it again at renewal.

Q: Does the score jump always look this good?

A: Sites starting from a very low baseline (no blog, blocked crawlers, no dates) see the biggest jumps, because there's the most low-hanging fruit. A site that's already at 70+ won't move nearly as dramatically from the same amount of work.