OneGuide

OneGuide sells a knowledge network to private equity and venture capital firms, and oneguideportal.com is how it gets delivered: a WordPress multisite network where every client firm gets its own white-labeled portfolio portal on its own domain, fed from a single content hub. I was the engineer behind that network: the multisite architecture, the domain mapping, the editorial tooling, the member management, the deploy pipeline and the performance work that kept it usable as it grew.

Key Takeaways

  • Ran one codebase serving nineteen sites, including fourteen white-labeled firm portals, several on the client firm's own hostname.
  • Made white-labeling real at the session level, with the cookie domain derived from the request host so a portfolio executive signs into their firm's brand.
  • Turned the WordPress admin into a curation console for client users: two verbs, Show/Hide and Recommend, with editing surfaces removed and hidden content genuinely unreachable.
  • Built member management as an API: bulk cohort creation from CSV that provisions the WordPress user, community profile, CRM contact and custom fields in one validated pass.
  • Made per-firm behavior a settings page rather than a fork: content arrival policy, account defaults, branding and activation email per site.
  • Kept a 74-plugin multisite fast and stable through tested update batches, caching architecture and deploy tooling.

Organization

OneGuide is a team of roughly ten selling functional knowledge to PE and VC firms: expert-written guides for the operating questions every portfolio company has. Each client firm expects its own domain, branding, content policy and member base, delivered from one editorial hub.

Challenge

Every client wants their own website and there is only one small team. The network had to deliver per-firm identity, per-firm content policy and per-firm membership from one codebase, on a heavyweight plugin stack, without curation choices leaking through direct URLs and without every new firm becoming a new maintenance burden.

Solution

  • A subdomain multisite with hostname mapping, host-derived cookie domains and host-aware redirects for rebranded portals.
  • A per-site settings page covering content syndication policy, account activation defaults, branding and the activation email.
  • Curation tooling: visibility controls that cascade between guides and their authors' expert profiles, with front-end guards on unpublished content.
  • A member API for export and bulk onboarding, joined to the CRM, plus a hand-built responsive activation email with live preview.
  • Performance architecture: Redis object caching keyed per site, reduced write pressure, and a system cron replacing WP-Cron.
  • Four environments behind one deploy command, shipping only custom code and configuration.

Results

  • Nineteen sites and fourteen firm portals from one codebase and one deploy.
  • Member onboarding effort per cohort down roughly 90%.
  • Per-portal curation effort down roughly 75%.
  • Portal response time improved roughly 30%.
  • 74 plugins carried through 13 tested update batches, then handed over cleanly.