Software built where it's used

Most point-of-sale software is built for markets where the internet doesn't drop, prices sit still, and mobile money isn't the default way people pay. It mostly works — until it doesn't, usually at the worst possible moment, mid-sale, with a queue at the till.

We started Zoolk to close that gap: a POS built assuming those conditions from the start, not retrofitted for them. That meant designing for offline use as a normal state, not an error case; pricing transparently in the currency a business actually budgets in; and building local mobile money in as a first-class way to pay, not an afterthought.

It also meant paying attention to how businesses actually operate on the ground — multiple branches run by one owner, staff who need clear boundaries on what they can do, customers who run a tab and settle later. These aren't edge cases to us; they're the default we designed around, wherever a business runs.

Zoolk is still early. We're a small team, we ship often, and we'd rather build fewer things well than pile on features nobody asked for. If something about how you run your business isn't well served by Zoolk yet, we want to hear about it — tell us.