McKercher Labs | McKercher Corporation

What it does

Built for operations the group runs itself.

McKercher Labs designs and builds the systems the group depends on. The publishing platform behind this site, the staff tooling behind it, and the live installation map behind the energy businesses are all its work, running in production rather than described in a proposal.

That is the basis of the practice. Building for service operations is a different problem to building software in general, and the group runs service operations at scale, so the operating problem is understood before a system is proposed. It is not positioned as a general-purpose software developer or an artificial intelligence organisation.

Work begins as internal development against a defined problem, and is offered commercially only where it has proven itself in use. A suitable project has an accountable owner, access to the operating context, and an outcome that can be assessed afterwards. Projects are contracted, delivered, and accounted for in Australia.

External work is held to the same test. A system built for a client is handed over on completion, and McKercher Labs retains no access to it, holds no editorial role in what it carries, and does not maintain it in production. Where that work appears below, the client names the relationship in its own disclosures first.

Established: 2021
Model: Internal first
Focus: Service operations
Delivery: Bespoke projects
Accountability: Australian

Systems in production

What's running, what's building.

mckercherOS

Staff-facing operating platform for the group, in production for publishing, editorial workflow, group updates, and enquiry handling

In production, staff access

Customer-facing operating platform for the energy businesses, in production as the client sign-in portal, and as the live installation map with its public API

In production, publicly inspectable

Field reference for the solar trade, with a fault-code library across fifteen brands, standards explainers, and calculators built for use on site

In production, publicly inspectable

5 more systems4 publicly inspectable

mckercher.com.au

Group publishing platform, with editorial governance, structured data, and automated content checks

In production, publicly inspectable

pswenergy.com.au

Established retail platform for the installation business, with migration to a pswOS build underway

In production, rebuild underway

perthsolarwarehouse.com.au

The group's longest-running retail property, in service since 2013

In production, publicly inspectable

solaranalytica.com

Energy-data platform publishing sourced market reports, indices, and grid monitors, with every figure named to its source

In production, publicly inspectable

Evidence-based solar product benchmark, with its Watt assistant, built for Solar Analytica Pty Ltd and handed over on completion

In production, publicly inspectable

Production and maintenance

Built here. Kept running by someone else.

McKercher Labs designs and builds. It does not carry ongoing production maintenance for what it ships, whether the system belongs to a client or to the group itself, and the register above is no exception to that.

That work is carried out by Gigabit Agency (opens in a new tab), an independent engineering firm. Gigabit Agency also provides services to McKercher Corporation as a client, on a paid, ongoing basis. The two are separate businesses, and neither holds an equity interest in the other.

Project shape

From operating need to measured use

01
Define the operating problem
Establish the people, decisions, information, and constraints involved before proposing a system response.
02
Design the connected workflow
Map responsibilities, handovers, information flows, customer communication, and the controls required for accountable use.
03
Integrate with the operating environment
Connect appropriate existing systems and records without treating technology as a substitute for process ownership.
04
Measure the operational result
Assess adoption, visibility, consistency, and administrative load against the outcome defined at the beginning of the project.
05
Maintain operating ownership
Leave responsibilities, records, controls, and future changes with an identified owner so the system remains useful after initial delivery.

Public project evidence standard

Further reading

Where the detail lives.

Update, 13 Aug 2026Pulse archive gains stronger evidence controlsTwelve migrated articles now carry source-backed publication dates, with stronger checks aligning legacy article cards to the evidence retained in each record.Update, 21 Jul 2026A shared view of the McKercher groupGroup activity, business identity, current guidance, and organisational standards now sit in one public reference point.

Get in touch

Discuss a bespoke systems project

McKercher Labs considers projects with a defined service operation, accountable owner, and measurable operating requirement.

Make a project enquiry