Talk about your next project
Roadrunner case study

The lesson

Show each use case as a worked example of the product handling one plain-language request, so the reader sees the work instead of reading a claim about it.

The move

The hero puts the headline over two stats, "9 weeks" from kickoff to live and "~1 min" to generate a quote, next to the Watershed logo. A sticky side card lists Industry, Team and Products with an "On this page" menu, beside "Meet Watershed" and a pull quote from Laura Forth, Director of Revenue Operations. "Road to Roadrunner" lays out where the homegrown Salesforce Flows setup hit its limits: Slack approvals, discount math left to the rep, and contract changes that erased history. "Three ways Watershed’s RevOps team runs on Roadrunner" follows, with Admin Agent, Quote Agent and Data & MCP sections. The Admin Agent and Quote Agent sections each show a mockup of a typed request and the agent's result, while the Data & MCP section uses text and a quote only, and the page closes on an impact section.

Why it works

  • Our readThe Admin Agent mockup changes a seat warning from 5,000 to 500 and runs draft tests, so a RevOps buyer can judge the product from one concrete task.
  • Our readListing the old setup's three specific failures gives each later use case a clear problem it answers.
  • Our readQuotes from both the RevOps director and an account executive cover the two people a quoting tool has to satisfy: the admin and the rep.

What not to copy

Don't copy Watershed's sustainability context, the CPQ and Salesforce Flows details, or the agent product names. Keep the two-stat hero, the sticky profile card with jump links, a short list of where the old setup broke, and one use case per section, with a mockup of a real request where the product's work can be shown, and a customer quote.

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.