Skip to content

Software

Software built for a purpose.

Not a template with your logo on it. Each of these was designed around who uses it and what they have to get done. All of them run below with invented organisations and data. Use them.

01Public service

Case management and complaint intake

Who uses itPublic-service teams, community offices and any organisation that answers to the public.

What gets lost without itComplaints arrive on WhatsApp, at the counter and by phone, then disappear between departments. Nobody can show the resident what happened.

  • WhatsApp, Mon 21:48Lampu jalan depan blok C Lorong 7 dah tiga malam tak menyala.
  • Counter form 0415, Tue 07:55Lampu jalan rosak dekat gerai minuman, Lorong 7.
  • Phone call, Tue 08:05Street light out near the surau junction. No name given.
CRC-2041, one caseStreet lamp out: post LP-07-143 reports, Lighting and Electrical

Interactive demonstration

Case management and complaint intake

For an invented public-service centre: the Civic Response Centre

Invented organisation and dataSuggestions are scripted for this demonstration: no live AI call
  1. Intake
  2. Triage
  3. Acknowledge
  4. Repair
  5. Verify
  6. Close
  7. Oversight

01 / 07Three reports of a dark street lamp came in overnight and this morning. CaseDesk thinks they are one problem. As Aina, the duty officer, open them as one case.

Three people report the same dark street lamp on three channels. Follow it to one case: a suggestion, a person's decision, a promise to the residents, evidence, a supervisor's check, and the record of all of it.

  1. IntakeThree reports of a dark street lamp came in overnight and this morning. CaseDesk thinks they are one problem. As Aina, the duty officer, open them as one case.
  2. TriageCaseDesk suggests a unit and a priority, with its reasons. You decide each one. Show me raises the priority: a dark street where children walk at night is a safety risk to the public.
  3. AcknowledgeThe case has an owner and a promise. Tell the residents who can be reached.
  4. RepairThat night, as Hafiz from the lighting crew: attach the after-photo and mark the lamp fixed.
  5. VerifyNext morning, as Mei Ling, the supervisor: check the evidence before anything is closed.
  6. CloseTell the residents it is fixed and how to reopen it. Every report in the case closes with one repair.
  7. OversightAs Ravi, the centre manager: see the promise kept, and which promises are at risk now.

The system, in four partsYou ran it from start to finish.

  1. InputThree reports of one lamp: WhatsApp, the counter, the phone
  2. SystemOne case, located and linked, with a promise and evidence
  3. Human decisionThe officer decides unit and priority; a supervisor checks the evidence
  4. OutcomeEvery reachable resident is told; the audit trail keeps each step

Start a project like this

02Operations on paper

The step that cannot be skipped

Who uses itPlants, workshops and production floors that still run on batch cards, clipboards and logbooks.

What gets lost without itThe batch card says a step was done. Nobody can prove it was, and the product has already left.

  • BatchWB-2417 ext. white
  • Charges1194 ✓
  • Anti-mould✓ F 08:50
  • Pails59 x 20 kg
Filling, refusedThe anti-mould additive has no recorded weightA tick is not a weight

Interactive demonstration

The step that cannot be skipped

For an invented paint maker: Warna Bayu Sdn Bhd

Invented organisation and data
  1. About to fill
  2. Locked
  3. Weighed in
  4. Filled
  5. Reconciled
  6. Day-end check

01 / 06Kavitha has batch WB-2417 at the filling line. The paper card shows the anti-mould additive ticked. Press Start filling.

A batch of exterior paint is about to be filled. The batch card says the anti-mould additive went in; the record has no weight for it. See the step refused, weighed with proof, reconciled and checked against the paper.

  1. About to fillKavitha has batch WB-2417 at the filling line. The paper card shows the anti-mould additive ticked. Press Start filling.
  2. LockedFilling was refused: the additive has no recorded weight. Go to Faizal at the mixing station: weigh it in, or say you are not sure.
  3. Weighed inThe additive is on record with a photo of the scale's display. Filling is open: record each pallet as it is filled.
  4. FilledBoth pallets are recorded, each with its own label. Close the batch: what went in is checked against what came out.
  5. ReconciledClosing worked out what went in against what came out: the loss is computed, not typed, and checked against the 2.5% limit. The pallets wait in quarantine for the lab. At the end of the day Mr Tan checks the paper card against the record.
  6. Day-end checkThe day is signed, every difference explained. The record shows who did what, when, with what proof.

This is an interactive workflow demonstration with sample data, not a connected plant system.

The system, in four partsYou ran it from start to finish.

  1. InputA batch card ticked, and a weight that was never recorded
  2. SystemA step that refuses to proceed until the weight is typed from the scale, with a photo of its display
  3. Human decisionThe operator weighs it; the owner decides holds and checks the paper at day end
  4. OutcomeEvery kilogram accounted for, and the paper and the record compared

Start a project like this

03Leadership

Escalations, decided

Who uses itOwners and managers of growing companies, where issues climb to the person who can approve them.

What gets lost without itAn issue goes up as WhatsApp messages, then becomes a meeting: five people, an hour, no clear decision, nothing written down.

  • GaneshRaises it on the floor
  • Li TingGives finance's view
  • NorhayatiDecides on one screen
Decided1 h 40 min, no meetingEveryone told; the record wrote itself

Interactive demonstration

Escalations, decided

For an invented spice-paste maker: Lada Tujuh Sdn Bhd

Invented organisation and dataSuggestions are scripted for this demonstration: no live AI call
  1. Raise it
  2. A view
  3. One screen
  4. Decide
  5. Everyone told
  6. The record

01 / 06Ganesh, the production manager, raises the issue from the floor on his phone. Before he sends it, the system shows where it will go.

An issue raised on the factory floor goes to the right person, gathers the views it needs and is decided on one screen, without calling a meeting.

  1. Raise itGanesh, the production manager, raises the issue from the floor on his phone. Before he sends it, the system shows where it will go.
  2. A viewLi Ting in finance gives her view on her laptop, item by item. Ganesh will not see it until the decision.
  3. One screenPuan Norhayati opens the escalation: the ask, the money, Li Ting's view on each item compared by rule, and a suggestion that is not a decision.
  4. DecideShe decides on that screen. Here she approves and adds a condition of her own.
  5. Everyone toldGanesh and Li Ting see the decision and their own actions, and acknowledge them.
  6. The recordThe record wrote itself: who raised it, who gave a view, who decided, what and when. No meeting.

The system, in four partsYou ran it from start to finish.

  1. InputAn issue raised once, with the facts and the ask
  2. SystemRouted by approval limit; views compared by rule; a suggestion, not a decision
  3. Human decisionThe person with the authority decides on one screen
  4. OutcomeA recorded decision, with conditions, actions and owners

Start a project like this

Where AI sits

A suggestion, a reason, and a person who decides.

  1. 01SuggestThe system proposes a unit, an action or a direction.
  2. 02ExplainIt shows why, in the words of the record itself.
  3. 03DecideA person accepts, changes or rejects it, and the choice is recorded.

In these demonstrations the suggestions are scripted: no live AI model is called, and no data leaves your browser.

Tell us what's getting lost.

Yours will not look like any of these. It will look like the way your organisation works.