County Revenue Systems Compared: Safaricom, JamboPay, CountyPro, Techno Brain & CountyERP

Published: March 2026  |  Audience: County Procurement Teams, CEC Members Finance, Chief Officers Finance, County ICT Directors

This comparison is based on publicly available information including county tender documents, published case studies, and COB Budget Implementation Review data. It is intended to help county teams ask better evaluation questions, not to make definitive technical claims about competitor systems.

The Market Context

Since 2013, Kenya's county governments have adopted a range of digital revenue collection and financial management tools. The market has evolved from basic M-Pesa Paybill integrations to more sophisticated systems involving GIS-supported property mapping, multi-channel payment integration, and some attempts at ERP-style integration across HR, finance, and procurement.

Despite this investment, Kenya's counties collectively missed KES 19.56 billion in own-source revenue targets in FY 2022/23 — a 34.1% national shortfall. The technology that exists has not closed the gap. Understanding why helps counties make better procurement decisions.

Safaricom / myCounty / ICRMS

What it is

Safaricom, through its myCounty platform and ICRMS-backed systems, has been the dominant county revenue digitisation player. By 2024, Safaricom's solutions were reportedly active across 43 counties for cashless payment systems, with 17 counties having a fully integrated end-to-end implementation. The Kisumu County deployment is a frequently cited case study.

What it covers well

• M-Pesa payment integration — Safaricom's direct control of the Daraja API gives their implementations seamless M-Pesa STK push and Paybill connectivity
• Wide county reach — 43-county footprint means most revenue officers have used or been trained on Safaricom-connected systems
• ICRMS alignment — Safaricom has positioned its offerings as ICRMS-compliant under the 2025 regulations framework

Limitations county teams report

• Revenue collection focus — the core Safaricom/myCounty offering is primarily a payment and revenue collection layer; it does not typically provide integrated HR and payroll, procurement, or financial management capabilities in the same system
• Integration with non-Safaricom systems — counties using Safaricom for revenue collection often have separate HR, finance, and document management systems that do not share data, creating the reconciliation problem ICRMS regulations are designed to address
• Commission structure — some Safaricom-connected implementations involve transaction fees that, over time, create significant commission costs for the county
• Kisumu performance data — despite a high-profile Safaricom/myCounty implementation, Kisumu County achieved only 63% of its OSR target in FY 2022/23, indicating that payment infrastructure alone does not close the revenue gap

JamboPay / Web Tribe

What it is

JamboPay (operated by Web Tribe) was Nairobi City County's primary revenue collection system for a significant period, reportedly processing over KES 40 billion in collections over the life of the contract before the arrangement was replaced. JamboPay also operates in other counties.

What it covers well

• Multi-channel payment processing — JamboPay supports M-Pesa, card payments, and bank transfers at high volume
• Large-county experience — Nairobi's scale provides genuine stress-testing of the platform's capacity
• Business permit and property billing — JamboPay has implemented SBP and property-linked revenue workflows

Limitations county teams report

• Revenue intermediary model — JamboPay operates as a payment intermediary, not a county-owned system; the county does not own the underlying platform or data architecture
• Nairobi replacement — the fact that Nairobi eventually replaced JamboPay's primary role raises questions about long-term suitability as a sole-source revenue platform
• Limited ERP scope — JamboPay is a revenue collection and payment processing tool; it does not address HR and payroll, financial management, procurement, or CIDP planning in an integrated way
• Commission structure concerns — intermediary payment models typically involve per-transaction fees that create long-term TCO disadvantage versus county-owned systems

CountyPro (iLabAfrica / Strathmore University)

What it is

CountyPro is a county ERP developed by iLabAfrica at Strathmore University. It has been deployed in Kiambu, Taita Taveta, and Busia counties, with published reports of 73% revenue increases in some implementations.

What it covers well

• Local development — CountyPro is a Kenyan-developed system with deep familiarity with county government workflows and PFM Act requirements
• ERP scope — CountyPro attempts to address multiple county functions beyond revenue collection, including some financial management modules
• Academic backing — the Strathmore University association provides technical credibility and research support
• Revenue improvement data — the 73% revenue improvement figures, if verified against COB data, would represent strong performance evidence

Limitations county teams should explore

