Talk about your next project
Recall AI case study

The lesson

Tell the challenge as the options the customer tried and rejected, then show your product meeting the criteria they set for the last option.

The move

The hero pairs a video still with a play button and the title "Recall + Allego Case Study", followed by a "Quick Specs" card listing company name, industry, headcount, headquarters and website, plus one-line Problem and Solution statements. Under "Challenge: Enabling online meeting recordings quickly & easily" the story walks through numbered options, "Use each meeting platform's APIs", "Build their own meeting bot" and "Find an external integration that could support online meetings", and ends with three criteria: Coverage, Simple integration and Partnership. "Solution: A comprehensive, easy-to-use third-party API" reuses those three criteria as subheads, with quotes from Phil Costa, SVP of Product Development, under Simple integration and Partnership. A short "Result" section with a closing quote leads into a demo link and a footer CTA band.

Why it works

  • Our readWalking through native APIs and an in-house bot before the purchase answers the build-versus-buy objection a technical buyer already has.
  • Our readReusing Coverage, Simple integration and Partnership as the Solution subheads lets a reader check each requirement against what was delivered.
  • Our readThe Quick Specs card with Problem and Solution lines gives a skimmer the whole story and a fit check before the long text starts.

What not to copy

Don't copy Allego's meeting-platform names, the telephony history or Phil Costa's quotes about integrations being a tax. Keep the specs card with one-line problem and solution, the numbered options the customer weighed, the buying criteria repeated as solution subheads, and a named quote inside each part.

More from Recall AI

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.