"The inquiry came in Saturday afternoon. I never even saw it. She showed up and became a client."— Razif Yusoff, co-founder, Fit Kaki
Find the trapped capability. Build the system. Prove the outcome.
Lucky Shovel builds AI systems for real-world operations — systems that answer, remember, watch, and decide. We measure the baseline before we build, and we show you exactly what changed.
Most businesses don't lack capability. It's trapped.
It's trapped in WhatsApp threads nobody can search. In the head of one overloaded owner. In documents scattered across clients and chats. In repetitive questions, forgotten follow-ups, and field signals nobody reads in time. We build the system around that trapped capability — so it can move again. The fuller argument — why I build this way — lives at zzag.net.
Unanswered messages
Customers ask. Nobody replies in time. The lead cools, the booking slips, the owner apologises again.
One person's head
Client history, promises, prices, decisions — all carried by whoever has been there longest. Usually the owner.
Scattered documents
The contract is in email, the amendment in WhatsApp, the proof of address in someone's camera roll.
Unread signals
The data exists — in the field, in the logs, in the inbox. It just never becomes a decision in time.
Prove
or kill.
We think AI should be measured by what it changes, not what it promises. Every engagement runs the same loop — and the loop has an exit.
Map the work
We sit inside the real workflow first — people, tools, bottlenecks, failure modes. No deck. No demo theatre.
Measure the baseline
Response times. Missed leads. Manual hours. Open obligations. If we can't measure it, we won't claim it.
Deploy the smallest useful system
Inside the tools your team already uses — WhatsApp, Telegram, the phone line. Not another dashboard to ignore.
Track obsessively
Usage, behaviour, outcomes, drift. Every meaningful action the system takes leaves a receipt.
Prove — or kill
If the numbers move, we scale it. If they don't, we say so and stop. You should never pay to keep our experiment alive.
Four systems. One method.
Problems that kept repeating across clients became focused products. Each one stands on its own; all of them run on the same method.
Zero Wait zerowait.tech
Calls answered, WhatsApp handled, bookings kept. For service businesses tired of being their own receptionist.
● Deployed · taking clientsMRDK mrdk.io
Private operating memory for owner-led teams. Chat mess in — client context, open loops, receipts, and finished work out.
● Pilot deployments openKomplyze komplyze.com
Gets Singapore SMEs audit-ready across PDPA, safety, and employment — starting with a free assessment. Runs on MRDK.
● In active client workRaih AI raih.ai
Plantation intelligence for oil palm estates — digital twins and predictive analytics, built with operators in the field.
◌ In field developmentReceipts, not promises.
Our systems log what they do; so do we. Here is work that shipped, in the words of the people running it.
"Every business owner I know needs to see this."— Shawn, Infiniti Professional Services
Disclosure: Fit Kaki is co-founded by our founder. Our systems run there first, on live operations, before any client engagement.
Small by design.
Zulfadli Ghani
Systems builder. Also co-founder of Fit Kaki, a senior-strength social enterprise — because trapped capability isn't only a business problem. zzag.net
J Nathania
Makes sure that what was promised is what gets delivered — and that every engagement leaves a paper trail worth auditing.
- Singapore-registered. Lucky Shovel Pte. Ltd. · UEN 202426301M
- Singapore-hosted. Client systems run on Singapore infrastructure, PDPA-conscious by default.
- Auditable by design. Baselines, receipts, and outcomes you can put in a report.
- Small on purpose. You work directly with the people who build your system — no account managers, no handoffs.
- Backed by a partner network. Specialist engineers across Singapore and Indonesia when a build needs more hands.
Got trapped capability?
Tell us where the work hurts. We'll tell you honestly whether a system would help — and what we'd measure first.