The questions engine
Your contact form and your customer survey are the same thing
Which is why the form on your website can branch, score and report like a research tool — and why the answers end up on the customer instead of in someone else's database.
Most businesses buy a form builder, then a survey tool, then something for NPS, and end up with three products that each hold a few answers about the same person. None of them can see your customers, so every insight needs exporting before it means anything.
Here there is one engine, and it sits inside your marketing rather than beside it. A contact form is a questionnaire with one screen. A recommendation quiz is a questionnaire that branches. An NPS run is a questionnaire with one question on a schedule. Because they are the same object, the humble form on your website inherits everything the research tool can do — and every answer lands on the customer record where the rest of their history already is.
The same engine, six jobs
A contact form
The front door. Lands as a real lead with the answers attached, not an email you have to re-type into something.
A qualifying quiz
Score the answers and route accordingly — the same run can tell the visitor what suits them and tell your team how serious they are.
A recommendation flow
Branching questions that narrow to an answer, so a visitor who does not know what they need can arrive at it themselves.
A customer survey
Sent to a named audience, chased when they do not reply, reported when they do.
An NPS run
Ask the one question on a schedule and watch the number move rather than guessing.
An intake questionnaire
Everything you need before the job starts, asked once, stored on the customer.
What it does that a form builder does not
Branching, so nobody answers questions that do not apply
Questions can be grouped and connected, and a run follows the path the answers open. The shortest honest questionnaire is the one that finishes.
Version history, with revert
Edit a live questionnaire and the previous version is still there to go back to. Anyone who has broken a running survey at 9pm understands why this matters.
Send it to people, not just to the internet
Build an audience, invite them, see who has not answered, and remind exactly those people. Response rate is mostly a chasing problem, and chasing is the part everyone skips.
Or publish it to anyone
A public link that works with no login at all, stepping through one question at a time — the same questionnaire, no account required.
Reporting that is more than a list of answers
Per-question aggregates and a cross-question matrix, so you can see how one answer moves with another rather than reading responses one at a time.
Help writing the questions
Suggested questions for what you are trying to learn, because the reason most surveys are bad is that writing good questions is genuinely hard.
Duplicate what worked
Copy a questionnaire and adjust it, rather than rebuilding the good one from memory every quarter.
The answers are the point
A form tool gives you responses. This gives you a customer who now has answers attached — so the quiz that recommended a package is visible on the same record as the quote you later sent, the job you did, and what they paid. That is the difference between collecting data and knowing something.
Build one
The template ships a paste-ready recipe for building a public quiz, survey or recommendation flow on your own site. The repository is always the most current reference.