Intern
What you actually do
You run the lab. Screenshots. One email. You do not build a dedupe Zap when the test duplicates.
Library / Tool / Write-in test: one person, three actions, one contact
Write-in is how you know GHL is a system. This checklist is a one-hour lab: submit the live form, book the live calendar, mark a payment (or $1). You should see one contact, stages that moved as jobs, UTMs if the URL had them, and the first spine message. Calendar full and pipeline empty fails the test.
Write-in is how you know GHL is a system. This checklist is a one-hour lab: submit the live form, book the live calendar, mark a payment (or $1). You should see one contact, stages that moved as jobs, UTMs if the URL had them, and the first spine message. Calendar full and pipeline empty fails the test.
Use production paths. Staging lies. Thank-you redirects drop UTMs in production.
Do the three actions in one hour with one email.
If you needed to merge, stop. Fix email match. Do not celebrate a 'dedupe automation'.
Notes blobs fail. Answers should be fields.
This test is a weekly habit after any page, calendar, or snapshot change.
Intern
You run the lab. Screenshots. One email. You do not build a dedupe Zap when the test duplicates.
Operator
Production paths. After every change. Identity key is email (and phone rule). Notes are not fields.
CEO
Write-in % on this test is the gate. Until it is 100% on form and book, more traffic is more leak.
Throwaway email, live form, live calendar, payment, contact, opportunity, UTM fields, spine, duplicate check.
Form → contact + mapped fields
Book → same contact, stage booked
Pay → Won or customer; spine/onboarding correct
Second submit same email → update, not a second person
Email + phone you control. URL with test UTMs.
Why: You need to see mail and SMS.
Done when: Identity written down.
Through thank-you. Open GHL immediately.
Why: Lag stories hide mapping bugs.
Done when: Contact exists, fields mapped.
Same email. Confirm opportunity moved.
Why: This is the calendar-as-second-database test.
Done when: One contact, stage booked.
$1 on a real price or a documented test mode.
Why: Won without pay is the other lie.
Done when: State matches money.
Same email, different last name or UTM.
Why: Duplicates are the identity bug.
Done when: Still one contact.
Run the hour. Screenshot each step. Fail is a ticket, not a vibe. You do not 'clean it later'.
Refuse new pages and spend until the last write-in test passed. This is the cheapest gate.
Staging only. Merge after. UTMs empty. Calendar full, board empty. Team says GHL is flaky.
The checklist below is the test. All boxes or it failed.
In addition, yes. Not instead. Production redirects and live calendars are the leak.
Then skip pay, but write 'Won untested' on the sheet. Do not pretend Won is true.
After every writer change, and once a week anyway. Tokens die.
This lives in the browser until you copy it out. The point is to write the spec before anyone opens Workflows or Flows. Print or screenshot when it is true.
You can receive SMS and email.
Not the GHL preview only.
Fail if dump-in-notes.
Empty = thank-you or hidden fields failed.
New contact = identity fail.
Empty pipeline = second database.
Calendly + GHL both = fail.
Within an hour.
Do not silently skip.
Merge needed = fail. Fix match key.
Date + URL. This is the artifact.
This week
This week: run the full checklist on production, file tickets for every fail, no new landing until form+book pass.
Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.