Notes from
the house
Engineering deep-dives, design notes and field reports from the teams behind Forsa, Zunu, Navvo, QAce, Kemble, Vollo and Virox.
Two surfaces, one messaging core
Why Kemble Work and Kemble Circle are the same product wearing different clothes, and what it takes to make one permission model serve a company and a community at once.
read article →
Voice is four problems pretending to be one
Recognition, synthesis, understanding and orchestration each have their own failure modes. Stitching four vendors together is why most voice products feel broken.
read article →
One million meals, rescued one surprise bag at a time
How Forsa's matching engine decides which bags go live, when prices drop, and why 95% off still makes sense for a bakery at 9pm.
read article →
Why we rebuilt the ERP around a single data layer
Most ERPs are decades-old suites moved to the cloud. A look at the architecture that lets Zunu propagate a posting across every module in 0.4 seconds.
read article →
Teaching a map to think in two languages at once
"وين أقرب صيدلية مفتوحة؟" should work exactly as well as the English. Inside Navvo's bilingual search.
read article →
Record-and-replay is dead. Agents reason about your app instead
Brittle selectors snap on every refactor. Here's how QAce relocates elements by role, text and context.
read article →
Your files, your rules: designing storage enterprises can trust
Granular permissions, auditable sharing and sync that never surprises you, the principles behind Virox.
read article →
One house, seven ventures: how we choose what to build next
Every venture starts with the same question, is this broken in a way that craft can fix?
read article →