Skip to main content

About

A team, a method, clear commitments

Your technology partner: we design, build, integrate, deploy and evolve the systems that run your operations.

Address
Pointe-Noire, Republic of the Congo
Languages
Français · English

Who we are

A technology partner rooted in Pointe-Noire

Your technology partner: we design, build, integrate, deploy and evolve the systems that run your operations.

Technology that makes growth simpler.

What our clients are after

  • Automate repetitive work
  • Bring operations together
  • Cut down on errors
  • See what is actually happening
  • Make decisions easier
  • Strengthen security
  • Connect equipment, software and people
  • Reduce operational downtime

The team

The faces behind your projects

A young, deliberately small team, extended by a network of specialists brought in as a project requires.

  • Elisée NGOLO OSSERE

    Elisée NGOLO OSSERE

    Cybersecurity · Data science

  • Gloire Rhesa BITEMO

    Gloire Rhesa BITEMO

    Offensive security · Full-stack development

  • Emmahüs Casimir ONDONGO

    Emmahüs Casimir ONDONGO

    Artificial intelligence · Natural language processing

  • David

    David

    Software architecture · Full-stack development

  • Hilarion BAMA

    Hilarion BAMA

    Business development · Communication

Our method

Clear stages, delivered in increments

Every stage produces identified deliverables. At any point you know what has been done and what remains.

  1. 1 to 2 weeks

    Understand

    We start from your actual operations, not from a theoretical specification. Field interviews, process observation, an inventory of the tools already in place and of what genuinely gets in the way.

  2. 1 to 2 weeks

    Frame

    We turn the findings into a scope: what the first batch covers, what it deliberately leaves out, and what it will cost. You stay free to continue or stop there.

  3. 2 to 4 weeks

    Design

    Data model, screens, permissions, integrations. The database schema comes before the framework: it is the part that costs the most to correct afterwards.

  4. Two-week iterations

    Build

    Delivery in usable increments. You see and use the product throughout, rather than discovering it at the end.

  5. 1 to 2 weeks

    Deploy

    Data migration, role-based training, production start-up under supervision. The switchover is prepared and reversible.

  6. Continuous

    Evolve

    Corrective maintenance, security updates, and new functionality prioritised with you as your needs change.

Our commitments

What sets our way of working apart

  • We start from the business, not the technology

    The technical choice comes after understanding the problem. A well-modelled database beats a fashionable framework.

  • We deliver in usable increments

    You see and use the product throughout the project. No six-month tunnel followed by an unpleasant surprise.

  • Security is built in from the design stage

    Role-based permissions, audit logging, encrypted secrets, systematic server-side validation. It is not an option billed at the end.

  • We document and we train

    Your teams must be able to run the system without calling us for every question. Both the code and its operation are documented.

  • We know the local constraints

    Intermittent connectivity, power cuts, mobile money, equipment that has to keep working offline. We design for that, not against it.

  • You own the code and the data

    The repository, the data, the hosting accounts and the domain names are in your name. We create no artificial dependency.

Frequently asked questions

Frequently asked questions

Do you only work in the Congo?
Our operating base is in Pointe-Noire, Republic of the Congo. We work remotely for design and development, and on site for the phases that require it: framing workshops, IoT site surveys, training and deployment.
How big is your team?
We are a young and deliberately small team, extended by a network of specialists brought in as a project requires. We would rather say so plainly than claim a size we do not have.
Do you work with small organisations?
Yes. Splitting the work into batches lets you start with a limited budget on a narrow but genuinely useful scope, then extend if the result justifies it.
How does a first conversation go?
A thirty- to forty-five-minute conversation, with no commitment, to understand your context and your need. We then tell you honestly whether we are the right partner, and if not we point you elsewhere.
How long does a project take?
A first usable batch is generally delivered six to twelve weeks after framing, depending on scope. A complete ERP or a multi-site IoT platform is built over several months, in increments delivered regularly.
How is your pricing set?
A fixed price per batch after framing, or time and materials for continuous support engagements. The framing itself is costed separately, which leaves you free to continue or not.
What if the need changes during the project?
That is normal and expected. Changes are folded into the prioritisation of the next batch. A change that calls the current batch into question is costed and decided with you before it is started.
Who owns the code and the data?
You do. The code repository, the data, the hosting accounts and the domain names are in your name or transferred to you. We create no artificial dependency.

Africa Tech Services

Want to talk it through?

A first thirty-minute conversation is enough to tell whether we are the right partner.