Are Councils Difficult Customers?

I've spent years selling technology to local government. So I'll say what a lot of vendors only say quietly over coffee.

Councils can be a hard customer.

And vendors have helped make them that way.

Both things are true. If we want better outcomes for communities, we need to be honest about both.

What makes it hard

Not because of the people. The vast majority of council staff I work with are capable, committed and stretched thin. It's the system around them.

  • Procurement is built to avoid risk, not to create value. Months of process for something that could be piloted in weeks.
  • Decisions sit across many hands. Councillors, executive, IT, finance, service teams, audit. Plenty of people can say no. Very few can say yes.
  • Every council does things its own way. Across Australia and New Zealand, that can mean more than 600 versions of the same process.
  • Vendors are treated as suppliers to be managed, not partners to work with. Contracts are written to assign blame, not share access.

The private sector isn't perfect either. Large companies have their own committees and procurement rules. The difference is pressure. When delay costs revenue, businesses are pushed to decide faster, focus on outcomes and treat good suppliers as partners. In councils, the cost of delay is just as real. It's just harder to see. 

Why councils are careful 

Vendors have earned some of this caution. 

As an industry, we've over-promised. We've locked councils into systems they can't get out of. We've charged for every small change and disappeared after go-live. Councils learnt to be careful because they got burnt. 

Their caution is a rational response to our behaviour. 

Scale plays a part too. Australia has approximately 540 councils, and New Zealand has 78. To a large international software vendor, that's a small market. When growth targets are set offshore, attention follows the bigger deals. Roadmaps drift, support thins out, and councils in Australia and New Zealand slip down the priority list. 

It isn't malice. It's maths. Councils still feel it. 

But it isn't one-sided. Read any Auditor-General report on a failed government IT project, and you'll find the same things. Requirements that were never clearly defined. Weak governance. Vendors who promised more than they could deliver. Both sides assuming the other knew what good looked like. 

These aren't technology failures. They're relationship failures. 

So the question isn't who's to blame. It's how we break the cycle. 

What a real partnership looks like 

The councils we've done our best work with tend to do four things well: 

  • They're clear on the outcome, not just the specification. 
  • They give one person ownership and the authority to decide. 
  • They share the problem early, before it becomes a tender. 
  • They measure success by what the community gets, not only by risk avoided. 

For vendors, the obligations are just as clear: 

  • Say what you can't do. 
  • Build things councils can own and reuse, not things that lock them in. 
  • Stay after go-live. 
  • Price fairly and openly. 

Both sides have obligations. Ownership can't be outsourced. 

Trust is built by delivering 

None of this works without trust. And trust isn't built in a pitch, a tender response or a contract. It's built by delivering. 

One project done well. Then another. Then a vendor who picks up the phone when something goes wrong and fixes it. 

That takes time. It also takes councils willing to give the relationship a chance to get there. 

Too often, the relationship ends before it has had a chance to work. A small issue becomes a reason to retender. A new manager starts again with someone else. Each time, both sides lose the knowledge and goodwill that took years to build. 

Two councils show what the alternative looks like for us. 

City of Greater Bendigo is a longer-term partner. We work closely with their team to support their business plans and priorities, not just to deliver a project and move on. 

Warrnambool City Council worked with us in depth to build the AI Infringement Assistant. It delivered real benefits to the council and its community from day one. And because it was built to be reused, other councils don't have to start from scratch. 

Neither happened in a single tender cycle. Both came from sticking with each other long enough to do something worthwhile together. 

Why it matters 

At Symphony3, more than 55 councils now use our platform connectors. The reason it works is simple: each connector built for one council can be reused by the next. Faster delivery, lower cost, no starting from scratch. That only happens when councils and vendors treat each other as partners rather than adversaries. 

Every month a project stalls, a resident waits longer for a permit or consent. A complaint goes unanswered. A staff member re-keys data that should flow on its own. Councils are under real financial pressure, and every dollar lost to friction is a dollar not spent on services. 

If we build trust through delivery and give the relationship time, councils win, vendors win and, most importantly, communities win. 

Whether you work in a council, sell into one or simply care about your local community, I'd like to hear your view. What's the one change that would make the biggest difference? 

Thomas Hynes, CEO, Symphony3