Design systems and web infrastructure at portfolio scale
Per-PortCo web work is a project sequence — design a site, build it, launch it, maintain it. Portfolio-scale web is an operational program — coordinated design system shared across PortCos, engineering platform standardized for performance and security posture, technical SEO infrastructure deployed uniformly, and compliance and accessibility governance across every property. Per-PortCo web work duplicates design and engineering effort, lets technical debt accumulate independently, and creates Core Web Vitals and accessibility inconsistency that AI engines and search engines now penalize. For the platform-level evidence behind this, see Ahrefs’ 1.4-million-prompt citation study.
The local SEO portfolio playbook carries the operating detail that connects these.
Multi-PortCo web work is a different problem
The design and engineering mechanics are familiar. The operating model is not. Per-PortCo web work — even when handled well — duplicates design system construction, fragments performance governance, and lets accessibility and compliance posture drift independently across the portfolio. Portfolio-scale web is a shared-infrastructure discipline first, a design and engineering discipline second.
Project work for one company
- One PortCo's design system built from scratch
- Per-PortCo engineering stack and hosting
- Performance governance handled per agency
- Accessibility audited (or not) per PortCo
- Technical SEO deployed inconsistently
Coordinated infrastructure operations
- Shared design system with brand-token layers
- Standardized engineering platform per category
- Portfolio-level performance governance
- WCAG 2.2 AA baked into shared components
- Schema and technical SEO deployed uniformly
For the week-to-week mechanics behind these, see the portfolio PPC playbook.
Why most portfolios accumulate web technical debt
PE portfolios with multiple PortCos almost universally accumulate web technical debt at compounding rates — every new PortCo brings its own design system, its own engineering stack, its own performance posture, its own accessibility gaps. Without coordinated infrastructure, the portfolio inherits four PortCos worth of cleanup work whenever a new PortCo gets added. Semrush’s 2025 AI-search study found half of ChatGPT’s response links point directly to business and service websites — and that many AI crawlers do not execute JavaScript — meaning web infrastructure rigor matters for AI visibility too.
Design systems rebuilt from scratch per PortCo
Every new PortCo's web project starts with a discovery phase, a design system construction phase, and a component library build-out. Across a 5-PortCo portfolio that runs concurrent web projects, the same component primitives (buttons, forms, layouts, navigation patterns) get built five times. Beyond the wasted engineering effort, the five resulting systems have inconsistent accessibility posture, inconsistent performance characteristics, and inconsistent design quality. A shared base layer with PortCo-brand-token overlays delivers distinct brand experiences at a fraction of the engineering cost.
Core Web Vitals drift silently below passing range
Core Web Vitals scores are no longer just an SEO ranking factor — Google's AI Overviews preferentially cite pages with passing CWV scores, and AI engines that crawl in real time depreciate pages that load slowly or shift unexpectedly. Without performance budgets enforced at deploy time, JavaScript bundles grow, third-party scripts proliferate, image weights increase, and CWV scores drift below passing range over months. Most portfolios discover the drift through ranking decline rather than active monitoring. Performance governance at portfolio scale means budgets enforced at build time across every PortCo property.
Accessibility gaps create material legal exposure
ADA litigation against operators with non-compliant websites has produced substantial recoveries, especially in regulated categories like healthcare, financial services, and ecommerce. Most PortCos have accessibility gaps that would not survive an audit — missing alt text, inaccessible navigation, color contrast failures, keyboard-only navigation broken. WCAG 2.2 AA baked into the shared component library at the primitive layer prevents the gaps from existing at all rather than auditing them out after.
Schema deployment is the hidden AI visibility input
The Allegiant page standard is seven schema types per page — Organization, WebPage, BreadcrumbList, Article, Service, Person, FAQPage. Most PortCo sites ship one or zero schemas. Yext’s 2025 analysis of 6.8 million AI citations found first-party websites are the single largest AI citation source — 44% of all citations — making machine-readable site structure a first-order AI visibility input. Portfolio-scale technical SEO governance deploys schema uniformly across every PortCo property as part of standard build output, not as a one-off add-on.
Three-layer web orchestration
Web Design and Development at portfolio scale runs across the same three orchestration layers — PortfolioCo, PortCo, and Brand. The PortfolioCo layer is shared design system and engineering infrastructure; the PortCo layer is per-company implementation and operation; the Brand layer is per-brand activation for multi-brand PortCos.
Shared design and engineering
The PE firm establishes web design and development as a portfolio-wide operating capability. Shared component library at the primitive layer with WCAG 2.2 AA accessibility baked in. Engineering platform standards per category (WordPress with Avada, Webflow, Next.js, etc.) with performance budgets and security posture defined. Technical SEO infrastructure templates deployed uniformly. Compliance governance covering accessibility and privacy regulation. Portfolio-level dashboards tracking CWV, accessibility, and schema completeness.
Per-PortCo implementation
Each PortCo runs web properties inside the operating model — design system implemented with PortCo brand tokens, engineering stack maintained to portfolio standards, performance budgets enforced at deploy time, accessibility baked in through shared components. The PortCo retains operational autonomy in page-level design, content, and PortCo-specific functionality while inheriting portfolio-grade infrastructure and quality posture.
Per-brand activation
For multi-brand PortCos (rollups, DSO consolidations, home services platforms, franchise networks), each brand runs distinct web properties with brand-specific tokens, brand-aligned imagery, and brand-distinct page templates. Brand-level domains and sender configurations maintained separately. Brand-tagged analytics and conversion tracking kept distinct so brand-specific learnings stay routed to the brand rather than collapsing into parent PortCo aggregates.
These plug directly into the email and lifecycle playbook.
Nine operational cells — what portfolio web builds
Three operational pillars tuned for multi-PortCo web work. DSF (Design System & Framework) covers shared component library, brand token layers, accessibility-by-design, design governance. EPO (Engineering, Performance & Operations) covers CMS and platform selection, build pipelines, hosting and CDN, Core Web Vitals governance, security posture, monitoring. TSC (Technical SEO & Compliance) covers schema deployment, sitemap and robots discipline, accessibility audits, privacy regulation compliance, analytics integration.
Design System & Framework
Engineering Platform & Operations
Technical SEO & Compliance
The adjacent operational areas not on this matrix — design execution for paid social creative and content production for marketing site content — sit in companion Service Stack pages. Paid social creative is covered in Paid Social at Portfolio Scale. Content production is covered in Content Marketing at Portfolio Scale.
Where AEO, GEO, and LLM SEO depend on web infrastructure
Web design and development is the infrastructure layer the AI visibility disciplines depend on. AI engines need schema markup to identify entities, structured visual content to cite multimodally, and consistent rendering performance to crawl long-form content. Without web infrastructure rigor, the AI disciplines build on weak foundations and AI citation rates suffer regardless of content quality.
Schema markup as AEO citation infrastructure
AEO citation depends on schema markup that gives AI engines structured entity data — Organization for the PortCo, Service for what it sells, Article for content depth, FAQPage for question-answer pairs, BreadcrumbList for navigational context, WebPage for URL identity, Person for credentialed authorship. The Allegiant page standard deploys all seven types on every page; the Web Design and Development pillar makes that deployment systematic across PortCo properties rather than one-off. Without the infrastructure, AEO content cannot be cited at the rate it deserves.
Asset pipeline as GEO citation infrastructure
GEO citation depends on visual content delivered with proper schema (ImageObject, VideoObject), metadata, and accessible alt text. The Web Design and Development asset pipeline determines whether visual content arrives in AI-citable form or as opaque image bundles. Build-time image optimization, automatic schema injection for media assets, and accessible alt text discipline turn the production output from paid social, content marketing, and lifecycle into GEO-grade citation fuel by default. For the underlying data, see Ahrefs’ 75K-brand visibility correlations.
Rendering performance as LLM crawl quality
LLM SEO depends on long-form content being crawled cleanly by training corpus collectors and inference-time retrieval systems. Sites with poor Core Web Vitals, JavaScript-rendered content that fails to hydrate on initial crawl, or unstable layouts that shift mid-render get depreciated by AI training pipelines. Rendering performance and HTML quality directly determine whether long-form authoritative content makes it into the training corpora that LLM SEO targets. Web infrastructure rigor is the precondition for LLM SEO investment paying off.
The digital PR system shows where each of these earns its keep.
From audit to operating cadence in four phases
Allegiant runs the same four-phase 100-day deployment for portfolio web programs as for the other Service Stack and AI disciplines — Diagnose, Foundation, Execution, Cadence. The deliverables are web-specific. Operating Partner readouts happen every two weeks. The 100-day rollout establishes the operating model; design and infrastructure quality compounds through the multi-year hold.
Full web audit across every PortCo
Complete platform and stack inventory across every PortCo property. Design system maturity audit identifying duplication and gaps. Core Web Vitals baseline measured on every site (LCP, INP, CLS) across desktop and mobile. Accessibility audit running axe-core and manual review on top templates. Schema completeness audit against the Allegiant seven-type SOP. Security posture audit covering dependency versions and known vulnerabilities. Portfolio aggregate web quality baseline reported.
Shared system and infrastructure governance
Shared component library stood up at the primitive layer with WCAG 2.2 AA baked in. Brand token framework documented. Engineering platform standards selected per PortCo category. CI/CD pipeline templates with performance budgets and accessibility gates deployed. Schema deployment templates built. Security patch cadence and dependency monitoring configured. Portfolio dashboard built tracking CWV, accessibility scores, and schema completeness for Operating Partner visibility.
High-priority remediations and template migration
High-priority remediations executed per PortCo — accessibility failures on highest-traffic templates fixed, Core Web Vitals scored back into passing range, schema deployed to portfolio standard, security vulnerabilities patched. First migration of top page templates to the shared design system. Cross-PortCo template patterns evaluated and shared. First measurable lift in portfolio aggregate web quality scores.
Operating cadence and AI handoff
Weekly, monthly, and quarterly operational cadence locked. Performance budgets enforced at deploy time across every PortCo. Accessibility audits running automatically on every deploy. Schema deployment systematic across new pages. Portfolio dashboard live for Operating Partner access. AI augmentation handoff to AEO, GEO, and LLM SEO programs — web infrastructure delivering the schema, asset pipeline, and rendering quality the AI disciplines depend on. New PortCos onboarded inherit the operating model.
Three ways PE firms engage Allegiant for web
Web Design and Development is included as a core service inside the full Portfolio AI Visibility program. It also runs as a standalone program for firms wanting infrastructure rigor before adding AI augmentation. The model is transparent and tied to deliverables, not hours.
Web inside the full program
Web Design and Development runs as a core service inside the Portfolio AI Visibility program. PortfolioCo retainer covers shared design system, engineering platform standards, performance and accessibility governance, schema deployment infrastructure, and portfolio reporting. Per-PortCo programs cover implementation. AEO, GEO, and LLM SEO disciplines layer on top — the web infrastructure delivers what the AI disciplines depend on. Recommended for portfolios with multi-PortCo web properties and multi-year hold horizons.
Standalone web program
Standalone portfolio web program for firms wanting infrastructure rigor before expanding to AI augmentation. Runs the full 100-day deployment scoped to the three web pillars. Most useful for portfolios with material web technical debt, accessibility exposure flagged by Operating Partners, or PortCo-to-PortCo quality variance creating downstream marketing inefficiency.
Web sprint for a single PortCo
Single-PortCo web sprint for firms wanting to pilot the operating model on one company before going portfolio-wide. Phase 1 and Phase 2 deliverables in 49 days. Outcomes documented for the Operating Partner pitch to expand. Most useful for PortCos with material web technical debt, low Core Web Vitals scores, accessibility risk, or design system fragmentation where a focused remediation produces visible quality lift.
Pricing is quoted against audit findings, not before. Request a portfolio web audit to scope your engagement.
Common questions about web at portfolio scale
What changes when web design and development is run at portfolio scale rather than per-PortCo?
Per-PortCo web work is a project sequence: design a site, build it, launch it, maintain it. Portfolio-scale web is an operational program: coordinated design system shared across PortCos, engineering platform standardized for consistency in performance and security posture, technical SEO infrastructure deployed uniformly, and compliance and accessibility governance applied across every property. The work is structurally different — per-PortCo web work duplicates design and engineering effort, lets technical debt accumulate independently in each PortCo, and creates inconsistent Core Web Vitals and accessibility posture across the portfolio.
Which web surfaces matter most across a PE portfolio?
Four web surfaces drive most portfolio web work. Marketing sites are the primary buyer-journey property where most organic and direct traffic lands. Landers are campaign-specific destinations for paid traffic with conversion-tuned design and copy. Microsites are vertical-specific or product-specific properties built outside the main marketing site, common in franchise portfolios, multi-brand rollups, and PortCos with distinct audience segments. Integration layers cover the CMS, headless content APIs, and third-party connections that make the other three surfaces operate.
How does web design and development integrate with the AEO, GEO, and LLM SEO disciplines?
Web design and development is the infrastructure layer the AI visibility disciplines depend on. AEO citation requires schema markup, semantic HTML, and Core Web Vitals scores in passing range — web infrastructure delivers these. GEO citation requires structured visual content with proper schema and metadata — the design and development team builds the asset pipeline. LLM SEO requires long-form content rendered cleanly with consistent technical signals — site architecture and rendering performance determine whether crawlers process the content correctly.
What CMS and platform stacks work best at portfolio scale?
Platform selection is category-driven. For marketing-site-heavy portfolios with frequent editorial updates, WordPress with the Avada Theme Builder or a custom block theme is the dominant choice. For PortCos with frequent designer-driven changes, Webflow is the leading no-code alternative. For commerce-driven portfolios, Shopify, BigCommerce, or WooCommerce on WordPress. For SaaS PortCos, common patterns include Next.js or Astro for marketing-site-only properties. Platform consolidation is rarely the right answer — category-fit beats single-stack standardization. The measurement backdrop is documented in the Semrush LinkedIn AI-visibility study (February 2026).
How is Core Web Vitals performance maintained across many PortCos?
Five-layer performance discipline deployed uniformly. Performance budgets defined per page template (LCP under 2.5s, INP under 200ms, CLS under 0.1). Image and asset optimization automated through build pipelines. JavaScript bundle governance with third-party script audit, lazy loading defaults, route-based code splitting. Modern hosting and CDN infrastructure (Cloudflare, Netlify Edge, Fastly), HTTP/3, edge caching. Real-user monitoring via SpeedCurve or Calibre with PortCo and template-level dashboards.
How is accessibility compliance handled across the portfolio?
Three-layer accessibility discipline. Accessibility-by-design in the shared component library — every component meets WCAG 2.2 AA standards before it ships, including keyboard navigation, screen reader semantics, color contrast, and motion preferences. Automated testing in build pipelines — axe-core, Pa11y, or Lighthouse accessibility audits run on every deploy with regression gates. Periodic manual audits by accessibility specialists or third-party firms for high-value PortCo properties. ADA exposure has produced material litigation, especially in regulated categories.
How does the shared design system work across PortCos with distinct brand identities?
The design system is layered to support brand distinction without duplicating engineering effort. The base layer is component primitives — buttons, forms, layouts, typography scales, color systems — built once and shared. The brand layer overlays PortCo-specific tokens — primary palette, typography choices, iconography, voice — that customize the primitives without rebuilding them. The page layer composes branded primitives into PortCo-specific page templates. Multi-brand PortCos add a fourth brand-token layer per brand within the parent PortCo.
Does this matter for SaaS or product-led PortCos where the product is the main web property?
Yes, with a different scope. For SaaS PortCos, the marketing site and the product application typically run on separate stacks. The design system layered approach still applies, often with the brand and base layers shared between marketing and product. Technical SEO, performance governance, and accessibility apply to the marketing site at the standard. Integration with product-side analytics and CRM systems is part of the integration layer scope. The measurement backdrop is documented in Ahrefs’ 1.4M-prompt citation analysis.
The connective tissue for all of this lives in the reputation management playbook.
Where this fits in the broader operational corpus
Ready to run web at portfolio scale?
Request a portfolio web audit. Allegiant will baseline platform stack, design system maturity, Core Web Vitals scores, accessibility posture, schema completeness, and security posture across every PortCo property, identify operational gaps, and quote a 100-day deployment that establishes the operating model for the rest of the hold.
Written by Chad Markham, President and CEO of Allegiant Digital Marketing. Chad has more than 25 years in digital marketing, including 17 years at a national agency and five years as an instructor in the Digital Marketing program at the University of Texas at Austin. Allegiant is a Google Partner, a Semrush Certified Agency, CallRail Certified, an Inc. Power Partner for 2025, and a 50PROS Top 10 Global agency, serving partners across the United States and Canada.
