Selected work

The work, with its baseline attached

Every write-up here starts from what the business was doing before, states how the numbers were measured, and says plainly what the migration cost. A result without a baseline is a slogan.

Case 001 · Education · 3 branches

A three-hour Monday, reduced to twelve minutes

A coaching institute was fielding 300 enquiries a month across four personal phones and losing track of most of them. Admissions, fee follow-ups and attendance moved onto one WhatsApp-native system in four weeks. Here is what changed, what it cost, and what we would do differently.

Read the case study →

All case studies

1 published · 3 in the queue

WhatsApp automation

WhatsApp CRM for a three-branch coaching institute

One shared inbox, payment links per instalment, and batch occupancy in plain view. Four weeks from first migration to switching the personal numbers off.

3h → 12mMonday admin

+17 ptsconversion

−63%overdue fees

SaaS platforms

Multi-tenant booking platform for a services marketplace

Tenant isolation at the query layer, subscription billing, and an admin console the operator could run without us.

—write-up pending

Internal tools

Replacing a shared spreadsheet with an operations console

Orders, dispatch and reconciliation in one place, with role-based access so branch staff stopped seeing everything.

—write-up pending

Mobile

React Native app for a field team that works offline

Local-first capture, conflict resolution on sync, and an over-the-air release train that does not need store review.

—write-up pending

Start a project

Your operation, on the same stopwatch.

Send the workflow that eats the most time each week. You will get back a scope note with what can be automated first and what it would take.

Start a project → See what we build