The annual sales plan is meant to give the business a clear destination. But what happens when the assumptions behind the plan start changing weeks, or days, after it's finalized?

Accelerating product cycles and shifting market opportunities are putting pressure on enterprise organizations to revisit their sales plans more frequently.

At Google, for example, product updates that once arrived quarterly can now happen multiple times a week. At Dell Technologies, the AI infrastructure boom is reshaping demand and sales coverage requirements. And at a rapid-growth company like Boomi, emerging growth opportunities are creating reasons to revisit execution priorities throughout the year.

The case for more agile, frequent planning is now clear. But how are leaders making it work in practice?

How do you build more continuous planning rhythms into an organization accustomed to annual cycles? Which elements of the plan can realistically change midyear? And how do you create greater agility without undermining the stability sellers need?

To explore how leading enterprises are navigating these tradeoffs, we brought together three senior operators for the closing session of The Sales Planning Summit:

• Melissa Fenner, Director, GTM Strategy and Transformation, Google

• Tim Cole, SVP, Revenue Operations, Boomi

• Natascha Garmendia, Sr. Director, GTM Sales Strategy & Planning, Dell Technologies

The conversation examined the operational realities of more frequent planning: how these leaders identify opportunities to adjust course, what they're willing to change (and what they deliberately protect), plus how they coordinate decisions across Sales, Finance, HR, and other stakeholders.

Here are the practical lessons from the discussion to help you build more adaptability into your own sales planning operations.

But first, why are teams needing to adopt a faster cadence for planning to start with?

The case for more agile sales planning

As our experts agreed, historically, revisiting an annual sales plan was often a reaction to something going wrong (a major market downturn, missed performance expectations, a revenue target that suddenly looked unattainable.)

Today, however, some of the strongest reasons to revisit planning assumptions are coming from positive developments the original plan couldn't anticipate.

Melissa Fenner described how accelerating product development at Google, particularly around AI, is creating new demands on the GTM organization:

Ultimately, when a company's products, market opportunity, or selling motions evolve, how quickly can its sales coverage and resource allocation follow? This is the new test facing GTM leaders.

The original plan may have distributed resources appropriately based on what was known at the start of the year. But an emerging product opportunity could warrant additional specialist support. A new selling motion might require different coverage. Stronger-than-expected performance in a particular region might justify further investment.

These decisions can carry significant implications, even when the company's annual financial commitments remain unchanged.

But can a business actually hope to move this quickly? Is this cadence of planning realistic?

That's where our speakers got very specific about the misconceptions around more agile planning.

Tim Cole distinguishes between the revenue objectives the organization is committed to delivering and the underlying assumptions about how it will achieve them:

In other words, you can preserve your annual revenue destination while continuously evaluating headcount deployment, functional contributions, elements of the compensation strategy, and other execution decisions.

Small, well-timed adjustments can help keep the organization on course without waiting for performance gaps to accumulate into much larger problems.

The opportunity is to always be inspecting the assumptions behind the plan, even as the destination remains fixed.

• Which investments are producing the expected return?
• Where is demand developing faster than anticipated?
• Are the original resource allocations still the best way to achieve the number?

These questions turn planning into a mechanism for identifying and acting on opportunities throughout the year.

1. Protect seller commitments while creating flexibility elsewhere in the plan

Nonetheless, greater planning flexibility introduces instability for the people responsible for delivering the results.

Reallocating accounts, introducing new coverage, or changing sales roles may make sense for the business. But these decisions can also affect a seller's territory potential, quota attainment, or expected earnings.

At Dell, Natascha Garmendia explained that the organization continues to use an annual plan as its foundation, supplemented by quarterly or semiannual reviews and ongoing monitoring of business conditions.

When changes are warranted, Dell generally favors adjustments to resource allocation, specialist deployments, and targeted incentives while keeping core territory structures, quota-setting philosophies, and compensation arrangements stable.

Melissa described a complementary approach at Google. Her team uses pooled specialist and overlay resources that can be redirected toward emerging priorities without repeatedly changing core seller assignments.

For some initiatives, Google also ring-fences selected accounts, providing additional resources to support a particular GTM motion while limiting disruption to the broader sales organization.

These approaches suggest a useful principle: Build more of your planning flexibility into the resources and tactics surrounding the seller before reconsidering the seller's core commitments.

The flexibility still comes with responsibilities.

Natascha emphasized that Dell evaluates potential hardship created by coverage changes and considers how to address the impact on individual reps. Tim reinforced the importance of making any unavoidable changes understandable and fair, particularly when a seller's earnings opportunity is affected.

For sales compensation leaders, the business case for a midyear adjustment should therefore include its implications for seller opportunity.

A decision may improve aggregate coverage or resource efficiency while creating unintended consequences for individuals. Those consequences need to be considered before the change is approved.

Overall, the more flexibility organizations can build around the seller, the more responsive they can become without constantly renegotiating the conditions under which sellers are expected to perform.

2. Make faster planning decisions without chasing every performance signal

