Use cases

The same system, four different days.

Telecom, security, electrical and civil, building supply — the four trades the platform was hardened in. Different work, the same failure: the job is real and the record of it is scattered. Here is what changes when it is not.

Job references and figures below are worked examples, not real customer jobs

By trade

01 · Telecom & ICT

480 metres of fibre, three regions, one margin.

Today

A fibre contractor wins a backbone run. The survey is in a site engineer’s phone, the cable order is a WhatsApp voice note, and nobody knows the job’s real cost until the accountant closes the month.

With the system

The survey opens the site. Material requests come off the tasks that need them, so procurement sees the cable draw the same day. Labour and materials land against the job while the crew is still on it — the margin is a number, not an autopsy.

Telecom & ICT — worked example

SITEMWZ-02 opened from survey480 M

MATERIALCable drawn against taskREQ-0118

COSTLabour + materials to dateTZS 2,910,000

MARGINAgainst quoted valueLIVE

02 · Security systems

Which camera, on which floor, commissioned by whom.

Today

A CCTV and access-control installer finishes a hotel job. Two years later the client calls about a failed door controller and nobody can find the commissioning record or the serial number.

With the system

Every device is a task against the site, with attachments and a photo check-in from the person who commissioned it. The service history is part of the site record, not a folder on somebody’s old laptop.

Security systems — worked example

SITEARU-05 · 34 devicesCOMMISSIONED

TASKDoor controller, level 3PHOTO ON FILE

HSEToolbox talk logged6 ATTENDED

SERVICECallout raised from historyREQ-0244

03 · Electrical & civil

The safety record an auditor will actually accept.

Today

Substation civils across two regions. Toolbox talks happen, but they live on signed paper in a site office, and proving them a year later means a drive and a filing cabinet.

With the system

Topic, attendees, duration, and notes are logged against the site by the responsible worker on the day. Arrival is timestamped. When a client or a regulator asks, the record is already there — and so is the person who ran it.

Electrical & civil — worked example

SITEDOM-01 substation civilsACTIVE

ARRIVALCrew confirmed on site07:14

HSEWorking at height9 ATTENDED

REPORTDaily report + status photoFILED

04 · Building supply

Which products get bought together, and by whom.

Today

A building material supplier knows last month’s total and nothing else. Reorder decisions are made from memory, and the best customers are whoever the counter staff happen to remember.

With the system

Reorder levels flag low stock before it becomes a lost sale. Retail analytics segment customers by recency, frequency, and value, and surface which products move together — so a cross-sell is a recommendation, not a hunch.

Building supply — worked example

STOCKCement 42.5N below reorderALERT

RFMTop segment identified38 CUSTOMERS

BASKETBought with · rebar ties0.61 LIFT

ACTIONRanked recommendationISSUED

One day

Nine people. One record. Nobody retypes anything.

A Tuesday on site DAR-07. Every line below is written by a different person from a different place — and every one of them lands in the same job history.

06:50Site supervisor
Opens the daily plan for DAR-07. Four crew assigned, two tasks carried over from yesterday.
07:14Crew
Arrival confirmed with a timestamp. GPS position logged against the site.
08:02Site supervisor
Toolbox talk logged — topic, six attendees, twenty minutes, notes.
10:31Fitter
Material request raised against the task that is waiting on it. Procurement sees it immediately.
11:05Admin
Purchase order issued against the project budget. Allocated-versus-spent updates on the spot.
13:40Customer
Opens their own portal, sees progress and deadlines on their project. Nothing belonging to anyone else.
16:20Admin
Invoice raised from the job record. TZS, 18% VAT, TIN and bank details already on the PDF.
16:21The system
Journal entries post themselves — receivable, revenue by service line, VAT payable. Balanced or refused.
17:38Crew
Daily report filed with a status photo. The job’s history closes the day complete.

Your customer

They stop calling to ask where the job is.

Every customer gets a portal into their own projects, purchase orders, deadlines, and progress — and nothing belonging to anyone else. That isolation is enforced on the request, not by hiding a menu.

Requests they submit arrive as trackable records with a type, a status, and a source, ready to be turned into a quote. Not an email that gets lost under forty others.

Customer portal — worked example

PROJECTPROJ-DAR-07-2026IN PROGRESS

MILESTONESecond fix complete18 JUL

POIssued and acknowledgedPO-0093

REQUESTNew scope submittedUNDER REVIEW

VISIBLEOther customers’ jobsNONE

The last row is the one that matters: a customer can never see another customer’s work.

Your trade is not on this page. It still fits.

These four are where we started. The chart of accounts, the roles, the document templates, and the report forms are all configured per deployment — so the system is shaped around your work, not the other way round.

Book a call See everything the platform covers