← muthari.com

Specialist vs general contractors: why the software is different

Muthari guides · for contractors who fabricate what they install

A general contractor coordinates: it buys packages, manages subcontractors and controls a site. A specialist contractor fabricates what it installs: it runs a factory and a site, buys raw material rather than packages, and owns the truth in between — which batch went to which zone, which stage each zone reached, what left on the truck, what went into the wall. That difference is why general-contractor software fits a specialist badly. It has no goods receipt that writes stock, no batch with a QC decision, no production stage gated on a drawing, no delivery note that a site receipt closes, no claim built from installed quantities. Fabrication software has the opposite gap: it stops at the factory door. The specialist contractor has been running the space between on WhatsApp.

Five ways the work is different

A factory and a site

The general contractor's operation is the site. The specialist's is two operations with a truck between them, and most of the losses happen in the gap: material issued to the wrong zone, a panel rebuilt because nobody knew it was in coating, a delivery the site says never came.

Batches, not packages

The GC receives a finished package and signs. The specialist receives 300 of an ordered 500 profiles, rejects 50 at incoming inspection, quarantines them, returns them, and issues the rest to three zones. Each of those is a record with a quantity and a name, and the store is the department that writes them.

Stages with inspection at the end

A GC tracks a subcontractor's percentage. A specialist moves each zone through fabrication, finishing and inspection, against a drawing that may be revised halfway, and cannot ship anything that has not passed.

Zones, not activities

The GC's unit is the subcontract package. The specialist's unit is a zone of the BOQ — one label, one quantity — which is what is taken off, requested, fabricated, shipped, installed, inspected and claimed. Everything hangs off it.

Claims from installed quantities

The GC certifies subcontractors; the specialist is the one being certified, line by line, against installed quantities the consultant will check. The claim must carry its own evidence and must never claim the same quantity twice.

What that means for software

What it does not mean

A specialist still needs the tools it has. The accounting system or ERP runs the money; the fabrication software runs the cutting lists and machine data; the consultant's document system runs the correspondence. The specialist's operating layer sits between them — the one place where the work moves and the record writes itself — and should not pretend to be any of them.

How Muthari OS handles this. Muthari OS is built around the fabricate-and-install spine rather than a general contractor's: engineering (the submittal and drawing register with response ages and gates), procurement (request, multi-step order approval, goods receipts with partial-delivery arithmetic that mint stock batches), store (an append-only movement ledger with QC decisions, issues by zone, approved borrows between projects), factory (zone stages with the drawing revision on every stamp and QC before dispatch), logistics (delivery notes, trips, a QR per zone, site receipt with the signer's name), site (daily installation entries capped at zone quantity, MIR and WIR verdicts with stamped photos, gated handover), and commercial (approved budgets gating claims, variations and omissions on the record, previous quantities derived from the last invoice). It is not an ERP and not design software; it runs beside them. Built by contractors in the trade.

The operational model this implies · What construction operations software is

Book a free demo  See the whole system →