DrillCall

Industry playbooks

Government / Public Sector sales call playbooks

Your buyers are running services on systems inherited from an amalgamation, watching FOI clocks tick toward a deemed refusal, and knowing that anything over the procurement threshold means nine months of open tender and a report to Council. Practise here and you learn to handle the tender wall, the onshore-hosting interrogation and the 'come back at budget bid time' deferral without losing the deal or your champion.

Every call type for Government / Public Sector

Scripts, sample dialogue, objection handling and a live AI buyer for each one.

Who you're calling

In Government / Public Sector, the people who pick up are council and agency decision-makers. The titles you will actually reach:

  • Director of Corporate Services
  • Chief Information Officer (Local Government)
  • Manager, Customer Experience / Customer Service
  • Manager, Governance, Risk & Compliance
  • Records & Information Manager (FOI/RTI Coordinator)
  • General Manager / Chief Operating Officer
  • ICT Procurement & Contracts Manager

What keeps them up at night

Name one of these in your first thirty seconds and you have earned the rest of the call.

  • The service-request backlog lands in the Mayor's inbox

    Potholes, illegal dumping, overhanging trees, barking dogs — logged at the counter, by phone, through three different web forms and a general enquiries mailbox that nobody owns. When a request sits for six weeks the ratepayer stops emailing the depot and emails the Mayor and their ward councillor instead. Now it's a councillor request with a due date, a briefing note, and someone in Corporate Services chasing the works crew for a status update that doesn't exist in any system. The buyer's real pain isn't the pothole — it's that they cannot tell the Mayor what's happening with it before the next Ordinary Meeting.

  • FOI/RTI requests eat staff weeks against a statutory clock

    A single request can mean trawling shared drives, four mailboxes, and a records system from 2011, then redacting third-party personal information page by page. The clock is statutory — 20 or 30 business days — and blowing it means a deemed refusal, an Ombudsman or Information Commissioner review, and a line in the annual report. One or two determined applicants (a journalist, a residents' action group, a disgruntled former contractor) can consume a 1.5 FTE records team for a quarter.

  • Legacy systems inherited from amalgamation

    Three former shires merged, and they still run two property and rating systems, an asset management platform nobody has been trained on since the vendor was acquired, and a request log that is genuinely a shared spreadsheet in the depot. Nothing talks to anything. Address data doesn't match between systems so the same ratepayer exists four times. Any new system has to sit on top of this mess, not assume it's been cleaned up first — and the person who understood the integration left in the last voluntary redundancy round.

  • Everything above threshold goes to open tender, and the timeline is brutal

    Above the procurement threshold it's a public RFT: specification written, probity advisor engaged, advertised for 21–28 days, evaluation panel scored against weighted criteria, then a report to Council for resolution. Six to nine months minimum, and the sponsor has to defend the business case to a Council that just deferred the pool upgrade. Champions are exhausted before they start and often quietly hope you'll tell them there's a panel arrangement or a threshold-splitting option — which there usually isn't, and shouldn't be.

  • Personal and political risk aversion

    Nobody in a council gets promoted for a system that worked. They get named in an audit finding, an Ombudsman report, or a front-page story when one doesn't. The buyer is weighing a modest efficiency gain against the possibility of being the officer who signed off on an offshore-hosted platform that leaked ratepayer data. Their default is 'show me another council my size, in my state, who's live and will take my call' — and if you can't, the decision defers to next budget.

  • The budget bid window is narrow and immovable

    Operational money is committed. Anything new is a budget bid drafted around February–March, argued at the workshop, adopted with the annual plan in June, and available from 1 July. Miss it and the conversation is genuinely dead for eleven months — not slow, dead. Reps who don't know where the buyer sits in that cycle waste an entire quarter demoing to someone with no money and no path to money.

What they'll push back with

The objections that come up on nearly every call, and a response that keeps the conversation alive.

“We can't just buy this. Anything over our procurement threshold has to go out to public tender.”
Understood, and I'd be worried if you told me otherwise. Two questions: what's the threshold, and is there an existing panel or whole-of-government arrangement we could be listed under? If neither, the useful work right now isn't a proposal — it's helping you build a defensible specification and business case so that when it does go to market you're comparing apples to apples. I'll give you the functional requirements, the records-compliance clauses, and the evaluation criteria we'd expect to be scored against. If a competitor writes a better spec than we do, we deserve to lose it. Can we also scope a below-threshold pilot in one service area so you're testing rather than guessing before the RFT is written?
“Data sovereignty is non-negotiable. It must be hosted onshore with government-grade security.”
All data resides in onshore regions, no offshore replication, no offshore support access — I'll send the hosting attestation and our assessment report before we go further. Who's your assessor: does this need to clear an internal security review, or does your ICT strategy require a formal certification level? I'd rather bring that person into the conversation at week one than have them kill it at evaluation. And separately from hosting — records disposal, retention schedules and export on exit are usually where councils get burned, so I'll show you exactly how records are captured, sentenced and handed back if you ever terminate.
“There's no money this financial year. It'd have to be a budget bid.”
That's fine, and it's actually the conversation I want to have. When do bids need to be with the Executive — February? Then we've got eight weeks to build the numbers with you, not for you. What I need from you is the current cost: FTE hours on FOI processing, overdue request volumes, the cost of the Ombudsman matters last year. If we can't build a bid that survives a hostile question from a councillor, it shouldn't get funded. What's the format your Executive expects, and who else's bid are we competing against internally?
“Which councils our size are already using this? I want to speak to them.”
Fair, and I'd ask the same. I'll give you three references — one post-amalgamation authority with a similar staff headcount, one in your state so the FOI legislation matches, and one that went to open tender so they can tell you what the process was actually like. I'd also encourage you to talk to their records manager, not just their CIO, because the records manager will tell you what went wrong. Do you want me to arrange a site visit? Most of our best decisions came from an officer spending a morning watching another council's contact centre.
“We've got two rating systems and an asset platform from before the amalgamation. Nothing here integrates with anything.”
That's the normal starting point, not the exception. We don't require you to consolidate first — we sit above and pull identity and property data via API or scheduled file, and we handle duplicate address records rather than assuming they've been cleansed. But I'm not going to promise integration I haven't scoped. Can you get me your CIO or the systems owner for 45 minutes so I can look at what's actually there? If one of those systems can't be integrated safely, I'd rather tell you now and phase it than discover it in implementation and blow the go-live.
“We're heading into caretaker period before the election. Nothing's getting decided.”
Agreed — no decision should be made in caretaker, and I'm not going to push one. But caretaker is when your team has the most capacity for the unglamorous work: mapping the current request workflow, quantifying the FOI hours, drafting the spec. If we do that now, you're ready to move the week the new Council is sworn in instead of starting from a blank page. Who's likely to be the sponsor on the other side of the election, and will the executive structure survive it?
“My staff are already stretched. They don't have capacity for a system implementation, and the union will have a view about workload.”
Then the implementation plan has to be honest about who does what and when. Realistically we need about a day a week from a records officer and a customer service team leader for eight weeks — that's it, and if you can't commit that, we should delay rather than fail. On the workload point: bring the union in early and be straight that this changes how requests are logged, not headcount. The councils that hid that had a rough time. What's your consultation obligation for a system change like this?

Their language

Use these the way they do. Getting one wrong costs more credibility than getting none of them right.

Jargon

  • Procurement threshold (the dollar figure above which open tender is mandatory — differs by state and by council policy)
  • RFT / RFQ / EOI (Request for Tender, Request for Quote, Expression of Interest)
  • Panel arrangement / preferred supplier list (pre-approved vendors you can buy from without going back to market)
  • Probity advisor (independent overseer of the tender process; can rule your contact with the buyer improper)
  • Delegations / delegated authority (what an officer can sign versus what needs a Council resolution)
  • Council resolution and Ordinary Meeting (decisions carried at a public meeting with minutes and a report)
  • Caretaker period (pre-election window where no significant decisions are made)
  • FOI / GIPA / RTI (Freedom of Information and its state equivalents — with statutory turnaround clocks and deemed refusals)
  • Records disposal authority / retention and sentencing schedule (what must be kept, for how long, and how it's legally destroyed)
  • Data sovereignty and onshore hosting (data and support access must remain in-country)
  • Business case / gate review / budget bid (the internal funding path; nothing happens outside it)
  • Capex versus opex (subscription models often break a council's capital funding assumptions)
  • Amalgamation (forced council merger — the origin of most legacy system chaos)
  • Ratepayer (not 'customer' — they fund you and they can vote you out)
  • Councillor request / mayoral referral (a service request with political weight and its own SLA)
  • Unqualified audit opinion (the clean audit result the Executive protects at all costs)

Metrics they are measured on

Percentage of FOI/RTI requests determined within the statutory period (20 or 30 business days) — reported publicly, Open service requests and the count overdue against service level, by category and by ward, Average days to close a request — pothole, tree, animal, planning enquiry each tracked separately, Contact centre call abandonment rate and average speed of answer, First-contact resolution percentage and percentage of requests lodged through digital channels versus phone or counter, Number of Ombudsman or Information Commissioner complaints, reviews and adverse findings per year, Community satisfaction survey score for 'ease of contacting council' and 'responsiveness to requests', Cost per transaction / cost per service request, and open internal and external audit findings

Related industries

Buyers with adjacent pressures, and the same call types against them.

Practise against a Government / Public Sector buyer

A live AI prospect with Government / Public Sector context — their pressures, their jargon, their objections. They talk back, they interrupt, and they can hang up on you. You get a scored breakdown when the call ends.

Start a roleplay