Every keystroke is kept.
The canvas saves as you build and the applicant’s form saves as they answer. A closed tab loses nothing on either side.
Bloomery / About · the manifesto
The form builder for the person on the other side of the form.
Most form tools are built for whoever sends the form. We build for whoever has to finish it.
01 — The problem
A form is a conversation. Most of them are interrogations.
Somewhere, a program manager is reading the ninth PDF of the morning, retyping an answer into a spreadsheet, and forwarding a file to a colleague who may or may not own it. Meanwhile an applicant is on page two of a form that asked for the same thing twice.
Both of them are doing work the software should have done. That is the gap Bloomery was built into: blocks you drag rather than code you commission, logic that hides what doesn’t apply, scoring that arrives with the submission, and an inbox where every response already has an owner.
Fig. 01 — A response, the moment it lands
02 — Principles
Four opinions we’ll defend in public.
They decide what gets built, what gets cut, and what we say no to when a feature request is loud.
- A/ P.01
Finishing is the feature.
Every block, every default and every page break is judged by one number the sender never sees: how many people got to the end. If a field doesn’t earn its place, the builder makes it easy to delete.
Test · would you answer this on your phone? - B/ P.02
Ask only what applies.
Branching isn’t an advanced option hidden in a higher tier’s footnote. It’s how a form respects people, so a documentary applicant never meets the audio questions.
Test · does every path reach Submit? - C/ P.03
Responses should arrive with an owner.
Data that lands unassigned is homework. Tagging, scoring and routing belong in the product, written once as rules, not rebuilt every Monday in a triage meeting.
Test · who reads this, and do they know yet? - D/ P.04
Pricing should fit on one screen.
Three plans, billed annually, every number visible. No quote calls for a tool that builds forms, and no feature quietly moved up a tier after you’ve built on it.
Test · can you explain the bill in one breath?
03 — Under the canvas
How it’s built, and how it’s looked after.
The unglamorous decisions that decide whether a form still works at 11:58 on deadline night.
Spec 3.1 / Autosave
Spec 3.2 / Test paths
Logic is checked before it ships.
Run every branch from the editor and see which questions each path reaches. Dead ends are flagged before an applicant finds them.
Spec 3.3 / Audit
Changes leave a trail.
Orchard workspaces keep audit logs of who edited a form, who reassigned a response and when, so reviews stay defensible.
Spec 3.4 / Support
Questions get a reply, not a ticket maze.
Help-center guides cover the common builds. For everything else, write to team@bloomeryworks.com and a person answers.
04 — Heading
Where it’s going next.
A direction, not a promise sheet. We’d rather ship a small thing that works than announce a large thing that doesn’t.
Fig. 02 — Working roadmap, Oct 2026
- Now
Sharper reviewer workflows
Multiple reviewers per application, blind scoring and side-by-side comparison, so shortlists come from consensus and not from whoever read first.
- Next
Smarter routing rules
Route on score, tag and answer together, with a dry run that shows where the last hundred responses would have gone.
- Later
More places for responses to land
Deeper two-way sync with the tools already on the integrations list, so data moves out without a CSV in the middle.
05 — Start
Build the form you’d want to fill in.
Plans start at $129 a year, billed annually. Three sizes, every price on the page.
Get started