Location Square
Turning a WordPress brochure site into a service operations platform with bookings, vendors and property management.
The problem
Location Square started as a WordPress site. It could show services, but the actual business ran outside it: bookings over phone and email, vendors coordinated by hand, and residential block management tracked separately. The client needed an operations platform, and WordPress had nowhere left to grow.
Off-the-shelf plugins could not model the real structure: customer bookings fulfilled by vendors, property blocks with their own billing, and content editing that should never touch operations.
How it works
WordPress audit
Mapped what the old site did, what the business actually needed, and migrated the content.
Modern rebuild
Next.js frontend with a NestJS API on PostgreSQL owning all business logic.
Service bookings
Customers book services, vendors fulfil them, Stripe handles payment.
Block management
A separate system for residential blocks with billing, issue reporting and its own authentication.
Content management
A CMS layer so site content stays editable without touching operations.
What I built
- Three systems with strict boundaries: customer service bookings, block management and content management.
- Six roles across the platform, from customers and vendors to block admins and residents, each seeing only their own area.
- Stripe payments for service bookings, with offline payment tracking on the block side.
- A pnpm monorepo with a Next.js frontend and a NestJS API, deployed on AWS with Cognito authentication.
- A content editing role so the client updates the website without a developer, replacing what WordPress used to do.
Outcome
The website went from describing the business to running it. Bookings, vendor fulfilment, block billing and content editing all live in one platform, and the WordPress ceiling is gone.