Partner Program
Your clients don't pay you to format documents. They pay you for judgment — which controls matter, what the regulator will accept, how this site actually runs. ProgressOS takes the production work off your desk so more of the engagement goes into the part they're actually buying.
A procedure suite that takes eight days to write is not eight days of expertise. It's one or two days of expertise and six days of transcription, formatting, version control and re-work. You're billing your most experienced people at day rates to do production work.
At, say, A$1,800 a day, saving a single day a month covers a ProgressOS licence several times over. Most partners save considerably more than one day — and the saving compounds, because the capacity you free up is capacity you can sell.
More engagements in the same calendar, without hiring for production capacity you only need in bursts.
Fixed-price work stops eating your delivery days. The scope you quoted is the scope you deliver.
A structured draft in the room, not three weeks later. Review cycles start while the workshop is still fresh.
ProgressOS is designed around the documentation ANZ heavy industry actually runs on — not generic business process templates.
JSEAs, SWMS, risk registers and safe work procedures across multiple client sites, aligned to the Model WHS Regulations.
Policy and procedure libraries for ISO 9001, 14001, 45001 and 55001 certification and surveillance programs.
BPMN process maps, swimlane flows and process libraries generated from plain-language description rather than Visio time.
Training content, learning objectives, competency questions and assessment criteria built from the operational documentation itself.
Work instructions extracted from OEM manuals — the conversion work that normally means SME workshops and months of effort.
Operational readiness and commissioning documentation at volume, across sites, to a consistent structure.
Written for people who will bet a client deliverable on the answer, so it says what is true now rather than what is on the roadmap.
Documents currently export under Progress Collective branding. Configurable client branding is what we're building next, and the partners we're working with now are shaping how it works. If it's a blocker for your engagements, say so early — that's exactly the input we want.
Work is organised into projects inside your workspace, so each client's process maps, procedures and risk documentation live in their own space rather than one shared pile.
Included from the Professional plan up. When you're mid-engagement with a deadline, you're not in a general queue.
No. It replaces the forty hours between the workshop and the deliverable. The workshop still needs you in it, the controls still need someone who knows the site, and the document still needs your name on the review. What goes away is the transcription.
ProgressOS produces a draft. A competent person reviews and approves it — you. The duty holder does not change and neither does your professional sign-off. The review step is a control, not a formality, and the workflow is built around it.
Not yet, and we would rather say so plainly than surprise you mid-engagement. Documents export under Progress Collective branding today. Configurable client branding is what we are building next, and the partners we are working with now are deciding how it behaves — including whether branding is set per workspace or per client. If that timing matters to your engagements, it is worth a conversation now rather than later.
Yes. Work is organised into projects inside your workspace, so each client's process maps, procedures and risk documentation stay in their own space rather than in one shared pile. Branding and document templates are currently set at workspace level, not per project.
No. Start free, move to a paid plan when the work justifies it, and change plan as your workload does. Consulting workload is lumpy and the arrangement should survive a quiet quarter.
Mining and resources, utilities, energy, manufacturing, infrastructure and construction, and local government — asset-intensive and regulated operations. The document types are built for ANZ practice: JSEAs, SWMS, work instructions, ISO-aligned procedures and risk registers.