Case Study
WP SiteLauncher — embedding project management where the work happens.
Agency PM tools live outside WordPress. Agencies live inside it. We built the platform that closes the gap — workspaces, tasks, sitemaps, and approvals, embedded directly in client sites.
- Built for
- Pee-Aye Creative ↗
- Live at
- wpsitelauncher.com ↗
OVERVIEW
A collaboration platform agencies run WordPress builds on.
WP SiteLauncher is the project-management layer agencies use to scope, build, and ship WordPress sites with their clients. Workspaces, tasks, discussions, sitemaps, page templates, knowledge bases, approvals — all of it, in one place.
The catch: instead of living in a separate SaaS the team has to switch tabs to, SiteLauncher embeds directly inside the client's WordPress admin. The work and the conversation about the work happen on the same surface.
THE CHALLENGE
A SaaS product idea — and no engineering team to build it.
Pee-Aye Creative had spent years inside the WordPress agency ecosystem and spotted the gap: there was no project management tool built for the way agencies actually ship WordPress sites. Existing PM tools live outside WordPress and treat the site as an artifact instead of the workspace.
PAC knew what to build and who would buy it. What they didn't have was an engineering team to ship a multi-tenant SaaS — Laravel API, agency-facing React dashboard, and a WordPress plugin embedded inside every customer site, all kept in sync, all production-ready.
That's where we came in.
THE APPROACH
A three-piece architecture so the dashboard, the API, and the site stay in sync.
We split the product into three independent surfaces that share one source of truth. The WordPress plugin handles in-site collaboration. The Laravel API holds the data and the rules. The React dashboard gives agencies cross-site control. Each piece does one thing well, and they sync over signed REST calls.
That separation lets a website developer work inside a client's WordPress admin — leaving Figma-style comments directly on live pages, spinning them into tasks, and closing feedback loops without ever leaving the site. An agency lead manages twenty client builds from a single dashboard. The platform team ships features to either surface without breaking the other.
THE STACK
Production stack, end to end.
WordPress plugin
React 18 bundle embedded in WP admin. Connects directly to the API from inside any client site.
Laravel API
PHP 8.2 / Laravel 12 with Passport for OAuth2. 40+ resource types — workspaces, tasks, discussions, sitemaps, templates, approvals.
React dashboard
Vite + React 18 standalone app. Agency-facing control center for accounts, billing, and cross-site management.
Storage & infra
DigitalOcean Spaces for file uploads and CDN. SureCart for subscriptions. HMAC-signed sync between WP and the API.
THE OUTCOME
Live, earning, and growing.
WP SiteLauncher launched in 2025. It now serves 100+ paying agencies running 150+ WordPress sites through the platform, with 60+ features shipped post-launch.
Subscription billing runs through SureCart. Files live on DigitalOcean Spaces. The Laravel API handles license validation, workspace state, and signed sync with every connected WordPress site. The whole platform sits on production infra we own and operate.
WHAT'S NEXT
Scaling the platform, not just the feature list.
The roadmap is now driven by paying agencies — what they need to onboard their next ten clients, where the platform slows them down, what they'd happily pay more for. We ship in tight cycles with PAC's team, with feedback loops measured in days, not quarters.
The technical work shifts from "build the product" to "scale the product" — performance, observability, billing edge cases, multi-tenancy hardening. Less greenfield, more discipline.
Ready to start your next project?
We read every inquiry. If we're a fit, we reply within two working days with a short, honest note about scope and fit.