Tribal knowledge, spreadsheets and a black box
When Zack Helm took on territory planning at Beeline, the process looked like most companies'. Planning relied on institutional memory and spreadsheets passed between finance, sales leadership and RevOps. The cycle took two to three months and consumed roughly 40% of the team's collective time.
Beeline's territories aren't simple. The sales team covers multiple segments, multiple product lines and two continents, so territories have to balance geography, account mix, segment coverage, historical context and growth potential. That complexity is what broke the spreadsheet approach, and what made the lack of transparency so damaging. Reps couldn't see how their territories were built, or why.
There wasn't true transparency with territories. There's no true sentiment of why territories are being balanced the way they are when you're doing it through Excel.
The missing piece in the RevOps stack
Beeline had been building out the rest of its RevOps function: forecasting, pipeline management, qualification, win/loss analysis. Territory design was the weak link, and it limited the return on everything else. Better pipeline management doesn't help much if reps are covering the wrong accounts in the wrong geographies.
Three things that mattered most
Getting started was fast. Beeline talked through its current state and pain points, set guardrails for what territory designs needed to balance, and BoogieBoard generated initial scenarios quickly enough to start internal discussions almost immediately.
1Salesforce data, not stale exports
With the old Excel approach, data was stale the moment it was exported. BoogieBoard connects directly to Salesforce and syncs account data on a schedule, or on demand, so every territory model starts from what's actually in the CRM.
2Scenarios you can keep and compare
In Excel, moving a few states from one territory to another was slow, and comparing the before and after was even harder. In BoogieBoard, the team could make that change in minutes and keep both versions for a side-by-side comparison. Because scenarios are generated at the click of a button, the question is no longer how many territory designs the team can build — it's which one is best.
3Many variables, balanced at once
Beeline's territories had to account for segments, ICP account counts, historical bookings, open pipeline and geographic boundaries all at once. In spreadsheets, balancing that many variables was effectively impossible. BoogieBoard let the team set every one of those criteria and see what the data actually supported, rather than designing around what felt right.
We leveraged BoogieBoard to really revamp the data we're using for territory design. The biggest shift was going from opinion-based planning to data-driven modeling.
