Society management platform — multi-tenant from day one
Owned the architecture decision for a property and community platform: tenancy model, API contracts, and RBAC, so a delivery team could build without redesigning isolation later.
The problem
A property and community product needed one codebase to serve many societies, with strict data isolation, custom branding, and reporting — without a database per customer. The buyer needed an architect to lock the tenancy model before engineers started building.
The role and approach
Led the architecture, not just the implementation. Wrote the tenancy decision, API contracts, and role model first, then reviewed the team’s work against those contracts. Stack matched what agency teams already knew: NestJS, Prisma, Next.js, Expo.
The outcome
The team built against a fixed isolation model instead of discovering tenancy bugs in production. New societies could be onboarded as tenants of one platform rather than as separate installs.
Hard decisions
- 01Shared schema with row-level tenant isolation, not a database per society — operational cost stays flat as societies are added.
- 02API contracts and RBAC written before feature work, so the delivery team implemented a decision instead of inventing one.
- 03Role was architect and reviewer: own the tenancy model, then step back while the team builds against it.
Lesson for future clients
Agencies and funded founders hire the decision, not the pull requests. Write the tenancy model and the contracts first; review the team against them.