Customer Onboarding Questionnaire: What to Ask (+ Template)

The best customer onboarding questionnaire is short, specific, and only asks for information you cannot get anywhere else. The research puts hard numbers on "short": 70% of customers abandon an onboarding process that takes more than 20 minutes, and 10-question forms average 28% lower completion than 3-question forms. Roughly 15 questions is the ceiling, and every one has to earn its place.

This guide covers the 15 questions that consistently earn their place in B2B SaaS onboarding, the questions to delete because sales already answered them, a copy-ready template, and the delivery tactics that decide whether the form comes back in two days or never.

What is a customer onboarding questionnaire?

A customer onboarding questionnaire (also called a client intake form) is a structured set of questions you send a new customer right after the deal closes, usually as part of the sales-to-onboarding handoff. Its job is to capture the stakeholders, goals, technical constraints, and logistics you need to run a sharp kickoff and build the onboarding plan.

It is worth getting right because onboarding is where retention gets decided. Companies with a strong onboarding process see 50% higher new-customer retention, and over 90% of customers feel the companies they buy from could do better at onboarding. The questionnaire is the first working artifact of the relationship, and it signals either "this team is organized" or "this will be a long six months."

Why do customers ignore onboarding questionnaires?

Because most are too long, too generic, and ask the customer to repeat things they already told your sales team.

The completion data is blunt. Across billions of form sessions, the average form completion rate is 51.7%, and that includes forms people need for their own benefit, like applications and checkouts. Anything that reads as a survey does far worse in B2B: the average B2B NPS survey response rate is 12.4%. Length compounds the problem, with field-level tests showing completion peaking at 4-6 fields (51%) and falling to 31% at 7 or more.

Redundancy is the quieter killer. 65% of customers say they often have to repeat information to different teams. Gartner found that 60% of software buyers regret a purchase, and 43% name a problematic handoff between sales and implementation as a top driver. Nothing signals a broken handoff faster than an intake form asking "what are your goals?" three weeks after your AE ran a discovery call about exactly that.

Picture the usual failure: kickoff is Thursday, the questionnaire went out ten days ago, and it is still sitting unopened next to 40 other unread emails in your champion's inbox. The fix is a shorter form, delivered better, at the right moment.

What questions should a customer onboarding questionnaire ask?

Only questions you cannot answer from the sales cycle, your CRM, or the customer's website. That single filter, which Dock's guide to client questionnaires also treats as the golden rule, usually cuts a bloated form in half. What remains falls into four groups.

Stakeholders and decision rights (questions 1-4)

Sales usually knows the champion and the economic buyer. What they rarely capture is who does the work and who can unblock it. Hidden stakeholders surface in week 6 otherwise, usually holding a security review you did not know existed.

1. Who is the day-to-day point of contact, and what channel and response time work best for them?
2. Who has final sign-off on go-live, and who can approve scope changes or escalations?
3. Which teams will use the product daily, and who represents those end users during setup?
4. Who is the technical contact for integrations, security, and access provisioning?

Success definition (questions 5-7)

You need the internal scoreboard, in the customer's own words, in writing. It becomes the anchor for every status update and the reference point if priorities drift mid-project.

5. What must be true 90 days after kickoff for this project to be called a success internally?
6. Which metric will you report to leadership to justify this purchase?
7. Are there hard deadlines shaping the timeline (contract dates, product launches, audits, renewals)?

Technical and data readiness (questions 8-10)

These answers drive the critical path. Data and access are the two places onboarding stalls first, so identify owners now, then run the collection process itself through your pre-kickoff data checklist.

8. Which systems must we integrate with on day one, and who owns each of them?
9. What data needs to move into the product before go-live, and where does it live today?
10. Which security, compliance, or procurement steps apply to vendors like us (SSO, DPA, vendor risk forms)?

Working logistics and history (questions 11-15)

The last group protects your schedule and surfaces risk early. Question 12 is the one implementers consistently call the highest-signal question on the form: previous failed attempts predict where this one will wobble.

