Segment first, then branch
Open with a role or category question and route each answer to its own section. You get comparable segment sizes and each group answers questions that make sense for them.
A market research survey exists to produce numbers you can act on: which segment wants what, how much they will pay, and which of two directions is worth building. It is the survey type most often ruined by good intentions, because the temptation is to ask everything.
Not a stock template. Build it in a few minutes from a blank form, or describe it and let AI draft the questions on a paid plan.
The discipline is closed-set questions. A free-text box in a survey of four hundred people is four hundred paragraphs nobody will read; a budget allocator in the same survey is a chart that answers the question you asked.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| Which best describes your role? The segmentation question, branch on it | Dropdown |
| How big is your organisation? Bands, so the answers aggregate | Multiple choice |
| How do you solve this today? | Checkboxes |
| Rate how well each of these works for you | Rating grid |
| Split 100 points across these priorities Forces the trade-off a rating question lets people dodge | Budget allocator |
| Rank these in the order you would want them | Priority matrix |
| What would you expect to pay for this? Price bands, never a number box | Multiple choice |
| What would stop you buying it? The one open question. Keep it to one | Paragraph |
Open with a role or category question and route each answer to its own section. You get comparable segment sizes and each group answers questions that make sense for them.
A budget allocator gives respondents a fixed total to divide, and a priority matrix makes them rank. Both prevent the outcome where every option is rated "very important" and nothing is learned.
Willingness to pay as a multiple choice of bands, not an open number. Bands compare across respondents; free-text prices do not.
Send the survey to a contact list in paced batches, embed it, or share the link. There is no respondent panel to buy from, you bring the audience.
One segmentation question, a behaviour question about what people do today, one forced trade-off (budget allocator or priority matrix), a price band question, and one open question about objections. Everything else is usually curiosity rather than research.
It charts closed-set questions in the response summary and exports everything to CSV. There is no cross-tabulation, weighting, or significance testing. Take the CSV into a spreadsheet for that.
No. There is no respondent panel. You reach your own audience by link, embed, or an emailed contact list.
Only for segment-specific follow-ups. Branching means two respondents did not answer the same questions, so keep anything you intend to compare on the path everyone takes.
Scales, grids and summaries, questions built to aggregate.
Feature19 types, including specialist ones most builders skip.
FeatureRoute each answer choice to its own section, so people only see what applies.
TemplateCSAT and NPS with the follow-up question matched to the score.
TemplateRate the experience, then ask the follow-up that fits the rating.
TemplateAsk the budget, timeline, and fit questions before the first call.
Use caseRun satisfaction and product-feedback surveys where the follow-up question depends on the answer you just got.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.