Long-form resources for two enterprise audiences

PagerDuty was our first AI content systems client. It needed in-depth resources for technical leaders and for customer experience leaders, with limited bandwidth and partial brand guidelines to start from.

At a glance

Client
PagerDuty, incident management
Work
Two ebooks with supporting pieces, and an AI content workflow
Engagement
Early 2025, two months
System
Wordful (early version)

Before

The turning point

Give each audience its own argument. Instead of one general ebook, technical teams got the case for reliability, and customer experience leaders got the link between IT operations and their customers. Brand guidelines and customer profiles went into the AI workflow itself, so drafts started on brand, with editors reviewing at each stage.

What we built

Diagram of the AI workflow behind the PagerDuty ebooks: inputs such as working titles, a persona deck, draft voice guidelines, existing assets and call transcripts are prepared into a library, turned into frameworks, drafted, reviewed and iterated, then published as an ebook.
The workflow behind both ebooks.

After

Read the work

Read the full story

The problem

PagerDuty serves enterprises that run critical digital operations. It needed long-form resources for two different buyers: technical leaders responsible for reliability, and customer experience leaders who feel the impact when systems fail. Teams worked in isolation, brand guidelines were still taking shape, and there was little in-house bandwidth for this kind of content.

Two audiences, two arguments

Rather than one ebook trying to serve both, each audience got its own case. One ebook made reliability a competitive advantage for technical teams. The other connected IT operations to the customer experience, with practical guidance for handling incidents.

Brand in the workflow

PagerDuty's style and messaging guidelines and its customer profiles went directly into the AI workflow. Frameworks were mapped from existing assets, and outlines were built for each segment, so drafts started from what PagerDuty already knew and how it already sounded.

Editors at every stage

The workflow kept people at the points that matter: frameworks, drafts, and revisions were reviewed and refined before anything shipped.

What PagerDuty keeps

  • Two ebooks and their supporting pieces
  • A reusable workflow and framework for future long-form content

If this sounds like you

Need long-form content for more than one audience? Tell us what you need. No prep needed.

Send a message

Prefer to talk? Book a free scoping call.

Tell us what you need

We'll only use your email to reply. Privacy policy