11. What does your team's availability look like for the next 6-8 weeks (meeting cadence, blackout dates, competing projects)?
12. Have you tried to solve this problem before, and what happened?
13. What worries you most about this implementation?
14. How do you want status communicated (Slack, email, live dashboard), and how often?
15. Is there anything we have not asked that would surprise us later?

Field design matters as much as question choice. Forms that open with easy fields see 18% higher completion, requiring a phone number drives 37% more drop-off, and picklists outperform free text for anything standardized. Put names and dropdowns first, save open-ended questions for the end, and mark optional fields as optional.

What should you leave out of the questionnaire?

Anything your company already heard. Before adding a question, check the opportunity notes, the proposal, the mutual action plan, and the discovery and demo recordings. Goals, pain points, current tooling, and the reason they bought are almost always in there already.

This is also where AI earns its keep in onboarding. If your sales and discovery calls are recorded, Stipulate extracts the stakeholders, goals, risks, and commitments straight from those transcripts, so your questionnaire shrinks to the handful of questions nobody has actually asked yet. That is the difference between a 25-field intake form and 10 questions a champion can answer in eight minutes.

Cut nice-to-know questions without a downstream action, duplicate contact fields, and anything you could Google. Every field you keep is a tax on the person you most need goodwill from.

Copy-ready template: the 15-question onboarding questionnaire

Send the questionnaire with a short note that sets expectations. Something like:

"Welcome aboard! To make your kickoff on [date] count, we have 15 short questions, about 10 minutes. Your answers build the kickoff agenda and your rollout plan, so nothing gets asked twice. We have pre-filled what we learned during the sales process; please correct anything we got wrong. Stuck on a question? Skip it and [name] will pick it up on the prep call. We would love it back by [date, 3-5 business days before kickoff]."

Then the 15 questions from above, in compact form: day-to-day contact and preferred channel; go-live sign-off owner; daily-use teams and end-user rep; technical contact; 90-day success definition; leadership metric; hard deadlines; day-one integrations and owners; data to migrate and where it lives; security and procurement steps; team availability; previous attempts; biggest worry; status update preferences; anything that would surprise us.

Three delivery rules make the template work: give an honest time estimate, set a deadline tied to the kickoff prep call rather than a vague "when you get a chance," and state explicitly that answers get used (people abandon forms they suspect go nowhere).

How do you get customers to actually complete it?

Tie it to something the customer wants, keep it short, and remove friction. In practice:

1. Anchor it to the kickoff date. "We build your kickoff agenda from this" converts the form from admin work into schedule protection. A form with a consequence gets finished.
2. Pre-fill what you know. Auto-filling earlier answers into later questions lifts completion by 10%, and pre-filled sales-cycle facts show the customer you listened.
3. Front-load the easy fields. Names and picklists first, essay questions last, for that 18% completion lift.
4. Let autofill work. Properly labeled fields let the browser do the typing, and autofill users abandon forms at least 75% less often.
5. Allow save-and-resume. A busy champion rarely has 15 uninterrupted minutes. Purpose-built intake tools such as Content Snare, Dock, and Rocketlane support multi-session completion, automated reminders, and file uploads, which is exactly the gap that makes plain Google Forms feel cheap for a five-figure contract.
6. Ask the rest later. Progressive profiling, asking a little now and more as the project unfolds, beats one long form in 78% of A/B tests.
7. Chase on a clock. If the form is untouched after 5 business days, switch channels and offer to fill it out together on a 15-minute call. If the customer stays silent, escalate using the gone-dark playbook before the kickoff date slips.

Next steps

An afternoon of editing is usually enough to fix an underperforming questionnaire:

1. Print your current form and cross out every question sales already answered. Expect to lose a third of it.
2. Rebuild around the four groups: stakeholders, success definition, technical readiness, logistics. Cap it at 15 questions.
3. Rewrite the delivery email with a time estimate, a kickoff-anchored deadline, and pre-filled answers to correct rather than blanks to fill.
4. Track two numbers for the next quarter: questionnaire completion rate and days-to-return. Both belong next to your core onboarding metrics, because a slow intake form is an early warning for a slow go-live.

The questionnaire is a small artifact with outsized leverage: 15 good questions, asked once, at the right moment, save weeks of chasing later.