Service

Custom business software

A platform built around your organisation, not a package you have to work around.

The problem

What we see most often.

The package does not fit your rules

Your academic regulations, your approval chain or your chart of accounts do not fit the boxes provided. You end up adapting your procedures to the software, when it should be the other way round.

Your data lives in ten files

Every department keeps its own table. Nobody holds the consolidated figure, and when management asks for it, it takes three days — and two different versions circulate.

You depend on a developer you cannot reach

The developer has left, the code is undocumented, nobody knows where the passwords are. The smallest change becomes a project.


Our answer

A platform built around your organisation, not a package you have to work around.

Most software sold in the DRC was designed somewhere else, for organisations that work differently. So people adapt it, work around it, and keep spreadsheets on the side “for what the software cannot do”. Two years later, the real information system lives in those spreadsheets.

We take the problem from the other end. We start by watching how your organisation actually works — not how the org chart says it works — then we build the tool around that reality.

It takes longer at the start. It is also why a platform is still in use five years later.

Deliverables

  • A written specification, approved before the first line of code
  • Mockups of every screen, approved before build
  • Complete source code, in a Git repository you own
  • Technical documentation: architecture, installation, operations
  • A user manual in French, with screenshots
  • Training for your teams, and support through the first real cycle
  • Migration of your existing data, with quality checks

How it runs

Step by step.

STEP 01

Observation

We spend time on site, watching how the work is really done. This step always uncovers cases the original brief left out.

1 to 2 weeks
STEP 02

Scoping

Written specification, agreed scope, firm schedule and budget. You sign off on what you are going to receive.

1 to 2 weeks
STEP 03

Design

Architecture, data model, mockups of every screen. You approve before a line of code is written.

2 to 3 weeks
STEP 04

Build

Regular releases you test as we go. Never a tunnel: you watch the platform grow.

6 to 12 weeks
STEP 05

Rollout

Go-live, data migration, on-site training, and a period of running old and new in parallel.

1 to 2 weeks
STEP 06

Support

We stay until the first complete cycle has gone through successfully. Then corrective and evolutionary maintenance.

Ongoing

Our commitment

We do not publish prices. We publish a process.

Every project is different: an honest quote means having understood the need first. Here is what you can count on when you write to us.

The first conversation is free

Scoping, analysing your need and writing the proposal cost you nothing. We start charging when we start producing.

An answer within 48 working hours

Written by someone on the team, not by a robot. And if your request falls outside what we do well, we would rather tell you straight away.

A readable quote within 5 days

Line by line, with the estimated time next to each item. You will know what you are paying for, and why it costs that.

The quote is the price

The signed figure is the invoiced figure. If the scope changes along the way — it often does — we price it and you decide before anything is built.

Frequently asked

What people ask us most.

How long does a complete business platform take?

Three to six months for a typical scope, including observation and data migration. A single module can ship in six to eight weeks.

Who owns the code?

You do, from day one. The Git repository is created in your organisation's name, not ours. You can hand it to another supplier at any time.

What if our needs change along the way?

They always do. Minor changes are absorbed in the fixed price; a change of scope is priced in a written amendment and accepted before it is built.

Do you work with our IT team?

Yes, and we prefer it. Your developers join the code reviews and receive the full documentation. The goal is that you can maintain the platform without us.

What if our internet connection is poor?

We design for that constraint. Several of our platforms run entirely on a local network, syncing again on their own when the link comes back.

Let's talk about your project

Tell us where you stand today.

Free first conversation, an answer within 48 working hours, a detailed quote within 5 days.

Custom business software in Kinshasa — Enywork SARL