We build it with your team, not for them
You send the boss and one staff member. We map your processes department by department, then build the automations together using Claude, on your accounts, in working sessions. When we finish, your own people can keep building. Programmes run from RM6,000 for a micro business to RM180,000 for a phased rollout at 100 staff.
Software you cannot maintain is a liability
The usual outcome of an automation project is a system nobody inside the company understands, and a vendor you must call for every small change. We teach while we build so that stops being true.
What you get on day one
- Working automations on your real documents
- Your processes written down properly, often for the first time
- Two people who can read, change and fix what was built
What you get in year two
- New automations your own team builds without us
- No per-change invoices, no vendor queue
- A team that treats AI as a tool, not a threat
Four stages
Map
We walk your floor, interview each department, count the hours each task really takes, and check what your systems will let us reach.
Week 1Choose
Every candidate process is scored on volume, time, data readiness and clarity of rules. We write a one-page brief for each one we build, and you sign it.
Week 1–2Build together
Working sessions of three hours. Your people drive; we guide. Each session ends with something running and a note written by your team.
Weeks 2–8+Hand over
Your person builds a small automation alone while we watch. You keep the runbook, the briefs and the accounts. Support afterwards is optional.
Final weekScope and price by company size
A session is three hours with your people. Work between sessions is included in the fee.
| Staff | What gets built | Sessions | Weeks | From |
|---|---|---|---|---|
| Under 5 | Two or three automations and one simple tracker the owner can edit — quotations, follow-ups, invoice chasing | 4 | 3 | RM6,000 |
| About 10 | Order to job to invoice, end to end, with a shared status board and a daily summary | 6 | 6 | RM15,000 |
| About 20 | An internal platform across sales, purchasing, operations and finance, with three to five automations feeding it | 10 | 8 | RM28,000 |
| About 50 | Department by department: five or six modules, approval chains, accounting integration, management reporting | 14 | 12 | RM60,000 |
| About 100 | A phased programme with your own internal build team, permissions and audit trail, delivered quarter by quarter | 22+ | 20 | RM120,000 |
Discovery is RM4,500 and is credited in full against the programme if you proceed within 30 days. Software subscriptions and usage are paid by you directly to the vendors — we do not resell software.
What the software costs you
Two different things, and most companies are never told the difference.
Subscriptions — for people
A seat for each person who works with AI: writing, checking, researching, building. Flat monthly fee. About RM82 per person; a heavier seat for whoever does the building.
Usage — for the automations
Once a workflow runs on its own, it is billed per document — fractions of a sen each. A thousand invoices processed automatically costs a few ringgit.
| Staff | Typical setup | Software per month |
|---|---|---|
| Under 5 | One seat for the owner, light automation | RM90–130 |
| About 10 | One builder seat, two normal seats, 500–1,500 documents | RM620–750 |
| About 20 | One builder, five seats, 2,000–4,000 documents | RM970–1,320 |
| About 50 | Two builders, a dozen seats, 5,000–12,000 documents | RM2,200–3,100 |
| About 100 | Three builders, 25 seats, 15,000–30,000 documents | RM4,200–6,700 |
A rule you can hold us to: software should cost roughly one to three percent of the salary cost of the work being automated. If three clerks cost you RM11,500 a month, a software bill of RM150–350 is right. Anything far above that is a platform being sold to you, not a solution.
Eight sessions, each ending with something that works
| # | Session | They leave with |
|---|---|---|
| 1 | Accounts, spend caps, and the rules on what company data may go where | Working accounts and three jobs already done faster |
| 2 | Writing a process down: trigger, inputs, rules, outputs, who approves | Two process briefs they wrote themselves |
| 3 | The first automation, built live on your real documents | One workflow running |
| 4 | Connecting email, files, spreadsheets and your accounting system | The workflow fed from where work actually arrives |
| 5 | Building the internal screen your colleagues will open | A working page or dashboard |
| 6 | Exceptions and approvals — designing for the 10% that does not fit | An exception list, tested with bad data on purpose |
| 7 | Running it: deployment, access, monitoring, cost control | A one-page runbook in their own words |
| 8 | Handover test — they build something small alone while we watch | Proof they can continue without us |
Micro businesses compress this into four sessions. Larger programmes repeat sessions 3 to 7 for each department, with a builder trained in each.
When this does not work
- The owner sends someone else. Processes change only when the person who can decide is in the room.
- Nobody's time is protected. If your builder is pulled into month-end for three weeks, the programme stalls — we would rather pause than carry it alone.
- The data is on paper or locked away. If a system has no export and the records are handwritten, we will tell you at discovery instead of taking the project.
- You want it done for you. That is a different service and a different price. We will say so rather than pretend.
We would rather turn down a programme at the discovery stage than deliver something your team cannot keep running. You will get that answer in writing, with the reasons.
What owners ask before starting
Who from our side needs to be involved?
Two people: the owner or department head, and one staff member who knows the process and is willing to learn. The owner matters because only he can change how work flows; the staff member matters because they keep it running after we finish. Half a day a week each, protected in the calendar.
What if our people are not technical?
None of our clients' builders have been programmers. If someone can write a clear email and use Excel, they can do this. The AI writes the code; your person decides what the business needs and checks the result.
What do we end up owning?
Everything. The automations run in your accounts, under your billing, with your passwords. You get the written process briefs, a runbook, the prompt library and recordings of every session. Nothing is locked to us.
How is this different from hiring a software house?
A software house delivers a system and a support contract. We deliver a working system and two people who can extend it. The second and third processes cost you our time only if you want them to.
What does it cost to run afterwards?
Usually RM90 to RM1,300 a month in software for companies up to 20 staff, depending on volume. Subscriptions for the people building and using it, plus pay-per-document usage for the automations. We set a spend cap in your account on day one.
How quickly do we see something working?
The first automation runs on your real documents in week two or three. If a project cannot show something useful by then, the scope was wrong and we change it.
Book your free 45-minute call预约 45 分钟免费咨询
Tell us which task wastes the most time. We'll come back within one working day with whether AI can fix it, and roughly what it would cost.告诉我们哪项工作最浪费时间。我们会在一个工作日内回复：AI 能否解决，以及大概费用。
- +60 12-787 3525
- Email电邮
- [email protected]
- Based in所在地
- Seremban, Negeri Sembilan · serving Klang Valley and nationwide森美兰芙蓉 · 服务巴生谷及全马
- Languages语言
- English · Bahasa Malaysia · 中文
Thank you. Your enquiry has been sent.谢谢！你的询问已成功发送。
Jack will reply within 1 working day on WhatsApp or email. If it's urgent, message us on WhatsApp now.Jack 会在 1 个工作日内通过 WhatsApp 或电邮回复你。如有急事，可以直接 WhatsApp 我们。