Reforge’s Brian Balfour on Second Acts, a Foundational Law of Retention, AI-Native Product Teams and More
5 MIN READ
|
Updated on December 19, 2025
TL;DR
In part two of this Second Acts episode, Reforge CEO Brian Balfour joins Chargebee’s Krish Subramanian to explore why SaaS second acts can be deliberate or disruption-driven, why retention potential is ultimately limited by the natural frequency of a use case, and how small teams ship faster than bloated orgs.
Drawing on lessons from HubSpot and Reforge, Balfour shares:
- HubSpot’s deliberate CRM bet vs. Reforge’s disruption-driven pivot
- Why even strong product–market fit can be upended by market headwinds, especially when the use case is episodic
- Retention as the category decider and why it depends on workflow frequency
- How small, hybrid teams outpace bloated orgs
- What it really takes to incubate a startup inside a larger company
- Why capital discipline matters as much as product strategy
Deliberate vs. forced second acts: HubSpot vs. Reforge
Balfour contrasted two very different second acts:
- HubSpot: a deliberate second act. Entering CRM was not obvious at the time, but founders Dharmesh Shah and Brian Halligan looked ahead to IPO, set a future goal of 50% YoY growth, and incubated the CRM effort as a separate team with effectively its own board cadence.
- Reforge: a second act made inevitable by disruption. After years of course business growth ($10M bootstrapped, then $30M within 18 months of raising capital), the 2022 downturn devastated edtech, and AI disruption raised existential questions. Reforge shifted into AI-native SaaS products for its core audience of product and growth teams.
Product–market fit doesn’t guarantee lasting growth
Balfour didn’t set out to build an education company. He was obsessed with growth and frontier practices. But the courses found instant traction:
- Bootstrapped to $10M in four years
- After venture funding, it grew to $30M in 18 months
“It was the most instant product–market fit I’d ever felt in my life.”
Still, the use case was episodic. Customers loved Reforge, but didn’t need it all the time:
“Our biggest churn response has always been: I love Reforge, I just don’t need it right now.”
Lesson: Even strong product–market fit can be undermined if the use case itself is episodic.
SaaS retention depends on frequency, not features
Retention, Balfour insists, is the category decider:
“Retention makes or breaks companies. The one that always emerges as the winner is the one with the highest retention and engagement.”
But 80% of retention potential is baked into the natural frequency of the workflow. You cannot make quarterly book-closing a daily event. Instead, companies win by expanding into adjacent, higher-frequency use cases.
He cites Calm: retention spiked when it added sleep (a nightly use case) alongside meditation (occasional).
At Reforge, courses remained episodic, so the team stopped trying to change natural behavior and instead focused on nailing the experience when customers returned.
From Silicon Valley to real-world enterprise workflows: adapting frontier insights
Balfour cautioned against over-indexing on Silicon Valley customers.
“The supermajority of the technology market is now outside of Silicon Valley.”
Healthcare, fintech, and retail teams have different workflows, legacy systems, and decision patterns. Many AI deployments fail because vendors don’t account for this messiness. Reforge leverages frontier insights from its expert network but adapts them for messier enterprise contexts. Krish summarized this as “borrowing from the frontier, bridging to the enterprise.”
How small SaaS teams ship faster than bloated orgs
Balfour discussed how product development has ballooned:
- Once: the triad of PM, designer, and an engineer.
- Now: 8–10 specialists, with 3–5 tools per step.
The result is handoffs, context loss, and slow cycles. As Balfour noted, it isn’t just humans who lose context — AI systems do too. Each handoff between human and AI fragments information further, which Reforge is working to solve with its end-to-end product suite
“The best products are built by small teams iterating very fast, tightly with the customer.”
Reforge organizes into squads of 4–7 people with hybrid skills. Across ~40 people and 4–5 products, this structure enables rapid shipping while staying close to customers.
Leadership lessons from HubSpot: building a startup within a startup
HubSpot’s CRM effort was run as a startup within the startup:
- Physically separated, with its own rituals
- Presented to a board of Dharmesh, Halligan, and then-COO J.D. Sherman every 1–2 months
- Received “funding”, like a venture-backed company
“There is pain in absorbing it back into the core part of the company. But the alternative is that it never succeeds.”
Balfour’s leadership principles:
- Constraints are good
- You cannot skip steps; throwing 30 people at a new product from day one does not work
- Resources can accelerate the steps; HubSpot’s customer base helped the team learn faster
“The organizational habits that work for 400 people don’t create success conditions for a 5-person team.”
Capital discipline: venture-backed ≠ venture-scale
Balfour closed with reflections on funding strategy: venture-backed ≠ venture-scale; non-venture-backed ≠ non-scale.
- Great businesses can be bootstrapped or VC-backed; what matters is matching funding to signals.
- The real danger: raising venture without venture signals, which leads to down rounds and fire sales.
What’s next: retention, teams, and capital in SaaS second acts
Balfour’s core message: SaaS second acts succeed when leaders treat retention, team design, and capital choices as deliberate, disciplined bets.
Listen to the full episode below. Missed the part 1 recap? Catch up on Balfour’s take on SaaS monetization, including why old models break and the three tests every pricing model must pass.
Even more insights
Discover lessons from the field on using pricing to drive adoption, build sticky habits, and create an unfair advantage in AI markets.
Get the Pricing for AI Distribution Playbook →
