One process, not a wish list
The single task eating the most hours. If you bring five, we will spend the call ranking them instead of understanding one — and ranking is something you can do faster than we can.
Contact
Bring one process that's eating your team's week. We'll tell you on the call whether it's a good candidate, roughly what it would cost, and whether we're the right people for it — including when the answer is no.
Tell us about the process
Where we are
Kuala Lumpur, Malaysia — working across Southeast Asia, Greater China and Australia. Calls in English or Mandarin.
What happens next
The whole point of this sequence is that you can stop at any point and still have something useful.
01
Today
A paragraph about the process is enough. You don't need a specification or a budget figure.
02
Within a working day
Thirty minutes with an engineer. By the end you'll know whether it's a candidate and the rough cost range.
03
If there's a fit · fixed fee
We observe the real process and write it up: what to automate, what not to, effort, and expected savings. The document is yours regardless.
04
No pressure
Build with us, build it in-house from our scope, or shelve it. All three are fine outcomes and we've seen each of them.
Before the call
None of them need preparing formally. Rough answers make the thirty minutes far more useful than a polished brief does.
The single task eating the most hours. If you bring five, we will spend the call ranking them instead of understanding one — and ranking is something you can do faster than we can.
"About two hundred a week, maybe fifteen minutes each" is enough. This one number decides whether anything is worth building, and we would rather test it in the first ten minutes than the third meeting.
Names and roles. The people doing the work know the exceptions that never made it into the documentation, and every project that goes well involves them from the first week.
The marketplace, the ERP, the spreadsheet, the WhatsApp group. Especially the spreadsheet and the WhatsApp group — the unofficial systems are usually where the real process lives.
A minute of review, an annoyed customer, or a refund that should not have gone out. This determines the whole design, and it is the question most vendors do not ask.
Including tools you bought and stopped using. Knowing what failed and why saves us proposing it again, and occasionally the right answer is to configure what you already own.
What happens next
We are a small team in one time zone. These are the real numbers, not aspirational ones.
| Typical | Notes | |
|---|---|---|
| First reply to an enquiry | Within one working day | Malaysia time, Monday to Friday. A person, not an autoresponder. |
| Scoping call scheduled | Within a week | Thirty minutes, video or phone, no deck. No NDA needed for this one. |
| Go / no-go opinion | On the call itself | We say no to roughly a third of what we are asked about, and we say it there rather than in a follow-up. |
| Scoping week starts | Two to five weeks out | We run six to eight engagements a year, so there is usually a queue. We will tell you the real date, not a hopeful one. |
| Written scope delivered | Day five of that week | Fixed fee, yours to keep, and usable by another firm if you would rather. |
| Existing clients, support | Same working day | Business hours only. Systems are built to degrade safely rather than need a 3am rescue. |
For procurement and IT
If you need to clear us through a security review, ask on the first call and we will send this before the second one.
What we access, where it is processed, how long anything is retained, and which sub-processors are involved by name. Written to be forwarded to a security team without translation.
Your cloud account, your VPC, or on-premise. Where a client requires it we hold no copy of anything and have no standing access to production — access is granted per change and logged.
Full IP assignment on delivery, no licence-back, no minimum term on the retainer, and mutual confidentiality. We will work from your paper if your legal team prefers it.
Malaysian company registration, professional indemnity cover and W-8BEN-E or equivalent tax documentation, provided on request without a call.
We can usually arrange a direct call with an operator at a comparable business, including one who ended their retainer and now runs the system themselves. That conversation is worth more than a case study.
No SOC 2 or ISO 27001 certification. If your process requires one, we are the wrong vendor and we would rather you know that now than after four weeks of questionnaires.
Pricing & FAQ
If your question isn't here, ask it on the call — we'd rather answer it before you commit than after.
The scoping week is a fixed USD 3,500. Build projects typically run USD 18k–60k depending on how many systems we integrate; a single narrow capability can be less. Operating retainers run USD 2k–8k per month with no minimum term. You get a firm number in the scope document, not a range that moves later.
Four weeks is our median from kickoff to a system doing real work, with a pilot on your actual data in week three. Anyone promising production in days is either shipping a demo or skipping the evaluation work.
It stays in your infrastructure wherever the workload allows. Where a hosted model is genuinely better, we use providers with zero-retention terms and tell you exactly which data crosses that boundary. If your policy requires everything on-premise, we use open-weight models and state upfront what that costs in accuracy.
It will — the question is whether you find out first. Every task has an agreed accuracy bar, a confidence threshold below which the case goes to a person, and a full audit trail. We design the failure path before the happy path.
Entirely — source, prompts, eval sets and documentation. No licensed runtime, no lock-in that makes leaving expensive. Clients stay because the operating work is worth buying, not because they can't go.
It's the normal starting condition and part of what the scoping week is for. Often the first phase is data work rather than AI work — and occasionally the honest finding is that cleaning the data delivers most of the value with no model at all.
That's the preferred arrangement. We build alongside your engineers so the knowledge stays with you, and we're glad to be the ones who leave once your team can operate it.
English, Simplified and Traditional Chinese, Bahasa Malaysia, Bahasa Indonesia, Thai and Vietnamese are in production today. Customer-facing copy is written per market, because translated support replies read as translated support replies.