Talk about your next project
Composio case study

The lesson

Make the product's role a named section of its own, so the reader sees exactly which part of the customer's system the brand carries.

The move

The page opens with the headline 'How Pelago Health gave every employee an AI agent without sharing a single password,' an attribution line for the Senior Director of Engineering, and a large '160' card for Composio-powered agents. A strip below adds '1' personal agent per employee, from day one, and '0' passwords shared with the platform. A one-paragraph summary leads into three labeled sections, 'Agents for every employee, inside a regulated boundary,' 'Archie, born inside the firewall' and 'The credential broker behind every agent.' A row of three quotes from the same executive follows, then 'See what other teams built with Composio' and a closing call to action.

Why it works

  • Our readThe headline promises a specific outcome, and the '0' passwords tile proves it before the story begins.
  • Our readSeparating what the customer built from where Composio fits shows that Pelago built Archie and Composio supplies the credential layer, which reads as honest credit.
  • Our readThe problem section lists the constraints of a regulated healthcare setting, so the security reader sees their own requirements before the solution.

What not to copy

Don't copy Pelago's healthcare context, the Archie name, the invoice reconciliation anecdote or the zero-passwords hook. Keep the stat-tile hero, the short summary, the problem, customer build and brand-role sections in that order, and a quote row that restates each point.

More from Composio

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.