Why we built a form backend for agencies
Form backends price by submission and think in single sites. Agencies manage thirty sites for other people. FormDock is what happens when you design for the second group.
Every freelancer and small web studio has the same folder somewhere: a dozen client sites, each with a contact form, each wired to whatever form service was convenient the day it shipped. One client is on a legacy Formspree account, two are on Web3Forms keys nobody wrote down, one posts to a PHP script on shared hosting that will break the next time PHP is upgraded.
The forms work — until one doesn't, and the client calls asking why they haven't had a lead in three weeks. That call is the reason FormDock exists.
The pricing problem
Form backends overwhelmingly price per submission, laddered steeply. The best-known charges $15/month for 200 submissions. For a personal site that's fine. For an agency it means your costs scale with your clients' success, invoicing is a mess of per-site subscriptions, and you're quietly incentivized to under-provision spam protection because every blocked-then-retried submission counts.
FormDock is flat: $15 for 1,000 submissions across unlimited forms, $39 for 10,000 with unlimited client workspaces. One invoice. Your client's launch going well should be good news, not a billing event.
The ownership problem
The subtler issue is that single-site form tools have no concept of the agency relationship. The person who builds the form is not the person who answers the leads — and both need different things. The client needs the lead in their inbox, now. The agency needs the archive: proof the form worked, a searchable record when the client says something went missing, and a clean export when the engagement ends.
So FormDock's core object is the workspace — one per client. Notifications route to the client's inbox (white-labeled with your studio's name on the Agency plan); the audit trail stays in yours. Handing off a site to the client someday? Export the CSV, transfer the workspace. Done.
The one unforgivable error
A form submission is usually a sales lead — sometimes a five-figure one. Losing it is the only failure a form backend truly cannot walk back. That principle shaped the architecture: every submission is written to the database before anything else happens. Spam-flagged? Stored, quarantined, reviewable. Over your plan cap? Stored; only the notifications pause. Email provider down? Stored, and delivery retries with backoff until it lands.
What we deliberately didn't build
- No form builder — you build forms in your own markup, your own design system. We're the backend only.
- No logic and branching — that's a different product with a different buyer.
- No email marketing sequences — your notification email is transactional, and keeping it that way is what keeps deliverability high.
FormDock is the boring, load-bearing half of every contact form you'll ship this year. Point your form at an endpoint and forget about it — that's the whole product. If you run client sites, we think you'll feel the difference in the first invoice.