Strategy
Designing one website for customers, investors, and candidates
Enterprise SaaS and AI platforms often need to speak to buyers, investors, partners, and candidates on one site. Here’s how we keep the story clear.
Most marketing sites are built for one audience: the buyer. But a growing number of the platforms we work on, especially fundraising-stage AI and infrastructure companies, need to speak to customers, investors, partners, candidates, and press at the same time, often on the same homepage.
Get this wrong and you end up with a site that's diluted for everyone. Get it right and every visitor feels like the site was built for them specifically. Here's the approach that actually works.
Start with one narrative, not five
The instinct is to build separate paths immediately: a customer section, an investor section, a careers section. But if you start there, you end up with five disconnected pitches instead of one company. We always start with a single core narrative; who the company is, what it's built, why it matters, and let every audience-specific page branch off that same story rather than tell its own.
Answer the audience's first question, fast
An investor's first question is different from a customer's first question, which is different from a candidate's. The homepage can't answer all of them in depth, but it needs to signal within a few scrolls that each audience is going to find what they need. That usually means a homepage structured in layers: broad vision first, then progressively more specific paths for each visitor type.
Don't force a single conversion goal
Most marketing sites are built around one CTA: sign up, book a demo. Multi-audience sites need to resist that instinct. A customer's next step is a demo. An investor's next step is a data room or a call with the founder. A candidate's next step is the careers page. Forcing everyone toward the same button either annoys the audiences it wasn't meant for, or dilutes the CTA for the one it was.
Build it to scale before you need it to
These sites tend to grow fast; new press, new whitepapers, new product lines, new hires. If every new asset requires a page rebuild, the site becomes a bottleneck within months. We build these on modular, CMS-driven templates from day one so a new whitepaper or press mention is a content entry, not a design project.
The test we use
Before shipping, we ask: could someone from each of these audiences land on the homepage and know within ten seconds whether they're in the right place. If the answer is yes for all of them, the structure is working. If it's yes for only the primary audience, it's not done yet.
