Features / Spec sheet, rev. Oct 2026

The intake toolkit for teams done chasing replies.

Seven capabilities. One canvas, one inbox, no developer ticket in between.

Get started Read the spec Plans from $129/yr · billed annually

01 — Capabilities

Everything a form should have shipped with.

Each capability below: what it does, what it saves you, and where it sits in a real intake workflow.

C-01 — Block canvas

Drop a block. The form reflows.

Thirty-four question blocks live in a searchable palette: short text, dropdowns, rating scales, rankings, file uploads, quiz points. Drag one anywhere and the numbering, progress bar and logic references update around it.

Benefit — a new question goes live in the time it takes to drag it, not the time it takes to file a ticket.

Fits · draft on Monday, share the link by lunch
Fig. 08 — Build tab, block searchAutosaved
C-02 — Branching logic

Ask less by asking smarter.

Skip a page, reveal a follow-up, end early, or pipe an earlier answer into a later question. Rules read like sentences. Run Test paths and Bloomery walks every branch to confirm each one reaches Submit.

Benefit — applicants only meet questions that apply to them, so page two stops being where people quit.

Fits · long applications with more than one track
Fig. 09 — Logic rules, Q5
C-03 — Scored quizzes

Grades itself. Shows its working.

Give each answer a point value, weight whole sections, set a pass mark. Submissions arrive graded, with the missed questions listed beside what the applicant chose and what was correct.

Benefit — reviewers read answers instead of adding up marks, and every score can be traced to a question.

Fits · pre-screens, certification checks, onboarding tests
Fig. 10 — Section scores, pre-screen
C-04 — Shared inbox

One inbox. Nobody asks who has it.

Every response lands in one inbox your whole team can see. Filter by status, tag as you read, select a handful and act on all of them at once.

Benefit — no forwarded emails, no “did anyone pick this up?”

Fits · weekly review with three or more readers
Fig. 11 — Inbox, Oct 29Synced 2m ago
C-05 — Routing rules

Write the rule once. Stop forwarding forever.

Route by any answer, score or tag: Documentary entries to Devon, Audio to Priya, anything with a budget flag to Maya. Rules run in order and show how many responses each one caught.

Benefit — submissions arrive already sitting with the person who should read them.

Fits · replaces the Monday triage meeting
Fig. 12 — Routing, 4 rules
C-06 — Multi-step intake

Long applications, short sittings.

Split a form into steps with a visible progress bar. Applicants save and resume from a link, so a forty-question application can be finished across three evenings without starting over.

Benefit — you see where people stall, step by step, and fix that one page.

Fits · grants, fellowships, vendor onboarding
Fig. 13 — Step funnel, Oct 1–28
C-07 — Fast search

Find the response without leaving the keyboard.

Press ⌘K to search applicants, forms and actions in one box. Jump to a person, open a form, or run “Route to…” on whatever you have selected.

Benefit — a reviewer clears a queue without reaching for the mouse.

Fits · reviewers working through hundreds of entries
Fig. 14 — Command palette

02 — Security

Applicants hand you their lives. Act like it.

Intake forms collect IDs, finances and personal statements. Access is a setting you control, not a promise.

S-01 / Identity

SSO on Orchard

Sign your reviewers in through your identity provider and remove their access in one place when they leave.

S-02 / Accountability

Audit logs

Every export, reassignment and rule change is written down with who did it and when, ready to hand to an auditor.

S-03 / Least access

Roles per workspace

Readers see their lane. Admins edit rules. Designers touch the canvas but never the responses.

03 — Integrations

New response in. Right tool pinged.

Native hooks for Slack, Sheets and Zapier push each new submission where your team already looks. Map a field to a column, a channel or a contact property and you’re done.

Fig. 15 — Connected tools

01Slack
02Sheets
03Zapier
04HubSpot
05Mailchimp
06Asana
Fig. 16 — Integration settings

04 — Reliability

A form that’s down is a deadline missed.

Applications close on a date. These are the behaviours that keep that date from becoming a bad day.

R-01

Drafts survive

Answers save as applicants type. A dropped connection or a closed laptop loses nothing, and the saved link picks up at the same question.

R-02

Nothing is overwritten

Edit a published form and Bloomery keeps the version applicants already started on, so half-finished answers still land in the right fields.

R-03

Your data leaves with you

Export every response as CSV at any time, files included. Your inbox is a working tool, not a lock-in.

R-04

Deadlines enforced

Set a close date and time. The form shows a clear closed message afterward instead of quietly accepting late entries.

05 — Start

Seven capabilities. Pick your plan.

Plans start at $129 a year, billed annually. Every plan has the canvas, the inbox and the logic.

Get started