MOVING FROM CONTENT FRICTION TO STRATEGIC SIGNAL: APPFOLIO

Appfolio
Appfolio

Your content team is good. They're producing — a podcast, benchmark reports, blog posts, video. The work is high quality. But somehow, with all that production, audience growth is flat. The podcast burns 30+ hours per episode and gets one publish. The team is sprinting toward the next deadline every week and can't figure out why none of it is adding up.

That was AppFolio. A strong team producing genuinely good content, with no system underneath any of it connecting the work to what actually mattered.

TL;DR

  • Client: AppFolio — property management software for residential properties and community associations
  • Situation: High-quality content with no operational system behind it. Podcast consuming 30+ hours per episode with flat audience growth. The content team was executing week-to-week without a framework to connect their work to business goals or ICP priorities.
  • The work: Content strategy advisory — content calendar framework, podcast production playbook, content atomization system, social best practices workshop, and copywriting for industry-specific thought leadership content
  • The shift: From producing more content to building the system that makes existing content work harder — and gives the team a foundation to build from instead of reinventing every time
  • The outcome: A content calendar mapped to ICP priorities and campaign goals, a repeatable podcast production process, a thought leadership library tied to business themes, and a team that could plan quarters instead of just surviving weeks

The Challenge

AppFolio's content team wasn't the problem. That's actually what made the situation harder to see clearly.

They were producing genuinely good work — a branded podcast (The Top Floor), benchmark reports, blog content, and video. The team cared about what they were making. But the operations underneath it were quietly burning everyone out, and the results reflected it.

Podcast episodes were taking 30+ hours each to produce. When an episode finally dropped, it got one publish and moved on; no clips, no blog recap, no newsletter pull, no systematic guest follow-up. Thirty-plus hours in. One asset out. Promotional materials weren't ready when episodes launched. Timelines were consistently missed. The team was sprinting every single week toward the next deadline without any room to step back and ask whether any of it was working.

Here's the hard thing about being a content team that's stretched thin: you don't have time to build the systems that would stop you from being stretched thin. You're just surviving. And when audience growth stays flat despite all that effort, the instinct is to do more (more episodes, more posts, more formats), which makes everything worse, not better.

There was also a deeper problem underneath the operational one. There was no shared framework connecting the content to anything. No clear line between what the podcast was covering and what the business was trying to achieve. No structure for which content was meant to reach which audiences at which stage of their journey. Different formats running in parallel without reinforcing each other. Content existing — but not accumulating into anything.

The team wasn't failing. They were building on sand.

  • Podcast production consuming 30+ hours per episode with flat audience growth
  • No follow-up process with guests after episodes launched
  • Promotional assets not ready when episodes dropped
  • Timelines consistently missed across content types
  • Each piece of content treated as one-and-done — not extended across channels
  • No clear connection between podcast topics and broader business goals or ICP challenges
  • High-effort formats (podcast, video) not being reused or built on
  • Team with no breathing room — just surviving week to week
  • No framework for pushing back on content requests that didn't serve the strategy


The Shift

What had to change wasn't what AppFolio was creating. It was how the team thought about what creation was for.

The belief going in: "We need to produce more content to drive awareness." The real problem was that they already had plenty of content, they just didn't have a system to make it work across channels, connect it to the topics their ICP actually cared about, or multiply the value of the high-effort formats they were already investing in.

One podcast episode isn't one piece of content. It's clips, a blog recap, a newsletter pull, social assets, a guest relationship, and a signal for the next quarter's themes, if you have the process to pull it apart and put it back together. Without that process, 30 hours becomes one asset. With it, 30 hours becomes the anchor for an entire month of connected content.

The same logic applied to the content calendar. There was no shortage of ideas. What was missing was the organizing logic, which themes connected to which ICP challenges, which formats served which stages, and how everything related to what AppFolio was actually trying to achieve. That's not a creative problem. It's an operational one.


The Work

We worked alongside the AppFolio content team as a thinking partner and advisor across the marketing team (not just the podcast, and not just a strategy handoff). The engagement covered content strategy, production workflows, thought leadership copywriting, team process, and the framework that gave the team the organizing logic to build their own content calendar.


Content Calendar Framework

Before the team could build a calendar that would actually hold, they needed a framework for what went in it and why, and the confidence that what they were building connected to something real.

