Go back

Territory Planning with Meghan Gill: Data-Driven Operational Cadence for Q4 & 2027

11m 33s

Territory Planning with Meghan Gill: Data-Driven Operational Cadence for Q4 & 2027

In this Revenue Builders segment, Megan Gill, former VP of Sales Operations at MongoDB, shares how she scaled the function from $100 million in revenue with roughly 60 to 70 reps to a $2 billion public company with 600 to 700 reps over 15 years. She explains that sales operations evolved into three pillars: field operations, planning and compensation, and systems, process, analytics, and reporting. Field operations teams sit close to sales leaders in each geography and act as the interface between centralized operations, finance, and the field, handling territory design, comp plan design, and resource allocation. Planning became a continuous full-year cycle, with Q1 for issuing plans, Q2 for identifying changes, Q3 for top-down and bottom-up planning, and Q4 for systems and implementation. Megan notes that the definition of sales operations shifts as companies grow, moving from building tools and reporting to optimizing segmentation and resource use. She also shares a contrarian view on revenue operations, arguing that combining sales, marketing, and customer success operations works early on but that keeping operations close to the business is better at scale. Finally, she emphasizes that fair territory planning, using total addressable market to give every rep an equal shot at hitting their number, is essential for productivity and retention.

Transcription

1524 Words, 8386 Characters

English
Speaker 1Welcome to Revenue Builders, hosted by John Kaplan and John McMahon. In this Revenue Builders segment, we're diving in with Megan Gill, VP of Sales Operations who scaled MongoDB from $100 million to a multi-billion dollar enterprise over 15 years. She knows what it takes to build operational discipline at scale. In this conversation, Megan breaks down how to structure your operational cadence and territory planning, so it actually enables your sales leaders instead of burying them. This is the operational foundation that separates solid execution from chaos during planning season. Let's dive in.
Speaker 2So when I took over sales ops, it was right before we went public. So we were around 100 million in revenue, probably 60 or 70 reps. And so it was me, one analyst, and a couple of Salesforce folks. By the time I left MongoDB, we were a $2 billion public company. We had probably 600 or 700 reps. And sales operations was organized into a few different pillars. There was a field operations team that was sitting close to each of the sales leaders and supporting each of the leaders in their geo, and was kind of the interface between centralized ops, finance, and the field. Then we had a team that was focused on planning and comp. And then we had a team that was focused on systems, process, analytics, and reporting. So it definitely evolved over time into being a much more specialized function.
Speaker 3And what did the people in those, let's go through each one of those. What did the field ops people do that couldn't be done centralized?
Speaker 2Well, what happened over time was a lot of the stuff that was being done centralized got put into the field. So for example, like, you know, you probably remember, John, we went through many planning cycles where we worked together on things like territories and comp plan design and how many reps are we going to put in each region. All that stuff eventually got pushed into the field ops team. So there would be like a leader for, say, North America, and they would sit with that. The sales ops leader was kind of like their COO who would figure out how many, what resources are we putting? What are we going to put in there in each of the different functions? So not just reps, but SA's, SDR's, partner reps. They would figure out what the territories were going to look like. They would be doing all, running the operational cadence on the ground. And then a lot of the reporting to support that was done centrally so that everybody was kind of singing from the same hymn sheet, if you will. So we had centralized like dashboards to track, you know, productive capacity and pipeline and things like that. But, you know, when you're in the field, there was someone there to sort of, you know, run it locally.
Speaker 3Yeah, that makes a lot of sense because they have more local knowledge than you do at the corporate level, right? And then, so comp and planning, compensation, that's comp plans, right? And then what's planning? Well, you talked about planning. What is that? Is that for planning for next year?
Speaker 2Yeah, I mean, it's funny because my husband was always joking with me. You're always planning. And that was like, you know, a big shift, I would say, as we got bigger is, you know, it wasn't like, OK, we're just going to have a few meetings about the comp plans in Q4 and then we'll be ready to go. Planning became basically a full-year process. So in Q1, you're issuing all the new plans, you're enabling on the decisions that you made. In Q2, you're starting to think about, OK, like, what are the changes we might want to make for next year? What are the big needle movers? And then also, what kind of growth do we want to have for the following year? By the beginning of Q3, you have preliminary. We would have preliminary numbers and we would spend Q3. Basically, the exec team would come up like me and the exec team would come up with like the high level numbers. Then we would distribute them out to the main regions and they would go back and do their bottoms up planning. And then Q4 was all about systems and implementation. So and we never sort of like left that cycle. We're always, always in planning mode because if you make changes that might have been easy to make when you're smaller, as you get bigger, can have a much larger downstream impact, whether it's on how Salesforce is configured, how you're enabling the reps, how you're paying the reps. So it became it became quite an endeavor. And that became like the big basically where I was spending most of my time. I was like, OK, it's FY24. I'm thinking about FY26.
Speaker 3Yeah. And when you talked about the evolution of sales operations. You know, when you go when I go to different companies and talk to different companies, sales ops means different things to different companies. And it basically is probably because of what you've outlined that as you get bigger and bigger, sales ops and the definition for sales ops really changes.
Speaker 2It does. And yeah, as you get bigger, it becomes much more of a focus on definitely focus on the planning. Early on, there was much more of a focus on just like building the tools, making sure you have the right reporting and dashboards, that you have the right capabilities to do pipe gen or in space. And then once that infrastructure is in place, then it really shifts towards how do we make sure we're segmenting the sales force the right way, that we're utilizing our resources in the most optimal way. So it definitely it definitely changed over time.
Speaker 3Yeah. Now, just just from my understanding, because you hear a lot of companies now calling it revenue ops. So what's the difference or is there a difference between sales ops? And revenue ops from what you know? So my understanding
Speaker 2of RevOps is that the concept is that you bring together all of the different operations functions, so not just sales, but marketing, CS, maybe you have a services ops team into one function so that you are all aligned on the same metrics and it sort of allows better cross functional collaboration. I have a bit of a contrarian view on that. I think that it's probably great early on when you're you're resource constrained, like, you know, to build a set if you're an early stage startup, like why build a marketing ops team and a sales ops team, probably easier to build one cohesive team. But over time, you know, you want your operations team to be close to the business. And I mean, who likes working with a big centralized function, which is why it was so important to have to me to have that field operations. And I mean, who likes working with a big centralized function, which is why it was so important to have that field operations.
Speaker 3And so keeping the database clean, that was always one of the biggest challenges that we had. So I think that's one of the things that we've been working on. have been there like four or five years. And then they start saying they're going to pull some accounts away from them for the three or four new reps in the territory. And then they say, well, if you do that, you know, I'm going to quit. And then the poor new reps that come in don't really have a chance at making the number because they got a little sliver of the pie. So it's so important for productivity, as you know, to make sure that those territories are evenly divided, give everybody a chance to make the number.
Speaker 2Yeah. And we had, I mean, we've changed the process many times and I, you know, I left MongoDB back in February, so they could have changed it since I've been there for all I know. But for a while we were working off this concept of total addressable MongoDB market. So TAM. And so we try to quantify the value of each account and give each rep, show them like, okay, you have X million dollars of TAM. It's the same as the guy sitting next to you. So you have an equal shot at hitting your number. And then that really helped us see like, okay, well, this person doesn't really have enough to work with or this person's got more than they can possibly prospect into. Thanks for listening
Speaker 4to today's episode. If you enjoy the content, please subscribe, rate and review the show to help us reach more people. This show is brought to you by Force Management, where we help companies improve sales performance, executing the growth strategy at the point of sale. Check out forcemanagement.com for more information. you

