Proofworks designs, builds and owns production software for industries we've worked in for decades — and puts the same engineering capability to work for clients through our automation studio.
Built by the founder. Proven in production.
The products and the studio aren't separate bets — they compound each other.
Vertical platforms we design, build, own and grow — solving real, painful problems in specific industries. Long-term equity value, and living proof we can ship production systems.
The same engineering capability, put to work for clients: private automations that remove operational friction. Cash today, into pain buyers already feel — and a source of proven patterns for future products.
The products prove we can build. That proof wins studio clients. Studio work funds the next product — and every client build becomes a reusable pattern. Round and round it goes.
Each one started the same way — a process someone was doing by hand, badly, at scale. Examples of what we build, not the limit of it.
Bid teams answer from memory. BidEngine drafts from their own evidence library — every claim traceable to work they actually did.

The flagship. A full bid workflow — intelligence, gate, draft, score, check — where most tools only do the drafting.
The other side of the table: scoring that is fast, consistent and defensible, with moderation and sign-off built in.

Built single-tenant from day one — evaluation data is sensitive by definition, so it runs in the client's own environment.
Contractors re-key finished jobs into the client's CAFM and hope it stuck. ProofSync moves it across and reads it back to prove it landed.
An evidence layer above the CAFM — it doesn't replace anyone's system, it makes two of them agree.
The data on who needs work doing is public — just scattered across a dozen registers. Rivant turns it into a ranked pipeline.

Built for programme origination — finding the work worth doing before it reaches a tender portal.
Every technology gets its own spreadsheet and its own specialist. ScopeNow assesses a site once, not five times.
One platform, many modules — because the hard part of scoping is the site, and the site doesn't change per technology.
A maintenance helpdesk is a full-time coordinator that never stops. Terri runs the desk — takes the call, raises the job in the CAFM, chases the contractor, and stops for a person when it needs judgement.

The call is about a tenth of her. The rest is operating your system — as a licensed user, authorised by you.
Everything above was designed and built by the people you'd be working with. If you've got a process that looks like one of these — manual, repetitive, expensive, and quietly costing you work — that's the studio's job.
Whether you've got a process to automate, a product to back, or a partnership in mind — let's talk.