Apex Performance

Operational data integrity·Process maturity transformation

Bad data does not announce itself. It just spreads.

We find what is silently broken underneath. Then we build the workflow that runs on top of it.

What it costs to build on it

Before anything is built on top

Automation does not fix a broken process. It multiplies it.

A process you have not examined can be automated exactly as it is. The result runs faster. It is also faster at whatever the process already gets wrong. We establish what is there first, in writing. We repair nothing until you have decided what matters.

The system you specify

  1. Intake
  2. Making
  3. Proofing
  4. Authorisation
  5. Custody
  6. Tracking
  7. Scorekeeping

What it runs on

4,183 records a month

One record

700148223874

03/04/2026

Read month first, this invoice is thirty days older. That decides whether anybody chases it.

D03

Five of your seven stages are standing on them.

There is no patch for this. Somebody reads the file first and writes down what is actually in it. Then you decide what to build.

Automating this does not change the number. It changes how quickly you reach it.

Where that starts

Ten seconds, with a date from your own records

Your ageing report may be a month out, on dates that look correct.

Day, month and year, written in numbers. Nothing typed here leaves your browser.

Read day first 3 April 2026
Read month first 4 March 2026

30 days apart. Read month first, this record is 30 days older. That decides its ageing bucket, and whether anybody chases it.

You write day first. Your tool reads month first. The dates compute wrong. Nothing in the value says which convention was typed. Where both readings work, only you can settle it. Where both orders sit in one column, no single convention repairs it.

One delivery, read end to end

Synthetic delivery — shapes real, content invented

A file can reconcile cleanly and still be wrong.

This delivery was accepted.

  • entity-a-ap-jul.xlsx 12 → 15 → 16 columns across three deliveries APX-D04 · shape drifted
  • entity-a-ap-aug.xlsx 16 rows · the file being scanned scanned
  • entity-b-remit-aug.zip 3 members · one encrypted APX-D08 · listing needs no password, reading does
rows read16 / 16
classes found8 / 8
The file says18typed into the summary block

Four records that do not exist

APX-D06 · the summary was typed once. The rows moved on.

The rows say14rows with a populated key
Delivery entity-a-ap-aug.xlsx, sixteen rows as received. Two of them are sub-total rows rather than records. Column four has no header and carries the entity code.
# vendor_ref counterparty no header — this column carries the entity code invoice_date amount status
014500911144450Tenaga Selatan Sdn BhdENT-A0412/03/202648,200.00settled
02700148223391Melur Logistics BhdENT-B1119/03/20267,915.40settled
0333201884007412Kilang Damai Sdn BhdENT-C0221/03/2026126,400.00settled
0488001100220000001→ 88001100220000000Arus Murni EnterpriseENT-D0124/03/20263,180.00settled
054500911144683Sri Wangsa TradingENT-A0427/03/202619,640.00settled
0633201884007509Bina Utara Sdn BhdENT-C0202/04/202688,050.00pending
078.80011002200005E+16Selat Timur Sdn BhdENT-D0114/04/202661,900.00settled
0833201884007633Nusa Kirana BhdENT-C0217/04/202633,700.00pending
09sub-total, rows 01–08388,985.40
104500911144902Harmoni Steel Sdn BhdENT-A0922/04/202675,220.00settled
11700148223874Pinnacle Freight BhdENT-B1103/04/20263 Apror4 Mar52,140.00settled
1233201884007788Batu Emas ResourcesENT-C0206/05/2026118,900.00settled
134500911145037Anggerik Retail Sdn BhdENT-A0904/13/202616,275.00settled
14700148224120Puncak Aman Sdn BhdENT-B1124/05/2026143,600.00settled
15sub-total, rows 10–14406,135.00
1633201884007915Wira Cemerlang BhdENT-C0227/05/202621,050.00settled

Defect register

  • D01Identifier damaged by precisionrow 04Still in the file. Up to 10 references would match once stored
  • D02Collapsed to scientific textrow 07Unrecoverable — a fresh extract is the only route
  • D03Date order unresolvablerow 11Thirty days apart. It decides the ageing bucket
  • D04Delivery shape drifted3 deliveriesAmounts are read from the wrong column
  • D05Data under no headercolumn 4Postings land against the wrong entity
  • D06Summary disagrees with the rows18 v 14
  • D07Rows that are not recordsrows 09, 15Processed volume is overstated by two
  • D08Archive member will not openunrecoverableThe batch fails mid-run, after the window has closed

Scan complete

This delivery was accepted. Eight of the ten faults were in it.

Two of the eight cannot be recovered from this copy. Those need a fresh extract from the source.

See where your own operation sits

Where does yours sit

Every operation runs the same seven stages.

Work arrives, gets made, gets checked, gets approved, gets filed, gets kept, and gets counted. One question per stage. Answer all seven, tell us where to send the result, and it appears here and in your inbox. Apex keeps a copy.

The ladder: every stage sits on it. These seven questions reach L4.

  1. L1Ad hocDepends on who is on shift. No defined method.
  2. L2RepeatableA method exists, informally. Results vary by person.
  3. L3DefinedDocumented, published, actually followed.
  4. L4InstrumentedThe process emits data about itself.
  5. L5Self-improvingThat data drives change on a cadence.
Work moves left to right 0 / 7
  1. –Intake
  2. –Making
  3. –Proofing
  4. –Authorisation
  5. –Custody
  6. –Tracking
  7. –Scorekeeping

Answered –

Answer all seven to see an indicative level.

Built on public maturity-model norms: the CMMI level structure and ISO 9001 process discipline. The custody standard is read against published data-protection law: the PDPA 2010 in Malaysia, the GDPR in Europe, and HIPAA where health information is held. It reproduces no vendor's instrument and no client's material. We do not quote peer benchmarks we do not hold.

What stands behind it

Kudrat Lokman

Bank Negara Malaysia·The Wharton School·COO, building the world's first AI-native takaful operator

Ten named faults
Each on a permanent code. Codes are never reused and findings are never renumbered. A report written today still reads correctly in two years.
A library of broken files
One file for every fault. If a fault stops being caught, the build fails. The files were written to the detectors, so this is not an independent test.
Three house rules
We report what is wrong and never change your file. We assert no finding the data cannot support. A fault is never quietly dropped from the tests.
Eight controls for letting AI near your data
In development and not yet issued. Each control states whether it is in force today, built at engagement start, or still on the roadmap.
Seven stages every operation runs
The same seven the Assessment scores you against.

The codes, the files and the rules hold regardless of who reads the report.

Two ways in

Find out where you actually stand. And what to move first. Whether or not you do it with us.

The Assessment

You leave with a level you can defend. You leave knowing which of the seven stages is weakest, and why it is the one to move first. And where your reporting and your data disagree, if they do. Ninety minutes with whoever actually runs the operation. The gauge above takes your word for it. This one does not.

Guided, by invitation. Not self-serve.

The Blueprint

The thing you have been meaning to build, designed as if you were starting today. It starts with three days inside the operation and two weeks inside the data. That ends in an implementation plan: what to build, and in what order. Then it gets built, with named human approval points.

Starts with the seven free questions above. Either door stands alone.

build@apexperformance.my