Our approach
A reference framework, adapted to your context.
For SAP, our reference framework is SAP Activate. For Salesforce and custom applications, we work in short iterations. In both cases, the method adjusts to your context, your pace and your governance. What never changes: the decisions we secure with you, and the autonomy of your teams at the end of the engagement.
The principle
Two platforms, one single team.
Every company starts from its own legacy, culture and pace. A multi-country regional group, an SME in Dakar and a public institution have neither the same constraints nor the same calendar. So we do not apply the same recipe to them.
We keep a stable framework, known to our teams and to your software vendors, and we adjust the depth of each phase, the frequency of decision points and the level of formality to your project. What you gain: teams that are operational from day one, deliverables that are comparable from one phase to the next, and documented decisions that nobody rediscovers along the way.
The four pillars
What guides every one of our engagements.
Four simple principles, applied to SAP projects as much as to Salesforce or custom projects. They prove themselves in the way we work, not in a brochure.
Client-centred approach
We start from your business, your users and your real constraints: the OHADA framework, national taxation, connectivity, seasonality of activity. The system adapts to your organisation, not the other way round.
Continuous innovation
We follow developments at SAP, Salesforce and in the cloud to offer you what brings concrete value: automation, analytics, AI applied to your processes. Without chasing fads.
Flexibility and adaptability
Scope moves, and so do priorities. Our teams know how to reorganise a work package, shift a milestone or reinforce a workstream without losing the thread of the trajectory. That is what the word agility means in our name.
Operational excellence
Reviewed deliverables, tests run on your data, cutovers rehearsed in dry runs. Quality is proven in acceptance testing and in operation, not in committee.
For SAP
SAP Activate: five phases, one single thread.
SAP Activate is the vendor's own method. We use it on conversions to SAP S/4HANA, new implementations, RISE with SAP and GROW with SAP, and we streamline it for SAP Business One.
Discover
Set the strategy before setting up the system: target analysis, scope definition, building the decision file. At the end of this phase, leadership knows what the project must change, at what cost and for what value.
Prepare
Get the project ready to run: mobilising the teams (yours as well as ours), governance, planning and environments. On exit, everyone knows their role and the calendar is committed.
Explore
Confront the standard with your reality: fit-to-standard approach, business workshops, functional and technical design. Every deviation from standard is examined, then decided with full knowledge of the facts.
Realize
Build and prove: configuration, developments, data migration, integration testing and user acceptance testing led by the business. The system is validated on your data and your volumes, in real conditions.
Deploy
Cut over and anchor: go-live, user training, hypercare, then an organised handover to operations. The engagement ends when your teams operate autonomously.
For Salesforce and custom applications
An agile approach, in iterations.
A CRM or a business application is built with its users. We move forward in short sprints, we regularly show what works and we adjust based on your feedback. Adoption is prepared during the project, not afterwards.
Scoping
Objectives, priority user journeys, data to migrate, integrations with the ERP and other systems. The first work package is chosen to deliver visible value quickly.
Sprints
Short cycles, with a scope committed at the start of each cycle. Business teams take part in the workshops and watch the result take shape.
Regular demonstrations
At the end of each sprint, we demonstrate the product on real cases. Whatever does not fit is corrected in the next sprint, not discovered at final acceptance.
Feedback and prioritisation
Your feedback feeds the backlog. You decide the order of priorities, with a clear view of what each choice costs and yields.
Adoption
User training, internal champions, measurement of actual usage and continuous improvement after go-live. A tool that is not used has no value.
The engagement model
Three ways of working with us.
The role is chosen at the start of the engagement, written into the contract, and then does not change without your decision. Here are the three formats we practise.
- As integrator: we deliver
We run the project end to end, from scoping to hypercare, with our SAP, Salesforce, data and development consultants. A format suited to SMEs as well as to a targeted scope within a large regional group or an institution.
- As client-side advisor
Facing an integrator or a software vendor, we sit on your side of the table: verifiable requirements, demanding acceptance testing, well-prepared trade-offs. We defend your interests, and yours only.
- As team reinforcement
Our consultants join your set-up, under your governance or your partner's, on the work packages where their expertise makes the difference: finance, supply chain, integration, data, CRM.
The decisions we secure
Six decisions that commit you for the long term.
A transformation hinges on a small number of decisions that are hard to undo. We prepare them with you, alternatives and costs included, before they turn into constraints.
The scenario
Conversion, new implementation or selective transition; private cloud, public cloud or on-premise; SAP S/4HANA, SAP Business One or Odoo depending on your size. A defensible scenario for your context, not for a catalogue.
The scope
What goes into the first wave, what follows, what stays out. A scope that holds is the first protection for the calendar and the budget.
Deviations from standard
Every custom development is costed over its full life cycle: build, operation, upgrades. Standard first, custom only when it creates real value.
The data
What to migrate, how far back in history, with which quality rules, and who is accountable for it. Data is prepared from the Explore phase onwards, never in the last week.
The cutover
A cutover plan rehearsed in dry runs, timed to the minute, with entry, exit and rollback criteria. Go-live is decided on facts, not on a date.
Hypercare
The first weeks of operation with the project team at your side, clear rules for handling incidents, then an organised transition to support and continuous improvement.
Skills transfer
Your autonomy is part of the deliverable.
A successful project is one that your teams know how to keep alive. From the scoping phase, we identify the internal champions: business owners, application key users, administrators. They take part in the workshops, in acceptance testing and in the cutover, and together with them we document what matters for operations.
This requirement stems from our roots in Dakar. SAP and Salesforce skills must grow in the sub-region, at our clients as much as in our own teams. Training local teams is not an end-of-project option, it is a component of the engagement.
Once the engagement is over, we can stay at your side with support and application management →, backed by written service commitments.
Our commitments
Three commitments, written into the contract.
Delivery
Methodological framework, milestones, regular reporting, service commitments: what this page describes is written into our contracts. The method is not a sales promise, it is a clause.
Quality
Consultants who bridge business and technology, continuous training on the platforms we put to work, signed confidentiality commitments, continuity of service over time.
Partnership
Relationships that last, independent advice, no engagement extension decided on your behalf. And complete transparency, on risks as much as on costs.
Putting the method to the test
Let's confront the method with your reality.
Thirty minutes with a senior consultant are enough to map out your current situation, the decisions ahead of you, and how this framework would apply in your organisation.
Let's talk →