Resources
Everything we have
written down.
This page indexes everything on the site that is not a product or sector page: guides on survey design, a glossary of survey terminology, the help centre, the blog, four competitor comparisons, and the trust documents — security, UK GDPR, the sub-processor list and the accessibility statement. If you are trying to answer a procurement question, start in the trust column. If you are trying to write a better survey, start with the guides.
Some of these sections are still filling up. Where that is true, the page says so rather than padding itself out with filler.
Learn
Guides
Long-form, step-by-step writing on survey design — question wording, branching structure, scoring models, running a consultation. Nothing is published yet; the page lists what is coming and where the answer already lives.
Glossary
Plain definitions of the vocabulary that surrounds surveys: matrix questions, piping, branching, Likert scales, screeners, response and completion rates.
Blog
Notes on what we are building and why, and on the parts of survey work that are more opinion than fact. No posts published yet — the page sets out the four strands it will carry.
Help centre
Task-shaped answers for people already inside a survey: where a setting lives, what a toggle does, why a question is not showing.
Trust and compliance
These four pages exist because public sector, education and healthcare buyers ask the same questions in the same order, and deserve a written answer rather than a sales call.
Security
Where responses are stored, how organisation isolation is enforced, what happens to uploaded files, and which claims we are not making.
UK GDPR
Controller and processor roles, lawful basis, data subject rights, and what to do when you need a DPIA answered.
Sub-processors
The full list of third parties involved in delivering the service, what each one does, and where it processes data.
Accessibility statement
The standard we build respondent-facing surveys against, what is tested, and the known gaps rather than a blanket claim of conformance.
How the site is organised
There are four kinds of page here, and knowing which one you want saves a lot of clicking.
Feature pages describe what the software does
One page per capability, written to be specific rather than persuasive: conditional logic and its any/all rule matching, the 16 question types, scoring, weighting and bands, save and continue, file uploads, CSV and PDF exports, and per-survey partner logos. The product overview ties them together.
Solution pages describe who has the problem
The same product seen from six angles — local government, charities, education, healthcare, market research and HR. Nothing about the software changes between them; what changes is which capability you will actually lean on and which questions a buyer in that sector is obliged to ask.
Resource pages teach something
Guides, the glossary and the blog are meant to be useful whether or not you ever open the builder — writing a matrix question well matters even if you are running the survey in something else entirely. The glossary is live; the guides and the blog are still being written, and both pages say so rather than listing articles that do not exist.
Trust pages are evidence
Survey content and responses are stored on Supabase in London
(eu-west-2), encrypted in transit and at rest, with
row-level security throughout and organisation isolation pinned
server-side. Uploaded files sit in a private bucket, read through signed
URLs that expire after 300 seconds. We are not ISO 27001 certified and
have not completed a SOC 2 audit, and the
security page says so plainly rather than
implying otherwise.
Comparisons
Written against each competitor's own public documentation, with the date we checked it stated on the page. Where a rival does something better, the comparison says so — all four comparisons start from the same index.
Reading is not building.
Most questions about a survey tool are settled faster by putting a real question set into it than by reading another page. When you have finished testing, clear the test responses — uploads and half-finished sessions go with them.
- Feature, solution, resource and trust pages, all indexed above
- Comparisons written against each rival’s own documentation
- Survey content and responses stored in London
