Municipalities carry statutory duties that spreadsheets were never built for: an indigent register that must survive audit, a cemetery that must be findable, an asset register that feeds mSCOA. We build the systems that carry them.

The work is the same across the country, and so are the things that go wrong: registers nobody trusts, records that cannot be produced at audit, and services delivered to people the system cannot verify.
Free basic services go to households that qualify. That means identity verification against Home Affairs and a register that can prove why each name is on it.
MFMA and the Auditor-General ask for evidence, not assurances. Every approval, change and payment needs a trail that was written at the time.
Burial registers, asset histories and applications survive the officials who created them. Paper and personal spreadsheets do not.
Citizen data is governed by POPIA and the national cloud policy. Our government systems run in AWS Cape Town, not offshore.
Each system runs on its own, and they share one login and one citizen record when a municipality takes more than one.
Applications, means testing, Home Affairs verification and the free basic services register, with the approval trail an audit asks for.
Plot allocation, burial records, grave search and exhumations, with mSCOA-aligned finance and a map of every section.
The asset register through its whole life: acquisition, condition, maintenance, depreciation and disposal.
Advertise a post, shortlist against the criteria you published, and keep the record of how each decision was reached.
Log a fault, route it to the department that owns it, and tell the resident what happened without them phoning back.
Run procurement from advert to award, with the evaluation record and the documents held in one place.
What a municipality usually asks for before a committee meeting.