Field Note

The number isn't changing. Now what?

You brought the bridge, you asked what assumption you were missing, and the answer was some version of "the number is the number." Fine. The number's ugly. Now figure out what it requires.

Stop relitigating it

This is mostly for managers. Once the quota is set and you've made your case, stop arguing about it with the team every Monday. They already know it's big. Hearing you complain about it just tells them you don't think it's hittable, and they'll believe you.

A manager's job isn't to complain upward or enforce downward. It's to translate the number in both directions: explain to your boss what the territory can actually do, and explain to your team what the number actually requires.

Work backward

Start from the quota and walk it down: required bookings, then the pipeline that takes at your real win rate, then how many opportunities that is at your average deal size, then what it means per rep, per month. Keep the math simple enough to put on one whiteboard.

Somewhere in that list is the part nobody can see yet. That's where the plan goes. It's usually new pipeline, and it's usually needed earlier than anybody wants to admit.

A hard number can still be a fair one

Some quotas are crazy. A lot of them are just hard. The difference is whether you can draw a line from where you are to the number, even if the line is steep. If you can, it's a plan. If you can't, go back to the bridge.

Try it

Pipeline Check works backward from the quota to the pipeline and deals it takes, per rep and per month.

Try it

More field notes

Mark Flournoy

Made by Mark.

I spent six years leading federal partner sales teams at AWS, after plenty of years carrying a number myself. QuotaBird is mostly stuff I wish we'd had back then. Most of it's free. If the problem's messier than a little tool can handle, we can talk it through.