The breadth trap
Most AEC software launches with broad geographic coverage. The pitch deck says "works across all North American building codes." The product supports NBCC, OBC, BCBC, ABC, and a handful of US state codes. The marketing claims "regulatory compliance built in."
The reality behind that claim is usually a set of generic templates with a jurisdiction dropdown. The templates use the same language regardless of whether the user selects Ontario or British Columbia. The code citations are shallow - "in accordance with applicable building code requirements" rather than "in accordance with OBC Part 4 and CSA A23.1-14." The product knows that building codes exist. It does not know what they say.
This approach works for construction management tools, where the core value is project coordination, not regulatory interpretation. It does not work for sealed engineering documents, where the core value is regulatory accuracy - the engineer's professional opinion that the work conforms to specific, named standards.
A sealed field review report under OBC 1.2.2.2 is not a generic inspection report with an Ontario header. It is a document that cites specific OBC articles, references specific CSA material standards by clause number, classifies observations against specific conformance criteria, and carries the personal liability of the engineer who sealed it under PEO Regulation 941. Every one of those specifics is jurisdiction-dependent. A tool that gets them wrong - or gets them approximately right - produces a draft that the engineer must fix before sealing.
What regulatory fluency actually requires
Fermito speaks Ontario building code natively. This is not a marketing claim - it is a description of how the generation prompt is constructed. Here is what "natively" means in practice:
OBC clause structure. The Ontario Building Code is organised into 12 parts with a specific article numbering system (Part.Section.Subsection.Article). A field review report that cites "OBC 1.2.2.2" is citing Part 1, Section 2, Subsection 2, Article 2 - the clause that defines the field review obligation. The generation prompt knows this structure and produces citations in the correct format. A generic tool that treats "OBC 1.2.2.2" as a text string rather than a structured reference cannot verify that the citation is valid.
CSA material standards. The OBC references CSA standards by name - CSA A23.3 for concrete design, CSA S16 for steel structures, CSA O86 for wood structures, CSA A23.1 for concrete materials and construction. Each standard has a publication year, a clause structure, and specific requirements that field review observations should reference. A report that cites "CSA A23.3-14, clause 7.4.1" is making a precise regulatory claim. A report that cites "CSA standards" is making a vague one. The generation prompt is tuned to produce the precise form.
PEO practice context. Ontario's professional engineering regulator has published practice bulletins and guidelines that shape how sealed documents are produced and reviewed. The generation prompt operates within this context - it knows that the reviewing engineer's responsibility is defined by Regulation 941, that the seal attests to professional judgment, and that the document must meet the standard of care expected of a licensed Ontario P.Eng. This context informs the language, the finding classifications, and the recommendation structures.
Inspection category vocabulary. Different types of field reviews use different observation vocabularies. A concrete pour review references slump tests, placement procedures, vibration, curing, and formwork removal timing. A waterproofing review references membrane adhesion, surface preparation, lap dimensions, and drainage testing. The generation prompt is tuned across these category-specific vocabularies using real Ontario field review reports as training material.
Each of these elements is specific to Ontario engineering practice. A tool that supports OBC and BCBC equally must maintain two complete sets of regulatory knowledge, vocabulary, and citation formats. A tool that supports six provinces must maintain six. The engineering effort scales linearly with jurisdictions, and the quality at each jurisdiction is inversely proportional to the breadth of coverage.
Why Ontario first
Fermito chose Ontario as its initial jurisdiction. The choice was driven by four factors:
PEO is a mature regulator with published practice infrastructure. Ontario's professional engineering regulator has been operating since 1922. Its regulatory framework - the Professional Engineers Act, Regulation 941, published practice bulletins - is comprehensive, publicly accessible, and well-understood by practitioners. Building a product within this framework is possible because the framework is documented. Less mature regulatory environments - where the rules exist but the published guidance is sparse - would require more interpretation and more risk.
The OBC references CSA standards by name. Ontario's building code explicitly references the CSA material standards that govern structural, mechanical, and electrical engineering work. These references are specific enough that a field review report can cite the exact clause governing the element under review. This specificity is the foundation of regulatory fluency - without named references, the drafting tool would be generating generic conformance language rather than precise regulatory citations.
The market is concentrated. Ontario has the largest concentration of structural and building-science engineering firms in Canada. The Greater Toronto Area alone has several hundred firms producing sealed field review reports on a regular basis. This concentration means that a product built for Ontario engineering practice can reach a meaningful market without geographic expansion. The addressable market is large enough to validate the product in a single jurisdiction.
Our product development is grounded here. Structek Consulting, the structural engineering firm whose sealed reports informed our product development, is a GTA-based practice. The generation prompt is tuned against their report output, their template format, and their observation language. Building the product against a real firm's real work - rather than against a hypothetical firm in a hypothetical jurisdiction - required that the firm and the product share the same regulatory context.
What expansion looks like
Fermito will expand beyond Ontario. The question is when and how, not whether.
British Columbia (BCBC). The BC Building Code is modelled on the National Building Code of Canada but has province-specific amendments, particularly around seismic design requirements and energy efficiency. Engineers and Geoscientists BC (EGBC) has its own practice guidelines and professional responsibility framework. Supporting BCBC requires a new regulatory knowledge base, updated citation formats, and category-specific vocabulary tuned to BC construction practices. This is real engineering work - not a configuration toggle.
Alberta (ABC). Alberta adopted the National Building Code with province-specific amendments. APEGA (Association of Professional Engineers and Geoscientists of Alberta) has its own practice standards. The regulatory differences from Ontario are smaller than BC's but still significant enough to require dedicated prompt tuning and vocabulary development.
Quebec (CCQ). Quebec presents a unique challenge. The Construction Code of Quebec has its own structure and numbering. OIQ (Ordre des ingénieurs du Québec) operates under Quebec's Professional Code rather than a standalone engineering act. And Quebec has a statutory French-language requirement - sealed engineering documents must be available in French. Supporting Quebec means building bilingual generation capability, a French regulatory knowledge base, and French observation vocabulary. This is a separate product initiative, not a feature addition.
Each provincial expansion follows the same pattern: read the regulatory framework, build the citation knowledge base, tune the generation prompt against real reports from that jurisdiction, and validate against a practising firm. The work for each province is measured in months, not weeks. Attempting all four simultaneously would produce four mediocre implementations instead of one strong one.
What Ontario firms get from the focus
Every improvement to the generation prompt, every new observation phrase in the library, every refinement to the citation formatting benefits Ontario firms first and exclusively during the focus period. This is a feature, not a limitation.
When a single-jurisdiction tool processes a report that cites CSA A23.3-19, clause 13.4.2, it can verify the citation format against the known structure of CSA A23.3. When a multi-jurisdiction tool processes the same citation, it must determine which jurisdiction's citation format applies, which version of the standard is current in that jurisdiction, and whether the clause number exists in the referenced edition. The single-jurisdiction tool is faster, more accurate, and easier to debug.
When a single-jurisdiction tool encounters a new observation pattern - a type of structural element or a construction technique that has not appeared in the training material - the prompt can be updated immediately because the update applies to one regulatory context. A multi-jurisdiction update must be validated across all supported jurisdictions to ensure that the new language is appropriate in each context.
When a single-jurisdiction firm reports an issue - a citation format that does not match their house standard, an observation phrase that uses non-standard terminology - the fix applies to the shared context. Every Ontario firm benefits from every other Ontario firm's feedback. In a multi-jurisdiction tool, a fix for an Ontario firm might not apply to a BC firm, and the support burden scales with the number of regulatory contexts.
The firms that benefit most from Fermito today are the firms that practise in the jurisdiction where Fermito is deepest. That jurisdiction is Ontario, by design and by commitment. The depth is not an accident of geography - it is the product strategy that makes regulatory fluency possible.