How AIQ Built an AI-Powered Product Knowledge Engine on Top of LaunchNotes
AIQ powers modern customer loyalty and engagement for brands and retailers. Its platform takes fragmented customer data and turns it into personalized experiences across every touchpoint — marketing, loyalty programs, mobile apps, digital shopping, owned ecommerce, and a growing retail ad network. It's a platform built to scale. The product communications process, however, hadn't kept up.
Where They Are Now: LaunchNotes as AI Infrastructure
Most companies use LaunchNotes to communicate product updates. AIQ uses it as connective tissue.
AIQ has integrated the LaunchNotes MCP (Model Context Protocol) server into their internal AI tooling, where it acts as the connective tissue on both ends — the write layer that drafts release notes into LaunchNotes, and the read layer that pulls them back out to answer questions.
Here's how it works in practice. The LaunchNotes MCP server is the foundation — a single integration that makes every release note instantly retrievable by AI. On top of that, AIQ has configured custom Claude skills that orchestrate the drafting process: pulling relevant details from Intercom, ClickUp, Slack, and GitHub, holding AIQ's brand tone, and writing a complete draft announcement directly into LaunchNotes. What used to take 3–4 hours now takes under 45 minutes, including editing and adding screenshots. No release gets missed, no matter how small.
The same MCP connection powers the consumption side too. AIQ has built an internal AI bot that, when asked about any product capability, searches LaunchNotes to check whether the topic has been covered in a release announcement, then returns a summary of the feature along with a direct link to the updates page. They're extending this to their customers next.
This is the flywheel that makes it compound: every release note, properly categorized at publish time, becomes a structured fact an AI can retrieve on demand. Good categorization used to pay off only once — at the moment of publication. Now it keeps paying off every time someone asks a question.
The difference is night and day. With the addition of the LaunchNotes MCP Server, it has allowed us to make customizable skills that work for our organization. This alone has saved so much time and money. Kevin Bowman, Senior Product Manager, AIQ
Before: One Person, Two Product Lines, No Consistent Process
Kevin Bowman has been in this story from the beginning. He joined Dispense — acquired by AIQ — in 2021, starting in Customer Success before moving into product management. When AIQ acquired Dispense, Kevin came with it, and has been a Senior PM at AIQ ever since.
That continuity matters, because Kevin didn't inherit the before state. He lived it.
Post-acquisition, AIQ was managing product communications across multiple product lines with no consistent approach. Dispense had been manually maintaining distribution groups inside an email provider to send release notes to clients. The broader AIQ platform housed its changelog in a help documentation page that customers were expected to find on their own. Neither approach scaled. Neither really worked.
CS and Sales felt perpetually underprepared. Customers weren't adopting new features because they didn't know they existed. Cross-functional teams were out of sync. And there was no single place — internal or external — where anyone could go to see what had changed.
The in-app announcements AIQ had tried for major releases helped at the margins, but they were marketing-focused rather than changelog-focused, didn't cover smaller releases or bug fixes, and required Engineering involvement every time. It wasn't a system. It was a workaround.
Lack of communication and clear transparency into our releases left everyone frustrated. CS and Sales felt unprepared, customers were frustrated and felt like they weren't seeing progress.
Kevin Bowman, Senior Product Manager, AIQ
The Breaking Point
The situation came to a head when a large multi-site operator (MSO) — one of AIQ's most important customer segments — reached the end of its patience.
This wasn't a minor complaint. The MSO needed standard operating procedures in place across dozens of retail locations before any product update went live. When functionality changed unexpectedly, it wasn't just an inconvenience — it was an operational problem that cascaded across their entire network. After a direct call with their leadership team, the urgency was undeniable.
AIQ needed a solution, and it needed one fast.
After a call with their leadership team to listen to their frustrations, we knew we needed to act fast. We quickly signed with LaunchNotes and were able to get up and running before our next release.Kevin Bowman, Senior Product Manager, AIQ
They were up and running within days — custom header matched to AIQ's brand, previous release notes migrated and backdated from the old help documentation page. That MSO stayed, continued to renew, and added new locations each time they expanded, eventually growing across 5 states.
After: From Single-Digit Views to 50%+ Open Rates
The results were immediate and measurable.
The old help documentation changelog was receiving single-digit views per week. The first announcements sent through LaunchNotes hit a 40%+ open rate. As the team refined their process — segmenting release notes by category and product — that number climbed further. Today, AIQ maintains a greater than 50% open rate across thousands of customers.
We went from single digit views per week on our help documentation to email announcements being sent to thousands of customers while maintaining an over 50% open rate.
Kevin Bowman, Senior Product Manager, AIQ
Feature adoption followed. Store-level implementation of new features, which used to take weeks or more, now happens within days of release. Customer questions about what has shipped have dropped sharply — in a recent two-month window, AIQ's CS team was asked about a shipped feature exactly once.
The impact spread across every team. CS and Support could reference release notes directly in customer conversations. Sales could show prospects a living record of shipping velocity. Marketing used announcements as a starting point for features that warranted a fuller GTM push. And senior leadership found an unexpected use case: LaunchNotes became a tool for investor conversations.
Senior leadership once called it a game changer for investor talks. It's an easy way to show progress.
Kevin Bowman, Senior Product Manager, AIQ
By the Numbers
What Kevin Would Tell a Peer
Kevin's framing is simple: if your product communications aren't scaling with your customer base, you have a scalability problem. And scalability problems don't solve themselves.
Using LaunchNotes feels purposeful. It's always easier to spend the time on something when you know it will be seen.
Kevin Bowman, Senior Product Manager, AIQ
Where They Are Now: LaunchNotes as AI Infrastructure
Most companies use LaunchNotes to communicate product updates. AIQ uses it as connective tissue.
AIQ has integrated the LaunchNotes MCP (Model Context Protocol) server into their internal AI tooling, where it acts as the connective tissue on both ends — the write layer that drafts release notes into LaunchNotes, and the read layer that pulls them back out to answer questions.
Here's how it works in practice. The LaunchNotes MCP server is the foundation — a single integration that makes every release note instantly retrievable by AI. On top of that, AIQ has configured custom Claude skills that orchestrate the drafting process: pulling relevant details from Intercom, ClickUp, Slack, and GitHub, holding AIQ's brand tone, and writing a complete draft announcement directly into LaunchNotes. What used to take 3–4 hours now takes under 45 minutes, including editing and adding screenshots. No release gets missed, no matter how small.
The same MCP connection powers the consumption side too. AIQ has built an internal AI bot that, when asked about any product capability, searches LaunchNotes to check whether the topic has been covered in a release announcement, then returns a summary of the feature along with a direct link to the updates page. They're extending this to their customers next.
This is the flywheel that makes it compound: every release note, properly categorized at publish time, becomes a structured fact an AI can retrieve on demand. Good categorization used to pay off only once — at the moment of publication. Now it keeps paying off every time someone asks a question.
The difference is night and day. With the addition of the LaunchNotes MCP Server, it has allowed us to make customizable skills that work for our organization. This alone has saved so much time and money. Kevin Bowman, Senior Product Manager, AIQ
Before: One Person, Two Product Lines, No Consistent Process
Kevin Bowman has been in this story from the beginning. He joined Dispense — acquired by AIQ — in 2021, starting in Customer Success before moving into product management. When AIQ acquired Dispense, Kevin came with it, and has been a Senior PM at AIQ ever since.
That continuity matters, because Kevin didn't inherit the before state. He lived it.
Post-acquisition, AIQ was managing product communications across multiple product lines with no consistent approach. Dispense had been manually maintaining distribution groups inside an email provider to send release notes to clients. The broader AIQ platform housed its changelog in a help documentation page that customers were expected to find on their own. Neither approach scaled. Neither really worked.
CS and Sales felt perpetually underprepared. Customers weren't adopting new features because they didn't know they existed. Cross-functional teams were out of sync. And there was no single place — internal or external — where anyone could go to see what had changed.
The in-app announcements AIQ had tried for major releases helped at the margins, but they were marketing-focused rather than changelog-focused, didn't cover smaller releases or bug fixes, and required Engineering involvement every time. It wasn't a system. It was a workaround.
Lack of communication and clear transparency into our releases left everyone frustrated. CS and Sales felt unprepared, customers were frustrated and felt like they weren't seeing progress.
Kevin Bowman, Senior Product Manager, AIQ
The Breaking Point
The situation came to a head when a large multi-site operator (MSO) — one of AIQ's most important customer segments — reached the end of its patience.
This wasn't a minor complaint. The MSO needed standard operating procedures in place across dozens of retail locations before any product update went live. When functionality changed unexpectedly, it wasn't just an inconvenience — it was an operational problem that cascaded across their entire network. After a direct call with their leadership team, the urgency was undeniable.
AIQ needed a solution, and it needed one fast.
After a call with their leadership team to listen to their frustrations, we knew we needed to act fast. We quickly signed with LaunchNotes and were able to get up and running before our next release.Kevin Bowman, Senior Product Manager, AIQ
They were up and running within days — custom header matched to AIQ's brand, previous release notes migrated and backdated from the old help documentation page. That MSO stayed, continued to renew, and added new locations each time they expanded, eventually growing across 5 states.
After: From Single-Digit Views to 50%+ Open Rates
The results were immediate and measurable.
The old help documentation changelog was receiving single-digit views per week. The first announcements sent through LaunchNotes hit a 40%+ open rate. As the team refined their process — segmenting release notes by category and product — that number climbed further. Today, AIQ maintains a greater than 50% open rate across thousands of customers.
We went from single digit views per week on our help documentation to email announcements being sent to thousands of customers while maintaining an over 50% open rate.
Kevin Bowman, Senior Product Manager, AIQ
Feature adoption followed. Store-level implementation of new features, which used to take weeks or more, now happens within days of release. Customer questions about what has shipped have dropped sharply — in a recent two-month window, AIQ's CS team was asked about a shipped feature exactly once.
The impact spread across every team. CS and Support could reference release notes directly in customer conversations. Sales could show prospects a living record of shipping velocity. Marketing used announcements as a starting point for features that warranted a fuller GTM push. And senior leadership found an unexpected use case: LaunchNotes became a tool for investor conversations.
Senior leadership once called it a game changer for investor talks. It's an easy way to show progress.
Kevin Bowman, Senior Product Manager, AIQ
By the Numbers
What Kevin Would Tell a Peer
Kevin's framing is simple: if your product communications aren't scaling with your customer base, you have a scalability problem. And scalability problems don't solve themselves.
Using LaunchNotes feels purposeful. It's always easier to spend the time on something when you know it will be seen.
Kevin Bowman, Senior Product Manager, AIQ
