The story
- 01 · Problem
Several partner brands and one team doing the work behind them. Client data, tasks, finances and reports were spread across separate tools and ad accounts, and reports were assembled by hand every month.
- What had to change
- The operating model was the requirement: partner agencies selling under their own brand, one team doing the work, per-client marketing data in one database, and analysis that runs without an analyst. The boundary is designed so the business keeps its leads and payments, and the agency works with growth signals.
- 02 · System
A branded agency panel: every client with its Ads, Analytics, Search Console, Business Profile, Meta, website, leads and invoices in one place, plus prospects, projects, tasks, calendar, files and team roles. A morning digest summarises every client account.
- Connected
- OAuth to Google and Meta; a Google Ads API application approved for the agency; IMAP/SMTP; Google Calendar; DataForSEO; a custom WordPress plugin.
- Automated
- Nightly sync → deterministic analysis → health scores and recommendations → an AI-written morning digest. Code computes the numbers; AI only interprets a frozen snapshot.
- 03 · Implementation
Connectors to Google Ads, GA4, Search Console, Business Profile, Meta, PageSpeed and a custom WordPress plugin; a nightly sync, a weekly journal and a monthly PDF report; a free-audit flow that turns a prospect into a deterministic audit, a public audit page in three languages and a proposal draft. All under the agency’s own domain and brand.
- 04 · Result
The agency runs on its own branded system: real client work is tracked there (5 completed projects with around 150 tasks) and every client account gets a morning summary. In pilot. Running more than one agency brand on the same system is what turned it into PlexWizz.
Technical detail
- Architecture in detail
- Built as the first tenant of a multi-tenant platform: the agency’s own domain, sign-in bound to its host, emails, PDFs and the mobile app in its brand; a database-first rule (the interface reads only stored data; external APIs are called by scheduled syncs).
- Layers
- Business Architecture Software Data AI Integration Infrastructure
- Stack
- NestJS React PostgreSQL Redis Cloudflare