Forms and surveys decision
ValidateThat
A single developer can build a useful core (card sorts, tree tests, embeddable collector and local analytics) in a multi-week project, but the full product's value depends on participant recruitment, AI synthesis and polished reports which are costly to replicate, so keeping the paid service makes sense for teams needing those extras.
Visit website↗$19/mo
$228/yr
Read off the official pricing page.
$100one-off60 h to build
$50/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 4 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All ValidateThat alternatives, with the arithmetic →
What a replacement has to do
- Create a study (card sort / tree test / first-click), publish it (host + embed snippet), collect responses, compute analytics (clusters, dendrograms, similarity matrices), export results.
What it still won’t have
- Built-in verified participant recruitment network (Prolific integration and credits)
- AI-generated synthesis, SWOT and transcript analysis
- Branded PDF reports and priority support
- Polish, reliability guarantees (99.9% uptime claim) and GDPR compliance attestation
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 4 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal UX-research service using React (Vite) frontend, Node.js (Express) API, and Postgres on a single DigitalOcean droplet; use D3.js for dendrograms and hierarchical clustering (js libraries) and Puppeteer or wkhtmltopdf for PDF export. In scope: (1) user sign-up and simple account pages, (2) study creation UI for open/closed card sorts, tree tests and first-click tests, (3) embeddable one-line JS snippet that opens a modal and posts responses to the API, (4) response storage in Postgres, (5) analytics endpoint producing similarity matrix and hierarchical clustering and a dendrogram renderer, (6) CSV export and a simple shareable report viewer. Out of scope: built-in participant recruitment integration, paid participant credits, advanced AI synthesis or competitor mapping, multi-seat team billing, and SSO. Include input validation, error handling, automated tests for API and critical UI flows, and Docker-based deployment scripts.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score67
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productValidateThat — Free Card Sorting + UX Research Stack
- official pricingPricing — Free, Starter, Pro & Team Plans | ValidateThat
- open sourceLimeSurvey/LimeSurvey
- open sourceTDuckCloud/tduck-survey-form
Integrity checks
What held up, and what did not.
