Multi-tenant Coworking Space Management SaaS
Space management SaaS for coworking operators. Each operator runs their own branded site with custom pricing, member booking, calendar sync, and connected accounting/CRM — on one shared backend.
One platform from front desk to billing.
Operators get the live dashboard, package management, and floor-plan view. Members book rooms and buy passes from their own app. The kiosk handles check-ins and visitors at the door. Stripe, QuickBooks, and HubSpot stay in sync without manual export.
This is an animated mockup of the coworking platform we'd build — not a live product. Member names, occupancy, and revenue figures are illustrative.
Operator dashboard
Live occupancy, MRR, new members, and bookings on one screen. Activity feed shows check-ins, payments, and signups in real time.
Configurable packages
Day Pass, 10-Pass, Weekly, Monthly, Dedicated Desk, and Custom team plans. Each package gates resources (rooms, hours, locker, mail) and pricing.
Member booking + meeting rooms
Members reserve rooms, phone booths, and event space from a calendar with conflict resolution. Credits deduct from their plan; visible balance updates live.
Kiosk check-in
Tablet at the front desk handles member check-in, day-pass purchase, visitor sign-in, and on-the-spot room booking — no staff required.
Live floor plan + access control
See who's in the space right now. Door access ties to the active membership; expired plans block entry automatically.
Integrations: Stripe · QuickBooks · HubSpot
Payments through Stripe, invoices and accounting sync to QuickBooks, leads and members flow into HubSpot — all without manual export.
Space management SaaS for coworking operators. Each operator runs their own branded site with custom pricing, member booking, calendar sync, and connected accounting/CRM — on one shared backend.
Multi-tenant by subdomain: each operator's site lives at their own subdomain with their branding, pricing rules, and resource catalog. One backend handles billing, calendar sync, accounting (QuickBooks), payments (Stripe), CRM (HubSpot, Salesforce), and team comms (Slack).
Operators sign up and get an auto-provisioned subdomain with their brand applied. They configure pricing rules per resource (desks, rooms, equipment), onboard members, and run their day-to-day from the operator dashboard. Members book resources through a unified calendar that respects availability and conflict rules. Financial state syncs to QuickBooks; new members and bookings forward to the operator's CRM; team alerts arrive in Slack. New operators come online via the subdomain provisioning pipeline — no per-tenant deploy.
How a request flows through it
Each request enters at the top of the diagram, flows through every box, and lands at the bottom — exactly the way the production system behaves. The scan-line traces where a live request would be right now.
What it's built with
The interesting parts
Multi-tenant by subdomain
Each operator's site lives at their own subdomain with their branding, pricing, and resource catalog. New operators provision automatically — no per-tenant deploy.
Member booking on shared calendar
Members book desks, rooms, and equipment through a unified calendar that handles availability, conflict rules, and resource-specific constraints.
Accounting, payments, and CRM integrations
QuickBooks for accounting, Stripe for payments, HubSpot/Salesforce for CRM, Slack for team alerts — wired in from day one so operators don't run a parallel toolchain.
Per-tenant pricing rules
Each operator sets their own pricing rules per resource and per member tier; the platform applies them at booking time without code changes.
The calls that did most of the work
A handful of engineering choices shape how a system feels. Here are the ones we'd still defend — alongside what each one cost.
Multi-tenancy by subdomain
Subdomain isolation gives each operator a clean brand identity and clean cookie/CORS boundaries — easier to reason about than path-based multi-tenancy.
Tradeoff: DNS and TLS provisioning have to be part of the onboarding pipeline rather than a deploy-once concern.
MongoDB for the document model
Tenant-specific schemas (custom branding, custom pricing rules, custom resource types) fit a document store more naturally than a single relational schema with many nullable columns.
Tradeoff: Cross-tenant aggregate queries and reporting are harder than they would be in a single shared relational table.
Multiple third-party integrations from day one
Operators expect QuickBooks, Stripe, HubSpot, Salesforce, and Slack to be wired in — adding them post-launch is a slower path than including them in the initial build.
Tradeoff: Five external APIs means five sets of credentials, rate limits, and webhook contracts to manage.
Tell us what you're building.
Free 30-minute call. Real humans, real timelines, no follow-up emails forever.