Intern
What you actually do
Two personas or one writer test. Loser URL killed. You are not installing a second quiz 'to compare'.
Library / Compare / ScoreApp vs Typeform: one door per job, answers on the contact
ScoreApp is a scored door with bands. Typeform is a logic/UX door. GHL forms are a writer. The leak is two quiz tools plus a GHL form, all half-mapped. Choose by whether you need bands that split journeys, or long logic, or neither — then one door, fields on the contact, high vs low paths if you score. This is not a template beauty contest.
ScoreApp is a scored door with bands. Typeform is a logic/UX door. GHL forms are a writer. The leak is two quiz tools plus a GHL form, all half-mapped. Choose by whether you need bands that split journeys, or long logic, or neither — then one door, fields on the contact, high vs low paths if you score. This is not a template beauty contest.
ScoreApp is right when a band should change the journey (book vs slow proof) and you will map answers. It is wrong as a lead magnet that everyone still gets the same Calendly email.
Typeform is right when logic/UX is the named gap and write-in is true. It is wrong for taste, or as a second quiz beside ScoreApp.
GHL forms are right when the job is a straight writer and you want fewer tools. They are wrong only if you have a real logic/band gap you refuse to fake.
Shared leak: CSV, notes blob, one workflow for all outcomes, sales opens the quiz tool to prep.
How to choose: do you need a band? If yes, ScoreApp (or a scored Typeform, not both). If you need long logic without a score, Typeform. If neither, GHL form. Kill the extras. Wiring this week: keep/kill, field map, two persona tests if scored, UTM, inbox demoted.
Intern
Two personas or one writer test. Loser URL killed. You are not installing a second quiz 'to compare'.
Operator
One door per job. Bands only if paths differ. GHL is prep. Inboxes die.
CEO
A quiz that does not change CRM state is content. One door with fields is the system. Extra form tools are a tax.
Door (quiz/form), band or logic result, GHL fields, high vs low path, CSV habit, UTM hidden fields, sales-visible answers.
One public door per job (quiz or apply or contact)
Answers → named GHL fields the same day
If scored → high path ≠ low path
Typeform/ScoreApp inbox is not the CRM
Qualify, apply, contact, magnet. One.
Why: A door trying to be all four is four writers.
Done when: One job on the spec.
If high vs low must differ, you need a score tool. If not, do not add ScoreApp for fun.
Why: Scores without path splits are vanity.
Done when: Band table or 'no band'.
ScoreApp or Typeform or GHL. Unpublish the others for this job.
Why: Two doors split brains and UTMs.
Done when: Loser URLs dead.
Fields, not notes. High/low if scored.
Why: Otherwise sales will leave GHL.
Done when: Two completes, two paths or one straight writer.
GHL is the list.
Why: Inboxes recreate the vault.
Done when: A week of follow-up from GHL only.
Bands change journeys. Answers on fields. High books, low proofs. Wiring: webhook, two tests, CSV off.
Logic/UX gap, one job, write-in true, no second quiz. Wiring: map, UTMs, partials rule, inbox demoted.
Vault + CSV + one email for all outcomes + sales in the quiz UI. Tool brand does not install a path split.
Band needed? Logic needed? Else GHL. One door. Fields. Kill extras this week. Beauty is not a third tool.
That can be two jobs. Two quizzes for one job cannot. Write the jobs. If they collide, pick one.
Enough to pick it as the one door. Not enough to skip the band split and field map.
Same rule as Typeform: writer to spec. Do not collect a fourth door.
This week
This week: job of the door, band yes/no, pick one tool, field map, persona tests, unpublish extras.
Both can be a filing cabinet. Neither is a system until write-in and stages are jobs.
Read ↗Pretty vs native does not matter if two links both take Discovery.
Read ↗DTC lifecycle and coaching spines are different jobs. Two senders is a tax.
Read ↗Rebuilding from memory every client is how you never productize. Blasting a zip is how you never train.
Read ↗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.