ABOUT
It started with one spreadsheet of questions.
In 2021 a client came to us with a spreadsheet: a column of questions, a column saying what each answer should be — text, a date, a dropdown, a file. They wanted it turned into a working form. Simple ask.
It wasn’t simple. We went looking for a tool that could build a form straight from structured data like that, and there wasn’t one. Everything on the market wanted you to start from scratch and place every field by hand. To do it properly — from the data, the way the client had it — meant writing custom code. For a form.
SIX YEARS OF THIS
The same walls, over and over.
That first job wasn’t a one-off. Across six years of building for clients, the same tools kept getting in the way in the same ways — and I kept noticing exactly where.
JotForm asks you to make too many decisions before you’ve made anything. Category, then type, then a dozen more choices — you can lose ten minutes to decision paralysis before the first question exists.
Typeform has genuinely nice pre-built templates, and I’ve reached for them. But it gets expensive fast at any real volume, and the submissions always felt like they lived off to the side, disconnected from the actual workflow they were supposed to feed.
Google Forms is where smaller teams and schools land when they’ve been priced out of everything else. It works. But it’s rigid — you get almost no real say over how the form looks or feels, and eventually that stops being good enough.
And underneath all of them, the same wall: the moment a form needs real logic — fields driven by data, multi-branch conditions, reporting tied to the responses — you’re back to hiring a developer. Every time.
WHAT IT DOES TODAY
So we built the tool that job needed.
Everything below is shipped — things you can do in FormNest right now, today.
Start from a real template
Pick something close to what you need, adjust it, done. No blank canvas and no maze of categories and field types to wade through before you've built anything.
Page mode and guided mode from one schema
Build a form once and it ships two ways — a classic page, or a guided one-question-at-a-time flow. The mode is a setting, not a rebuild.
Conditional show/hide logic
Fields appear or hide based on earlier answers, so a single form adapts to each respondent instead of asking everyone everything.
Industry-specific modules
Field groups built for particular kinds of work, so a viewing request or a service ticket starts with the questions that job actually asks.
Full creative control
Real say over how a form looks and feels — not three theme presets and a logo slot.
THE NEXT PHASE
Where it’s headed.
This part is the plan, not the product — what we’re building toward, stated as what it will be rather than what it already is.
We’re building toward forms backed by live data connections — where a dropdown will fill itself from a real database instead of a list you type out and maintain by hand.
The next phase will deepen conditional logic into genuine multi-branch workflows, so the complex, enterprise-grade forms that still get built by developers today will be something you can assemble yourself.
And we’re working toward reporting that will go well beyond basic charts — reporting tied directly to your submissions, not a separate dashboard you have to wire up.
WHO’S BEHIND IT
Built and run by one person.
That’s the honest version: FormNest is built and run by one person, shaped by the six years of client work that came before it. No team page, no origin-story mythology.
What matters more is the part you’ll actually touch: how little stands between an idea for a form and a working one. Start from a template that’s close, change what you need, publish it as a page or a guided flow. That’s the whole point — getting from “we need a form for this” to a real form, without a developer and without the maze.
FREE PLAN · NO CARD