An ERP procurement is only the starting gun in a municipal waste company

An ERP procurement takes months: requirements definition, competitive tendering, comparing bids. That's justified, especially in a municipal waste company, where the procurement decision is made within a strictly regulated public-procurement process and has to hold up to scrutiny even afterwards.

But the procurement decision doesn't yet determine whether the project succeeds. The problems that surface during rollout are familiar to anyone who has been part of an ERP project: schedules slip, responsibilities become blurred partway through, and communication turns reactive exactly when it's needed most.

Where rollout problems usually come from

Three recurring causes stand out once an ERP project starts to sprawl:

Responsibilities are left open. Roles are clear during tendering, but once the project starts, it isn't always obvious who decides what — especially once the schedule slips or requirements get refined.

Communication turns reactive. Deviations are often heard about only once they already block the next phase, not while they would still be easy to fix.

The supplier and the customer end up on opposite sides. When something deviates from plan, the situation is easily treated as a problem that "one side has to solve", rather than a shared matter approached together.

In a municipal waste company these risks are amplified further: managing data on customers and properties, regulatory requirements and changing operating models bring complexity that can't all be anticipated at the procurement stage.

What kind of model prevents this

At Softera we follow a clear way of working in every rollout:

• Named responsibilities and one point of contact per area from the very start of the project — not only once something goes wrong.
• An agreed steering-meeting rhythm that stays the same throughout the project, regardless of whether it's proceeding as planned or not.
• Deviations on the table immediately, not once they've grown into a blocker. An open view of the situation is part of the agreed way of working, not an exception.
• An escalation path agreed in advance, in place before it's needed — not something improvised in the middle of a crisis.

The public sector's special features in rollout

A municipal waste company doesn't operate in the same environment as a private company, and that shows in the rollout too:

• Political decision-making and the schedules of the board or council can affect the project's progress, not just its launch.
• The principle of public access means communication and documentation are transparent in a way that doesn't apply to private-sector projects.
• Budget accountability to taxpayers means changes and additional requests must be justified precisely.

A successful rollout isn't luck

A good procurement process creates the conditions, but the outcome is decided by what happens afterwards: how clearly responsibilities are divided, how openly deviations are communicated, and how thoroughly a shared way of working has been thought through before the first bend in the road.

"It isn't luck. It's the result of planning and a model that, at Softera, we aim to have in place even before the contract is signed."