Structural Diagnostic · Worked example

The lead-intake system of this website.

A sample diagnostic is only worth reading if the system in it is real, so this one is about mine. It was run on the parts of ampwriter.com that turn a visitor into a conversation: the diagnostic form, the newsletter forms, the chat widget, and the offer itself. The findings are exactly what I found. The fixes are live on the page you're reading.

Systemampwriter.com lead intake
DiagnosedNov 14, 2026
TreatedNov 14–15, 2026
StackNetlify, static site, Claude Code

1. Where it depended on someone remembering

On paper, every lead had two homes. Each form submission was stored by Netlify Forms and copied to an n8n automation workflow. In practice, the copy went to n8n's test webhook address, which only accepts requests while the n8n editor is open on someone's screen. The second home never received anything. Netlify kept the submissions, but nothing told anyone they were there.

That matters because of what the form promised: "Delivered to your inbox within 24 hours." The promise depended on a person checking a dashboard nobody had a reason to open. Had a real request come in on a busy week, it would have sat there until someone happened to look. The two systems were connected in the sense that data passed between them. They were never actually joined, and the gap had to be bridged by memory.

The chat widget was a second entry point with its own problems. It opened by itself five seconds after page load, greeted visitors with "Hey 👋—looking to get more leads?", and told them that "most clients recoup the investment in the first 30 days," that builds take one to two weeks (the standard here is four), and that I "usually reply instantly." None of that was true of how this practice works. The setting meant to turn auto-open off didn't work either: a zero was silently replaced with four seconds in the code.

2. What the system couldn't see

One more thing turned up along the way: the homepage's hero video had been returning a 404 since July, because the file was never uploaded. The first thing on the page had been an empty box for four months.

Diagnosis. Lead intake ran on two systems that were connected but never joined, with a promise on top that only memory could keep. Adding another tool or a faster integration would have automated the gap, not closed it. The fix had to be structural first: one place leads land. Then a loop that checks the promise without anyone needing to remember to check.

3. What was fixed, in the order it had to be fixed

Priority 1: one place for every lead

The n8n copy and the webhook function behind it were removed. Every entry point (diagnostic form, newsletter forms, and the chat widget, which now has its own form) writes to Netlify Forms and nowhere else.

Why first: a feedback loop needs a single source to watch. With two homes, one of them broken, any monitoring would have watched the wrong one.

Priority 2: an offer and copy that match the practice

The chat widget was rewritten in the site's own voice, every claim it couldn't back up was removed, and it no longer opens by itself. A paid first step was added: the Structural Diagnostic, the document you are reading the format of. It's $1,500, credited in full toward a build.

Why second: intake only needs to be reliable once the page is asking for the right thing.

Priority 3: a loop that checks the promise

A script now pulls every form and chat submission, logs it to the project tracker, and flags anything unanswered for more than two business days. It runs automatically at the start of every working session, so the check doesn't depend on remembering to check. The public promise was rewritten to what the loop can actually guarantee: a personal reply within two business days.

Why third: the loop can only measure a process that exists in one place, which Priority 1 created.

Priority 4: next

When the first client engagement completes with permission to publish, its diagnostic replaces this one as the lead example.

4. What changed for the person doing the work

No step was handed to a machine that should stay human. I still read and answer every lead myself. What changed is that the system now does the remembering: it collects every lead in one place, says when one is waiting, and says when the promise is about to be broken. My time goes to the reply instead of the inbox.

5. What it would have cost as a client engagement

Line itemScope hereFee
Structural DiagnosticThis document: findings, sequence, role note, quote$1,500
Lead Capture & Follow-UpSingle intake, chat-lead form, unanswered-lead loop$1,500
Less diagnostic creditBuild signed within 30 days−$1,500
Total$1,500

Copy rewrites and the hero repair would sit outside a fixed-fee build. They're listed here because a diagnostic reports everything it finds, not just what it can sell.

Run one on your operation.

Ten business days. A map of where the work depends on someone's time, the three fixes that matter most in the order they have to be built, which roles change, and a fixed quote. $1,500, credited in full if you build within 30 days.

Book a Structural Diagnostic →