Skip to main content

Software development

Software that fits the way you work

When no product on the market matches how you work, adapting your teams to the software costs more than the other way round.

The problems we address

What brings you here

Off-the-shelf software imposes its own way of working

Your teams work around the tool with parallel spreadsheets. The official data and the real data drift apart.

Per-user cost explodes as you grow

A subscription per head becomes unreasonable beyond a certain volume, especially for occasional users.

An existing application can no longer be maintained

Abandoned technology, the original developer gone, no documentation. Every change becomes risky.

The application does not work offline

In the field, in poorly covered areas, the tool becomes unusable exactly when it is needed most.

Deliverables

What you receive

  • Business web applications (back office, portals, extranets)
  • Android and iOS mobile applications
  • Multi-tenant SaaS platforms
  • Client portals and partner areas
  • Marketplaces and matching platforms
  • Internal management systems (stock, field work, case files)
  • Modernisation and takeover of existing applications
  • APIs and integration services

Benefits

What it concretely changes

A tool the teams actually use

Designed with the end users and tested by them before going live.

No per-user cost

You pay for the build and the hosting, not a subscription proportional to headcount.

A base that accepts change

Automated tests on the critical rules, documented code, and an architecture that lets a module be added without redoing everything.

You own the code

The repository is handed over to you. Another provider can take it on.

Features

What we can do in this area

  • User-experience design and prototyping
  • Database modelling and migration
  • Fine-grained role and permission management
  • Offline mode and deferred synchronisation
  • Data import and export in your partners' formats
  • Document generation (quotes, invoices, reports, certificates)
  • Email, SMS and push notifications
  • Search, filters, sorting and pagination over large volumes
  • Action logging and change history
  • Automated tests and continuous integration

Our approach

How we go about it

  1. Journeys

    We describe the user journeys before the screens, and the screens before the code.

  2. Data model

    The relational schema is laid down and validated early: it is the part that costs most to fix afterwards.

  3. Short iterations

    A version installed every two weeks on an acceptance environment you can reach.

  4. Business acceptance

    Your users test on real cases and report back through a single, tracked channel.

  5. Go-live

    A planned switchover, verified data migration, and a rollback procedure ready.

Architecture

How it is built

We favour simple, explicit architectures: one application service, one relational database, queues for asynchronous work. Complexity is added when it is justified, not on principle.

  1. Interface

    A web application rendered on the server for search visibility and display speed; a native or cross-platform mobile application depending on the use.

  2. API

    A documented, versioned interface with input validation and uniform error handling.

  3. Business domain

    Business rules kept apart from HTTP transport and from the database, and therefore unit-testable.

  4. Persistence

    PostgreSQL with versioned migrations, integrity constraints and indexes matched to the queries actually run.

  5. Deferred processing

    A job queue for sending email, exports, imports and long-running work.

  6. Operations

    Structured logs, metrics, alerts and restorable backups that are actually tested.

Technologies

Relevant technologies

  • TypeScript
  • JavaScript
  • PHP
  • Java
  • Python
  • Next.js
  • React
  • Angular
  • Vue.js
  • Node.js
  • NestJS
  • Express
  • Laravel
  • Symfony
  • Spring Boot
  • React Native
  • Expo
  • Flutter
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Socket.io
  • GraphQL
  • Docker
  • Nginx
  • Sentry
  • GitHub Actions
  • Mobile Money
  • PawaPay
  • Stripe

Frequently asked questions

Frequently asked questions

Custom software development

What does custom software cost?
It depends on how many processes are covered and which integrations are needed. We produce a costing after a framing phase, and split the work into batches so you can stop or continue at each stage.
Who owns the source code?
You do. The repository is transferred to you and the technical documentation comes with it.
Can you take over an application built by someone else?
Yes, after a technical audit that assesses the state of the code, the outdated dependencies and the cost of taking it on. We will tell you honestly if a partial rewrite would be cheaper.
Will the application work on an unstable connection?
We design a degraded mode when the use demands it: actions queued locally, synchronisation on reconnection, and explicit conflict resolution.

Africa Tech Services

A project around “Software development”?

A first thirty-minute conversation, with no commitment. We will tell you plainly whether we are the right partner — and if not, we will point you elsewhere.