Selling Into Government and Public Sector: Procurement Rules, Budget Years and Who Actually Says Yes

Public sector is not enterprise with more forms

The first mistake reps make with councils, agencies, trusts and departments is assuming it's a slower version of the enterprise motion. Same discovery, same MEDDIC sheet, same "who else needs to be involved", just with a longer legal review and a portal you have to upload a PDF into.

It isn't. The rules that decide whether your deal happens are written down somewhere public, they were written before you called, and nobody in the building has the authority to bend them for you. That's genuinely different from private sector, where a motivated VP with budget can shortcut almost anything. In public sector the motivated officer is often the person telling you why they can't shortcut it.

Once you accept that, the job gets easier, not harder. You stop trying to create pressure and start trying to work out the shape of the path. There are only a few possible shapes.

The map: four roles, and only one of them wants to talk to you

Forget "the buying committee". In a council or an agency there are four functions you need to identify, and they behave very differently.

The officer with the problem

This is your entry point and usually your only genuine ally. Service manager, team leader, head of something operational — waste, housing repairs, adult social care, revenues and benefits, highways, licensing. They have a service to run and a backlog or a complaint volume or a statutory duty they're at risk of missing.

They are almost never the person who signs. They are the person who writes the case. If you cannot get an officer to describe your product in their own words to their own manager, you have nothing, regardless of how well the demo went.

The officer's incentive is not growth. It's not efficiency in the abstract either. It's usually one of three things: a service that's failing publicly, an inspection or audit finding they need to close, or a mandate that landed on them from above with no extra headcount. Find which one and you've found the deal.

The manager with the delegated spend limit

Everybody in a public body has a delegated authority — a written amount they can commit without going further up. Heads of service have one. Directors have a bigger one. Cabinet or the board has the top of it.

This is the single most useful thing you can learn on a first call and almost nobody asks for it. Not "what's your budget" — that question gets you a shrug because budget lives in a different place than authority. Ask instead: "Who signs a purchase at this size, and does it sit inside their delegation or does it need to go up?" Officers know the answer instantly. They deal with it every week.

If your deal sits comfortably inside a head of service's delegation, you have a signature deal. If it sits just above it, you have a completely different deal, and you may be better off scoping the first phase down so it lands inside the limit — not as a trick, but because a small proven pilot that one person can authorise is genuinely how most of these programmes start.

Procurement

Procurement is not a blocker and it is not a decision-maker. Procurement is a rules function. They will tell you the route, they will run the route, and they will not tell you which supplier to pick. Reps who treat procurement as an enemy waste months. Reps who treat them as a source of free, accurate information about the process do much better.

The question to ask procurement, once your officer introduces you, is simply: "Given the value and the category, what route would this take?" Direct award off a framework. A quotation exercise with a handful of suppliers. A full open tender. That answer is the entire commercial plan for your next two quarters.

Finance and audit

Somewhere behind all of this is a finance function that cares about one thing: is this spend defensible if someone asks about it in public. Not is it a good deal. Is it defensible. That's a different test and you should write it on a sticky note.

The threshold is the deal, not the price

Every public body publishes its own contract rules — in UK local government they're usually in the constitution or the contract standing orders, and they're on the website. Above certain values you must go out to competition. Above higher values you're into formal tender territory and national publication.

I'm not going to quote you numbers, because they differ by authority, by nation and by category, and they change. Go and read the actual document for the actual body you're selling to. It takes twenty minutes and it will make you the best-informed rep on that account by a distance.

What matters strategically is that the threshold, not your pricing model, determines the shape of your year:

Below the first threshold and you're in signature territory. One officer builds the case, one manager signs, you invoice. This is where your first deal in any authority should live if you can possibly get it there.

In the middle band you'll be asked for quotes alongside two or three others. This is winnable and it's fast, but it means your officer needs to have written the requirement in a way that reflects what you actually do. If the spec reads like a generic RFP, someone else wrote it, and you're column fodder.

At the top, you're into tender. Long, formal, scored, and largely decided before the document is published — by whoever spent the previous months shaping what the authority thinks it needs. If you find out about a tender when it appears on Find a Tender or Contracts Finder, you are already late. Bid it if the scoring genuinely favours you, but understand that you're bidding to learn the account, not to win it.

