For firms
Sealed-Work Drafting, across the whole firm.
We’re writing this page to the partner thinking about putting Fermito in the hands of every engineer in the office, not just one. Sealed-Work Drafting is a practice decision, not a tool decision. It rearranges the most expensive hour in the firm, and it does it across every report the firm ships. The page below is how we think about that rollout, written the way we’d talk about it across a kitchen table with the principal whose name is on the letterhead.
Four decisions we already made for you
Sealed-Work Drafting, the way we think a firm wants it.
Rolling a tool out across a practice usually means a procurement meeting about seat counts, integrations, and data policies. We already made those decisions, and we made them the way we think a principal would make them. The four below are what that looks like.
01 · The template is yours
Fermito writes in your house format from day one.
You ship us the Word template you already use. Header, footer, signature block, distribution list, the revision row your firm has sharpened for a decade. We ingest the actual file and tune generation so the first draft a reviewer sees reads like you wrote it, because you did. No generic report schema. No one-size Sealed-Work Drafting template imposed on a firm that already has its own.
DOCX ingestion · per-firm tuning · house-format output on every export
02 · The firm's voice
The callouts your principals sharpened belong in one place.
The observation language the firm has built over a decade - the sentences that show up in twenty reports a quarter - lives in a shared library, not in twenty different engineers' heads. Every revision a principal makes on a live report teaches the library a little more of the house voice. The tenth report on a site is drafted closer to the firm's standard than the first. The voice belongs to the firm, not to us.
Shared library · revision-as-training · firm-owned, firm-exportable
03 · The cost the firm sees
One line on one invoice, every month.
Pricing is flat-monthly, not per-report. The firm knows what Fermito costs next quarter without a usage model in the way, and the engineers doing the work never feel a meter on top of their day. Adding or removing an engineer is a one-click operation the firm controls, and the partners who want to see how the practice is using the tool can.
Monthly invoicing · firm-controlled access · usage visibility for partners
04 · The firm's workflow untouched
Fermito ends at the Word document.
You already have a review and distribution workflow. Bluebeam markup, email distribution, document management, the PE-reviewed path from draft to sealed file - we don't try to own any of it. Fermito hands you a finished Word document in your house format and stops there. Sealing and distribution are the firm's, and the firm's process is not broken.
DOCX handoff · Bluebeam-compatible · no forced workflow change
The first four weeks
Sized for a principal's morning, not a vendor's quarter.
The first month is designed around your week, not ours. Each week below is a real, bounded commitment. No six-month procurement cycle, no consulting-services wrap, no implementation phase that eats a principal's summer.
- 01Week 1 · We listen
We sit with a principal and an admin to understand the template set, the report categories the firm is actually producing, the firm's signature and distribution conventions, and the engineers in the first cohort. A discovery call sized for a principal's morning, not a vendor's quarter.
- 02Week 2 · We match the template
We ingest the firm's actual Word templates and tune generation to reproduce them. We generate a sample report against a real historical visit so a principal can read the output before any engineer logs in. If the output is not close enough to the firm's standard, we tune until it is.
- 03Week 3 · The first cohort runs it
The engineers in the first cohort get a walk-through of capture, review, and export. One hour per engineer, on the firm's calendar. The sessions are recorded so anyone who joins later does not need us in the room to learn the product.
- 04Week 4 · The firm ships real reports
The firm runs live sealed work on Fermito with direct access to the builder for the first month. Feedback from the first ten documents feeds back into the template tuning so the second ten are drafted closer to the firm's standard than the first. The firm sees the voice converge, week over week across Site Review Reports (also written FRR or Field Review Report) and sealed letters.
Your clients' work stays your clients' work
Client confidentiality is a design constraint, not a settings panel.
The reports your engineers write on Fermito are confidential practice under PEO Practice Bulletin - Field Reviews. We treat them as confidential client material by default. They are never used as training data. Not opt-in, not opt-out, never. We wrote that rule before we wrote the product.
Visit records, generated drafts, photos, and supporting documents are stored against the firm’s tenant and accessible only to the engineers the firm has given access. The firm owns the data end to end. The firm can export or delete all of it on request, and we will answer the request.
Our /security page has the full data-handling posture, incident response policy, DPA availability, and the SOC 2 roadmap. Read it end to end before the rollout call. If something on that page is not clear, say so, and we’ll rewrite it.
Who we built it for
Two to thirty licensed engineers, writing their own reports.
Sealed-Work Drafting is a practice decision with a practice-shaped price tag. A flat monthly line on one invoice, sized for the firm you already run, not a usage meter that grows every time an engineer walks a site.
Solo
One licensed engineer
The single-engineer practice running sealed work alone. The whole product, one line on the invoice, every month, across every supported doc shape.
Team
Two to ten engineers
The typical small-firm rollout. The firm's voice lives in the shared library, template tuning is done against the firm's own templates, and one line shows up on the invoice every month.
Firm
Ten to thirty engineers
Multi-principal practices with real template variance across report categories. Custom prompt tuning, SSO, and a named person on our side for template changes.
Full pricing is on the pricing page. A rollout call answers the size-fit question in the first ten minutes.
Next step
A rollout call takes thirty minutes and ends with a real answer on fit.
We don’t sell every firm that books a call. The call is there to decide whether your template set, your report volume, and your review posture are a match for what Sealed-Work Drafting on Fermito does today. If the answer is no, we’ll say so on the call, and we’ll say why.