1. Adoption risk: who has to be persuaded
This is the largest hidden cost and the most common cause of failure. A municipal portal or council-branded app starts with zero users, and getting residents onto it is a communications budget nobody puts in the tender. A platform used by 40 people in a city of 100,000 produces no useful data, and after two years of that it gets quietly dropped.
Ask directly: on the day we go live, how many residents already have this installed? If the answer is zero, the real project is not the software, it is the adoption campaign.
CleanSpot inverts this. The citizen app is free, public and useful on its own, so reports typically already exist in a territory before the council is a customer. That is worth verifying rather than believing. Ask us to show you what is already on record inside your boundary.
2. Does it dispatch, or only collect?
A reporting front end that emails your team is not a work management system. If reports land in a shared inbox and someone re-keys them into another system, you have added a step, not removed one.
What to test: can a report be assigned to a named person or an external contractor, reassigned, tracked through states, and closed with the outcome visible to the resident who raised it? That last part matters more than it sounds. Silence after reporting is the single biggest driver of people not reporting again.
3. Recurrence, not just tickets
Any system will tell you how many reports you received. Few will tell you that the same forty metres of one street generated eleven of them over six months.
That distinction is the difference between a ticketing tool and a planning tool. A ticket closes when the truck passes. A location keeps its history, and the history is what justifies a container, a change of collection frequency, or signage. When evaluating, ask to see the same physical spot reported repeatedly and what the system does with that.
4. Scope: waste operations vs citizen reporting
These are two different product categories that procurement sometimes bundles into one tender, and buying the wrong one is an expensive mistake.
Waste operations platforms handle route optimisation, container telemetry, weighing and billing. Citizen reporting platforms handle what residents see and report, and the dispatch that follows. Some vendors do both; most do one well and the other as a checkbox.
CleanSpot is squarely the second. We do not do routing, weighing, billing or bin sensors, and we would rather say that at the start of a procurement than in month four of one.
5. Data protection, settled early
For a European authority this is frequently what stops a pilot becoming a contract, and it is cheaper to answer in week one.
Where is data hosted, who is controller and who is processor, what is public and what is not, and can a resident export or delete their own data? Get the answers in writing before the pilot, not during legal review.
6. Total cost, including the parts not in the licence
- Licence or subscription, and what scales it: population, users, report volume
- Integration work, if reports must reach an existing back office
- The adoption campaign (see 1), which is often the largest line and rarely quoted
- Staff time re-keying between systems if dispatch is not integrated
- Exit: can you export your data, in a usable format, if you leave?
The context you are buying into
Portugal produced 5.27 million tonnes of urban waste in 2024, 517 kg per inhabitant, the EU-27 average, with 54% still going to landfill, down 5 percentage points on 2023 (APA state of the environment report).
Those are system-level numbers. A citizen reporting platform does not move them directly. What it does is tell you where the system is failing at street level between collections, which is information most authorities currently do not have in any usable form.
Sources
What does CleanSpot cost?
An annual dashboard subscription priced by population band. Tell us your municipality size and we will quote.
Can it run alongside our existing system?
Yes. It can cover the citizen-facing and dispatch side while an existing back office continues to do what it does. Tell us what you run and we will be straight about where it fits and where it does not.
Do you do route optimisation or bin sensors?
No. That is waste operations, a different product category. If that is the requirement, we are not the right vendor and will say so.
How do we evaluate adoption risk fairly?
Ask every vendor how many residents in your territory already use their app today, and ask them to show you. It is a question with a checkable answer, and it separates platforms that need an adoption campaign from ones that do not.