Talk about your next project
GitHub case study

The lesson

Lead with the customer’s measured results, then use the story to explain where those changes showed up in daily work.

The move

The story opens with the Accenture logo, a GitHub Enterprise label, and the title “With 12,000 developers using GitHub Copilot, Accenture doubles down on GitHub’s platform.” Three large metrics follow: “95% of developers enjoy coding more when using Copilot,” “67% of developers use GitHub Copilot everyday,” and “96% success rate with GitHub Copilot amongst users.” A compact fact block lists “Number of Seats,” “Location,” “Problem,” and “Solution,” then the body explains Accenture’s client work, the initial pilot, and the randomized controlled trial. The rest of the story moves through tests, technical debt, legacy code explanation, innersourcing, IssueOps, GitHub Advanced Security, and ends with a GitHub Enterprise trial CTA.

Why it works

  • Our readThe first screen gives the customer, product, headline, and three adoption results before the reader reaches the narrative.
  • Our readThe randomized controlled trial makes the Copilot claims feel measured instead of purely anecdotal.
  • Our readQuotes from Dan Schocke and Kristine Steinman move the story from coding speed to technical debt, confidence, collaboration, and security.

What not to copy

Don't copy Accenture's scale, Microsoft trial setup, or GitHub product stack. Keep the structure of headline metrics first, a short problem and solution panel, then named quotes showing how the work changed.

More from GitHub

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.