Your Quota Went Up and Your Patch Got Smaller: What to Actually Do in Week One

12 min read

Annual planning cut your patch and raised your number. Here is the practical week-one response, from the arithmetic to the exact asks to put in writing with your manager.

The plan is already signed

Annual planning lands the same way every year. A deck you did not see until that morning, a new number, a territory map with fewer logos on it, and a short speech about how this is a vote of confidence in you. Then everyone goes back to their desks and the Slack channel fills up with people asking each other whether they still own the account they have been working since August.

Here is the first thing to accept: the number is not moving. Comp plans get approved above your manager, usually above your manager's manager, and by the time it reaches you the finance team has already built next year's forecast on top of it. Spending week one arguing about the number is spending week one on the only variable that is definitely locked.

What is not locked: which accounts you work, what support you get, how the patch is defined, what happens the next time someone reshuffles it, and whether you find out in January or in June that the plan cannot be hit. That last one is the whole game. I have watched reps discover in month five that the arithmetic never worked, and by then the conversation is not a planning conversation anymore, it is a performance conversation. Those are two very different meetings.

So week one is not for negotiating. Week one is for finding out what you are actually holding, and putting your asks in writing while everyone still has planning energy and nobody has missed anything yet.

Do the arithmetic before you touch anything else

Most reps react to a quota increase emotionally, which is fair, and then behaviourally, which is a mistake. They decide to work harder. More dials, earlier starts, weekend prospecting. That is a plan built on effort when the problem is usually built on inputs.

Build the number backwards instead. Not with the numbers on the planning slide. With yours, pulled out of your own CRM, from your own closed-won.

Start with the annual number and divide it by your real average deal size — the one you actually closed last year in the segment you will be selling into this year, not the blended company average that includes one monster deal somebody's cousin brought in. That gives you deals needed. Divide deals needed by your own opportunity-to-close rate and you have qualified opportunities needed. Divide that by your meeting-to-opportunity rate and you have meetings needed. Divide meetings by your connect-to-meeting rate and you have conversations needed. Divide conversations by the dials it takes you to get one, and you have dials.

Then count your selling weeks on an actual calendar. Not fifty-two. Subtract the holidays your buyers take, the week of sales kickoff, the week you are in a training you did not ask for, your own PTO, and the dead stretch at the end of December when nobody signs anything. Whatever is left is what you have.

Now divide the dials by the selling days. Look at the number sitting in front of you and ask whether a human being can do that alongside the meetings, the follow-up, the proposals and the internal calls you are also required to attend. Some of you are going to look at that number and it will be fine. Some of you are going to look at it and realise the plan requires you to be on the phone more hours than there are hours.

That second outcome is not a reason to panic. It is information, and it is information you now have in January rather than June. It tells you the fix is not effort. The fix has to come from deal size, conversion, or account quality — because you cannot buy more hours.

Do the inventory test too

The capacity test tells you whether you can make enough calls. The inventory test tells you whether there is enough to sell to.

Count the logos left in your patch. Not the number of rows in the CRM export — the number of accounts that could realistically buy what you sell at a size that matters. Strip out the ones already under contract with a competitor for the next two years, the ones too small to clear your minimum, the ones who have told you no in a way that means no.

Take that count of real, winnable accounts and multiply by your honest win rate, then by your real average deal size. If the answer is comfortably above your number, good, you have a coverage problem you can solve with activity and prioritisation. If the answer is roughly equal to your number, you have a problem, because it means you have to win nearly everything. If the answer is below your number, the territory is arithmetically incapable of producing the quota and no amount of grinding changes that.

When I was selling inside AWS and Dell, the reps who did well after a territory change were rarely the ones who worked the most hours. They were the ones who worked out fastest where the winnable revenue actually sat and then went and stood on it.

Re-rank what is left of your patch

Assume nothing carries over. The accounts you loved last year may be the wrong accounts this year, because your number changed and the mix changed with it.

Pull your closed-won from the last two years and sort it by anything you can get your hands on: industry, headcount band, tech stack, who the champion reported to, whether the deal came in through inbound or outbound, how long the cycle ran. You are looking for the pockets where you win, not where the market is biggest. Every rep has a segment where their pitch just lands better, and most of them have never bothered to identify it explicitly. Find yours, then check how many accounts in your new patch look like it. That subset is where week two's dials go.

Do the same exercise with your losses, and be specific about the reason. Losses to price in a segment tell you something different from losses to no-decision. A patch full of accounts that historically no-decision on you is a patch that will eat a year of your activity and give you nothing back in Q4.

Go find what other reps left behind

This is the highest-return hour of your week one and almost nobody does it.

When territories get redrawn, accounts fall through the cracks. Reps leave, patches get merged, someone gets promoted mid-quarter and their pipeline gets distributed by whoever was closest to the spreadsheet. Ask your ops person — nicely, with a coffee — for a few lists.

Accounts in your new patch with no logged activity in the last year. Closed-lost opportunities from more than a year ago where the loss reason was timing, budget or an incumbent contract, because contracts end. Accounts that took a first meeting and then went dark, which is different from accounts that said no. Accounts previously owned by a rep who is no longer at the company. And the ones nobody thinks to ask for: accounts that were touched by marketing, went to an event, downloaded something, and never got a call because they landed in a patch that was in flux.

Those lists are full of people who have already shown some form of interest and have not heard from your company since. A named account with a two-year-old conversation on file is a warmer starting point than a cold logo somebody bought from a data vendor, and you already own it.

While you are at it, ask about the accounts that left your patch. If some of them moved to enterprise, find out who has them now, and find out which ones that rep does not intend to work. Enterprise reps with big patches routinely have accounts they will never call. Some of them will happily hand one back or split it rather than let it sit. That is a five-minute Slack message with a real chance of a yes.

