The new Enterprise PMM is hired to build "customer proof that help our biggest deals close". Yet the enterprise page, where every demo request starts, has eight customer logos and not one customer story, quote or named result, and it does not link to the Descript story, which already proves the enterprise case: 13 models in production through one integration, and new-model evaluation cut from over a week to one or two hours. The only number on the page is an illustrative example.
First action
Add the Descript result and link to the enterprise page this week.
How to measure it
Enterprise page demo-request rate
- Now
- –
- Target
- +20%
- By
- 60 days
Steps
Pull the proof
Descript and Pax Historia numbers plus any approved quotes.
Product Marketing Manager, Enterprise 1 day
Ask logo customers
Request one quote and one number from each of the eight logos.
Product Marketing Manager, Enterprise 1 week
Design the band
Proof under the hero, one line per buyer group.
Product Designer 2 days
Ship it
Enterprise page, demo confirmation email and AE deck.
Product Marketing Manager, Enterprise 2 days
Replace the example
A real blended-cost result in place of the illustrative -27%.
Product Marketing Manager, Enterprise 1 month
Measure
Demo requests per visit before and after.
Director, Growth Marketing 4 weeks
Why it works
Add a proof band under the hero: the Descript numbers with a link to the story, two short quotes from logo customers, and one line per buyer group (engineering: day-0 models; finance: spend by team; security: zero data retention; procurement: one contract). Swap the illustrative -27% for a real, approved customer figure as soon as one is cleared. Put the same proof in the demo confirmation email and the AE deck.
Enterprise buyers want to see a company like theirs succeed, and the strongest proof OpenRouter has is published but sits two clicks away from the page that asks for the demo.
Ready to use
ChecklistEnterprise proof band
[ ] Descript: 1 -> 13 models in production, 1+ week -> 1-2 hours to evaluate a new model (link to story) [ ] Two quotes from logo customers, with name and title [ ] One proof line each for engineering, finance, security and procurement [ ] A real blended-cost result to replace the illustrative example [ ] Same band in the demo confirmation email [ ] Same slide in the AE and SE deck [ ] Demo-request rate tracked before and after
Risks and how to handle them
Customers slow to approve quotes
Start with the published Descript story and add quotes as they clear.
Logos without stories look thin
Rotate in each new story as the advocacy program produces it.
Evidence
- HiringProduct Marketing Manager, Enterprise (posted September 29, 2026): owns the enterprise journey "from demo request to signed contract to expansion"; will "build the sales narrative and customer proof that help our biggest deals close", "Build and maintain competitor comparisons", "run win/loss analysis", and "Stand up and scale advocacy, case studies, references, and a customer advisory board or design partner program".Source
- Your websiteEnterprise page (checked October 22, 2026): H1 "Your inference control plane"; a strip of eight customer logos (Lovable, Replit, Amplitude, Nvidia, Zoom, WTW, NIST, AMD) but no customer story, quote or named result anywhere on the page and no link to a case study; the only cost figure is an illustrative "Example: blended cost per 1M tokens -27%"; calls to action "Book a demo" and "Talk to us".Source
- Your websiteCustomer proof on the site: two customer stories, /customers/descript ("1 -> 13 Models in production", "1+ week -> 1-2 hours To evaluate a promising new model") and /customers/paxhistoria ("35k" daily players, "4.8M+" monthly requests); the blog's case-study section adds Rasp, an agent used by OpenRouter's own sales team. The Descript story is published at three URLs, each with its own canonical: /customers/descript, /blog/case-studies/descript-case-study/ and /blog/insights/descript-model-evaluation-queue/.Source