Amalan Setar · Heads of Department

Your team spends the day
retyping.

Read it. Type it. Type it again. Check it. Chase it. Almost none of it is judgement.
What it costs · what can be handed over · where we start
Amalan Setar
01 / 16
The pattern

One figure. Typed over and over.

Different departments, different documents. Always a person in the middle, keying it in.
Something arrives
they read it
One person,
one keyboard
types it
A system
types it again
A spreadsheet
and again
A chat group
WastedHours a day, every day, on typing
WrongOne typo is now wrong in three places
SlowNothing moves until someone gets to it
Six versions
of one move
Paper → System
Person → Person
Sheet → Sheet
System → System
Check → Approve
Remember → Chase
Amalan Setar
02 / 16
This is not new

It has already happened to three other industries

Not a forecast. The same professionals, the same output, a fraction of the cost. The figures are the rough drop each of these has seen.
Legal documents
95%
cheaper to get a contract drafted than it was two years ago.
Was RM 20,000 and weeks of back and forth
Now drafted in minutes, to ninety percent
A lawyer reviews the last ten percent
Accounting and finance
80%
cheaper to keep a set of books straight and current.
Was a bookkeeper plus an accountant
Now reconciled and flagged as it happens
Errors caught the same week, not at audit
Design and creative
70%
cheaper to produce the same body of work.
Was RM 5,000 to 15,000 a project
Now concepts in minutes, changed at will
The designer polishes, does not start blank
The one still to come
Software. Some firms still charge the old rates for it. We would rather build it at the new cost and pass you the difference.
Amalan Setar
03 / 16
Why nobody fixed this before

Software was out of reach. Not anymore.

To have software built around your own way of working you needed a tech team and half a million ringgit. That is why good operators live with the spreadsheet.

What it used to take

A CTO at RM 25,000 to 40,000 a month
Two or three engineers at RM 10,000 to 15,000 each
Three to six months before you see anything useful
RM 500,000 spent before you know if it was worth it
No guarantee it works at the end of it

What it takes now

A small team, with AI doing the volume of work
Weeks rather than quarters
Roughly a fifth of the cost for the same thing
Built around your workflow, not a tool you bend to fit
You own it outright. Nothing is locked to us.
What actually changed
The cost of building software collapsed. A system built for exactly how Amalan Setar works is now a normal thing to buy.
Amalan Setar
04 / 16
What makes this possible

It reads what people actually send

Software needs everything typed into a field, in the right format. That is the only reason this work stayed human. That constraint is gone.
Scanned document
A system screen
A chat message
FROM  MBSB BANK BERHAD
Payment advice – AS/TSP-RSKU-1
11/08/2026  09:14
advice_OR1030629.pdf
Email attachment
A photo of paper
01
It reads all of these
›
02
It knows what it is looking at – which lot, which stage, which amount
›
03
It does the next step and never forgets one
The limit
It still does not decide. It brings you the decision, already checked.
Amalan Setar
05 / 16
The one thing to understand

This is not a chatbot

Same technology underneath. Completely different job. One answers. The other does the work.

A chatbot

Waits to be asked
Sees only what you paste in
Answers. You still do the work
Forgets you by tomorrow
Runs only while you sit there

An agent

Given a job, not a question
Connected to your systems, files, inbox
Does the work, brings you the result
Remembers every case, permanently
Runs whether or not anyone opens it
In one line
A chatbot is a clever person on the phone. An agent sits at the desk.
Amalan Setar
06 / 16
How to think about it

Your people get their day back

Nobody is being replaced. The same team, spending the day on the work that grows the business instead of moving information from one place to another.
What we heard
What changes
Retyping
“I have to type this again somewhere else.”
Typed once. The agent puts it everywhere it belongs
Waiting
“I am waiting on someone before I can do my part.”
Your part starts the moment the document lands
Checking
“I have to check everything is attached.”
It reaches you already checked. You judge, you do not verify
Chasing
“I have to remember to chase this.”
Chased on the date, every time. Nothing runs on memory
Digging
“I pull this from four different places.”
One report, built before you ask for it
One person
“Only one person knows how this works.”
The steps are written down and run without them
Amalan Setar
07 / 16
Departments 1 – 4 of 7

Where this lands

One example each. Your team will have more, and better ones.
Project Team
Today
Reports by email and chat · tracker updated by hand · programme checked by eye
With an agent
Reads every report · updates the tracker · flags what is behind programme
Cost & Contract
Today
Every submission a different format · rebuilt into one table · rates checked line by line
With an agent
One comparison table · every rate out of line highlighted · against history
Sales & Marketing
Today
Social, walk-ins, agents, chat · logged by hand · follow-up from memory
With an agent
Every lead in one place · daily list of who has not been followed up
Customer Service
Today
Which purchaser? which unit? · look it up · reply · hope it gets tracked
With an agent
Identifies the unit · pulls the account · drafts the reply · tracks to resolution
Amalan Setar
08 / 16
Departments 5 – 7 of 7

Same pattern, different paperwork

