AviaryAI: Case Study Strategy

Overview

During the 2026-02-04 weekly sync, the team aligned on a format and approach for AviaryAI's case studies — both as web assets and sales collateral. A specific challenge was raised around the Mortgage Forward case study, which requires a non-data-driven approach due to the client being a technology company rather than a financial institution.

Case Study Format

The agreed format is a dedicated web page per case study, with a downloadable PDF available via a prominent button on the page. This serves two audiences simultaneously:

Organic / web visitors — the page is indexable, linkable, and contributes to SEO authority
Sales team — Aaron and Blessen can share the PDF directly in outreach or on calls without needing a separate asset workflow

"My advice would be to create a page that people can traffic, and then there's a button that says download PDF, and if you want them to download it." — Mark Hope

This avoids maintaining two separate formats (a standalone PDF and a web page) and keeps content in one canonical location.

Recommended Page Structure

Hero / client overview
Challenge / context
Solution (AviaryAI's role)
Outcomes / results (quantitative where available)
"Download PDF" CTA for sales use

Mortgage Forward: Tech-to-Tech Positioning

The Mortgage Forward case study presents a specific challenge: they are a technology company, not a financial institution, so the standard data-driven outcomes format (e.g., call deflection rates, cost savings) does not apply in the same way.

"Mortgage Forward one, they're not going to have data. They're a technology company, so they're kind of similar to us. So we'll need some way to kind of show them without doing that." — Justin Dwyer

Approach for Tech-to-Tech Case Studies

When the customer is a technology company rather than an end-user institution, the case study should shift emphasis from quantitative ROI metrics toward:

Integration story — how AviaryAI fit into an existing tech stack or product
Partnership narrative — the collaborative nature of the engagement
Capability demonstration — what became possible that wasn't before
Qualitative outcomes — speed to deploy, flexibility, developer experience, or product differentiation

This framing is also more appropriate when the customer may not yet have longitudinal data to share.

Workflow

Justin reviews and comments on Figma drafts for each case study
Sebastian publishes V1 as a live page on the AviaryAI site, including a PDF download button
Aaron and Blessen use the PDF in active sales outreach

Action Items (as of 2026-02-04)

[ ] Justin Dwyer — Add comments and feedback to case study Figma drafts
[ ] Sebastian Gant — Publish V1 case study page(s) with PDF download button once Justin's feedback is incorporated

^[1]
^[2]
^[3]