Rebuild the list, then dial

Give yourself two or three days of this and no more. Research is the most comfortable form of avoidance in our profession, and a rep can spend an entire January building the perfect account tier and never pick up the phone. Set an end date.

What you want at the end of it is a ranked list, in tiers, with contact data attached and a reason to call each one. Tier one is your best-fit segment with a trigger — new funding, a leadership hire, an expiring contract, a job posting that implies the problem you solve. Tier two is best-fit without a trigger. Tier three is everything else, worked in bulk when you have gaps.

And then dial. By the end of week one you should have made calls, because the fastest way to find out whether your new patch is any good is to talk to it. The theory you built on Monday survives contact with about six conversations. Better to learn that on the Friday of week one than in March.

The conversation to have with your manager

You get one clean shot at this, and it is now, while planning is still fresh and your manager still has some flexibility in what they can promise. In four months they will be managing a forecast gap and will have nothing left to give you.

Do not open with the number. Open with the math. Something like:

"I have built the plan backwards from the new number using my own conversion rates from last year. Here is what it requires in dials per day and here is what the patch can produce at my current win rate. I want to walk you through it and agree on what changes, because on these inputs I get to about here and I want us both to see that in January rather than June."

That is a completely different conversation from "my quota is too high." You are not complaining, you are presenting a model and asking for help closing the gap in it. Managers can work with a model.

Then ask for specific things. Vague support is not support. The list worth asking for usually includes: the account list locked for at least two quarters, with a commitment that any mid-year carve-out comes with a pro-rated quota adjustment. Clarity on how inbound is routed in your new patch and whether you get any. Named SDR support, or if there is none, an explicit acknowledgement that all pipeline is self-sourced so nobody pretends otherwise later. Access to a solutions engineer for the segment you are targeting. Confirmation of what happens to commission on the deals you sourced that moved to another rep — half of the resentment I have seen after a territory change comes from this one question going unanswered. And if the ramp into a new segment is real, a draw or a phased quota for the first quarter.

You will not get all of it. You will get some of it, and the ones you get are worth more than the ones you argue about.

Put it in writing the same day

Send a short email after the meeting. Not a formal document, not something that reads like you are building a case. Just: "Thanks for the time. Capturing what we agreed so I have it straight." Then the list. Then "let me know if I have any of this wrong."

That email does two things. It protects you, obviously. But more usefully, it converts a conversation into a set of commitments, and people behave differently towards written commitments. It also gives your manager something to point at when they go and ask their own boss for the SE hours they just promised you.

The meeting you are trying to avoid with all of this is the one that happens in June, after two quarters of missing, where the agenda is your activity levels and the framing is that you are the variable that failed. I have sat on both sides of that meeting. If you want to see exactly how it goes, we script it out in the two-quarter miss coaching 1:1 playbook — the tell is that almost none of it is about whether the plan was ever achievable, because that question expired in January. The same conversation runs in freight and 3PL teams and in real estate offices with different vocabulary and identical structure: the rep explains the market, the manager explains the pipeline, and nobody produces the arithmetic from the start of the year because nobody did it.

Do the arithmetic in week one and you get to have that conversation in January instead, when it is a planning problem and everyone is still on your side.

How to know the plan is genuinely impossible

Three tests. If one fails, you have a hard year. If two fail, you have a structural problem and you should escalate calmly, in month one, with the model attached. If all three fail, you should be thinking about whether you want this seat, and you should be thinking about it now rather than after you have burned your reputation on a plan that was never winnable.

The capacity test: the required daily activity exceeds what a person can physically do while also running the meetings that activity generates.

The inventory test: the winnable accounts in the patch, at your real win rate and real deal size, cannot produce the number even if you win nearly all of them.

The history test: nobody in this segment has ever produced this number, including whoever the top rep was last year. If the plan requires you to beat the all-time best performance in the territory in your first year in it, that is not a stretch goal, that is a forecast someone needed to balance.

When you escalate, do not escalate the feeling. Escalate the model, and end with a question rather than a complaint: "On these inputs I land short. What would you change — the account list, the segment, the deal size assumption, or the number?" Give them the four levers. One of them will move.

What to do next

If the honest answer is that the plan is reachable but only if your conversion improves, that is the most common outcome and the most fixable one. It means your week is not about more dials, it is about what happens on the dials you already make — the opening ten seconds, the moment they say they already have a vendor, the point in the discovery call where you should have asked one more question and moved on instead.

That is the part I would work on first, and it is exactly why we built DrillCall. Rehearsing the new segment's objections against an AI buyer before you spend your best accounts learning them live is a much cheaper way to find out that your pitch does not survive the shift from mid-market to enterprise. If you have just inherited a patch you have never sold into, run the calls in practice before you run them on the accounts you cannot afford to burn.

Practise these calls

The playbooks behind this post — a scripted opener, the objections you will actually hear, and an AI buyer to run it against.

About the author

Timothy Yang

Founder & CEO, DrillCall

I build products by getting on the phone. Four businesses built and exited, including a micro-task marketplace with 170,000+ users, and the common thread in every one was the same: nothing moved until I picked up the phone and sold. Cold outreach, discovery calls, closing. The unglamorous work that actually creates revenue. Right now I am building DrillCall, an AI-powered voice training platform where sales reps practice live calls against realistic AI buyer personas, 310 of them across 31 industries, and get a scorecard after every call. Think flight simulator, but for cold calls. I also run Vibe Coding Club, a community of over 3,500 builders shipping products with AI, and I have spent time inside AWS and Dell, so I have seen how enterprise sales machines work from the inside as well as from the founder seat. What I care about: expected value thinking, fast iteration, and talking to customers before writing a line of code.

← All posts