The other route worth knowing is frameworks. Sitting on the right framework can turn a tender-sized deal into a direct award. Getting onto one is its own project with its own calendar, and it's usually a company decision rather than a rep decision — but knowing which frameworks your prospects prefer to buy through is absolutely a rep job, and it's a great question to ask on a first call.

The financial year governs everything

Public budgets are annual, allocated in advance, and mostly cannot be carried forward. In the UK the local government financial year ends on 31 March; US federal runs to 30 September. Check the one your buyer actually runs on, including devolved and agency variations.

This produces two predictable windows and one dead zone, and if you plan your patch around them you'll be right more often than not.

The first window is the underspend period near the end of the year, when a service realises it hasn't committed money it was allocated. This is real and it moves fast, but it is a bad way to build a business because the deals are small, one-off, and often capital rather than revenue, which rules out subscriptions.

The second and more important window is the budget-setting cycle, which happens months before the year it funds. If your product needs a new line of money that doesn't exist today, your officer needs to be making that case during budget setting, not when you happen to call. Ask them directly: "When does your service submit its budget bids for next year, and what's the deadline for getting something into that?" If the answer is "three weeks ago", you now know your deal is a fourteen-month deal, and you can decide honestly whether to keep it in forecast.

The dead zone is the period just after budgets are set and just after elections or reorganisations, when nobody wants to commit to anything until the new structure settles. You can still do discovery in the dead zone. You should not be forecasting closes out of it.

Why urgency arguments fail and risk arguments win

Every bit of private-sector sales training tells you to build urgency. Cost of inaction, competitor moving faster, discount expiring Friday.

Run that on a council officer and watch what happens. Nothing. They don't get paid more for moving fast. Their competitor is not eating their lunch. And a discount expiring on Friday is, to a procurement-aware officer, actively suspicious — it looks like pressure applied to circumvent a process, which is the exact thing their rules exist to prevent.

What does move public sector buyers is risk. Specifically, downside risk that is already sitting on their desk. The inspection finding. The ombudsman complaint. The statutory deadline. The service that is going to be in the local paper. The backlog that a member is asking questions about at the next scrutiny committee. Officers move quickly on things that are going to hurt if they don't.

And there is a second, quieter driver that I think is underrated: audit-defensibility. Public money spent well but without a paper trail is a worse outcome for an officer than money spent adequately with a perfect trail. So your job is not just to be the best option. It is to make choosing you easy to justify in writing.

Practically that means giving your champion the raw material for their case, in their format, unasked. A one-page summary of what the thing does and what it costs across the contract term. A note on how you were selected — which framework, which comparison, which other suppliers were considered. Confirmation on data protection, on where data is hosted, on your security posture, on accessibility standards. Your standard terms, so legal isn't a surprise in month four. If your officer has to build all of that themselves, they'll do it for one supplier a year, and it probably won't be you.

When I hear reps complain that a public sector deal "went quiet", nine times out of ten what happened is the champion hit the internal paperwork stage, discovered how much work it was, and put it in the drawer. That's not a lost deal. That's a deal you didn't do the work for.

What a reference from a comparable authority is actually worth

More than anything else you have. More than your feature list, more than your pricing, more than your case study PDF.

But the word doing the work is comparable. Councils benchmark against a specific set of peers — similar size, similar type, similar demographics, similar political control sometimes. A metropolitan borough is not comforted by a district council. A county is not comforted by a unitary. A large teaching hospital doesn't care much what a small community trust did.

So stop leading with your biggest logo and start leading with your closest one. "We do this at [large famous city]" often lands worse than "we do this at three authorities about your size in your region, one of which had the same inspection finding you've got". The first sounds like you're too big and too expensive. The second sounds like a solved problem.

And the reference that matters isn't a written quote. It's a phone call between two officers who do the same job. Officers trust other officers. They will believe a peer telling them your implementation was painful but worth it far more than they'll believe you telling them it was seamless. Ask your happy customers whether they'd take a fifteen-minute call from a counterpart — most will say yes, because that's how their sector works and they get value from those calls too.

