A complete Work OS for a premium multi-location coworking network
Bookings, human resources, finance, gastrobar POS, client services, sales, and operations — all in a single multi-tenant system with a domain architecture. The platform blueprint that replaced dozens of scattered tools per location.
From scattered chaos to a unified blueprint
The problem was not a tool. It was the lack of a system.
Dozens of processes across scattered tools
Each location ran on its own mix of spreadsheets, chats, calendars, and forms. Bookings, payroll, collections, gastrobar inventory, and mail lived in silos that never talked to each other. No role saw the complete operation.
We mapped the business by domain and by role
We modeled each area as a domain with its entities, rules, and invariants — and each profile (superadmin, manager, front desk, HR, sales, client, employee) with exactly what it needs to see. The location became a cross-cutting dimension, not a copy of the system.
One system, one single truth per location
A booking, an invoice, an incident, or a till close is recorded once and shows up in finance, operations, and analytics in real time. The location filter is automatic and security is guaranteed by the database (RLS).
System blueprint
A modular map: explore the scale of the Work OS
Each block is a module in production. Select one to see what it solves. They all share authentication, roles, and the location filter.
Bookings
Real-time availability with benefits by client type.
- ◆Realtime availability of spaces and rooms
- ◆Benefits and allowances based on the client plan
- ◆Automatic filtering per location
Multi-tenant per location
One network, many locations, one single database
Each of the ~52 tables carries a location identifier. The system automatically filters what each role can see and security is enforced by Postgres with Row Level Security — not by the interface. Switching location keeps the same system with a different filter.
- ◆A sede_id filter running across every module
- ◆RLS enabled: isolation guaranteed in the database
- ◆Consolidated view for superadmin / leadership
| Record | Location |
|---|---|
| Meeting room booking | North location |
| Gastrobar till close | Central location |
| Mail received | South location |
| Time-off request | North location |
| Receivable issued | Central location |
| Maintenance incident | South location |
| Locker booking | North location |
| Quote sent (Kommo) | Central location |
Showing 8 of 8 records · example of the location filter
Development scope
Domain architecture (DDD), not an inflated CRUD
Entities, factories, Value Objects, and DTOs. The business rules live here, independent of the database.
Use-case orchestration: they combine domains, apply invariants, and coordinate external integrations.
An abstraction over Supabase. Persistence is a replaceable detail, not the center of the system.
150+ custom hooks over TanStack Query feed ~191 pages with caching, realtime, and consistent states.
Integrations in production
Stack: React Hook Form + Zod · Recharts · Framer Motion · Vitest + Playwright · Supabase
Outcomes
What changed once the business fit into one system
One operation, not seven silos
Bookings, HR, finance, POS, services, sales, and operations stopped being islands. The team works in one system with a single truth per location.
Each role sees exactly its own
Three portals and granular profiles (superadmin, manager, front desk, HR, sales, client, employee) cut the noise and the errors caused by badly assigned permissions.
Scales to new locations without a rewrite
Opening a location is a record, not a project. The multi-tenant architecture and the location filter absorb the growth of the network.
Maintainable by design
Separating domain, services, and repositories lets business rules evolve without breaking persistence or the interface. Covered with Vitest and Playwright.
Integrated with the real ecosystem
Kommo, Google Calendar, Gmail, WhatsApp, PWA push, and NFC connect the Work OS to how the network already works and communicates.
A 24/7 operation without paper
Mail handling with a state machine, checklists, till closes, and digital contract signing remove manual steps and lost traceability.
No-commitment assessment
Your network runs on dozens of tools. Turn it into a single system.
We map your processes by domain and by location, and project what they look like inside a unified, maintainable Work OS.