Maybe it's the same enquiry twenty times a week. Maybe it's digging through a WhatsApp thread to find what you promised a customer last Tuesday. I build the automation that takes that off your plate — and every system stops before the last step, so nothing gets sent or paid without you seeing it first.
A supplier invoice arrives by email as a PDF. AI reads it, pulls out the supplier, the date and the amount, and writes a row into a sheet marked to check. A message pings your phone so it doesn't get lost in your inbox. Nothing is ever paid automatically — you check the row, then you decide.
The screenshot is a synthetic demo invoice (INV-2026-0801, RM 318.60), built to show the flow. It isn't a real client transaction.
An enquiry comes in through a form. AI reads it, scores how hot it is, and drafts a reply in the same language the enquiry came in. It logs to a sheet and pings your phone so you see it fast. The draft waits for you — it's never sent on its own.
Real execution from 6 August 2026: a lead asking about CRM automation for their shop, scored warm.
A small food business in Kemaman runs its daily orders on a system I built. Customers order from a link rather than a chat thread, staff work from one clean list, and stock moves by itself as orders are confirmed — so what's left is a number somebody can trust instead of a guess.
It's a smaller operation than yours, and I'd rather say that than dress it up. What it shows is that I build and run whole systems, not just connect existing apps together — and that a non-technical person uses this one every day without me sitting beside them.
These are systems I built and run, not paid client projects. You would be my first paying client — which is exactly why the price is lower now than it will be later.
These three are what I built first, not the limit of what I take on. Almost every business has some version of the same shape underneath: something arrives, a person reads it, that person retypes it somewhere else, and then somebody has to be told. A quote, a delivery schedule, a class booking, a stock count, a weekly report, a follow-up that never happens — the paperwork changes, the shape underneath doesn't.
Tell me what the job actually looks like for you, and I'll look at how you're doing it now and come back with a proposal. And if it turns out the job isn't worth automating yet, I'll tell you that instead of selling you something.
I build the automation and run it for you — reading documents, drafting replies, keeping a sheet up to date, whatever the repetitive part of your day actually is. Built around how you actually work, not a fixed template.
Available now.
Not sure automation is worth it yet? We start with arithmetic rather than a sales pitch. If you retype thirty invoices a month and each takes four minutes, that's two hours gone every month, forever. If the sums don't work out in your favour, I'll tell you that honestly instead of selling you a project you don't need.
Available now, before the rate goes up.
Book a consultationAlso teaching: a short course on using Claude Code — building your own AI agents for your business, or building your own apps and websites without needing to be a developer first. Tell me you're interested and I'll send details.
What's being built, what it does, and what it deliberately doesn't do — all written down before anything starts. None of it stays inside a WhatsApp thread.
You see it working on your own real examples as it's being built. No long silence and then a big reveal.
The finished system runs against the agreed scope on your real work, and you sign it off. If it doesn't do what was agreed, it isn't finished.
To be straight with you, this cuts both ways. A written scope and an acceptance test protect you from paying for something vague — and they protect me from a job that quietly grows forever. That's the point.
It's a one-page scope, not a contract.
Aidi Hamid spent 29 years in oil and gas, including 8 as a process engineer at Petronas, before moving into AI automation full-time. Kerteh, where Velobit is based, is a Petronas town — and the habits from that world (write it down, test it properly, don't ship something that fails quietly) carry straight into how automation gets built here.
Velobit Digital Venture is a registered Malaysian business (SSM Reg. JR0190269-K), based in Kemaman, Terengganu. Work happens remotely by default — over WhatsApp, email and video call — so clients anywhere are welcome, not just nearby ones.
There's no price list, because there isn't a fixed one yet — I'll quote you a real number before any work starts, and I'll warn you now that it will look low. That's deliberate. What I'm short of isn't skill, it's a track record: real systems running in real businesses that I'm allowed to point to. So the trade is a lower rate now, in exchange for permission to write up what we build — with nothing in it you're not happy to share. The rate rises as the track record does.
It stores the numbers, but somebody still has to read the PDF and type them in — that's the part this replaces. The row lands in the same sheet or system you already use, marked to check, so nothing about your existing setup changes.
No. The typing goes, not the person. She stops keying forty invoices and starts checking forty rows that are already filled in. It's usually worth having her in the room when we talk about scope — she's the one who'll tell you honestly whether it actually works.
There's no published price yet. I'll quote you a real number before anything starts — and right now that number is lower than it will be once there's a track record behind it. The rate rises as that does.
Work it out on your own numbers rather than mine. If a task happens twenty times a week and takes five minutes each, that's roughly six and a half hours a month — multiply that by what an hour of that time is worth to you. I won't quote you a study about companies overseas; your own arithmetic is the only number that matters here.
Every system I build stops before the last step. It drafts, it flags, it logs — it doesn't send or pay on its own. You're always the one who presses go.
That's what the written scope and acceptance test are for. You know what's being built before you pay for it, and you sign off against real work at the end, not a promise.
No. If you can use WhatsApp and a spreadsheet, you can use what I build. That's usually the bar I design to.
No — work happens remotely by default, over WhatsApp, email and video call. Clients anywhere are welcome.
It depends on the job. We agree a timeline as part of the written scope, before anything starts, so you're not guessing.
Maybe — tell me what the job actually looks like and I'll look at how you're doing it now and come back with a proposal. If it turns out not to be worth automating yet, I'll say so instead of selling you something.
Prefer WhatsApp? Message me directly at 019-950 6617.