---
title: AviaryAI Case Studies & Verticals Content
type: article
created: '2026-03-11'
updated: '2026-03-11'
source_docs:
- raw/2026-03-11-aviaryai-weekly-call-129176325.md
tags:
- content
- seo
- webflow
- case-studies
- client:aviaryai
layer: 2
client_source: null
industry_context: null
transferable: true
---

# AviaryAI Case Studies & Verticals Content

## Overview

As of the March 11, 2026 weekly sync, AviaryAI's content pipeline has reached two significant milestones: three finalized case studies are ready to publish, and V2 copy for the verticals pages is complete. The next planned phase is gated content (playbooks, reports) designed to serve double duty as SEO assets and conversion events for paid campaigns.

See also: [[clients/aviaryai/_index]] | [[knowledge/google-ads/conversion-tracking-strategy]] | [[knowledge/seo/technical-seo-h1-structure]]

---

## Case Studies

### Status

Three case studies have been finalized and are ready to be added to the Webflow archive page. They currently exist as standalone sales collateral. Once published to the archive, updated URLs should be shared with the AviaryAI sales team (Justin Dwyer's request).

### Webflow Archive Implementation Notes

Adding the case studies requires modifying the Webflow archive **template page**, not just adding data entries. Key constraints:

- The developer should adjust the template as needed but **must not break existing published case study pages**.
- The archive uses a template-plus-data model; new entries may need to be handled as static vs. dynamic depending on design differences.
- Keep the archive template relatively bare-bones to minimize ongoing maintenance burden.

**Owner:** Sebastian Gant  
**Dependency:** Justin Dwyer to review new member onboarding design and provide comments before Friday.

---

## Verticals Pages (V2 Copy)

### What Changed

Sebastian completed a second-pass rewrite of all verticals page copy. The revision:

- **Condensed** longer sections for readability.
- **Retained keyword density** intentionally — because AviaryAI's domain rating is still building, content volume partially compensates for lower domain authority (ranking ≈ content × domain rating).
- **Preserved use-case keywords** throughout to support organic search targeting.

### Review Process

The V2 copy lives in the shared Google Doc (same document, previous version wiped). Justin Dwyer is asked to add comments directly in the doc.

**Owner:** Sebastian Gant (copy) / Justin Dwyer (review)

---

## Gated Content — Planned Next Phase

### Rationale

The team identified a gap: Google Ads currently has only one conversion action (Schedule a Demo click), which is insufficient to switch bidding from "maximize clicks" to "maximize conversions." Gated content assets solve this by creating additional trackable conversion events while also generating leads organically.

### Proposed Asset Types

| Asset | Conversion Event Type |
|---|---|
| Industry playbooks | Gated download (form fill) |
| ROI/impact reports (e.g., dormant account reactivation) | Gated download |
| Calculators | Interactive tool engagement |
| Demo audio/video | Video play event |

### Strategic Goal

These assets are intended to work across channels simultaneously:
- **Paid search:** Provide 5–6 conversion actions needed to unlock "maximize conversions" bidding (see [[knowledge/google-ads/conversion-tracking-strategy]])
- **Organic/SEO:** Blog posts and landing pages targeting verticals keywords drive traffic to gated assets
- **Email/ABM:** Assets serve as nurture touchpoints and re-engagement hooks

Justin Dwyer noted the goal is to have all channels — ABM, email, Google Ads, organic — feeding into the same conversion infrastructure so attribution and performance insight become actionable.

---

## Competitor Context: Retail AI

Retail AI appeared in Google Ads search term reports. Key distinction from AviaryAI:

- **Retail AI:** Broad horizontal play, targets technical users (developers), large content footprint.
- **AviaryAI:** Vertical focus (financial services / credit unions), targets business decision-makers (CEOs, ops leaders).

Implication for content strategy: avoid mirroring Retail AI's technical/developer-oriented topics. Blog posts and case studies should speak to business outcomes, not implementation details.

---

## Action Items

- [ ] Add 3 finalized case studies to Webflow archive page; share new URLs with Justin Dwyer (@Sebastian Gant)
- [ ] Review verticals V2 copy in shared doc and add comments (@Justin Dwyer)
- [ ] Review new member onboarding case study design; send comments to Sebastian by Friday (@Justin Dwyer)
- [ ] Draft blog posts targeting verticals keywords; share with Justin (@Sebastian Gant)
- [ ] Send demo audio to Mark, Sebastian, and Webflow developer to enable video/audio conversion events (@Justin Dwyer)
- [ ] Plan and scope gated content assets (playbooks, reports) as next content phase (@Sebastian Gant / @Mark Hope)