Talk about your next project
Asana case study

The lesson

Show the whole operating system before the narrative, then explain each workflow in the order work moves through it.

The move

The page opens with a left rail of customer facts, including region, key workflows, industry, company size, key features and integrations, beside the title “Coupa scales to support customers with Asana” and a short summary. A large customer photo is followed by compact “Challenges,” “Solutions” and “Outcomes” blocks, including “+658% time saved in 3 years” and “135 workdays per year,” then a named executive quote. The body explains “How Asana helps Coupa work smarter” through sections on standardized requests, roadmap alignment, project planning and reporting, with product images and quotes from PMO leaders.

Why it works

  • Our readThe left rail lets enterprise readers check fit quickly before committing to the full story.
  • Our readPutting challenges, solutions and outcomes near the top gives the whole case in a skim-friendly block.
  • Our readThe workflow sections follow the path from request intake to roadmap to in-flight reporting, so the reader can picture how the system works.

What not to copy

Don't copy Coupa's PMO process, priority scoring language or time-saved claim. Keep the customer fact rail, the early challenge-solution-outcome block and the workflow-by-workflow body.

More from Asana

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.