The Faceela methodology
Diagnose before you prescribe
Most failed implementations solved the wrong problem correctly. So we do not quote a system on the first call. We find out what is actually broken, write it down, and only then talk about what to build.
Four phases
What actually happens, in order
Nothing here is proprietary vocabulary. It is the sequence, and the fact that the last phase exists at all, that makes the difference.
- PHASE 01
Diagnose
Two weeks inside your operation. We map how the work is actually done, where two systems disagree, and what each gap costs you in a month.
- Every system in use is documented, including the shadow spreadsheets nobody mentions in meetings.
- We interview the people doing the work, not only the people who own the budget.
- You get a written diagnosis you can act on even if you never hire us.
- PHASE 02
Architect
A target design tied to operating decisions: which system holds which truth, who owns it, and what has to be true before go-live.
- One data owner per domain, named. Ambiguity here is what produces three versions of the same number.
- Configuration before customisation — custom code only where the business genuinely differs.
- A phased plan where each phase is usable on its own, so value does not wait for the final release.
- PHASE 03
Implement
Delivery in phases you can stop after. We train your team to run it, because a system that only we can operate is a system you do not own.
- Migration rehearsed on real data before it is done for real.
- Change management aimed at the people who will resist — they usually have a reason worth hearing.
- Documentation and handover written for your team, not for our next engagement.
- PHASE 04
Govern
The part everyone skips. Ownership, review cadence and metrics, so the system does not quietly decay back into chaos.
- Agreed metrics reviewed on a fixed cadence, compared against the baseline we recorded in the diagnosis.
- An upgrade path that does not require rewriting your customisations every release.
- A standing escalation route, so problems surface while they are still small.
Principles
What we will not do
These are the commitments that decide most of our arguments with clients, usually in the client's favour a year later.
We refuse out-of-the-box bandaids
A configuration that ignores how your business actually differs will be abandoned within a year. A customisation for something you could have changed in the process will haunt every upgrade. Telling those two apart is the work.
The diagnosis is yours either way
You get the written findings whether or not you hire us for the delivery. A diagnosis you cannot act on independently is a sales document, not an audit.
Every phase has to stand alone
If the programme is cancelled after phase two, phase two still has to be worth what it cost. Big-bang plans concentrate all the value behind the riskiest date in the schedule.
Resistance is information
The person blocking the rollout usually knows something the plan does not. We go and ask them before we escalate past them.
Next step
Ready to cure your system chaos?
Start with the diagnosis. Two weeks, a written report, and a clear answer on whether the problem is the system, the process or the governance.
Monday to Friday, 9:00 AM – 6:00 PM (GST)
Prefer we call you?
Leave your WhatsApp number and we will reach out.