Building the case to turn a corporate website into an AI-first revenue channel
Strategy, program management, and execution for a multi-workstream initiative to redesign how a global professional services firm shows up for buyers, human and AI alike.
- The problem
- Buyers now start their research with AI, and the firm's website wasn't built to show up in those answers.
- What I did
- I'm leading the program across three workstreams: the strategy, a generative engine optimization pilot, and a personalization framework.
- The result
- In progress. The strategy is built and ready to present, and the pilot is scoped and in procurement.
The channel hadn't changed. Buyer behavior had.
Large professional services firms invest heavily in their websites, but those sites are built for a world where buyers navigate directly to them. In 2026, a growing share of B2B buyers start with AI. They ask a question. They get answers. And the brands that aren't structured to appear in those answers don't exist in that moment.
This initiative is built around that recognition. The goal: redesign how a global firm's primary web channel works, including its architecture, its content, its intelligence layer, and its AI-facing infrastructure, and build the business case and operational machinery to make that transformation real.
The problem
The site was organized around internal capability structure, not buyer challenges. It wasn't designed to be cited by AI. It wasn't personalized. It didn't connect content to commercial outcomes. The result was an invisible channel: present for direct traffic, absent in the upstream AI discovery layer where buyers now form their shortlists.
The audience
Mid-market to enterprise B2B buyers researching complex technology and transformation services. Distinct audience segments include C-suite decision-makers, technical evaluators, and operations and procurement stakeholders, each with different triggers, different queries, and different content needs at each stage.
My role
Strategy and program management lead. Responsible for narrative architecture, workstream design, stakeholder alignment, vendor partnership, and keeping a complex multi-track initiative moving. Operating in close partnership with an executive sponsor who is accountable to the chief marketing officer (CMO).
The constraints
A new vendor requiring procurement and legal review. A design team that needed scope to stay focused. No existing generative engine optimization infrastructure. And the pressure to build a credible case for significant investment before a pilot could produce any results.
Three workstreams. One through-line.
The initiative isn't a single project. It's a coordinated program with three workstreams on a shared strategic foundation, each designed to reinforce the others. The strategy makes the case. The pilot is designed to validate it. Design makes the vision concrete.
The judgment calls that shaped the program.
These aren't descriptions of what was built. They're the reasoning behind why it was built this way.
- 01
Position the opportunity without discrediting what exists
The current site represents years of strong work, and the case for change couldn't come at its expense. The strategy frames the shift as a change in buyer behavior, not a failure of the site: what works for buyers who come to the site directly still works, and the opportunity is a new layer upstream that didn't exist when the site was built. That framing keeps the teams behind the current site as allies in what comes next, and it turns "fix this" into "build on this."
- 02
Reframe the problem as a split funnel, not a traffic problem
The instinct was to lead with site traffic or engagement metrics. That framing makes the problem feel like an SEO or UX issue. The more accurate, and more urgent, framing is that large language models (LLMs) have created a new upstream discovery layer that most brands aren't present in at all. "The funnel didn't shrink. It split." That one sentence changed how the entire narrative was organized.
- 03
Ground the case in independent research
Vendors were valuable for understanding what's possible, but a case for significant investment needs evidence leadership can trust on its own terms. Every core claim is grounded in independent research from Forrester, Gartner, 6sense, and Adobe Digital Insights. Vendor perspectives play their proper role: informing the solution, not proving the problem.
- 04
Order the five strategic bets by buyer impact, not internal logic
The five bets (Experience, Content, Channel, Intelligence, Technology) could have been ordered any number of ways: by cost, by complexity, by team ownership. The deliberate choice was buyer-first ordering: start with what the buyer experiences, end with the infrastructure that enables it. That sequencing makes the vision read as a coherent experience design argument rather than a list of capability investments.
- 05
Scope the pilot to the smallest version that proves value
The GEO pilot could have started with the full corporate domain. The deliberate choice was to scope it to a single business unit as the test environment, with clear criteria for what it needs to prove before expanding. That decision keeps the pilot achievable, the governance manageable, and the success criteria clean. It also makes the procurement conversation simpler: a bounded pilot is easier to approve than an open-ended platform commitment.
- 06
Separate deliverables for separate audiences
Three distinct audiences needed three distinct artifacts: senior leadership needs a strategic narrative, procurement and legal need a business case document, and the executive sponsor needs a use case deck for a working conversation. Combining any two of these would have made all of them worse. The discipline was to build each artifact for the specific decision it needs to enable, then link them rather than merge them.
- 07
Design the variable matrix around buyer state, not page type
The personalization framework could have been organized around content categories or site sections. Instead, it was designed around the buyer's state: their mode, their moment, their segment. That choice means the system can flex across any page rather than being locked to a specific template. It also makes the design team's job clearer: they aren't designing pages, they're designing responses to buyer states.
The Strategy: Making an Invisible Shift Impossible to Ignore
Researching a nuanced change in how B2B buyers find vendors, and turning it into a strategy senior leadership can act on: the evidence, the opportunity, the vision, and the solution.
Status: built and ready to present
The strategy works in four stages. It starts with the research: evidence that AI has split the buyer funnel into an upstream discovery layer, where buyers form shortlists inside AI answers, and a downstream validation layer, where they come to the website to confirm what they've heard. From there it states the opportunity, anchored in what AI-referred buyers are worth and what the firm is missing today. It sets the vision through five strategic bets, ordered by buyer impact. And it shows the solution: a personalization framework, an interactive prototype, real buyer scenarios, and a crawl, walk, run roadmap.
Detail on the competitive landscape and the AI agent experience supports the core argument rather than leading it. Leadership needs to see and react to the buyer experience first; the infrastructure behind it follows.
| Deliverable | Format | Audience | Purpose |
|---|---|---|---|
| Strategic narrative | Word | Executive sponsor | The research, opportunity, vision, and solution in one document, for review and alignment with the executive sponsor |
| Executive presentation (v12) | Word | Executive sponsor | Every claim paired with its evidence and source |
| Interactive wireframe prototype | HTML | Senior leadership + design team | Make the variable matrix and personalized experience tangible before the Figma build |
| Variable matrix system | Framework | Design team + executive sponsor | Define the buyer-state variables needed to design a personalized experience |
- Stage 1
Research
AI split the buyer funnel: discovery moved upstream into AI answers, and validation stayed on the website.
- Stage 2
Opportunity
What AI-referred buyers are worth, and what the firm misses by staying invisible upstream.
- Stage 3
Vision
Five strategic bets, Experience, Content, Channel, Intelligence, Technology, ordered by buyer impact.
- Stage 4
Solution
A personalization framework, an interactive prototype, buyer scenarios, and a crawl, walk, run roadmap.
The GEO pilot: vendor partnership and proof of concept
Scoping, designing, and mobilizing a generative engine optimization pilot with a net-new technology vendor, from initial vendor evaluation through procurement initiation and working session facilitation.
Status: scoped; in procurement and legal review
The pilot is designed around one guiding principle: the smallest scope that proves value with minimal governance and technical complexity. That means scoping to a single business unit as the initial test environment, with clear success criteria before any expansion. Keeping the pilot bounded isn't a compromise. It's the argument for why the procurement and legal review is worth initiating now.
Two detailed mid-market buyer journey use cases were developed to make the pilot concrete for the executive sponsor: a cybersecurity scenario (Director of IT Security at a manufacturing company, triggered by a peer's ransomware attack) and a finance and ERP scenario (Finance Operations Manager, triggered by a CFO mandate for Series C readiness). Each includes a day-by-day AI query sequence, emotional state annotation, channel behavior mapping, and content gap analysis, making the invisible AI window visible in the channel layer.
| Deliverable | Format | Audience | Purpose |
|---|---|---|---|
| Vendor business case (v3) | Word | Procurement + legal colleague | Initiate global legal review and procurement for net-new vendor onboarding |
| Buyer journey use case deck (v6) | PowerPoint / 10 slides | Executive sponsor | Make the pilot scenario concrete; surface content gaps as the evidence for why the pilot is needed |
| Vendor outreach email | Vendor contact | Reconnect, signal internal momentum, set up the pilot scoping conversation; establish tone-of-voice reference | |
| Working session notes + action log | Document | Executive sponsor, platform lead, vendor team | Capture alignment, open questions, and owner assignments from the cross-functional session |
| Constraint | How it was handled |
|---|---|
| Net-new vendor (no existing procurement path) | Built a standalone business case document specifically for procurement and legal, separate from the strategic use case deck. Kept the two documents linked but distinct so each could do its job for the right audience. |
| No GEO infrastructure exists yet | Designed the pilot to start with content scraping before requiring deeper content delivery network (CDN) or content management system (CMS) integration. The principle: prove the value of the content layer before committing to the technical architecture. |
| Content governance undefined | Flagged as an open question rather than a blocker. Identified analyst-relations content as the most credible early knowledge base source: already structured, reviewed, and authoritative. Left the broader governance design to the working session. |
| Pilot scope pressure (expand vs. focus) | Held the line on a bounded scope. The argument: a tightly scoped pilot with clean success criteria is easier to approve, easier to run, and easier to learn from than a sprawling one. Smallest and fastest path to proving value. |
Design and prototyping: making the vision concrete
Scoping and framing a personalization and design system that makes the strategic vision tangible for both executives and the design team, without getting ahead of what the program can actually build.
The personalization framework is built around buyer state rather than page type. Macro signals (mode, flavor, segment) define what the buyer is in the market for. Micro moments (spark, land, explore, act, follow-up) define where they are in the journey. Five GenAI experience archetypes (Adaptive Advisor, Thought Partner, Pre-Sales Assistant, Signal Amplifier, Lead Incubator) define what the site does for them at each moment.
The variable matrix system translates this framework into something a design team can work from: a defined set of inputs that determine which version of the experience a buyer sees. The interactive wireframe prototype makes this tangible for the executive sponsor without waiting for the Figma build to be complete.
| Deliverable | Format | Audience | Purpose |
|---|---|---|---|
| Variable matrix system | Framework document | Design team + executive sponsor | Define the buyer-state variables the personalized experience needs to respond to |
| Site intelligence personalization framework | Strategy document + archetypes | Design team | Define macro signals, micro moments, and GenAI experience archetypes for the site intelligence layer |
| Interactive wireframe prototype | HTML | Executive presentation / sponsor | Make the personalized experience tangible before the full Figma prototype is available |
| Design team scope brief | Working session + document | Design team lead + team | Define which variables to prioritize now, which to defer, and what the design team needs to solve for first |
What this program requires.
Program-level
AI strategy for marketing · Multi-workstream program management · Executive narrative development · Business case design · Stakeholder alignment · Executive stakeholder strategy · Revenue-connected framing · Vendor partnership and procurement
Strategy and content
Generative engine optimization (GEO) · B2B buyer journey mapping · Needs-led site architecture · Content strategy · Narrative architecture · Dark funnel analysis · Data sourcing and vetting · AI/LLM behavior applied to marketing
Design and execution
Personalization system design · Variable matrix frameworks · Interactive prototype development · Design team scoping · Pilot design · Cross-functional coordination · AI-assisted production workflows · Demand generation systems