Talk about your next project
Clay case study

The lesson

Lead with the customer’s outcome, then make the workflow believable by showing each automated step in order.

The move

The page opens with “ALL CASE STUDIES / ROOTLY,” the customer name, the title, and three impact claims: “100% Automation of outbound sales workflows, from list building to outreach,” “10x Outbound team performance with a lean sales org,” and “0 Manual research or list-building tasks required.” An “At a glance” rail lists the problem, Clay’s impact, and use cases before the story introduces Rootly, its industry, headquarters, and a quote about being “leaner, faster, and more precise.” The case then moves through “Impact TL;DR,” “The problem,” and “The solution: building a smarter sales engine with the AI Demand Generation Engineer,” before breaking the workflow into use cases such as “Automating company research and lead scoring” and “Real-time outreach triggered by ‘incident signals.’”

Why it works

  • Our readThe impact row gives a busy sales reader the whole promise before the page moves into the story.
  • Our readThe “At a glance” rail turns a long workflow story into a navigable list of problems, use cases, and impact.
  • Our readThe use-case sections make the implementation concrete, from lead scoring to incident-triggered outreach.

What not to copy

Don't copy Rootly's incident management context, AI Demand Generation Engineer role, or vendor mix with Apollo, UserGems, and 6sense. Keep the structure of impact metrics first, a left-hand story map, then a problem-to-solution story broken into specific workflow use cases.

More from Clay

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.