For firms
Fermito fits the way the firm already writes.
This is the firm-admin view of Fermito. It covers the things a firm asks before rolling a tool out across a practice — templates, seats, onboarding, data handling, and the first four weeks of live work. Every decision below is a decision Fermito has already made for the small and mid-size Ontario structural and building-science firms it is built for.
What rolling out Fermito looks like
Four things a firm gets on day one.
None of the four below is a roadmap promise. Each is a surface a Fermito firm touches in its first week of use.
01 · Templates
Fermito writes in the firm's house format from day one.
The firm ships Fermito the DOCX it already uses — header, footer, signature block, distribution list, revision history. Fermito ingests the actual file and tunes generation so the first draft a reviewer sees reads like the firm wrote it, because the firm did. No generic report schema, no one-size template.
DOCX ingestion · per-firm tuning · house-format output on every export
02 · Observation library
Standard callouts and phrasing live in one place.
The firm's standard observation language — the sentences that show up in twenty reports a quarter — lives in a shared library, not in twenty different engineers' heads. Every revision 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.
Shared library · revision-as-training · firm-owned, firm-exportable
03 · Seats + billing
Seat provisioning mirrors how the firm already runs.
Seats map to licensed engineers and staff reviewers. Billing is a single monthly line, invoiced to the firm. Adding or removing a seat is a one-click operation for the firm admin, and usage is visible by engineer for the partners who want to see it. No per-report surprise billing — no meter running behind the scenes.
Monthly invoicing · admin-managed seats · usage visibility by engineer
04 · Export + integration
DOCX export matches the firm's existing review workflow.
Fermito hands off a finished DOCX that drops into the firm's existing review and distribution pipeline — Bluebeam markup, email distribution, document management, however the firm already works. Fermito does not try to own the seal-and-distribute step. The firm already has a process there, and the process is not broken.
DOCX handoff · Bluebeam-compatible · no forced workflow change
Onboarding · four weeks end to end
Fermito's onboarding is sized for a principal's calendar, not a vendor's quarter.
The first month is designed around the firm's existing week. Each week below is a real, bounded commitment — no six-month procurement cycle, no consulting-services wrap.
- 01Week 1 · Discovery
Fermito works with the firm admin and a principal to understand the template set, the report categories in active use, the firm's signature and distribution conventions, and which engineers are in the first rollout cohort.
- 02Week 2 · Template tuning
Fermito ingests the firm's actual DOCX templates and tunes the generation prompt to match them. A sample report is generated against a real historical visit so the firm can see the output before any engineer logs in.
- 03Week 3 · Staff onboarding
The first cohort of engineers gets walk-through sessions on capture, review, and export. The sessions are scheduled around the firm's week, not a vendor's — typically one hour per engineer, recorded for anyone who joins later.
- 04Week 4 · Live with support
The firm runs real field reviews on Fermito with direct access to the builder for the first month. Feedback from the first ten reports feeds back into the template tuning so the second ten are drafted closer to the firm's standard than the first.
Data handling, by the rule
Client confidentiality is a design constraint, not a settings panel.
Field review work is confidential practice under PEO Practice Bulletin — Field Reviews. Fermito treats customer report content as confidential client material by default. It is never used as training data — not opt-in, not opt-out, never.
Visit records, generated drafts, photos, and supporting documents are stored against the firm’s tenant and accessible only to seat-holders the firm admin has provisioned. The firm owns the data end to end and can export or delete it on request.
Fermito’s /security page carries the full data-handling posture, incident response policy, DPA availability, and the SOC 2 roadmap. The firm admin is encouraged to read it end to end before a rollout call.
Sized for the firm
Fermito is built for 2–30 licensed engineers.
Smaller solo practices run on the solo tier; most Fermito firms sit in the team or firm tier. Pricing is flat-monthly, not per-report — the firm knows what Fermito costs next quarter without a usage model in the way.
Solo
1 licensed engineer
A single-engineer practice running field reviews without staff support. All four surfaces of the product, one seat, monthly invoicing.
Team
2–10 engineers
The typical small-firm rollout. Shared observation library, custom template tuning, and a single firm-level billing line. Priority support included.
Firm
10–30 engineers
Multi-principal practices with active template work across report categories. Custom prompt tuning, SSO, and a named point of contact for template changes.
Full pricing and features are on the pricing page. A rollout call covers the tier fit in the first ten minutes.
Next step
A rollout call takes thirty minutes and ends with a real answer on fit.
Fermito does not sell every firm that books a call. The call exists to decide whether the firm’s template set, report volume, and review posture are a match for what the product does today. If the answer is no, Fermito will say so on the call.