How to use a peer introduction between authorities

This is the highest-leverage motion in public sector and it's underused because it feels slow.

Officers in the same discipline know each other. They sit on regional groups, professional networks, improvement partnerships and shared-service arrangements. They compare notes constantly and they share suppliers openly, because they're not competing with each other for market share.

So after a successful deployment, don't just ask for a reference. Ask: "Who else in the region has the same problem you had? Would you be comfortable mentioning us next time you see them?" And then follow it up quickly, because borrowed credibility decays. When you do make that call you are not cold, but you are also not warm in the way a private-sector referral is warm — you have about ninety seconds of borrowed trust to spend before the officer decides whether this is a real conversation, which is exactly the situation I've written up in the warm call script for public sector.

The opener I'd use is short and names the peer immediately:

"Hi [name], I'm Tim from [company]. [Peer name] at [authority] suggested I get in touch — we've been working with her team on [specific problem] since [rough timeframe], and she mentioned you're dealing with something similar on [thing]. I'm not going to pitch you on a cold call. Is that actually a live problem for you, or has it been dealt with?"

That last question does a lot of work. It gives them a clean exit, which is exactly why they don't take it.

How long the cycle really is

Longer than you want and shorter than the horror stories.

A small deal inside one manager's delegation, where the problem is already burning and the money already exists, can close in weeks. I've seen it. It's rare but it's not mythical.

A deal that needs a quotation exercise realistically takes a few months from first conversation to purchase order, and most of that is queueing rather than deciding.

A deal that needs new budget takes a full budget cycle plus the procurement route on top. If you are selling something genuinely new to a service, plan for that and forecast honestly. The rep who tells their manager "this is a next-financial-year deal" in month two is trusted forever. The rep who rolls it forward one month at a time for a year is not.

The practical implication for your pipeline is that public sector patches need to be built wide and early. You cannot manufacture a close date. You can have many more live conversations than you'd need in a private-sector patch, and you can be relentless about knowing exactly where each one sits — problem identified, case written, delegation confirmed, route confirmed, money confirmed. Five gates. Every deal is at one of them, and "they're keen" is not a gate.

Opening the first call so you get twenty minutes

Council officers get called constantly, and their default is to route you to procurement to make you go away. So don't open like a vendor.

Open with the problem, in their language, specific to their service, and ask for a small, defined amount of time. Something like:

"Morning [name] — I know I've called you cold, I'll be quick. I work with [service type] teams on [specific problem], mostly authorities around your size. I'm not going to demo anything at you. I've got a couple of questions about how you're handling [thing] at the moment, and if it turns out we're useful I'll ask for twenty minutes. If not, I'll leave you alone. Have you got two minutes now?"

Three things are doing the work there. You've acknowledged it's cold, which buys credibility. You've said what you won't do, which lowers the cost of saying yes. And you've asked for something small and bounded, which is how officers make every other decision in their day.

Then actually ask about their process rather than their pain. "How does that get handled at the moment?" beats "what's your biggest challenge?" every time, because the first one they can answer factually and the second one sounds like a sales question. I've broken the whole thing down turn by turn, including the objections you'll get about procurement and framework agreements, in the government and public sector cold call script.

And when they say "you'll need to go through procurement", don't fold. Say: "Absolutely, and I'll do that properly. Procurement will tell me the route, but they won't tell me whether this is a problem worth solving in your service — that's your call, which is why I rang you first." That line works because it's true, and because it's respectful of a process they take seriously.

What I'd do next

Pick one authority in your patch. Read their contract standing orders. Find the officer who owns the service you're relevant to, not the director. Work out which of the three risk drivers is live for them right now. Then make the call, and make it in a way that gets you twenty minutes rather than a redirect to a procurement inbox.

That call is the whole game, and it's the part reps practise least. If you want reps to walk into those conversations already fluent — handling the "go through procurement" deflection, asking about delegated limits without sounding like they're fishing, spending a peer introduction properly — that's exactly what we built DrillCall for: repeated live reps against the calls that actually decide your quarter, before you spend a real one learning.