Talk about your next project
Composio case study

The lesson

When your headline number is an estimate, label it as one and show the math behind it in the story so the reader can check it.

The move

Under a breadcrumb, the Spinnable logo and a 'CUSTOMER STORY' label, the headline sits above a two-stat strip: '~100' integrations powering AI employee workflows and '700' engineering days of integration work avoided, marked 'EST.' An intro paragraph explains that an AI employee is only as useful as the tools it can reach. Then come three two-column sections, each with a small label and a plain heading on the left and prose on the right: 'THE PROBLEM' (AI employees need to work where the business works), 'THE BOTTLENECK' (Every integration was a week of work for one person) and 'WHAT CHANGED' (Connections in hours, shipped by more of the team). The page closes with five more customer story cards and a 'Power your agents with 1,000+ apps, in minutes.' call to action.

Why it works

  • Our readThe bottleneck section works out the 700 figure from at least a week per integration across around 100 integrations, so the estimate in the stat strip reads as a calculation rather than a claim.
  • Our readSplitting the old pain into a problem and a separate bottleneck lets the story name two costs: build time, and dependence on one specialist.
  • Our readSection headings written as plain statements let a skimmer get the whole before and after from the left column alone.

What not to copy

Don't copy Spinnable's AI employee framing, its hospitality and go-to-market role examples, or the week-per-integration arithmetic unless your customer gave you those inputs. Keep the two-stat strip, the labeled problem, bottleneck and change sections, and the habit of showing how an estimated number was reached.

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.