Respect the respondent
One question per screen, a visible progress line, and answers validated while they are typed. If a screen would make us impatient, it does not ship.
/ About Vorly
We make forms people finish.
That is the whole product. Vorly is a canvas for forms, quizzes and surveys, and a dashboard that tells you, question by question, where the people you asked decided to stop.
/ 01 — The problem
The form was never the point
A form is a small piece of writing that asks a stranger for their time. Most are built like a tax return: every field at once, every error at the end, every respondent asked every question whether it applies to them or not.
The people who build them rarely see what happens next. A submission count goes up, and the quiet majority who opened the page and left simply never appear. The one question that cost you half your audience looks the same on the report as the question that cost you nobody.
Vorly began as a refusal of that arrangement. Ask one thing at a time. Keep what was answered. Let the last answer decide the next question. And draw the leaving, so the person who built the form can see it and fix it.
Nothing about this is exotic. It is how a decent interviewer behaves. The work was making that behaviour easy enough that a team would do it on a Tuesday afternoon instead of filing it under next quarter.
A completed form is a conversation that went well.
/ 02 — Principles
Four rules we check every change against
Show the leaving
Every feature that collects an answer has to say something about the people who did not give one. Drop-off is a first-class number, not an export.
Plain over clever
Logic reads like a sentence: if the answer is Other, show Q4. A teammate who has never opened the builder should be able to follow it aloud.
Your data stays yours
Responses export in full, at any time, on every plan. The way out of Vorly is as well-lit as the way in.
/ 03 — How it is made
Small releases, announced where you will see them
Vorly ships in small, frequent changes rather than a yearly relaunch. Each one lands with a short written note in the product, saying what moved and why, so the canvas you built on Monday still behaves on Friday.
The dashboard is live because the forms are: a response is written once and read everywhere, so the chart, the table and the Slack alert never disagree about what happened.
Status and the public API are documented in the open, and the links to both sit in the footer of every page.
/ 04 — Support
Questions answered in writing, in order
Support is a shared inbox read by the people who build the product, so a bug report reaches the person who can fix it without passing through a script.
- Collective
- Priority queue, read ahead of everything else.
- Priority
- Incidents
- Posted on the status page as they happen, then summarised once resolved.
- Status
- Integrations
- Documented through the public API, with changes noted before they take effect.
- API
/ 05 — Where it is going
Three directions, none of them louder than the form
Direction 01
Sharper readouts
Drop-off that explains itself: which device, which answer path, which step took longest, all on the same funnel.
Direction 02
Better branching
Logic that handles scores, hidden fields and returning respondents, still readable as a sentence.
Direction 03
More places to send answers
New native integrations, chosen by what teams ask for most in the inbox.
Directions, not promises: they change as the inbox does.
Start with one question. See who answers.
Three plans, one canvas. Pick the one that fits the volume you expect and draw the first form tonight.