Series · Part 1 of 6
Building Djengo
On this page
Most of my career has been spent turning someone else's brief into working software. Backend leadership, fullstack delivery, mobile apps, the late-night fixes before a launch. I am proud of that work. But there is a ceiling on how much of a problem you can own when the product belongs to someone else.
Djengo is where I stopped being only the engineer. I founded it, I build it, and I sit with the operators who will run their business on it. That changes what “done” means.
The problem I kept seeing#
The operators I talked to were already doing the work. Reception, rooms, staff, payroll, guest money. It just lived in spreadsheets and tools that never talked to each other. Hotels, clinics, estates, and restaurants all had the same shape of pain:
- Revenue leaks when booking and billing live in separate systems.
- Payroll and approval mistakes happen when HR and finance do not share context.
- Guests get a broken journey: book in one place, pay somewhere else, chase a receipt.
- Enterprise ERPs exist, but they are priced and staffed for chains, not a 40-room hotel or a growing clinic.
What Djengo is#
“Djengo is the operations system for places that host people. Facilities, staff, bookings, and money in one multi-tenant workspace, with a guest path to discover, book, and pay.”
| Surface | Who it serves | What it does |
|---|---|---|
| Staff Workspace | Owners, managers, staff | Facilities, reception, kitchen, HR, payroll, approvals |
| Explore & Book | Guests | Discover places, check availability, book and pay |
| Mobile app | Staff on the floor | Clock in, request leave, work the task board |
| Admin console | Djengo team | Platform operations and support |
| Onboarding forms | New hires | Self-serve staff onboarding |
What changes when it is yours#
As an engineer, I could hand off a feature once it passed review. As a founder, the feature is not finished until an operator has used it on a busy day and come back the next morning. Onboarding is product. Support is product. The demo environment is product.
- I write the architecture and I also write the go-live checklist.
- I care as much about the empty state a new company sees as about the gRPC contract behind it.
- We sit with operators during go-live instead of dropping a self-serve maze on their desk.
- Every shortcut I take, I personally pay for in a support conversation later.
What this blog becomes#
I will keep writing about engineering and careers. But a growing share of this archive is now a build log. This series walks through how Djengo is put together and why: the architecture, the tenancy model, the facility model, the state machines that protect money, and the numbers behind 18 months of building.
“Platforms earn their keep when someone can open them on a stressful day and still get work done.”
Key takeaways
What to remember
- Founding means owning onboarding and support, not only code.
- Djengo unifies facilities, staff, bookings, and money.
- Done means an operator used it on a busy day.