Once leaders establish what can change, the next challenge is determining when to intervene.

More frequent reporting and increasingly sophisticated analytics make it easier to identify deviations from the original plan. But a movement in a metric doesn't automatically mean that a planning assumption needs to change.

Natascha described how her organization monitors several indicators between formal planning reviews to identify potential pressure points in the existing GTM deployment model:

But what matters most is what happens after a signal appears.

A shift in product demand could warrant redeploying specialists. Changes in customer segmentation might justify revisiting coverage. But a dip in performance could also reflect seller execution, market constraints, or assumptions about how quickly an investment should produce results.

Treating every deviation as a planning problem risks introducing unnecessary changes.

And with better analytics, that risk can actually increase.

Tim cautioned that you now have the ability to track so many metrics that it can be tempting to chase every encouraging signal, even when the opportunity may be only temporary:

To counter this issue at Boomi, the team has built a more disciplined approach around agreed metric definitions, historical performance, and targets mapped across the year.

They establish an expected trajectory against which actual performance can be evaluated, which helps leaders distinguish between a meaningful departure from the plan and a movement that may be entirely normal.

Tim also emphasized the importance of realistic time horizons. Entering a new market, for example, may require extensive groundwork before meaningful revenue materializes. Evaluating that investment too early can lead to unnecessary intervention.

Melissa added that understanding the root cause often requires looking across multiple metrics and gathering input directly from the field.

If marketing lead conversion declines, for instance, the underlying problem may be how long those leads waited for sales follow-up rather than lead quality itself.

To operationalize a more continuous planning rhythm, the implication here is to establish a shared decision process:

• Identify the deviation: What has changed relative to the original assumption or expected performance trajectory?
• Diagnose the cause: Does the evidence indicate a planning issue, an execution problem, or an external constraint?
• Assess its persistence: Is the change likely to last long enough to justify intervention?
• Select the appropriate response: Can execution or resource deployment address the issue before more foundational changes are considered?

The above process gives Sales, Finance, and RevOps a more consistent basis for deciding when intervention is warranted.

At the end of the day, you want to be able to act sooner on meaningful changes, with enough judgment to leave the plan alone when the evidence doesn't justify action.

3. Govern midyear changes with the same rigor as the annual plan

Even when the data supports an adjustment, there's still the matter of getting it approved, coordinated, and executed.

Continuous planning introduces more potential decision points throughout the year. Without clear governance, greater responsiveness can quickly become a source of disruption.

Melissa acknowledged that balancing proactive planning with organizational stability remains difficult, even at Google.

To help with this, her team sets a high bar for midyear changes, requiring a demonstrated ROI case and senior-level sponsorship before moving forward.

But approval is just the beginning.

When Google introduces a new role or GTM motion, the team works to make expectations explicit: how the role fits into the existing organization, what responsibilities it owns, and what successful execution should look like.

Melissa emphasized the importance of this practical guidance, templates, and clear expectations to help teams take on the change more efficiently.

A sound business case doesn't automatically make a change executable

Natascha further illustrated the challenge of making change a reality with an example from Dell.

Her team had considered converting certain traditional sales roles into non-selling roles. From Finance, GTM, and RevOps perspectives, the change made sense.

But when HR reviewed the proposal, the team discovered that the conversion couldn't proceed as envisioned.

The example highlights a constraint that's easy to underestimate when planning decisions are evaluated primarily through financial or operational models.

Changes to sales roles, coverage, and compensation may involve employment requirements, organizational policies, regional regulations, and commitments to individual employees. What looks optimal from one function's perspective may be difficult or impossible to implement across the enterprise.

At Dell, Natascha described the planning function as a coordinating force between regional RevOps, Finance, HR, and executive leadership. Rather than bringing every proposed change through a permanent standing committee, the team identifies the relevant stakeholders based on the decision at hand.

You'll also want to involve trusted frontline sellers throughout the year. Their perspective can reveal how a proposed change will land in the field, or whether its timing risks disrupting a critical selling period.

Just remember that cross-functional alignment needs to happen early enough to shape the decision, rather than simply approve or communicate it after the fact.

A repeatable governance process (where you know who has decision-making authority, which teams must validate feasibility, and what needs to be true before a change can move forward), ultimately makes greater planning agility possible. Your teams will spend less time rebuilding alignment from scratch and gain more confidence that approved changes can actually be carried through.

The next planning advantage is knowing when to change course

This discussion gave a more practical definition of continuous sales planning than simply increasing the frequency of planning cycles.

We discovered that at Google, Dell, and Boomi, annual commitments absolutely still matter and seller stability remains a priority. But the assumptions about how the organization achieves its goals are receiving more scrutiny throughout the year.

This shift is really about making better decisions regarding when and where to intervene.

You need the visibility to recognize when assumptions are no longer holding, the flexibility to adjust the right elements of the plan, and the governance to execute changes without undermining seller trust.

And as AI makes the operational work of planning faster, these capabilities will become even more consequential.