Tavus has 11 published customer stories and three strong results on its homepage, but /customers returns 404 and the homepage links to none of the stories. An enterprise champion who wants to forward proof to a CFO has nowhere to send them.
First action
List the 11 stories with the one number each can publish, and confirm the Piper wording with the customer.
How to measure it
Demo requests with a /customers visit
- Now
- –
- Target
- 30% of enterprise demo requests
- By
- 60 days
Steps
Inventory the stories
The 11 stories, their industry, use case and the single strongest number in each.
Founding Marketer (Brand, Product, Storytelling) 1 day
Settle attribution
Confirm how Piper is credited (Salesforce, Qualified or both) and use that wording on every page.
Enterprise Account Executive 3 days
Design the hub
Headline results, filterable cards, a short "how they built it" line per card.
Brand & Product Designer 2 days
Publish and redirect
Ship /customers in Webflow; link it from the homepage results and the menu.
Vibe Growth Marketer 1 day
Add to sales follow-up
A "see who builds on Tavus" link in every AE and BDR sequence.
Business Development Representative 2 hours
Measure
Track hub visits on demo-request journeys in HubSpot.
Growth Marketer 2 hours
Why it works
Build /customers as a hub: the three headline results (Piper, Aurora, Ruby) at the top, then every story as a card with industry, use case, channel and one number. Filter by use case (sales, L&D, healthcare, interviews). Link it from the homepage results, the menu, the AI SDR page and every sales follow-up email. Use one attribution for Piper everywhere, agreed with the customer.
The new Enterprise AE sells "a genuinely new product category", and a new category is bought on proof from peers. The stories already exist; this makes them findable by buyers, search engines and AI assistants.
Ready to use
ChecklistCustomer card fields
[ ] Customer name and logo approval [ ] Industry [ ] Use case (sales, L&D, healthcare, interviews, custom) [ ] Channel (web, Zoom/Meet, app) [ ] One published number [ ] Quote with name and title [ ] Link to the full story [ ] Date the result was measured
Risks and how to handle them
Customers limit what can be published
Use relative results or the use case alone where a number is not cleared.
Proof skews to sales use cases
Commission the next two stories in healthcare and L&D (idea 9).
Evidence
- Your websiteHomepage: "The human interface for AI", "Powering 150,000+ developers". Visitors first choose a Developer Account or a PALs Account ("personal AI companions"). Proof: Salesforce's Piper PAL SDR (6x meetings scheduled, 2x engagement, "#1 AI SDR agent on G2"), Orum's Aurora sales coach (50% faster ramp, 3x rep conversion, 25% more coaching revenue) and Med Learning Group / Regeneron's Ruby CME consultant (65% better comprehension, ACCME + AMA accredited). The homepage links to none of the 11 customer stories.Source
- Your websiteThe sitemap lists 544 URLs: 454 blog posts (28 "vs" posts such as heygen-vs-tavus, d-id-vs-tavus and anam-ai-vs-tavus, and 15 "alternatives" posts), 11 customer stories under /customers/ while /customers itself returns 404, and internal pages such as /lp/alex-top-secret-page-wip (a password page headed "For your eyes only") and /style-guide/vid-uploads.Source
- Your websiteThe AI SDR solutions page credits the same 6x meetings result to "Qualified × Salesforce", while the homepage says "Salesforce built Piper".Source
- HiringEnterprise Account Executive: sells "a genuinely new product category" to enterprise buyers with self-sourced pipeline; developers and enterprises use CVI "across sales, support, healthcare, learning & development, and more, in 30+ languages"; Tavus runs its own models for perception (Raven), conversational flow (Sparrow) and rendering (Phoenix).Source