The verdict in three sentences
For a 25,000-resident municipality in the Greater Toronto Area that receives 600 service requests a month, phone calls and a shared inbox no longer cut it: requests get lost, response times go unmeasured and council has no consolidated view. There are two routes in 2026: a subscription 311-style platform at roughly 5,000 to 18,000 CAD a year, or a custom tool at 30,000 to 65,000 CAD procured through a competitive quote process. The right choice depends on your workflows (roads, waste, streetlights) and your integration needs, with a realistic timeline of 12 weeks.
Subscription or custom: what a municipality actually pays
Citizen relationship platforms sold to local governments price by population and modules. They deploy quickly but impose their own categories and screens. A custom build starts from your real workflows: who receives, who approves, who goes on site, who replies to the resident.
| Criterion | Subscription platform | Custom tool (competitive quote) |
|---|---|---|
| Annual or upfront cost | 5,000 to 18,000 CAD a year (2026 market estimate) | 30,000 to 65,000 CAD one-off (market estimate) |
| 5-year cost | 25,000 to 90,000 CAD | 30,000 to 65,000 CAD + maintenance 4,500 to 9,000 CAD a year |
| Request categories | Configurable within a fixed frame | Mirrors your public works divisions |
| Geolocated reporting app | Often included, vendor branding | Municipal branding, photo and GPS |
| GIS and public works integration | Limited connectors | Dedicated connector to your GIS |
| Data ownership | Vendor contract, exit terms to negotiate | Data and code owned by the municipality |
| Time to go live | 4 to 8 weeks | 12 weeks |
Procurement thresholds matter too. Under most Ontario municipal purchasing bylaws, a project of this size goes through an invitational or open competitive process, typically with at least 3 bidders. Write the specification around request workflows rather than a feature checklist.
Response time: the table that wins over council
The real gain is not the software, it is the measurement. Most municipalities of this size cannot say how long a pothole takes between the call and the repair. With a tracked workflow, every request gets a timestamp at every step.
| Request type | Estimated monthly volume | Average time before | Target time after | Main gain |
|---|---|---|---|---|
| Roads (potholes, sidewalks) | 180 | 21 days | 10 days | Crews grouped by neighbourhood |
| Waste (illegal dumping, graffiti) | 220 | 7 days | 3 days | Geotagged photo, no scouting trip |
| Streetlights | 90 | 14 days | 6 days | Direct dispatch to the contractor |
| Parks | 60 | 18 days | 9 days | Seasonal scheduling |
| Parking and other | 50 | 10 days | 5 days | Automatic routing to the right division |
| Total | 600 | 14 days on average | 6 days on average | Every resident gets a reply |
These are 2026 orders of magnitude seen in comparable municipalities, not a guarantee. They help set contract targets and give council a measured report after 6 months.
What a well-scoped custom tool includes
A realistic 12-week scope has four building blocks. A reporting portal and app: the resident picks a category, takes a photo, GPS is attached and a tracking number is issued. A staff back office: request queue by division, assignment, status changes, internal notes. A field module on smartphone for public works crews, with before and after photos. A dashboard for the CAO and council: volumes, response times, overdue requests by ward.
Hosting stays in Canada, aligned with MFIPPA privacy rules, and data is kept minimal (name, contact, location). AODA and WCAG 2.0 AA accessibility for the resident portal must be in the specification from day one.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Illustrative example: Sarah, CAO of a 25,000-resident town in the Greater Toronto Area. Her front desk spends about 8 minutes per service call, entry and dispatch included. Of 600 requests, 70% come by phone, that is 420 calls and 56 hours a month. If the app absorbs half of those calls, the town frees 28 hours a month, or 336 hours a year, about 0.2 of a front desk position (roughly 13,000 CAD loaded). Add fewer scouting trips, estimated at 2 avoided per day, and a 50,000 CAD custom build pays back in 3 to 4 years while remaining municipal property.
FAQ
Do we have to run a formal procurement?
Yes, under most municipal purchasing bylaws a project above about 25,000 to 50,000 CAD requires a competitive process with several bids. A 30,000 to 65,000 CAD build usually goes through an invitational quote or an open RFP.
Does the reporting app need to be in the app stores?
Not necessarily: an installable web app (PWA) covers about 90% of use cases and avoids two store releases to maintain. Store publishing adds roughly 4,500 to 9,000 CAD and a developer account in the municipality's name.
How do we stop staff from falling back on phone and email?
Every channel (front desk, email, app) feeds the same queue, and the front desk logs a call in 2 minutes in the back office. Two half-day training sessions per division are enough for a team of 30 staff.
What happens if the vendor goes out of business?
With a custom build, source code and data are handed over to the municipality, which must be written into the contract. Maintenance can then move to another provider without a rewrite.
What running budget should we plan?
Plan for hosting, around 70 to 200 CAD a month, plus corrective and evolutive maintenance. At Kolonell, maintenance runs from 35,000 to 120,000 FCFA a month (50 to 180 EUR).
Let's scope your project. Share your request categories, your divisions and your volumes: we quote a custom tool in the 4,000,000 to 7,000,000 FCFA band (6,100 to 10,670 EUR) for a standard scope, delivered in 12 weeks. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
