(03) — Recent work / Featured case
Balona Hotel —
one team for the build
and the build-out.
Front-desk workflow, guest connectivity and venue-wide Wi-Fi sat on three disconnected systems. We rebuilt the operating layer and the network underneath it on a single backbone.
(01) — Brief
What they came with.
A growing boutique property in Accra running on three disconnected systems: a manual reservation spreadsheet, a basic POS, and a guest Wi-Fi network the front desk reset by hand when it stopped working — which was often.
They needed both the operating layer and the physical network rebuilt. They didn’t want two vendors handing off scope at the seam.
(02) — Constraint
Two problems,
one budget.
The number on the table covered software development. The network rebuild it implied — fresh cabling, switches, AP survey, VLAN segmentation — wasn’t in scope when we sat down. We engineered both lines against the original budget, by cutting where vendor defaults overshot and reusing the existing CAT6 backbone wherever it tested clean.
No phased follow-on. One number, one go-live.
(03) — What we did
The build, in two parts.
/ software
Property-management workflow.
Custom web app covering reservations, guest profiles, housekeeping schedules, billing, and nightly close. Built on React + Next on the front, Node + Postgres on the back.
Reconciliation that took the night manager an hour-and-change each evening now runs as a single end-of-day report; staff close on time, every night.
/ networking
Venue-wide Wi-Fi rebuild.
Full RF survey across the property, then 9 Ubiquiti APs deployed against the floor plan with VLAN-segmented guest / staff / management traffic. New PoE switching, structured cabling top-up, Tailscale for remote admin.
Staff Wi-Fi went from “sometimes” to “the kind you forget about.”
(04) — In their words
“One team scoped, designed, and deployed both the software and the physical network. Cut nightly reconciliation from hours to minutes; staff Wi-Fi went from ‘sometimes’ to ‘fine.’”
// representative paraphrase · pending public attribution
(05) — Results
What changed.
(06) — Stack
Tools we
actually used.
Stack picked against the constraint, not the brochure. Boring where boring wins (Postgres, Node), modern where modern pays (Next 15’s server actions for the close flow).
→ Same approach, your project next
More cases are under wraps —
ask, and we’ll talk.
We’d rather show you one named client than ten anonymous numbers. Most of our work isn’t public — pencil us in for a conversation and we’ll walk you through the relevant prior art.