FormBridge exists so a contact form never costs you a weekend again. Eight people, one product — receiving, validating, storing, and routing your submissions while you ship the actual product.
ST
BR
DR
DB
MJ
NM
AV
KK
We didn't set out to build a form tool. We set out to build the backend that stops good forms from becoming a weekend project. — Sumit Tejani, Product Owner
Every developer has lost a weekend to a "simple" contact form — the spam, the SMTP, the Zapier duct tape, the spreadsheet nobody shared. We'd each solved it half a dozen times before saying the quiet part out loud: this is a real product, hiding inside a category everyone treats as solved. So we built the backend we kept wishing existed — and nothing else.
The best form backend is the one you stop thinking about after a week. No surprises, no clever defaults.
A submission is a person trying to reach you — not a database row. We design every surface around that.
"Every dev tool starts the same way — someone gets so annoyed by a problem they refuse to stop thinking about it."
Encrypted at rest, never sold, never mined. GDPR-aligned with a DPA on request.
Picture a Saturday. You've shipped a clean marketing site. The last item: a contact form. Twenty minutes, you think. You're wrong. Two hours later you're neck-deep in Zapier policies, SMTP relay issues, and a spreadsheet someone forgot to share.
The first commit was twenty lines of Go and a Postgres table called submissions. Simple enough to ship in a day. Solid enough to build on.
Our own test notifications looked like they'd been mailed in from 1998 — plain text, no branding, dumped straight out of SMTP. If we wouldn't want it landing in our own inbox, we weren't going to ship it in yours.
The template designer shipped in March — drag-and-drop layout, brand colours, dynamic fields, no HTML required. First thing we did with it was rebuild our own templates.
It's the question every agency runs into eventually: can sales inquiries go to sales and support requests go to support — from the same form? The answer used to be "yes, with Zapier." We wanted it to just be yes.
Conditional routing shipped in May. Pick a field, set rules, route notifications anywhere. This was the feature that turned a personal itch into something worth putting a name on.
With the core product built, the team grew to get it ready for the world. Bansari Radadiya joined to build alongside Dhruvi. Dhruv Bhavsar and Manali Joshi joined as QA, running the checklist that catches what a small team building fast can miss.
Eight people, one product, one launch date circled on the calendar.
No beta. No waitlist theatrics. We built until it was ready, then flipped the switch. FormBridge officially launched on July 13, 2026 — open to everyone, from day one.
Product, platform, and quality — every feature you use passed through these five pairs of hands.
STBrought the idea, sharpened the thesis, and decides what ships, what waits, and what gets thrown out. If a feature surprises you in a good way, Sumit argued for it.
"What if we just built the form backend we keep wishing we had?"
BRCo-develops the platform with Dhruvi — picks up features and fixes across the codebase whenever a part of the roadmap needs an extra pair of hands. Two people building the same product, side by side.
"Two people building the same thing move faster than one."
DRBuilt FormBridge end to end — every endpoint, every retry, every encrypted byte. From the ingestion pipeline to the inbox UI, it's her code holding the product together.
"It should work. Then keep working. Then we ship the next thing."
DBRuns the release checklist that catches what automated tests miss — edge cases, real devices, real user chaos. If a bug reaches production, it wasn't for lack of trying to find it first.
"Untested is just a nicer word for broken."
MJOwns the test plans for every release — from a single form field to a full submission flow. Reproduces the bug report that says "sometimes it just breaks" until it isn't sometimes anymore.
"If I can't reproduce it, I can't trust that it's fixed."
Capital, architecture, and operations — the three people who gave a small team the room to build slowly and correctly.
NMShip the right thing, the right way. I'll handle the rest.
Capital, conviction, and organisational cover — the runway to build correctly. No quarterly OKRs. No pivot pressure. Just the long game.
AVSee further than the next sprint. That's the only architecture rule that matters.
Architecture reviews, the hard calls before every launch — always in the room. His instinct for what makes a product better is incredible.
KKA small team moves fast when everything around it just works. That's my job.
Infrastructure access, deployment pipelines, the hundred small "can-you-just" requests that could derail a team every week — absorbed, handled, done.
FormBridge is free to get started. Your first form is live in under 5 minutes — no backend code required.