You Are Not in the Budget

There is a meeting happening in October that you are not invited to.

Somebody at your best client’s company is going to sit in a conference room with a spreadsheet open and go line by line through next year’s spend. Every recurring cost gets a look. Every vendor gets a question. Somebody with a title you have never heard of is going to point at a row and say “what is this one, and do we still need it.”

If the answer to that question comes out of somebody else’s mouth, you have already lost. And you will not find out until March, when the renewal quietly does not happen and you get a very polite email about going a different direction.

This is budget season. It starts now and it is over by mid-November. It is the single highest-leverage window of the commercial year, and almost nobody who reads this is going to do anything about it, because it does not feel urgent. Nothing is on fire. Everybody is still paying you.

That is exactly what October looks like right before it goes wrong.

Every dollar a company spends sits in one of two buckets, and which bucket you are in decides everything.

Discretionary spend is what gets approved when things are good. It is a project. It has a start and an end. It got bought by one person who liked you, it gets justified fresh every cycle, and when somebody needs to find eight percent, this is the first place they look. It is not that they dislike you. It is that cutting you is easy, because cutting you does not break anything.

Structural spend is what has to get approved for the machine to keep running. It is not a project, it is a function. More than one person depends on it. Removing it creates a hole somebody has to fill on Monday morning. When the eight percent hunt comes around, nobody even opens this row, because opening it starts an argument nobody wants to have.

Here is the part that will sting. Which bucket you are in has almost nothing to do with how good your work is.

I have watched genuinely excellent operators get cut while mediocre ones survived, over and over, for one reason. The excellent one delivered beautiful work that lived in a folder. The mediocre one wired himself into something that would visibly break.

Quality keeps you from getting fired. Structure keeps you from getting cut. Those are two entirely different problems and most guys only solve the first one.

You have got about ninety days to move buckets.

Five steps. Pull out that one-page map you built on Monday, because this is what it was for.

You cannot show up to a window you cannot see.

Ask. Directly, this week, of your main contact at every account on your map. It is a completely normal question and it will not make you look desperate. It makes you look like somebody who plans.

“Quick logistical thing. When does your team lock next year’s budget? I want to make sure whatever we are doing in Q1 is lined up with your cycle instead of cutting across it.”

You will get one of three answers. A date, which is gold. A vague “sometime in the fall,” which means they do not know and you should ask who does. Or “we do not really do that,” which is almost always false and means you are talking to somebody too far from the money.

Write the date next to every account on your map. That is your calendar for the next ninety days. Everything else works backward from it.

Your champion is not that person.

Your champion loves you. Your champion is also, in almost every case, the one defending their own headcount in that meeting and has limited capital to spend on defending you too. You have been mistaking enthusiasm for authority.

You need to know three things: who runs that review, what they get measured on, and whether they have any idea you exist.

Some of that you can just ask your champion. “Who is going to be in the room when this gets reviewed? Is there anything they usually push back on that I should get ahead of?” A good champion will tell you everything, and will be relieved you asked, because now they have backup.

The rest is homework. I use Clay for this, because it keeps the map of who knows who and who moved where without me having to maintain it by hand, and the whole game here is knowing your way to the room before you need it. Half the time you already have a warm path in and you just never bothered to look.

This is the real work. Everything else is logistics.

You need one thing that breaks visibly if you go away. Not sadly. Visibly. Somebody has to notice on a specific Monday.

Ways I have watched this actually get built:

Own the reporting. If the number that gets read out in their Monday meeting comes from a dashboard you maintain, you are structural. Not because the dashboard is hard, but because unhooking it means somebody has to volunteer to rebuild it. Nobody volunteers.

Own a handoff between two departments. Every company has a seam where work falls through, usually between sales and delivery, or delivery and finance. If you are the bridge over a seam, cutting you reopens the seam, and everybody remembers what the seam was like.

Own an interface nobody else knows how to run. Not hostage-taking. Just competence. If you built the automation that moves their data between two systems, you are infrastructure. I build most of this with Make because I can hand a client something that runs on its own, that they can see running, and that has my fingerprints on every step of it.

Be more than one person’s dependency. This is the cheapest one and almost nobody does it. If three people at that company would feel your absence, you are three times harder to cut. Right now, for most of your accounts, the honest number is one.

Own a recurring meeting. The most underrated one on this list. If you run a standing monthly review that their people actually attend, cutting you means cancelling a meeting, and cancelling a meeting is a visible act somebody has to explain. A recurring thirty minute call on four calendars is worth more structurally than a beautiful quarterly report nobody opens.

Pick one account off your map. Pick one break. Build it in September. You have got the time, and you will not have it in November.

One warning. Do not build a break that makes their life worse. There is a version of this where a guy makes himself indispensable by being a bottleneck, hoarding a login, refusing to document anything. That works for about eighteen months and then it ends badly, because everybody eventually notices, and the day they replace you they replace you with prejudice. Build a break that helps them and costs them something real to unwind. That is the difference between being structural and being a hostage taker.

Here is the thing nobody tells you about that October meeting.

Your champion is going to have to defend you out loud, on the spot, from memory, in about forty seconds, while somebody who does not know you looks at a number.

You have never once helped them prepare for that.

So give them the language. Before the meeting, not after. One paragraph they can say without thinking, built around what the company measures, not what you delivered.

Not: “We redesigned their onboarding flow and delivered eleven assets.”

But: “Onboarding time dropped from eleven days to four, which is why Q2 churn was the lowest it has been in two years, and it is the same team that is handling the Q1 launch.”

Same work. One is a receipt. The other is an argument. Your champion cannot build the argument because your champion does not have your data.

Send it in early October. Frame it as helpful, because it is. “I know budget planning is coming up. Here is a short summary of where things landed this year in case it is useful for you.” No ask attached. Just ammunition.

We are going to go a lot deeper on how to build that document on Friday, because getting it right is a genuine skill.

The renewal conversation should never be the renewal conversation.

If the first time you raise next year is thirty days before the contract ends, you are negotiating from a position where the only available answers are yes, no, or discount. That is a terrible board.

Instead, in October, well before anything expires, have a completely different conversation. Not “will you renew.” Try this:

“I have been thinking about what next year should look like for you. Here is what I think we should stop doing, here is what I think is worth doing more of. What is changing on your end that I should know about?”

Two things happen. You find out what is actually changing, which is usually something you would never have guessed and would have found out too late. And you stop being a cost being evaluated and start being a partner planning. Those two people get treated very differently in an October conference room.

“This feels manipulative.” It is the opposite. Manipulation is letting somebody keep paying you for something they do not need. This is making sure that a decision about your work gets made with accurate information instead of a coordinator’s vague recollection. If you cannot make the structural case honestly, that is worth knowing in September rather than March.

“My clients are small. They do not have budget meetings.” Then it is one person, at a kitchen table, in January, looking at a bank statement and deciding what to cut. Same meeting. Smaller room. The advantage is you can probably get invited to it.

“I do not have time for this in September.” You will find the time in March, when the revenue is gone and you are prospecting from zero. It just costs about eleven times more then.

Getting cut is almost never a verdict on your work.

It is a verdict on your position. On whether you were a line somebody had to argue about or a line somebody could quietly delete on a Tuesday afternoon in October.

You have got until roughly mid-November to change which one you are. After that, the spreadsheet is locked and you are living inside somebody else’s decision until next fall.

Take your one-page map. Pick the single account you would be most damaged to lose.

Send that contact one email today, asking when their budget cycle locks.

One email. That is the whole move. You will know more about your next twelve months by Friday than you did all summer.

Refined. Relentless. Unapologetic.

Marcus