The problem
A social media agency runs the accounts of many clients at once: content to plan, approvals to collect, calendars that must not collide. Doing that in spreadsheets and chat groups works until the third client, and then every approval is somewhere different and nobody knows what is going out tomorrow.
What I built
A workspace platform for agencies, multi-tenant from the start: each agency registers and gets its own separate space, with its own clients, its own team and its own data. Content planning, approval flows and the shared calendar all live in one place, with roles deciding who can publish and who can only propose.
Built with
Next.js on a VPS shared with other services, with authentication and tenant isolation built in rather than added later. Releases go out one phase at a time, and anything touching the web server configuration is validated before it ships, because other sites live on the same machine.
Why it was done this way
The platform was designed for many agencies from the first day, even though it started with one. Retrofitting multi-tenancy onto a single-customer application means touching every query that reads data and hoping none was missed — it is the kind of rework that costs more than the original build.
