- Home
- Industries
Industries
Industrieswe know well.
Five sectors where we can name the systems the sector runs, the regulation that bites in it, and the operational shape a generalist would get wrong. Websites, web applications, integrations and AI automation, designed around how each one actually works.
A page per sector that says something true and specific, or no page at all.
The five
Five sectors,and why each one is here.
Each of these is a sector where the operational shape, the systems and the requirements are specific enough to say something true that is not true of the others. That is the whole test, and it is published below.
-
Construction and trades
A bid calendar, a season, a holdback and a prompt payment clock. Estimating, project management and payroll are three systems that rarely agree, and the quote that never got chased is the most expensive thing in the office.
-
Manufacturing and distribution
Account pricing per customer, product data with a long tail, and large accounts that mandate how you exchange documents with them. Most of the phone calls are order status, and most of the order status is already in the system.
-
Healthcare and clinics
Appointments, intake, recalls and a front desk that is interrupted all day. Health information law is provincial, it names a custodian, and it changes where a system may store a record and who may reach it.
-
Professional services
Intake, conflict checks, matters and engagements, and regulators who set rules on what a firm may publish about itself. The growth constraint is usually recruiting rather than demand.
-
Real estate and property
Listings that are perishable, leads that arrive at night, and a brokerage that is accountable for what its registrants publish. Property management runs on maintenance requests, rent cycles and documents.
The rule
What earns a sector page.
Industry pages fail the moment they become doorway pages: the same page with the sector noun swapped, published at scale, cheapening everything around it including the pages that were real. The defence is a gate, applied before any sector page is allowed to ship.
| The evidence | What it means | Why it cannot be faked |
|---|---|---|
| Named systems | The software that sector actually runs, by category and by common example, with the qualifier that every connection is checked by name during scoping. | Naming the wrong system is obvious to anybody who works in the sector, and it is the first thing they check. |
| Named regulation or standard | Something that applies to this sector specifically, written as a design requirement rather than as a compliance claim. | Generic privacy language fits everywhere, which is how you can tell it was not written for anyone. |
| The operational shape | The seasonality, the sales cycle, who signs, and where the manual work concentrates. | This is the block a sector swap cannot fake, because it is the part that is not about software at all. |
| The sector's own vocabulary | The words the sector uses, verified against real sources rather than reproduced from memory. Where we cannot verify a term, we do not use it. | Vocabulary is how a reader decides in four seconds whether the page was written for them or at them. |
| Four hundred words that appear nowhere else | Measured rather than assumed, across the sector specific bands of the page. | A page that is mostly shared text is a template with a noun swapped, whatever the heading says. |
Scroll the table sideways to read it.
Four out of five means the page does not ship. There is no partial credit and no draft published while the missing piece is researched, because a sector page that is four fifths true reads exactly like one that is entirely true, and the reader has no way to tell which one they are on.
What is true of every one
Four things these pages never do.
On every industry page on this site
- No city variants. Each sector has one page, not a copy for each city.
- No invented figures. A page describes the sector, the jobs a system does in it, and the arithmetic that sizes them. It never publishes a figure we would have to invent.
- Every scenario is an arithmetic you fill in. The calculation is published in full and every input is a dashed slot, because the shape of the sum is the part we know and your conversion rate is the part we do not.
- Every requirement is a design requirement. We name what a build here has to be designed around and what we document for your counsel. The determination is theirs.
If your sector is not listed.
Five sectors have a page of their own. If yours is not one of them, nothing here is closed to you. The service pages describe the work, and a discovery call starts with what is happening, not with your industry.
Start with the situationAsked and answered
Questions about these pages.
-
Why are there only five?
Because five are the ones we can write to the standard published above. The gate is five pieces of evidence and all five are required, so a sector we could half describe does not get a page.
-
Do you only work with these five sectors?
No. The service pages describe the work rather than the sector, and most of what a system does is the same whatever the trade. These five have pages because we can say something specific about them, which is a different question from who we will build for.
-
Is there a page for my city?
No. Each sector has one page, because the work is scoped and run remotely across Canada and the United States, with in-person meetings where that is practical. Publishing the same sector page with a city swapped is the practice these pages exist to avoid.
-
I am in one of the five. Where should I start?
On the sector page, which names the jobs a system does there and which services matter most. If what you actually have is a symptom rather than a service in mind, the router asks the question the other way round and lands you in the same place.
Bring the question your sector keeps asking.
A discovery call starts from what is happening in your business, not from a sector template. If the website is the question, the audit starts from the site as it is.