We helped develop the organizing logic: which ICP-relevant content themes to anchor around (asset management, investor lifecycle, staffing challenges, resident experience, risk and fraud prevention), how the different content types (podcast, pillar pages, reports, customer stories, blog, downloads) served different stages and audiences, and how formats could reinforce each other instead of running in parallel. With that framework in place, the AppFolio team built their own content calendar from the inside — each content type mapped to campaign themes and business priorities, so they had a real decision-making tool, not just a publishing schedule.

  • Identified ICP-relevant content themes to anchor the calendar around
  • Mapped content types to audience segments and journey stages
  • Built the organizing logic connecting formats to campaign goals
  • Helped the team structure a calendar they could actually build from and maintain

Podcast Production Playbook

Built a tactical playbook for Season 3 of The Top Floor covering guest prep, story structure, audio and video workflow, post-production asset delivery, and guest follow-up timelines. The goal was a repeatable process the team could hand off, follow, and improve — not reinvent every episode.

  • Guest prep process and pre-episode briefing template
  • Story structure and interview framework by episode type
  • Audio and video workflow from recording to final delivery
  • Post-production asset delivery checklist — what gets created, by when
  • Guest follow-up timeline so relationships didn't fall through after publish


Content Atomization System

Created a framework for turning each episode into clips, blog recaps, newsletter content, and social assets, with clear timelines mapped to the editorial calendar. This turned the podcast from a single asset into a content engine. Thirty-plus hours in, a full channel's worth of connected content out.

  • Clip identification criteria — which moments to pull and why
  • Blog recap format and template
  • Newsletter pull structure
  • Social asset creation checklist by platform
  • Timelines for each asset relative to episode publish date


Social Best Practices Workshop

Ran a workshop with the content team on what actually works in B2B social, format decisions, timing, platform-specific content choices, and how to connect social publishing to the broader editorial calendar. Gave the team a shared foundation so content wasn't going out differently depending on who was handling it that week.


Thought Leadership Copywriting

Wrote industry-specific content anchored in themes AppFolio's audiences actually searched for and cared about (asset management, investor lifecycle, resident experience, risk and fraud prevention). White papers, ebooks, and blog content that gave AppFolio a consistent voice across formats while meeting different ICP segments at different stages of their journey.

The goal wasn't volume. It was a thought leadership library tied to the calendar themes, so new content added to what was already working instead of starting from scratch every time.


Ongoing Advisory Support

Throughout the engagement, we helped the team prioritize requests against business goals, evaluate new format ideas, identify what to cut, and develop the language for pushing back on content that didn't connect to what they were trying to achieve. When the instinct was to say yes to everything, we helped the team build the framework for deciding what was worth doing and what wasn't.


The Outcome 

The team stopped reinventing from scratch every week.

The content calendar gave everyone (content, demand gen, campaigns, social) a shared view of what was coming and why. Production timelines became predictable. Guest relationships improved because follow-up became systematic instead of falling through the cracks. The team could say no to content requests that didn't fit because the priorities were visible and agreed on, not floating in someone's head.

The podcast is still The Top Floor. But now each episode feeds a full channel's worth of connected content instead of going up once and going quiet. The thought leadership library reinforces the calendar themes, so new content adds to what's already working. Formats that used to run in parallel now connect to and support each other.

And the team can plan quarters instead of just surviving weeks.

  • Podcast production is repeatable and sustainable — no more reinventing the process or scrambling before every episode
  • Content atomization happens systematically, not when someone has bandwidth
  • The content calendar maps formats to ICP priorities and campaign goals — every piece has a role
  • Cross-functional teams (demand gen, campaigns, social) can plan around the calendar because timelines are predictable
  • The team has a framework for evaluating what's worth doing — and language for saying no to what isn't
  • Thought leadership library gives the team assets to draw from across channels instead of building from zero each time

The Takeaway

If your content team is producing quality work but the results aren't moving, the instinct is to produce more. That's almost always the wrong call. The problem usually isn't the content — it's the system underneath it. What's your process for turning a podcast episode into 10 pieces of content instead of one? How does what you're publishing this month connect to what you're trying to achieve next quarter? Who decides what gets cut when the team is stretched thin?

Those aren't creative questions. They're operational ones. And until they're answered, you're burning your best people on a treadmill that doesn't go anywhere.


Producing quality content that's not driving results? 

Let's build the system that makes your work actually work for you.


Subscribe to the
Build Better Customers Newsletter

Semi-regular updates filled with no-frills problem-solving advice & recommendations.

Unsubscribe anytime.