Skip to main content
KataLeap

Odoo & ERP Systems

Odoo implementations that finish — configured for Saudi compliance, and actually adopted by the people who have to use them.

What You Get

  1. 1

    ZATCA-compliant e-invoicing working correctly, not as an afterthought.

  2. 2

    A configuration your team can operate without calling us every week.

  3. 3

    Arabic and English running side by side across the system.

Part of Technology & Data Transformation

Most failed ERP projects we are asked to rescue did not fail technically. They failed because the configuration reflected an idealised process nobody follows, and the staff quietly went back to spreadsheets.

How We Approach It

How we approach it

We configure against how your business actually operates, and we are direct about which of your processes should change to fit standard Odoo rather than being customised around. Every customisation is a maintenance cost you carry at every future upgrade, so each one should have to justify itself.

How an Engagement Runs

  1. 01

    Understand

    We map the process with the people who run it, before anything is designed. This step regularly changes the brief.

    Before any design
  2. 02

    Plan

    Scope, structure and a plan with dates and costs you can take to a board.

    Board-ready
  3. 03

    Deliver

    In increments you can see. Working software every two weeks; on advisory work, a decision closed at every step.

    Every two weeks
  4. 04

    Hand Over

    Documentation, training and full ownership. Support afterwards if you want it, not because you are stuck.

    Full ownership

Ready to Talk It Through?

A short call to understand the problem, then an honest view on scope, cost and whether it is worth doing.

Start a Conversation

Common Questions

Do you handle ZATCA e-invoicing compliance?

Yes, for Odoo implementations, for custom systems that issue invoices, and as a compliance review of a setup somebody else built. It is built into the implementation rather than added afterwards, because retrofitting compliance into an invoicing flow is considerably more expensive than designing for it.

Do you work in Arabic?

Yes. We deliver documentation, training, reporting and interfaces in Arabic and English, and we treat Arabic as a first-class design problem rather than a translation task applied at the end.

How do you price engagements?

Fixed price for well-defined scopes, and time-and-materials for discovery or open-ended work. We will tell you which one an engagement should be, and we will not quote a fixed price for something nobody understands yet — that pricing model only works by padding the number or cutting quality later.

Who owns the code?

You do, on delivery. Source code, infrastructure accounts and documentation. There is no licensing arrangement that keeps you tied to us.

More in Technology & Data Transformation

View the practice

Let’s Talk About What You’re Trying to Build

Tell us the problem, not the specification.