There’s a category of product work that never gets its moment.
Not the big launches. The platform rebrand, the flagship feature, the announcement with a press release and a coordinated social push. Those get resources and attention. I’m talking about everything else. The quality-of-life improvements. The new integration. The capability that your best customers have been asking for and your team shipped quietly on a Tuesday.
At both Twilio and Kustomer, I watched this happen constantly. Strong product work would ship, and then nothing. No forum. No audience. No context. Customers would discover it weeks later, or never.
So I built a program to fix that.
The Quarterly Release Program
The concept is simple: once a quarter, you give the full body of product work a stage.
Not just a changelog. A branded webinar. Live demos. A look at what shipped, what it enables, and what’s coming next. A space for customers to see the roadmap take shape in real time.
At Twilio, this became part of how we maintained the developer relationship between major launches. At Kustomer, it became the rhythm that helped customers understand our AI platform. Not as isolated features, but as a coherent and evolving system.
The format has a few consistent elements:
- A branded quarterly webinar. Not a product training, not a generic customer update. An actual event with a name, a visual identity, and a clear value proposition for attendees. The webinar walks through the most significant releases of the quarter, shows them in context, and connects them to the broader product direction.
- Live demos. Not slide decks with screenshots. The product, on screen, doing the thing. This is the credibility-builder. It signals confidence and makes the capabilities real in a way that copy never will.
- Early access teasers. The end of the webinar always points forward. What’s in the pipeline? What can customers get access to before it’s generally available? This creates anticipation and gives your most engaged customers a reason to stay close.
- Accompanying content. Each quarterly event has a release blog. A written version of the webinar narrative, optimized for customers who couldn’t attend live and for the search traffic that comes months later. The blog and the event reinforce each other.
Why It Works
The Quarterly Release Program solves a specific problem: small releases are too small to launch individually but too important to ignore.
When you batch them into a quarterly cadence, a few things happen:
- You create a predictable moment that customers and internal teams can orient around. People start saving the date. They know it’s coming.
- You give smaller features the context they need to land. A new integration is interesting. Six new integrations, shown together as a pattern of investment in your ecosystem, is a story.
- You build compounding momentum. By the second quarter, you have returning attendees. By the fourth, you have a community that’s tracking your roadmap.
The program also does something important for internal alignment. When there’s a quarterly stage, product teams want their work on it. That creates healthy incentives. It makes the release process feel like it matters, because it does.
What It’s Not
It helps to be clear on scope:
- It’s not a substitute for major launches. Big announcements still get their own moment.
- It’s not a customer success webinar. The tone is forward-leaning and product-forward, not onboarding-focused.
- It’s not something you hand off entirely to demand gen. The best versions of this program have a PMM at the center, owning the narrative, working closely with product, and making sure the story holds together across the webinar, the demos, and the content.
If your product is shipping faster than your marketing can keep up with, and whose isn’t, a quarterly release program is worth building. It doesn’t require a big team. It requires a cadence and a commitment to giving your product work the audience it deserves.