Note 3.1
autosave, always
The canvas saves as you work and shows when it last synced. A closed tab should never cost anyone an afternoon.
About Sorvo · the argument behind the builder
who is on the other side of your form?
Someone with a few minutes, a half-formed intention and no obligation to finish. Sorvo was built on a plain idea: a form is the first conversation you have with a person, and most are conducted badly. This page is the story of the product, the principles we hold it to, and where it goes next.
Spec 01 / the problem
the form was never the point. the answers were.
Teams collect applications, intake, feedback and quiz results for the same reason: they want to act on what people say. Yet the tools on offer tend to treat the form as a container, a grid of identical boxes presented in identical order to everyone who arrives.
The result is familiar. A candle maker is asked about linen. A buyer with a large monthly order sits through the same questions as a first-time browser. Somewhere around question four, the person decides the effort no longer matches the reward, and leaves without a trace.
Then comes the second failure, on the other side. Answers that do arrive land in a spreadsheet nobody opens until the quarterly review, by which time the form has been quietly losing people for months. Sorvo is our attempt to fix both ends of that pipe at once.
Spec 02 / principles
four rules we check every release against
- i.
respect the respondent’s time
Every question should earn its place for the person answering it. If a rule can spare someone a page that does not apply to them, the builder should make that rule the easy thing to write, in plain terms.
- ii.
make the leaving visible
Drop-off is the most useful thing a form can tell you. Views, starts and completions are on the dashboard by step, so you fix the step people abandon rather than rewriting the whole form on a hunch.
- iii.
let answers travel
A response is only worth something once it reaches the person who can act on it. Slack, Google Sheets, HubSpot and Zapier connect natively, and so do the tools your team keeps in other tabs.
- iv.
keep the canvas calm
Thirty-plus question types is a lot of power. The surface that holds it should stay quiet: one canvas, a palette that opens with a slash, an undo that always works, and no markup to babysit.
Spec 03 / how it is built and supported
small decisions, made in the open
Software is a long series of promises. These are the ones we make about how Sorvo is made, changed and looked after.
Note 3.2
paths you can preview
Every branching rule can be walked end to end before publishing, so a mistake is found by you and not by a respondent.
Note 3.3
a status page that tells the truth
If something is degraded, the Status page says so, with times. No euphemisms.
Note 3.4
support that reads your form
Write to help@sorvodigital.com and the reply comes from someone who opens your form and looks at it, rather than pasting a help-centre link.
Fig. 3.1 — every edit logged, every edit reversible
Spec 04 / where it is going
the direction of travel, stated plainly
No dates promised that we cannot keep. What follows is the order of our attention, and what it is for.
Now
shorter paths, sooner
Making branching rules quicker to write and easier to read back, so a form with a dozen paths stays understandable to the next person who opens it.
Next
sharper reading of drop-off
Deeper cuts on where people leave: by step, by device, by path, so the dashboard points at the fix rather than only at the problem.
After
more places for answers to land
Further native destinations for finished responses, chosen by what teams tell us they are copying and pasting by hand.
Spec 05 / next form
ask better. read faster. act sooner.
Annual plans begin at $159. The Enterprise Suite, at $719 a year, adds unlimited responses, SSO and a dedicated success manager.
Get access