The Revenue Formula

The episode delivers solid, experience-based insights on sales planning pitfalls that most practitioners would recognize and find actionable. The core claims - plans are often built for external audiences over internal execution, compounding tweaks mask risk, and hiring timing cascades into annual failure - are non-obvious enough to reward a good operator. However, the execution is conversational rather than densely packed; significant stretches are devoted to relationship anecdotes and soft rapport-building that could be trimmed. Most value clusters in the middle section (transparency, context, compounding effects, hiring, ramp), but filler exists.

“Most misses are baked into the plan before the year really even starts. A lot of times it's actually not an execution problem, OOO on the plan. It's the, the problem with the plan maybe.”

“And it's easy to sell to everybody, right? Like, I mean, what, what person that you've hired for a high salary is gonna say, no, boss. I don't think I could increase that by 5%. No one's gonna say it, but they're also not being a mathematician in that moment, right there. Having to defend their value in the business in that way.”

The framing of sales planning as a dual-audience problem (board vs. execution) is relatively fresh and insightful. However, most underlying frameworks - top-down planning bias, compounding effects, hiring lead times, ramp time dependencies - are widely known in ops circles. The specifics of *why* this breaks down (trust dynamics, incentive misalignment, capacity bottlenecks) add some originality, but the episode doesn't introduce genuinely novel methodologies or counterintuitive arguments that would justify a higher score.

“I think you're building a plan truly for two different audiences. And I think that's at the core of this. I think one is for, again, it's the, you know, the management team, the senior management team building this thing out. But one audience is your bosses and that's new investors.”

“if you are a CFO and you've already been in that sheet for, you know, a meeting a week for the fa past two months and you've already kind of lofted it to the board as I think we've got a plan, and then in the spirit of collaboration, you bring in your go to market executives, right? And I say the spirit of collaboration because that setup where you've already spent so much time in it, you could be really attached to that plan probably already.”

Scott Domareck is a four-time VP of Sales with tangible experience across SMB to enterprise, series A through public company exits. He demonstrates deep familiarity with real planning failures and has clearly executed at scale. His comments are grounded in specific scenarios and carry the weight of accumulated experience. The conversation between two practitioners who worked together directly adds credibility. This is a genuinely qualified guest - not a career podcast talker or consultant, but an operator with skin in the game. The only reason this isn't higher is that the episode doesn't push him into areas where his expertise becomes truly exceptional or differentiating.

“He was my VP sales back in the day at Falcon, and he's now a four times VP sales veteran. He has been through exits, scaling and all the pain and joy that comes with that.”

“But I think both you and I have the humility and to be on message here to, to be aware that a great deal of that hitting those targets, you know, most sales leaders brag about hitting, but it's not, you know, just that, that execution is that you planned really well, right?”

The episode lacks hard numbers, named companies beyond Falcon and Roblox, and concrete case studies. Claims about hiring delays, ramp times, and attrition are general ('H2 hires don't impact fiscal year,' 'BDRs take 3-6 months vs. 9-12 in enterprise') without specific data attached. The Falcon example is mentioned but not detailed with metrics. Most evidence is anecdotal or derived from the guests' experience rather than data, research, or named examples that would allow a listener to pressure-test claims or apply them precisely to their own context.

“in typical any, anything mid-market with a, a normal velocity and, and ramp time, uh, for those reps hires in H two really aren't impacting that fiscal year.”

“If you then only make the replacement higher, so to speak. Or the backfill hire in February or March, they have less time to deliver the same amount of pipeline and let's forget about sales cycles and all of that, right? In reality mm-hmm. In order to make up for one earlier missed hire, you actually need to hire two people to make up for that.”

Toni demonstrates solid question quality and willingness to follow Scott into uncomfortable territory (the dual-audience problem, trust gaps, capacity constraints). However, the conversation is heavily weighted toward collaborative affirmation rather than productive disagreement. There are long anecdotal digressions (the Williamsburg walk, the hungover car ride) that consume time without building the central argument. Follow-ups are mostly confirmatory ('Yeah, exactly') rather than probing or challenging. Scott's claims rarely face skeptical pressure, and the host could push harder on trade-offs, counterarguments, or the limits of these frameworks.

“So I mean, where's all of this starting? We already mentioned the spreadsheet. Um, and to be, I mean, this is my, my favorite topic from back in the day. Basically this whole top down planning process, right?”

“Does that resonate in any way? I don't know if you see that. Toni: I mean, it's, um, it's, um. I would call it a change management process that is being kicked off.”