Contact usFrançais
IBISYS
Capabilities

Integration and business systems

Odoo, Sage and the systems already running the business, made to agree with each other.

the business problem

Platforms disappoint because they are installed, not adopted.

Enterprise platforms are rarely disappointing because the software is bad. They disappoint because they were configured to the vendor default, connected to nothing, and handed to people who were shown them once.

Underneath them sits the other half of the problem: processes that never made it into any system at all. They run on paper, on spreadsheets, on habit and on messages in a thread, and they work until somebody is away.

The result is an organisation paying for platforms it uses a fraction of, while the work that matters most happens outside them.

what we provide

  • Deployment and configuration of Odoo or Sage around your operation rather than around the default
  • Connection to the systems already running the business, so a figure is entered once
  • Data brought across from whatever you are leaving behind
  • Steps still carried on paper and in habit, rebuilt as something that records itself
  • A review of what you are licensed for against what you actually use

typical engagements

Deployment and configuration

Standing up Odoo or Sage configured to the work rather than to the demo, with the data that has to come with it.

Connecting what exists

Making two systems that ignore each other agree, so nobody retypes a number that is already recorded somewhere.

Process digitization

Rebuilding the steps that run on paper and memory as systems that record what happened while it is happening.

how we approach it

The migration sets the timeline, not the software.

Deployment is the short part. What decides the schedule is moving data out of something old, and reconciling the versions of the truth that will turn out to disagree.

We follow the work before changing it. Digitizing a process as described rather than as performed produces a system people route around within a month.

We say when you are paying for a module you do not need. Licence spend grows easily and is noticed late, and a supplier who benefits from you buying more of it is not the right adviser on that question.

reference architecture

How the pieces fit

A reference model rather than any client's system. Most enterprise pain is a boundary problem rather than a product problem, and this is where the boundaries are.

  1. 01

    Process

    What actually happens, including the steps that live outside every system you own.

  2. 02

    Platforms

    Microsoft 365, Sage and the business applications around them, configured to the work rather than to a default.

  3. 03

    Integration

    What moves between them, and which direction is authoritative when they disagree.

  4. 04

    Customer record

    One history of the customer, assembled from every channel they reach you through.

  5. 05

    Reporting

    The numbers the organisation runs on, drawn from the platforms rather than re-keyed beside them.

technologies

  • Odoo
  • Sage
  • Microsoft 365
  • PostgreSQL
  • REST APIs

questions

We already own Microsoft 365. Is there anything left to do?
Usually a great deal. Most organisations use a fraction of what they are licensed for, and the unused part is often exactly what would replace a tool they are paying for separately.
How long does a migration take?
Weeks for a single platform, longer where data has to come out of something old. Getting the data out is what sets the schedule, and it is the part easiest to underestimate.
Will our people actually use it?
Only if it fits the work. A platform configured to the vendor's assumption of your process gets worked around, which is why we follow what happens before changing it.
Can you work with a platform you did not deploy?
Yes. Taking over something already running starts with an assessment, because the first job is finding out what it is genuinely doing.

often runs with

Bring us the problem.

We start with a working session on your actual operation, not a generic pitch. You leave it knowing what is happening, what is worth fixing first, and what the path forward looks like.