Skip to main content

Consulting & Digital transformation

IT strategy definition, master plans, business analysis and change management on critical projects.

IT strategy Roadmap BA Change
Strategy workshop at a whiteboard

Key features

The firm that stays after the report

A master plan is only worth what survives contact with the field. Since 2016 we have been framing transformations for executive teams, CIOs and public institutions across the CEMAC region — and we stay on to deliver them. The firm that writes your trajectory is also the one that deploys the ERPs it recommends and audits the systems it brings to life.

That position has taught us to refuse certain things. Two-hundred-page master plans nobody reopens after the validation committee. Tool benchmarks recycled from one engagement to the next. Five-year trajectories that ignore the real state of your teams, your connectivity or your budget. A useful framing comes down to three things: a prioritised trajectory, a budget per workstream, and milestones where you can say stop.

Eighteen consultants, twenty-nine references — from energy to international institutions — and five software products built in-house: when we talk about digital transformation, we are talking about a craft we also practise on our own systems.

Method

How we work

  1. 01

    Diagnosis & mapping

    4 to 8 weeks

    Application and process audit, interviews with sponsors and key users, measurement of technical and organisational debt. The output is a document your executive committee can read in one sitting — not two hundred pages.

  2. 02

    Master plan

    2 to 3 months

    A 3-5 year trajectory aligned with your strategic plan, prioritised by business value and effort, sequenced around dependencies, budget and your teams' real capacity. Each workstream is validated in committee, with an explicit stop-or-go milestone.

  3. 03

    Business analysis & steering

    6 to 18 months per project

    On critical workstreams — ERP overhaul, compliance, cloud migration — we lead the business analysis: requirements, vendor or integrator selection, build steering, user acceptance testing, go-live.

  4. 04

    Change management

    Ongoing

    Distinct training and support programmes per population — leadership, key users, end users — with adoption indicators tracked after go-live, not just on launch day.

Deliverables

What you receive

IS diagnostic report

Application map, technical and organisational debt, prioritised risk matrix.

Master plan

3-5 year trajectory, indicative budget per workstream, explicit decision milestones.

Business-analysis packs

Requirements, vendor or integrator selection grid, user acceptance plan.

Change-management kit

Communication plan, training paths per population, adoption indicators tracked over time.

Commitment

Never commissioned by a vendor. Our recommendation is bound only to your need — and to our own workload.
Fixed-price or time & materials engagements, transparent fees. And because we then deploy what we recommend, an unrealistic trajectory would land on us first.

Getting started

How to get started

  1. 1

    Scoping call

    45 minutes to qualify the context, stakes and deadlines.

  2. 2

    Written scoping note

    Proposed scope, approach, budget range.

  3. 3

    Within 48 business hours

    No commitment on your side.

FAQ

Frequently asked questions

How long does a digital transformation engagement take?

A full IS diagnostic usually takes 4 to 8 weeks; a master plan, 2 to 3 months. Business analysis then follows the project's pace (6 to 18 months).

Do you work outside Yaoundé?

Yes. We operate across Cameroon and the CEMAC region, on site or remotely depending on the phase.

Are you independent from software vendors?

Yes. Our consulting engagements are fixed-price or time-based, never vendor-commissioned — our recommendation is driven solely by your need.

Let's talk about your project

A demo, an audit, an ERP to roll out? One message is enough to start the conversation.