Skip to content
CodeWave Systems

Our work

Software we've built for real-world problems.

From payment platforms and business management systems to SaaS products and operational software, our work focuses on making complex processes simpler.

Discuss a project

Selected projects

Product

Payments & business operations · SaaS platform

MVerify

Problem
Staff at counters and in the field could not reliably confirm that an M-Pesa payment had actually arrived before releasing goods, and management had no single view of transactions across branches.
Solution
A verification platform with a web dashboard and a staff Android app that confirms Till and PayBill transactions, keeps transaction history per branch and supports STK Push requests.

Centralized transaction monitoring across branches

  • PHP
  • Laravel
  • REST APIs
  • Android
  • MySQL
View Case Study
Platform

Insurance · SaaS platform

ClaimTrace

Problem
Investigation firms tracked cases, assignments and reports across spreadsheets, email and chat, leaving insurers waiting for status and managers without a clear view of workload.
Solution
A tenant-based platform where investigations move through defined workflows, investigators are assigned and tracked, insurers and claim managers see status directly, and reporting and payroll come from the same data.

Automated investigation workflows with insurer-facing status

  • PHP
  • Laravel
  • Vue
  • Inertia
  • Tailwind CSS
View Case Study
Platform

Property management · SaaS platform

Rental Management SaaS

Problem
Landlords and agents managed units, tenants, rent, utilities and maintenance across ledgers, M-Pesa messages and phone calls — with no clear picture of who had paid and what was outstanding.
Solution
A subscription platform covering properties, units, tenants, rent invoicing with M-Pesa payments, utilities, maintenance requests, payroll and role-based access for owners, managers and caretakers.

Automated rent collection and tenant administration

  • PHP
  • Laravel
  • Vue
  • Tailwind CSS
  • MySQL
View Case Study
Representative engagement

Retail & distribution · ERP & POS

POS & ERP Systems

Problem
Sales, stock, purchasing and customer records lived in separate tills, spreadsheets and notebooks, so management could not see accurate stock levels or margins across branches.
Solution
A connected POS and ERP system: fast tills with M-Pesa and card payments, live inventory, purchasing and suppliers, customers, user roles and consolidated reporting across every branch.

Unified business reporting across branches

  • PHP
  • Laravel
  • ASP.NET Core
  • Vue
  • Tailwind CSS
View Case Study
Selected project

FinTech / payments · Payments

Wallet / Payment Platforms

Problem
Moving money through M-Pesa, cards and partner APIs left transactions in uncertain states — callbacks missed, retries handled manually, and reconciliation done by hand at month end.
Solution
Payment platforms with explicit transaction workflows (initiated → pending → confirmed → settled), double-entry ledgers, automatic reconciliation and partner APIs — across M-Pesa STK Push, Stripe and PayPal.

Every transaction traceable from initiation to settlement

  • ASP.NET Core
  • REST APIs
  • WebSockets
  • SQL Server
  • Redis
View Case Study
Representative engagement

Cross-industry · Custom software

Custom Business Applications

Problem
A process that mattered — approvals, requests, field data, records — ran on spreadsheets, paper and chat, with no audit trail, no reporting and no way to see where things were stuck.
Solution
Purpose-built applications with role-based screens, approval workflows, document generation, notifications and reporting, integrated with the systems already in use.

Reduced manual processes with a full audit trail

  • PHP
  • Laravel
  • ASP.NET Core
  • Vue
  • Blazor
View Case Study

Outcomes are described qualitatively. We publish figures only when a client has verified them and agreed to their release.

What the work has in common

Different industries. The same engineering discipline.

Whether the system verifies M-Pesa payments, tracks insurance investigations or runs a supermarket till, it is built the same way: from the real process, on a sound data model, with integrations and support treated as part of the job.

  1. 01

    Starts with the workflow

    Every system above began with time spent alongside the people who run the process.

  2. 02

    Modelled to grow

    Accounts, branches, tenants and roles are designed in from the first release, not bolted on.

  3. 03

    Integrated, not isolated

    M-Pesa, cards, SMS, accounting and partner APIs connected with reconciliation and retries.

  4. 04

    Supported after go-live

    Each system runs under monitoring and an ongoing support agreement.

Similar problem?

Have a process that looks like one of these?

Tell us how it runs today. We will show you which of these systems is closest — and what a version built for you would involve.

Start a ConversationSee our services