Business platforms
AI that works inside the systems you already run.
Customer records, ledgers, stock and day-to-day operations are already held in SAP, Salesforce or Odoo. We configure, extend and integrate all three and bring AI to them under the permissions you already set, so automation and insight show up in the screens your staff open every morning.
For Irish organisations, and the Irish operations of international groups, whose platforms need to work as one, from the group ledger to the service desk.
Partner status
- Salesforce, Summit Partner
- SAP, Gold Partner
- Odoo, Gold Partner
We hold partner status with SAP, Salesforce and Odoo, and our information security is certified to ISO/IEC 27001.
Each of the three is very good at one thing. Problems begin when one is stretched to cover work that belongs to another, or when spreadsheets and one-off scripts are all that hold them together.
We help you settle which platform owns which data and process, set each one up and extend it with care, and link them to AI and to everything else you run. Integration and AI work stays with the team that configures the platform: 2,400+ colleagues in software, cloud, AI engineering and platform work.
Three platforms, each with its own job
Written from projects we have run, not from vendor material. Plenty of organisations use two of the three, and some use all of them.
| Aspect | SalesforceCustomers and cases | SAPThe group ledger | OdooERP in modules |
|---|---|---|---|
| 01What it is for | The front office: customers, members of the public, partners and their cases. | One record of money, materials and production for every entity in a group. | A single ERP built from modules, right for a mid-market company or one subsidiary of a group. |
| 02Who usually runs it | Organisations with heavy volumes of customer or public contact, from one county to many countries. | Large groups, Government departments and State agencies with many legal entities and tight reporting rules. | Owner-managed and mid-market businesses, subsidiaries, smaller agencies and charities. |
| 03Where it is strong | Case handling, portals, quick configuration and a wide ecosystem of partners and apps. | Strong in finance, logistics and production, plus budget control for public bodies. | Wide coverage in a single database, a modest entry cost and an open-source core. |
| 04What to watch | Licence costs per user, governor limits and automation that nobody prunes. | Modifications that make every upgrade painful, and drawn-out programmes with no clean-core discipline. | So much customisation that the annual upgrade becomes a project of its own. |
| 05Built-in AI | Agentforce, drawing on Data 360, with the Einstein Trust Layer in between. | Joule and the wider SAP Business AI range; custom scenarios through SAP BTP’s generative AI hub. | Reading supplier bills and receipts, plus the AI tools that newer releases add. |
| 06Where we usually start | A health check of the current org, or a single agent on one service process, tested properly. | A readiness check and a route choice, well before ECC mainstream maintenance stops at the end of 2027. | Mapping the modules you need, then a first phase with fixed scope, usually finance set up to receive e-invoices ahead of Revenue’s 2028 date. |
| 07How it fits with the others | Facing customers and the public, with SAP or Odoo behind it, joined by APIs and events. | The group ledger, with Odoo in smaller subsidiaries and Salesforce facing customers. | ERP for subsidiaries, feeding results into an SAP core at group level. |
| More on Salesforce | More on SAP | More on Odoo |
- What it is for
- The front office: customers, members of the public, partners and their cases.
- Who usually runs it
- Organisations with heavy volumes of customer or public contact, from one county to many countries.
- Where it is strong
- Case handling, portals, quick configuration and a wide ecosystem of partners and apps.
- What to watch
- Licence costs per user, governor limits and automation that nobody prunes.
- Built-in AI
- Agentforce, drawing on Data 360, with the Einstein Trust Layer in between.
- Where we usually start
- A health check of the current org, or a single agent on one service process, tested properly.
- How it fits with the others
- Facing customers and the public, with SAP or Odoo behind it, joined by APIs and events.
- What it is for
- One record of money, materials and production for every entity in a group.
- Who usually runs it
- Large groups, Government departments and State agencies with many legal entities and tight reporting rules.
- Where it is strong
- Strong in finance, logistics and production, plus budget control for public bodies.
- What to watch
- Modifications that make every upgrade painful, and drawn-out programmes with no clean-core discipline.
- Built-in AI
- Joule and the wider SAP Business AI range; custom scenarios through SAP BTP’s generative AI hub.
- Where we usually start
- A readiness check and a route choice, well before ECC mainstream maintenance stops at the end of 2027.
- How it fits with the others
- The group ledger, with Odoo in smaller subsidiaries and Salesforce facing customers.
- What it is for
- A single ERP built from modules, right for a mid-market company or one subsidiary of a group.
- Who usually runs it
- Owner-managed and mid-market businesses, subsidiaries, smaller agencies and charities.
- Where it is strong
- Wide coverage in a single database, a modest entry cost and an open-source core.
- What to watch
- So much customisation that the annual upgrade becomes a project of its own.
- Built-in AI
- Reading supplier bills and receipts, plus the AI tools that newer releases add.
- Where we usually start
- Mapping the modules you need, then a first phase with fixed scope, usually finance set up to receive e-invoices ahead of Revenue’s 2028 date.
- How it fits with the others
- ERP for subsidiaries, feeding results into an SAP core at group level.
One connected landscape
Few organisations run just one of these. They sit beside bespoke applications, a data platform and public networks such as Peppol. What matters is how they cooperate: every fact has one owner, changes travel as events rather than overnight copies, and AI can look across systems without stepping round anybody’s access rights.
Our platform specialists share integration contracts with our integration and API, data and analytics and AI engineering people. So an SAP change does not catch Salesforce off guard, and an agent in Salesforce can touch an Odoo invoice only under rules you have approved.
- 01
One owner per fact
Every kind of data belongs to one system; the rest subscribe to its changes.
- 02
A single integration layer
APIs and events pass through one governed layer, watched from end to end.
- 03
Data that AI can use
What leaves a platform keeps its business meaning when it arrives in the data platform.
- 04
AI that respects access
Agents work across platforms only inside the rights you set, with approval steps and a log of each action.
- Salesforce
- SAP
- Odoo
- Data platform
- Agents and AI services
- Bespoke applications
- Identity
- Peppol and public networks
Read the diagram as text
Across the top, SAP, Salesforce and Odoo stand next to each other, and each one owns a different kind of data.
Each of them plugs into a single layer of APIs and events.
Under that layer are the services they share: identity, bespoke applications, agents and AI services, the data platform, and public and market networks such as Peppol, which Irish public buyers use to receive e-invoices.
How platform work connects to our other services
- Integrations & APIs
Interfaces, events and monitoring that tie the platforms to the rest of your systems.
- Architecture & Consulting
Deciding, on evidence, which platform owns which process.
- AI Agents & Automation
Agents that act in more than one platform, inside limits you set.
- All services
Everything we design, build and operate, in one overview.
- How we work
Each stage from first workshop to live operation, and what you get at the end of it.
Ireland
Platform choices in Ireland
In Ireland, choosing a platform is now partly a regulatory decision. Under Revenue’s published timeline for VAT modernisation, large corporates issue EN 16931 e-invoices for domestic B2B trade from 1 November 2028 and every business must be able to receive them from that date, so the ERP is directly in scope. Public buyers already receive and process EN 16931 e-invoices over Peppol under S.I. No. 258 of 2019.
NIS2 sets a higher bar for securing the layer that joins your platforms. As of autumn 2026 it is still making its way into Irish law through the National Cyber Security Bill, and S.I. No. 360 of 2018 applies until the new Act. The EU Data Act lets you move between cloud providers and get at the data your systems generate; both points belong in your platform contracts and exit plans.
We handle all of this while the platform is chosen and the architecture is shaped, not in a compliance check at the end.
- Data ActData Act, Regulation (EU) 2023/2854 (opens external site)
- NIS2NIS2 Directive (EU) 2022/2555 (opens external site)
- National Cyber Security BillNational Cyber Security Bill 2024 (General Scheme published August 2024) to transpose NIS2; not enacted (opens external site)
- Irish NIS regulations (S.I. 360/2018)S.I. No. 360 of 2018 (NIS1), in force until the National Cyber Security Bill is enacted (opens external site)
- Irish VAT modernisation (B2B e-invoicing)VAT modernisation: domestic B2B e-invoicing (EN 16931) and reporting to Revenue, planned in phases on Revenue’s timeline; the legal basis, Finance Bill (No. 2) 2026, is not yet enacted (opens external site)
- Irish B2G e-invoicingEuropean Union (Electronic Invoicing in Public Procurement) Regulations 2019: contracting authorities receive and process EN 16931 e-invoices via Peppol (opens external site)
Platform questions we are often asked
SAP, Salesforce or Odoo: which one should we pick?
Begin with the work to be done rather than the product name. Lots of customer contact and case handling suggests Salesforce. If you need one ledger for a whole group, with demanding finance, logistics or public budgeting, look at SAP. A mid-sized business or a subsidiary that wants one system at a sensible cost is usually best served by Odoo.
Plenty of organisations end up with two. Before any licence is signed, we write down which platform owns which data and which process.
Will you take over a platform another partner implemented?
Yes. First we assess the configuration, custom code, interfaces and open issues, and tell you plainly what to keep, fix or switch off before we accept responsibility for running it.
Are these the only platforms you work with?
They are the three where we hold partner status and keep dedicated specialists. Around them we build bespoke software, cloud and data platforms and AI systems, so the platform never sets the limit of what you can do.
How do you connect AI to these platforms without creating risk?
Only through the APIs each vendor releases and the platform’s own permission model, never by going round them. That means narrow permissions, approval steps and a full log. We test results against criteria agreed with you before go-live and after it, and anything uncertain goes to a member of staff.
Do you deliver these platforms for Irish public bodies?
Yes. We bring experience from 600+ government projects across the EU, finished and in progress, including in Ireland. We know the procurement, accessibility and interoperability rules that come with platform work for Government departments, State agencies and local authorities, from tender competitions on eTenders to S.I. No. 358 of 2020 for public websites and apps. See our public service work.
Unsure which platform should own which process?
Bring a picture of your current systems and the choices ahead of you. We will help you take the platform, integration and AI questions one at a time, in an order that makes sense.