Financial systems · Business automation

We build the software that moves money, and proves it stayed balanced to the cent.

Doitrix Tech Labs is a software studio in Nairobi. We design, build and run financial systems, integrations and the automation that quietly does the work nobody wants to do by hand.

Start a project See how we work
Reconciliation
same-day
First reply
~8 min
Releases
audited

The three things most of our work comes down to.

Systems that hold money correctly, the work around them that should not be done by hand, and the connections between them and everything else a business already runs.

Financial systems

Ledgers, payments and the guarantees they rest on.

  • Double-entry ledgers where an unbalanced transaction cannot be written
  • Payment flows with idempotent retries and full replay
  • Daily reconciliation against bank and processor statements
  • Audit trails that satisfy a real auditor, not just a checkbox

Business automation

The work nobody should be doing by hand.

  • Approval workflows with roles, limits and a recorded decision trail
  • Scheduled reconciliation, statements and regulatory exports
  • Document and data pipelines that fail loudly rather than silently
  • Internal tools your finance and ops teams will actually use

Integrations

Two systems that were never meant to talk.

  • Bank files, card rails, mobile money and processor APIs
  • Webhook intake that survives outages and replays cleanly
  • ERP, CRM and accounting sync with conflict rules you choose
  • One contract per integration, versioned and tested against

Custom builds, consultancy, and support for years after launch.

All six services

The work itself

Money code, written so it cannot fail quietly.

A rounding error is not an option here. The rules that keep a ledger honest are written as code and run as tests. This is the real thing, typed out.

ledger/DoitrixLedger.ts
An unbalanced transaction cannot be written.

How we work

From a rough idea to something you run.

  1. 01 · Understand the work

    Before anything is designed we learn how your business actually runs: who approves what, where the money is recorded, and which spreadsheet everyone secretly depends on.
    • Customer reach

  2. 02 · Make it precise

    The conversation becomes structured requirements, each small enough to build and specific enough to test. Scope stops being a feeling and becomes a list you can sign.
    • Requirements

  3. 03 · Design the system

    Services, data model, and the rules that must always hold. These are the expensive decisions to reverse, so they are made in the open and against your delivery date.
    • Design

  4. 04 · Build and prove it

    Every rule becomes a test, running on every commit. The pipeline blocks a release on a red run, and there is no override button.
    • Implementation
    • Testing

  5. 05 · Harden and ship

    Security review, server configuration, and the audit trail wired in. The deploy is repeatable and every approval is recorded, so we can say exactly what changed.
    • Acceptance
    • Deployment

  6. 06 · Run it with you

    Monitoring, on-call, patching and the reconciliation that surfaces drift the same day. Most of a product's life is this part.
    • Monitoring
    • Maintenance

Want to see it, not read it?

Walk the customer journey

The toolkit

Chosen per problem, not per habit.

No house framework we force on every job. Each ring is a discipline, each dot a tool we reach for when it fits. Choose a discipline to see its tools.

Disciplines

  • TypeScript
  • Go
  • Rust
  • Python
  • SQL
  • PHP

Have a process that should run itself?

Tell us how it works today, who touches it and where it slows down. We will tell you what we would build first, and why.

Talk to us

Median first reply of 8 minutes in business hours.