What we have actually built.

The Monday morning page

Overnight it reads what the business already produces: the updates, the inbox, the schedule, the cost report. By Monday morning there is one page waiting. What is on track, what slipped, and the few things that need a decision.

Nothing new has to be written by anyone. The information already existed. It was just spread across a week of threads.

The follow-up chasing can be handled by it too, or left to a person. That is a setting, not a rebuild.

What it proves

That a week of asking "any update" can be replaced by one page, using only what the business already writes down.

Status

Built and running

BOQ estimator

A Bill of Quantities is uploaded. Every line item is read, matched to rates, gaps filled, subtotals calculated, preliminaries and contingency applied. A completed estimate comes out in Excel.

30 seconds · 13 line items · 3 sections · $8.17M desalination plant upgrade, fully costed

The estimator is not replaced. The first eighty percent, the repetitive copy from the last project, is done for them. Their time goes to the twenty percent that needs judgement: adjusting rates, checking assumptions, and the things that only come from years on real projects.

What it proves

That a document heavy, rules based task can be done in seconds without the data leaving the client's control.

Data

Runs with zero data retention, so the Bill of Quantities is processed and immediately discarded. Or runs entirely offline on a local model, with no internet connection at all.

Finished documents from a project folder

Fourteen files from a real project folder: specifications, cost reports, risk registers, meeting minutes. One instruction: generate a steering committee report.

What came out: a formatted Word report with schedule and cost performance indices and top risks, an Excel dashboard with working formulas, and a PDF risk summary ready to send.

What it proves

That the output can be finished deliverables in the formats the business already uses, not answers in a chat window.

Data

Runs on the desktop. Files stay on the machine, history is stored locally, the folders it may see are chosen by the user, and each action is approved before it happens.

BidFlow

Tender documents in, structured analysis out. Every requirement, deviation and risk listed with the page it came from, plus an explicit list of what was not found.

A person still decides. They start from a marked-up document instead of page one.

What it proves

That a full document analysis system can be built and put into service, not just designed.

Status

Built and deployed

Certley

An Australian engineering certification marketplace and structural design platform. Live.

What it proves

Platform delivery end to end: design, build, deployment and operation.

Status

Built and running

HapiTech platform

The platform behind an engineering services business.

What it proves

A second delivered platform, built to serve a working business rather than a demonstration.

Status

Built

Multilingual survey platform

The problem. Reaching communities where English is not the first language, literacy varies, and people will not put their name to a response.

The design. Entry by QR code, no app and no account. More than one hundred languages. A voice mode for people who would rather speak than read. Anonymous submission. All data held in Australia. A live dashboard for the team, and an impact report a funder can read without translation.

Client

An Australian humanitarian organisation. Schollege is an approved vendor.

Status

Design and working animated demonstration. Not built.

What it proves

That the design work covers accessibility, language, data residency and the funder's reporting need, not only the technology.

Vendor progress reporting

The problem. Vendor updates arrive as emails, spreadsheets and PDFs, each in its own format. Most of a day goes into rekeying them into one report, and by the time it is issued it is already out of date.

The design. Updates are read as they arrive, in whatever format they come in. One consolidated report, with every figure traceable back to the update it came from. The day goes back to the person who was doing the rekeying.

Client

A large Australian water and desalination EPC contractor. Named on request with the client's permission.

Status

Assessed and designed with the business.

Site records capture

The problem. What happened on site is captured in notebooks, photographs, messages and memory, then written up later by someone who was not there.

The design. Records captured where the work happens, in the form the site team already uses, then assembled into the record the office needs, with each entry traceable to its source. The person on site stays the owner of the record. The double handling stops.

Client

The same EPC contractor.

Status

Assessed and designed with the business.

360,000 students

Twenty nine courses across e-commerce, digital marketing and AI, taught to more than 360,000 students over eleven years.

What it proves

That the training is not a side product built to sell consulting. It is the longer running half of the business.

Accreditation

CPD accredited