What shipped, what we learned on site, and where the platform is headed.
Product12 August 2026
Author once, project everywhere, keep the receipts
The thesis behind Briesa, in three moves.
A twelve-person concreter produces the same five documents fifteen times a year, in fifteen formats — one for every builder who engages them. The SWMS gets retyped, the insurances get re-uploaded, the licences get re-photographed, and none of it makes the next job any faster. The failure mode isn't ignorance of the rules; it's that compliance is administered by hand, by someone whose actual job is running a business.
Briesa's answer is three moves. Author once: your organisation's library — policies, SWMS, workers, competencies, plant, insurances — is written once and lives at organisation level. Project everywhere: every project, site and engagement draws from that library, so a site-specific document is an instance generated from a template, not a fresh document typed again. Keep the receipts: every action produces an append-only, version-bound record.
That last move is the one auditors notice. When the record is a by-product of doing the work — the pre-start signed on a phone, the SWMS acknowledgement bound to a revision — the audit pack isn't a separate exercise you scramble through the fortnight before. It's already there, because the work happened in the system that keeps the evidence.
Company12 August 2026
Why Briesa is construction-only
No generic core, no industry picker — one vertical, done properly.
Most compliance platforms are built horizontal: a generic core, a configuration layer, and a promise that it fits every industry. We went the other way. Briesa is for Australian construction, full stop — we archived the Industrial and Facilities modules rather than carry them half-built, and there is no industry picker in setup because there is nothing to pick.
Construction-only buys depth that a horizontal product can't reach. SWMS with the real high-risk construction work categories. Permits for hot work, confined space, excavation and working at height with dual sign-off. White Card captured at onboarding rather than tracked as its own register, because everyone in the industry holds one and they don't expire. Plant pre-starts that run from a QR code on the machine. None of that is configuration — it's the product.
The deepest consequence is structural. In construction, the same company is a subcontractor on Monday and a principal contractor on Tuesday, so Briesa never types an organisation as "builder" or "subbie" — your role is a property of each engagement, and three tiers of subcontracting is the same object repeated, not a special case. That's what lets one platform serve a sole trader in the ute and a builder running twenty-five sites, on one codebase, starting with NSW.
Pricing12 August 2026
Why you'll never pay Briesa per seat
Per-seat safety software punishes you for getting people onto safe systems of work.
Per-seat pricing has a quiet, perverse incentive at its centre: every worker you leave off the system to save a licence fee is a worker outside your safety system. In a category where the whole point is getting everyone signed on, inducted and across the SWMS, charging by the head means the bill grows precisely when the system is working. Past about twenty users, the per-seat leaders cost more than a complete platform should.
Briesa is priced per organisation — one flat monthly fee, banded by managed employee records, because that's the number that scales both your value and our cost. Field workers, contractors and visitors signing in are unlimited on every tier, including the smallest. The supervisor running a pre-start at 6am and the subbie acknowledging a SWMS are never a line item.
The tiers stay simple: each one up adds employees, sites and modules, training is included everywhere, and annual billing gives you two months free. If a builder invites you onto a project, you don't pay at all — responder accounts for uploading evidence and signing SWMS acceptances are free. Flat, predictable, and never a reason to keep someone off the system.
Product12 August 2026
Blueprints gets you certified. Briesa keeps you certified.
The ISO management system, generated from the work you're already doing.
ISO certification — 45001 for safety, 9001 for quality, 14001 for environment — has quietly become a de facto prerequisite for government and tier-one work in Australian construction. For an SME, the traditional path is paying a consultant thousands of dollars to produce a binder of management-system documents that starts going stale the day it's delivered.
Blueprints is our answer: an AI layer that generates your ISO-compliant management systems from your live operational data. Not a template pack with your logo swapped in — documentation built from the jobs, workers, plant and records already in your Briesa organisation, aligned to the clauses an auditor actually tests.
The second half of the sentence matters as much as the first. Certification isn't a document, it's an operating state, and most businesses lose it in the gap between audits. Because Briesa is where the daily work happens — the pre-starts, the incidents, the corrective actions, the training records — the evidence that keeps your management system true accumulates as a by-product. Blueprints gets you to the audit ready; the platform keeps you that way. It's a $199/month add-on on any tier, and included on Custom.
Company11 August 2026
Introducing Briesa
One platform for WHS compliance and site operations in Australian construction — built in Australia, for the people doing the work.
Compliance shouldn't live in a dozen disconnected spreadsheets, inboxes and binders. Briesa is the system we wished we'd had on site: one place that takes a business from the daily pre-start all the way to ISO certification, owned and hosted in Australia.
Today the demo is open. It runs the real platform on sample data — the hub, the registers, the dashboards — so you can walk the whole system before you bring your own organisation into it.
We're writing here as we build: what shipped, what we learned on site, and where the platform is headed. If that sounds useful, the changelog carries every release and the demo is the fastest way to see the current state.