Five systems for the daily work of a small business — storefront, books, people, insight and flow. Made in Phnom Penh, for shops that count in riel.
We spent our time in shops, kitchens and back offices around Phnom Penh before writing a line of code. The same three problems came up every time.
Foreign software assumes card payments, English-speaking staff and a price in dollars per seat per month. Khmer arrives late, as a translation layer over an interface that was never shaped around how business is done here.
Orders in chat threads. Stock in a notebook. Payroll in a spreadsheet someone keeps on one laptop. Invoices written by hand. Each part works — but nothing talks to anything else, so the owner is the integration.
A shop with four staff can't justify hundreds of dollars a month across five modules. So it stays manual, and stays invisible in its own numbers — right at the point where knowing them would matter most.
Each one solves a problem on its own. Together they become the operating system for a small business. We're building them one at a time, in public.
One link that shows everything you sell, a QR code for the table or the packaging, and orders that arrive somewhere you can actually read them. It replaces sending product photos one by one, fifty times a day.
Compliant invoices and receipts, expenses recorded as they happen, and a monthly picture your accountant can work from — instead of a shoebox of paper reconstructed the week before it's due.
Staff records, contracts, attendance, leave and payroll basics — kept in the shape Cambodian labour rules expect, so an inspection is a folder you open, not a week you lose.
Sales, costs and stock in one view, with the plan behind them: what to reorder, what to drop, what to charge. The management information a big company takes for granted, sized for a shop.
Customer records, follow-ups, quotes and jobs on a board — so nothing is lost between a message on Monday and a delivery on Friday, and anyone on the team can pick up where another left off.
Product names are working titles. They'll settle before the first system launches.
The order matters. Software built without step one is the reason so much of it goes unused.
We sit in the business for a day. What gets written down, what gets forgotten, who chases whom, where the money goes uncounted. No demo, no pitch.
Within two weeks there's something on a phone you can tap. Cheap to change, honest about what's real and what's drawn. We'd rather be wrong early.
A small group runs it on real work, free, while it's still rough. Their complaints are the roadmap. Nothing reaches general release without surviving this.
We release when a business would keep using it if we disappeared — not when a launch date arrives. Priced so a small shop says yes without a meeting.
Setup in person, support in Khmer, and someone you can reach. Software you can't get help with is software you stop using in a month.
Khmer is designed for from the first screen — the fonts, the line breaks, the sort order, the way a number and a date are read. English sits alongside it, not above it.
A shop shouldn't pay more because it hired a second cashier. Pricing is set so the answer is yes without a spreadsheet, and it stays the same as the team grows.
Most owners here run everything from a phone, often on a patchy connection. Every system is built for that first, and for a laptop second — never the reverse.
Export everything, any time, in a format another system can read. If you outgrow us or change your mind, your records come with you. No hostage-taking.
Field notes from Cambodian businesses, and the reasoning behind what we build. First pieces are being written now.
We're choosing the first businesses to pilot each system. You get it free while it's rough, and a direct say in what it should do.
We reply within two working days. No newsletter unless you ask for one.
Whether you want to pilot a system or need something built for how your business actually works — start with a conversation.