Podcast Summary

Key Points:

  1. Megan Gill scaled MongoDB's sales operations from $100 million in revenue with about 60 to 70 reps to a $2 billion public company with 600 to 700 reps over 15 years.
  2. Sales operations evolved into three specialized pillars
  3. Field operations teams sit close to sales leaders in each geography, serving as the interface between centralized operations, finance, and the field.
  4. Planning became a full-year continuous process, with Q1 for issuing plans, Q2 for considering changes, Q3 for top-down and bottom-up planning, and Q4 for systems and implementation.
  5. The definition of sales operations shifts as a company grows, moving from building tools and reporting to optimizing sales force segmentation and resource allocation.
  6. Megan holds a contrarian view on revenue operations, believing that combining sales, marketing, and customer success operations works early on but that keeping operations close to the business is better at scale.
  7. Territory planning is critical for productivity, and MongoDB used total addressable market to quantify account value and ensure reps had equal opportunities to hit their numbers.
  8. Uneven territories can cause tenured reps to quit and leave new reps with little chance of success, making fair territory division essential.

Summary:

In this Revenue Builders segment, Megan Gill, former VP of Sales Operations at MongoDB, shares how she scaled the function from $100 million in revenue with roughly 60 to 70 reps to a $2 billion public company with 600 to 700 reps over 15 years. She explains that sales operations evolved into three pillars: field operations, planning and compensation, and systems, process, analytics, and reporting. Field operations teams sit close to sales leaders in each geography and act as the interface between centralized operations, finance, and the field, handling territory design, comp plan design, and resource allocation.

Planning became a continuous full-year cycle, with Q1 for issuing plans, Q2 for identifying changes, Q3 for top-down and bottom-up planning, and Q4 for systems and implementation. Megan notes that the definition of sales operations shifts as companies grow, moving from building tools and reporting to optimizing segmentation and resource use. She also shares a contrarian view on revenue operations, arguing that combining sales, marketing, and customer success operations works early on but that keeping operations close to the business is better at scale.

Finally, she emphasizes that fair territory planning, using total addressable market to give every rep an equal shot at hitting their number, is essential for productivity and retention.

FAQs

It started with one analyst and a couple of Salesforce admins, then grew into specialized pillars: field operations, planning and compensation, and systems/process/analytics/reporting.

Field ops worked close to sales leaders in each region, handling territory planning, comp plan design, resource allocation, and local operational cadence while central teams provided dashboards and reporting.

Planning never stops: Q1 issues new plans, Q2 evaluates changes and growth targets, Q3 sets high-level numbers and bottoms-up planning, and Q4 focuses on systems and implementation.

RevOps combines sales, marketing, CS, and services ops under one function for aligned metrics. Megan sees it as useful early on but prefers keeping ops close to the business as companies scale.

It quantifies the value of each account so every rep has an equal opportunity to hit their number, helping identify reps with too little or too much potential.

Uneven territories can cause experienced reps to quit when accounts are taken away, while new reps struggle with too few accounts, so fair division gives everyone a chance to succeed.

Chat with AI

Loading...

Pro features

Go deeper with this episode

Unlock creator-grade tools that turn any transcript into show notes and subtitle files.