On March 24, 2026, Miro announced it was acquiring Reforge, including the Reforge team, the learning platform, and the company’s AI-powered product development tools. Reforge CEO Brian Balfour will join Miro as Chief Growth Officer. Reforge COO Tom Willerer will join as Chief Strategy Officer. The deal is subject to customary closing conditions.
The leadership moves got most of the headline attention. The detail that matters more for product teams sat further down the announcement: Reforge Insights, Reforge Research, and Reforge Build are being integrated into Miro’s Product Acceleration offering. Reforge Learning will continue to operate independently at Reforge.com.
If your team uses Reforge Insights as part of how product decisions actually get made, this article is for you.
Switch to Bagel AI
What Reforge Insights Does Today
Reforge Insights aggregates customer feedback from across a team’s tools, applies AI to surface themes, and helps product teams move from raw feedback toward product decisions. It sits on the qualitative side of the work: pulling signal out of conversations, surveys, support tickets, and reviews.
In the months before the acquisition, Reforge had been expanding Insights. Context Engine let teams upload roadmaps and strategy documents to personalize how feedback got analyzed. AI Long Form Surveys added automated follow-up questions and cohort targeting. Competitor Analysis pulled in public feedback from review sites and forums. The product was being actively invested in.
Customers named in Miro’s acquisition press release include Workday, Xero, SAP, Mastercard, and Netflix.
What Actually Changes
Miro’s stated plan splits the Reforge portfolio. Reforge Learning stays independent. Reforge Insights, Research, and Build move into Miro’s platform as part of the Product Acceleration solution. Both companies confirmed this split in their respective blog posts.
A few things remain unclear.
The integration timeline. Acquisitions that involve folding standalone products into a larger platform typically run 12 to 24 months from announcement to full integration. Brand transitions, billing migrations, SSO consolidation, and API rewrites operate on a calendar that resists compression.
Pricing and packaging. Miro hasn’t publicly stated whether Reforge Insights will continue to be sold standalone, get bundled into Miro plans, or shift to a new pricing tier at renewal.
The product roadmap. Brian Balfour and Tom Willerer have moved from running Reforge to executive roles at Miro with broader company-wide remits. The Reforge product team now sits inside a larger organization with different priorities. That changes how roadmap decisions get made.
The integration model. Miro has framed Reforge Insights as part of “Product Acceleration.” What that looks like inside the Miro interface is something the combined team will design over the coming months.
What Stays the Same in the Near Term
Both companies have said customers don’t need to take any action right now. Reforge’s blog post tells current Insights customers that products will continue to be supported and that Reforge Learning will continue on Reforge.com. The Spring Learning Cohort is proceeding as planned.
If you have an active Reforge Insights workspace, it keeps working. Your logins work. Your Slack integration works. Your data sits where you left it.
The relevant question isn’t about tomorrow. It’s about what your team’s Product Velocity stack should look like 12 months from now.
The Pattern Worth Noticing
This is the third major acquisition in the product tooling space in roughly 18 months. Pendo acquired Chisel Labs earlier in 2026. Several smaller AI-native product tools got absorbed into larger collaboration suites before that. The consolidation tends to follow a shape: focused product gets bought by larger horizontal platform, leadership transitions into broader roles, and the standalone product enters a multi-quarter integration phase.
Teams using these tools generally take one of three paths. They wait, see what the integrated experience looks like, and accept whatever bundle emerges. They move to alternatives during the transition window because the timing forces a procurement conversation anyway. Or they treat the moment as a forcing function to reassess what their Product Velocity stack actually needs to do.
Each path has tradeoffs. “Wait and see” is itself a choice with real costs, especially if the tool sits at the center of how your team works.
What Product Teams Should Actually Evaluate
Reforge Insights’ value proposition was synthesis. Pull qualitative feedback from many sources, find patterns, organize them so PMs can use them.
For some teams, that’s the right shape of tool. For B2B SaaS teams where revenue and product decisions are tightly linked, synthesis tends to be where the work begins. Knowing what customers are saying is one question. Knowing which of those things to act on, which features are blocking deals, which requests come from accounts that drive your ARR, and what dev-ready output gets handed to engineering at the end of the process is a different one. We’ve written more about why summary isn’t decision and why context, not speed, is the real competitive advantage for teams that want to dig deeper.
For teams reassessing their Product Velocity stack right now, the useful questions go beyond “what replaces Reforge Insights”:
- Does our current tool connect customer feedback to revenue context, or does it stop at themes?
- When a feature request shows up in Zendesk, can we see whether it’s coming from a $50K account or a $500K account?
- Does the output reach Jira and Salesforce automatically, or does someone manually copy it over?
- Are Sales, CS, and Product working from the same data, or different views of it?
- How long does it take from “customer mentioned this on a Gong call” to “engineering has a prioritized, scoped ticket”?
These questions matter whether your team stays with Reforge Insights through the Miro transition or evaluates alternatives. They’re the questions Reforge Insights was built to partially answer. They’re also the questions that tend to get harder to solve when a focused product becomes a feature inside a 100M-user horizontal platform.
If you want to put a number on the cost of the manual work involved in answering these questions today, the Bagel triage calculator is a quick way to see what your team is spending on feedback triage every week.
Where Bagel AI Fits
Bagel AI is an AI-Native Product Velocity Platform built for product & engineering teams. The platform connects GTM signals from Gong, Salesforce, Zendesk, Jira, and Slack into product decisions, and produces dev-ready artifacts at the end of the process. Bagel acts as the Product Decision Partner for the PM: every signal connected to context, every decision backed by evidence, every output usable by engineering.
Bagel covers some of what Reforge Insights does, and extends further. Where Reforge Insights focused on synthesizing qualitative feedback, Bagel ties every signal to business context: which accounts are affected, how much revenue is at stake, where in the customer lifecycle the request is coming from. Each customer gets a dedicated AI model trained on their own GTM and product data, rather than a general-purpose model applied across the board.
Output flows into the tools product and GTM teams already use. PMs see ticket-level context in Jira. AEs see deal-level context in Salesforce. CS sees account-level context in Slack. The team doesn’t change tools. The work just connects.
Bagel customers include Hivebrite, Zencity, HoneyBook, Tipalti, and Gong. For a direct side-by-side, the Bagel vs Reforge Insights comparison covers the differences in detail. Teams evaluating other tools in the same conversation often look at the Productboard alternative, Pendo Listen alternative, and Enterpret alternative pages as well.
What to Do This Quarter
Three suggestions for teams currently using Reforge Insights.
Get on a call with your Reforge account contact and ask direct questions. What’s the integration timeline? Will pricing change at renewal? What’s the migration path if Miro Product Acceleration turns out to be a different shape of tool than what you’re using today? You’re entitled to answers, and the answers you get will tell you a lot.
Audit how Reforge Insights shows up in your actual workflow. If it’s the system of record for product feedback, the cost of switching is high, and the cost of staying through ambiguity is also high. If it’s one of several tools that occasionally surface useful patterns, the calculation looks different.
Use this moment to revisit the underlying question. Less “what tool replaces Reforge Insights” and more “what does our Product Velocity stack need to do that it isn’t doing today?” The acquisition window tends to be a better time to ask that question than a normal renewal cycle, because everyone in the room knows the ground is shifting. The PM role itself is changing faster than most tool stacks have kept up with, and that’s worth factoring in.
A Final Note
This article isn’t a takedown of the Reforge deal. Brian Balfour built one of the most respected communities in product over the past decade. Miro is a serious company with a serious AI strategy. The combined entity may turn into something product teams genuinely want to use. Several quarters from now, Miro Product Acceleration could be a category-defining offering.
The point isn’t to predict the outcome. The point is to be honest that the transition will take time, that the tool’s shape will change, and that teams using Reforge Insights today have a real decision in front of them.
If you’d like to see what a Product Decision Partner built specifically for B2B SaaS revenue context looks like, book a demo with Bagel AI.
