
- Home
- Industries
- Construction and trades
One of the five sectors
Digital systems for Canadianconstruction and trades.
Contractors, subtrades and service trades run a bid calendar, a build season and a payment cycle that are all on different clocks. Most of the digital work here is about the gaps between them.
Fewer quotes that nobody chased, fewer status calls, and a record of what was issued and when.
Know what you are building? Book a discovery call. Not sure where the problem is? Request the audit.
HUREAL / Material studies
In your words
Soundslike this?
We send quotes all week and nobody owns chasing them.
Our estimator is the bottleneck and everything waits behind them.
A general contractor asks for a clearance certificate and we go looking for the current one.
The project manager and the office are working from two different versions of the same drawing.
We are hiring on every site and the careers page is a form.
Progress billing is a person, a spreadsheet and a lot of memory.
A homeowner or a site super calls to ask when we are coming, and somebody has to go and find out.
If the recognisable line is the last one, the shortest route is a customer portal, because a status question answered by the customer costs nothing to answer.
The operational shape
A bid calendar,a season, and a clock.
Three things shape almost every digital decision in this sector, and none of them is about software. A system designed without them is a system the office quietly stops using in July.
The calendar and the season
Work is won in one part of the year and delivered in another, and in most of the country the delivery window is set by weather rather than by demand. Tender closings cluster, the estimating desk floods, and the same team that is quoting in March is running sites in July.
That matters to a build because peak load is not the average load. A system sized for a quiet week is a system people abandon in the busy one, and the busy one is the only week that pays for it.
Who signs, and what they are signing
The person who signs is usually the owner, a principal or a VP of operations, and they are signing in the gaps between site visits. The decision is fast when the arithmetic is clear and it stalls indefinitely when it is not.
The second signature that matters is on the job itself: a general contractor, an owner's representative, or a consultant, each of whom has their own document requirements before a subtrade is even allowed on site.
Where the manual work lands
In the office, between estimating, project management and accounting. The estimate is built in one system, the job runs in another, and payroll and billing happen in a third, so somebody re-keys the same numbers two or three times per job.
The other concentration is chasing: quotes that went out and were never followed up, documents requested and not returned, and status questions answered one phone call at a time.
What we are not claiming. None of the above is a criticism of how this sector runs. It is a description of a business that is genuinely seasonal, genuinely document heavy, and genuinely built on relationships that do not move to software just because software exists. Where a process runs a few times a week and one person holds it comfortably, we will say so and recommend the smaller thing.
The jobs
Four jobs a systemdoes on a site.
Each one is a job, not a feature, and each one has a number attached that your office already tracks somewhere. The third column names the measure rather than a value, because a value for your business is yours to supply.
| The job | What it looks like here | The number it moves |
|---|---|---|
| Chase the quote | Every quote issued gets followed up on a schedule you set, twice, and then it stops. Every touch is logged against the job so nobody chases twice or not at all. | Win rate on quotes that were followed up, against those that were not. |
| Answer the status question | A customer, a site super or a general contractor checks the schedule, the documents and the stage themselves, at any hour, reading from the system that holds it. | Calls per week that used to be a person answering a question. |
| Stop the re-keying | The estimate, the job and the invoice read from one another rather than from a person retyping. Change orders exist in one place with a date on them. | Office hours per job spent moving numbers between systems. |
| Make the documents findable | Clearance certificates, training records, insurance, drawings and change orders in one place with expiry dates and an audit trail. | Time between a document being requested and a document being produced. |
Scroll the table sideways to read it.
Sized with your own numbers
What chasingis actually worth.
The most common first project in this sector is following up quotes, so here is the sum that sizes it. Every figure in it is yours. We do not publish a win rate or a chase rate for construction, because we would be inventing one.
| The number | Where you already have it | Your figure |
|---|---|---|
| Quotes you issue in a month | Your estimating system, or the folder they are saved in. | your figure |
| Share of them that get a second follow up today | Ask the estimator. The honest answer is usually a range. | your figure |
| Your win rate on quotes that were followed up | Compare won jobs against the ones with a logged follow up. | your figure |
| Your win rate on quotes that were not | The same comparison, the other way. | your figure |
| Average job value | Your accounting system, over the last twelve months. | your figure |
| Extra jobs a month if every quote were chased twice | The two win rates, the difference, multiplied by the unchased quotes. | the result |
| What that is worth a month | The line above, multiplied by average job value. | the result |
This is an arithmetic, not a claim. Every figure in it is yours, and the two win rates in the middle are the only ones that matter. If the difference between them is small, chasing is not your project and we will say so on the discovery call rather than after the build. The same arithmetic runs for status calls, for re-keying hours and for document turnaround, and it is the first thing we do together.
By category
What a constructionbuild connects to.
By category, with the systems this sector actually runs. Every connection is checked by name during scoping, because the one that matters most is usually the one that is hardest to reach.
Estimating and takeoff
Where the quote is built, and where the numbers everything downstream uses come from.
Bluebeam, Sage Estimating, PlanSwift, STACK, an in house spreadsheetProject management
Where drawings, submittals, RFIs, change orders and daily reports live.
Procore, Autodesk Construction Cloud, Buildertrend, CoConstructConstruction accounting and ERP
Where job costing, progress billing and holdback are actually tracked.
Sage 300 Construction and Real Estate, Jonas, Spectrum, QuickBooksField service and dispatch
Where a service trade schedules, routes and closes a call.
ServiceTitan, Jobber, FieldEdge, an in house boardTender and bid distribution
Where public and private opportunities arrive and where bids are submitted.
MERX, BC Bid, provincial and municipal tender portals, invitation servicesWorkforce and compliance records
Where clearance certificates, training records and site orientations are kept.
your payroll system, a safety platform, a document libraryApplicant tracking
Where an application from a careers page has to land.
BambooHR, Lever, Workable, an in house boardDocuments and drawings
Where the current version of a drawing is supposed to be.
SharePoint, Google Drive, Dropbox, the project management system
Every connection is validated by HUREAL's engineers during scoping and confirmed in writing before signature. Where a system genuinely cannot be connected, you hear it during discovery rather than during the build, and the scope is drawn around it instead of making a platform migration the price of entry.
What a build here is designed around
What a build herehas to be designed around.
Construction carries requirements a general business system does not, and most of them are about documents, dates and who received what. These are the ones a build in this sector is designed around, and the line between what we build and what your counsel decides.
-
Payment and lien legislationProvincial, and prompt payment where it applies
What we design forEvery province has lien legislation with holdback and deadlines, and several have added a prompt payment regime with statutory clocks and a right to adjudication, among them Ontario's Construction Act and Alberta's Prompt Payment and Construction Lien Act. A system that touches invoicing here records when a document was issued, when it was received and by whom, because those are the dates the clock runs from.
What we document for your counselThe issue and receipt record per document, with times and recipients, exportable. That is the evidence your counsel asks for first, and reconstructing it afterwards from an inbox is the expensive way to produce it.
-
Workers' compensation and safety recordsProvincial boards, and site requirements
What we design forClearance certificates, training records and site orientations have expiry dates, and a subtrade with a lapsed one does not get on site. Where a system holds them, it holds the expiry as a date rather than as a file name, and it tells somebody before the date rather than after.
What we document for your counselWhat is held, where, for how long, and who can reach it, prepared so your safety officer and your counsel are reading the same list.
-
Trade licensing and qualificationProvincial regulators and authorities
What we design forElectrical, plumbing, gas and other trades are licensed provincially, and what a business may say about its own qualifications is constrained by the regulator that issued them. Any claim of licence, certification or qualification on a site we build is traced to the document that supports it before it is published.
What we document for your counselThe claim, the document behind it, and the date it was checked, so a marketing page can be audited against a register rather than against memory.
-
AccessibilityWCAG 2.2 AA, plus AODA or the Accessible Canada Act where they apply
What we design forPublic sector and larger private sector organizations in Ontario carry accessibility obligations for information and communications, and bidding public work often brings requirements of its own. Keyboard, screen reader, contrast and reduced motion are tested rather than asserted, on every surface a person actually uses.
What we document for your counselThe test results per surface and the standard tested against, so a barrier report can be answered with a measurement instead of an apology.
-
PrivacyPIPEDA, and provincial privacy legislation where it applies
What we design forA careers page, a customer portal and a service history all hold personal information. A stated purpose per system, the smallest data set that does the job, and retention set per record type rather than left at a default.
What we document for your counselWhat the system holds, where it is stored, who can reach it and how long it is kept, written for whoever in your business owns that question.
HUREAL designs to a standard, tests against it, and documents what was built. The determination is your counsel's to make, and a vendor offering to make it for them is offering something they do not have. Our own conformance target and how to report a barrier are on the accessibility page.
Where to start
Which of the eightmatter most here.
Four services, and the reason in each
-
Agentic Operating Systems
Chasing is the single most expensive thing a busy office forgets to do, and it is the smallest thing an agent can take over first. Quotes followed up on a schedule you set, twice, then stopped, with every touch logged against the job.
-
Customer portals and booking
A site super, a homeowner or a general contractor checking status themselves removes the call rather than answering it faster. In a sector where the office is interrupted all day, removing the request is the larger saving.
-
Integrations and Data
Estimating, project management and accounting are three systems that were never designed to agree. Most of the office hours in this sector are spent moving numbers between them, and that is a connection problem rather than a software problem.
-
Corporate and marketing websites
Two audiences read the same site: the client building a shortlist and the tradesperson deciding whether to apply. In a sector hiring on every site, the careers half of the site is not an afterthought.
Read on this
Articles about scoping, pricing and running a build in this sector will live under the Insights index.
three articles to set
Asked and answered
What contractorsask us.
-
Can you connect to our project management system?
Usually, and we check the specific system by name during discovery rather than after signature. Mainstream construction platforms have ways in. Older and locked down systems are where the surprises live, so we look at those first and draw the scope around what we find.
-
Our estimator is the bottleneck. Can software fix that?
Partly, and it depends which part. Software can remove the re-keying, the chasing and the document hunting that surround estimating. It does not build the estimate, and anyone telling you it does has not watched one being built.
-
What happens in our busy season?
The system is sized for the peak rather than the average, because the peak is the only week that pays for it. That is a scoping decision made in the first session, and it changes what gets built rather than only how it is hosted.
-
We are hiring harder than we are selling. Does that change the project?
Yes, and it often changes which project comes first. A careers surface connected to your tracking system, saying what the work actually is, is a smaller build than most people expect and it competes for budget with the client facing half of the site.
-
Can a customer see their job without phoning us?
That is what a portal does, reading from the system that holds the schedule rather than from a copy of it. Which stages a customer sees, and which ones need a person, is decided in design rather than discovered in support.
-
Who owns what you build?
You do. The code, the content, the data and the accounts are yours with admin access from day one, and we build on mainstream technology so somebody who has never met us can maintain it.
-
What does it cost?
The build price is set after the discovery call and sent in a written proposal, because an honest number needs the scope. The arithmetic above is what we fill in together before anybody talks about a build.
Close
Two ways to start.Both end with a document you own.
Book a discovery call
For when you know which part of the office is losing time and want the scope before the spend. A discovery call with the people who run it, estimator included. We fill in the arithmetic above with your own figures, and afterwards you get a written proposal with a scope, a price and a timeline you can sign or walk away from.
Book a discovery callRequest a performance audit
For when you want the evidence before the decision. We look at what you have against the job you want it to do, and give you a prioritised plan with the arithmetic attached. The document is yours either way.
Request a performance auditKnow what you are building? Book a discovery call. Not sure where the problem is? Request the audit. If neither is right for you, we will say so, and tell you what is.
Not ready for either? Talk to the demonstration in your browser for three minutes, or paste your own address and hear it answer as your business. No form and no booking, and the transcript arrives by email a minute later.
Hear it work
Built for a season, a bid calendar and a clock.
HUREAL / Material studies