The documents change from desk to desk. The six moves do not.
Procurement
Today
Quotes as PDFs, emails, photos · comparison rebuilt by hand · chased from memory
With an agent
One comparison against spec · flag when a price moves · every order chased on the date
Finance & Accounts
Today
Keyed in · matched by hand · coded · filed · every one, problem or not
With an agent
Invoice matched to order and delivery note · coding proposed · only mismatches reach you
Company &
Corporate Admin
Today
Many companies · filings, licences, renewals, signatures · in one person's head
With an agent
What is due per company, before it is due · documents prepared · signature chased
Amalan Setar
09 / 16
One desk we have already sat with

The daily loop

One number. Typed three times. Every day. This is Credit Admin, not a template for every department.
01
Architect certificate arrives
›
02  AUTOMATED
IFCA raises the progress billing
›
03
Bank pays, advice by email
›
A person types the same figure, three times
04
By hand into IFCA
05
By hand into Excel
06
By hand into WhatsApp
They type it here · IFCA receipt entry, lot PT 20778
IFCA produces this · OR1030629, MYR 32,900, Stage 2E
One number.
Three systems.
Typed by hand.
Paper → system. Sheet → sheet. Figure → chat. Three of the six patterns, on one desk.
Purchaser onboarding runs the same way · typed, checked, retyped.
Amalan Setar  /  Credit Admin
10 / 16
The same loop · with an agent

Approve once. It does the rest.

It starts the moment the document arrives. Nothing downstream is retyped.
01
Architect certificate arrives
›
02  AUTOMATED
IFCA raises the progress billing
›
03
Bank pays, advice by email
›
The agent types it, three times, for you
04
Agent reads it, proposes the entry
05
A person approves. Once.
06
Agent keys IFCA, Excel and WhatsApp
Review and approve1 of 1
Debtor
MBSB-PUCHONG
98%
Lot
PT 20778
97%
Stage
2E
95%
Amount
MYR 32,900.00
99%
Bank advice
Not attached
Blocked
Approve
Send back
One approval · the agent then keys all three

It works the screens itself

  • IFCA · keys the receipt
  • Excel · writes the row
  • WhatsApp · posts the summary
  • Government portals · same way
    • If it can file on a government portal, it can work any screen your team uses.
    Not built yetThis is what we would build first, drawn from your own screens.
    IFCA staysThe system of record. We sit alongside it, never replace it.
    A person commitsNothing writes into a live system on its own.
    Your data, your callNo production data until you authorise it.
    Amalan Setar  /  Credit Admin
    11 / 16
    Cross-company

    Nothing reaches an HOD unchecked

    Before it lands on your desk, it has already been through its checks.

    What it checks first

    Everything attached
    All fields completed
    Complies with the SOP
    Numbers internally consistent
    Approvals and quotations present
    Anything unusual
    A step skipped
    Needs a further level of approval
    3 issues foundSent back
    Missing quotation
    Amount exceeds the approval threshold
    Supporting document does not match the amount
    What happensBack to the submitter, with the three reasons. The HOD never sees it.
    All checks passedReady for approval
    All required documents attached
    Within the approval authority
    Figures reconcile to the supporting documents
    What happensReaches the HOD already verified, every figure traceable. Only the decision is left.
    The bigger prize
    An internal control layer across the whole company, and how the SOPs finally get written down.
    Amalan Setar
    12 / 16
    Not a pilot idea

    We already run this for other people

    Different industries, the same six patterns. These are live systems, not demos.
    Volume, without more people
    86,491
    orders processed through one system, none of them keyed by hand.
    Four separate order channels, one place
    Live today, not a pilot
    The team was never scaled up to match
    Money out the door, on time
    300
    payments dispatched in a single run, straight from the source records.
    78 payees, not one bank number typed
    Bank confirmation matched back inside 24 hours
    Replaced a spreadsheet nobody trusted
    Right the first time
    0.06%
    of records wrong, measured continuously rather than spot-checked.
    Every figure traceable to its document
    Nothing writes to a live system without approval
    An error is caught the day it happens
    Amalan Setar
    13 / 16
    Timing

    This is the cheapest this will ever be

    The capability has arrived and the price has not caught up with it yet. Both of those are temporary.

    Three months ago

  • The models were not good enough
  • Generated code could not be trusted
  • Building was still too slow to be worth it
  • The cost did not justify starting
  • The tools did not connect to real systems
    • We know. We tried, and we did not recommend it.

    Right now

  • The models are the best they have ever been
  • Building runs about five times faster
  • The cost is a fraction of what it was
  • The output is production quality, not a toy
  • The tools reach into the systems you already run
    • Best capability, lowest cost. Those two rarely sit together.

    Twelve months from now

  • The AI companies are subsidising the price today
  • Exactly what Grab and Uber did to win rides
  • Billions spent to buy users and market share
  • When the subsidy stops, the price goes up
  • Everyone then pays more for the same thing
    • Build it now and you keep today's cost, not next year's.
    Why we are saying it now
    In a year this is ordinary and your competitors have it too. Today it is still an advantage.
    Amalan Setar
    14 / 16
    Over to you

    Two questions

    This is the part we actually came for.
    01
    What is the thing your team does repeatedly that consumes an absurd amount of time?
    02
    If you had one employee who could read every document, access every system, never forget anything and work around the clock, what would you give them?
    What good looks like
    Every department leaves today with one or two workflows where we can save serious hours, or directly make or save money.
    Amalan Setar
    15 / 16
    Amalan Setar
    16 / 16
    01 / 16 Amalan Setar