What we know, and what we should test

Three operating gaps. One measurable challenge.

The Credit Admin findings come from Amalan Setar's own workflow. Procurement is a hypothesis to test, not a claim.

2-3×

The same facts are entered again

Buyer and project data moves from documents into Excel, IFCA and other working files.

Time + mistakes
People

The process lives in individual heads

When the person changes, the handover depends on memory instead of a visible workflow.

Continuity + scale
RM20k

Approvals need evidence, not chasing

Management should see what is waiting, which rule applies and what proof is missing.

Visibility + compliance
Test

Can a wider supplier benchmark save money?

Run the same live requirement through the current process and an AI-assisted search.

Cost + control
These are not signs of a broken business. They are operating leverage waiting to be captured.
Amalan Setar01 / 05
What AI changes

Make the workflow carry itself.

Start with one real Credit Admin case. Keep the systems that work, remove the manual movement around them.

01

Document arrives

Invoice, contract, LOA or buyer letter.

→
02

AI reads it once

Buyer, project, amount, dates and clauses.

→
03

Staff review exceptions

Low-confidence fields are shown, not hidden.

→
04

Rules check the evidence

Missing proof stops the case before approval.

→
05

One verified handoff

Draft the update for IFCA and the working record.

MeasureMinutes per case
MeasureManual entries per case
MeasureExceptions caught
MeasureApproval turnaround
Outcome: staff handle judgement, the system handles movement, checks and history.
Amalan Setar02 / 05
Why this can become a business

One proven starting point. Seven workflows to map.

Go deep in Credit Admin first. Then map the remaining departments, connect only what proves useful, and build the operating core from evidence.

To map

Finance & Accounts

Invoices + reconciliation

Walkthrough done

Credit Admin

Billing + handover letters

To map

Project

Authority + contractor compliance

To map

Cost & Contract

Estimates + progress

To map

Sales & Marketing

Lead follow-up + conversion

To map

Customer Service

Enquiries + case history

To test

Procurement

Sourcing + quote comparison

To map

HR & Admin

Reviews + cost monitoring

Improve one workflow→Connect the useful patterns→Build the Malaysian property developer operating system
Amalan Setar03 / 05
The first measurable proof

A proof that grows into a blueprint.

Start with one live procurement challenge. Prove the value in Amalan Setar, then preserve the pattern that made it work.

One live brief

Exact specification, quantity, quality standard, delivery date and payment terms.

A

Current team

Normal supplier process.

VS
B

AI team

Wider search, normalised quotes, preserved evidence.

01Landed cost
02Specification match
03Quality confidence
04Lead time + terms
05Audit trail
1-2%saving is the hypothesis to test, not a promise.
Prove it hereOne live Amalan Setar requirement
→
Codify what worksEvidence, controls and repeatable workflow
→
Set the blueprintA capability the industry can follow
Amalan Setar04 / 05
The shared ambition

Build the blueprint here.

Twelve months inside real workflows can create the first Malaysian property-developer AI operating system.

Inside Amalan Setar

Lead with the operating advantage

Faster, more visible workflows shaped around how the company actually runs.

→
From proven work

Set the standard others can follow

A Malaysian operating blueprint grounded in evidence, not a generic software promise.

Months 1-3

Map + prove

First Credit Admin workflow.

Months 4-6

Control + test

Evidence gates + procurement proof.

Months 7-9

Connect + expand

Proven patterns across departments.

Months 10-12

Stabilise + codify

Operating core + industry playbook.

Shared buildRM30,000 / month
×
Build period12 months
=
Total commitmentRM360,000
Begin where the work is realOpen the first workflowName the executive ownerAgree the baseline measures
AMALAN SETAR · INTERNAL REVIEW