• County reference base — three counties is a smaller reference set than some other vendors; county teams should verify current active deployments and whether implementations are fully live across all modules
• Scale and support capacity — county procurement teams should assess iLabAfrica's support capacity for a new implementation alongside existing county commitments
• ICRMS certification status — verify whether CountyPro has formally been assessed against the 2025 ICRMS Regulations requirements

Techno Brain (RevenueACA)

What it is

Techno Brain's RevenueACA is a revenue management platform with GIS-supported property mapping capabilities. The Kirinyaga County implementation is the most widely cited case study — Kirinyaga achieved 118% of OSR target, one of the best-performing counties in Kenya's national dataset.

What it covers well

• GIS-supported property mapping — integrating geospatial data with the billing system to ensure all rateable properties are in the billing register is the most effective single intervention for land rates underperformance
• Multi-channel payment integration — RevenueACA supports M-Pesa and other payment channels
• Kirinyaga performance evidence — achieving 118% of OSR target is exceptional and attributable in part to GIS-driven billing accuracy
• Pan-Africa presence — Techno Brain operates across multiple African markets, which provides implementation experience and scale

Limitations county teams should explore

• Revenue scope versus integrated ERP — RevenueACA is primarily a revenue management system; counties considering integrated HR, payroll, procurement, and financial management alongside revenue may need to evaluate whether Techno Brain's full suite addresses those requirements
• IFMIS and ICRMS interoperability — verify the specific integrations available with National Treasury systems under the 2025 regulations
• Total cost of ownership — GIS-enhanced implementations typically involve higher initial setup costs; full TCO modelling over 5 years should be requested

Craft Collect (Craft Silicon)

What it is

Craft Collect is a revenue platform from the Craft Silicon group, positioned as an AI-powered county revenue solution with M-Pesa STK push integration and some HR and health module capabilities. It is targeted at Kenyan county governments.

What it covers well

• AI-enhanced revenue features — machine learning capabilities for revenue pattern analysis and anomaly detection
• M-Pesa STK push — direct mobile payment integration for field collection
• Module breadth — Craft Silicon's product range extends into HR and health, providing some cross-module coverage

Limitations county teams should explore

• County deployment evidence — county procurement teams should request verified county reference deployments with COB-corroborated revenue improvement data
• Integration depth — assess whether HR, health, and revenue modules share a unified data model or are separate products integrated via API
• ICRMS compliance evidence — request specific documentation of how the platform meets 2025 ICRMS Regulations requirements

The Shared Gap Across All Standalone Revenue Systems

A pattern emerges across all revenue-focused platforms: they address collection mechanics but not the full governance and compliance context that county finance teams operate in. None of the above vendors — in their publicly available content and county tender responses — currently:

• Explains the devolution governance structure (CEC Member / Chief Officer / COB accountability chain) in their product positioning
• Provides IFMIS and ICRMS interoperability documentation aligned with 2025 regulations
• Addresses ASAL county context — offline-first capability, intermittent connectivity, ICT composite index constraints
• Offers a Kenya-specific ROI methodology using COB benchmark data
• Uses correct Kenyan PFM terminology (CFSP, CBROP, CIDP, IPSAS) in evaluation materials

These gaps matter because the county finance officer evaluating a system needs to explain it in the language of the PFM Act, the COB review process, and the county assembly budget scrutiny cycle — not in generic ERP or fintech language.

The Integrated ERP Alternative

The core argument for an integrated ERP approach (rather than a standalone revenue collection platform) is that the OSR gap has multiple causes: inaccurate billing data, weak collection infrastructure, disconnected finance systems, manual payroll exposure, and poor audit trail integrity. A system that addresses revenue collection but not financial management, HR, and payroll compliance leaves three of those five causes unresolved.

CountyERP is designed as a fully integrated platform covering revenue collection (ICRMS-compliant), financial management (IFMIS-compatible, IPSAS-aligned), HR and payroll (ghost-worker controls, SRC compliance), procurement, and planning — all sharing a single data model. This means revenue data flows directly into CFSP and CBROP preparation; payroll runs from the same employee register that drives HR workflows; and procurement commitments are visible to the finance system before they become pending bills.

For a detailed comparison of how CountyERP addresses your county's specific requirements, book a demonstration. The County Revenue & ROI Calculator provides a financial model for the integrated ERP case using your county's own figures.