Platforms we implement
AI inside the ERP and CRM you already run.
In an Indian business group, the customer record may sit in Salesforce, the ledger and the plants in SAP, and a subsidiary or MSME unit on Odoo. We set up and extend each of them, link them to the IRP for GST e-invoicing and to your European entities, and add AI that respects the roles and approvals the platform already enforces.
For Indian business groups whose CRM, ERP and European subsidiaries have to work as one landscape.
Partner status
- Salesforce, Summit Partner
- SAP, Gold Partner
- Odoo, Gold Partner
We hold partner status with Salesforce, SAP and Odoo, and FromNine is ISO/IEC 27001 certified for information security.
Each of these platforms is strong at one job. Problems appear at the joins: a sales order keyed in twice, an IRN copied back from the portal by hand, or a European subsidiary that reports to the Indian parent through spreadsheets.
We first agree which platform owns which record, then configure and extend each one in tested releases and connect it to AI and to your other systems. FromNine is one company of 2,400+ people across AI engineering, software, cloud and platforms, so the consultants who configure a platform sit with the engineers who build its interfaces and the AI around it.
How the three platforms differ
Written from implementation work rather than vendor material. Many groups run two of the three, and some run all of them.
| Criterion | SalesforceCustomers and service | SAPLedger of the group | OdooERP for growing units |
|---|---|---|---|
| 01Role in your landscape | Relationships with customers, dealers and partners, their service requests and the portals around them. | The record of money, materials and production for a business group and each of its entities. | A single modular ERP for an MSME, a new business unit or a subsidiary abroad. |
| 02Where it is usually found | Banks, insurers, NBFCs, consumer brands and B2B sellers with high volumes of customer contact. | Business groups, large manufacturers and PSUs with several legal entities and demanding audits. | MSMEs, distributors, exporters and the smaller companies inside a larger group. |
| 03What it does well | Request handling, self-service portals, quick changes by administrators and a wide partner ecosystem. | Finance, procurement, production and plant maintenance in depth, with segregation of duties built in. | Many business functions on one database, a modest entry cost and an open-source core. |
| 04Risks to manage | Licence cost per user, platform limits and flows that multiply without an owner. | Modifications that make every upgrade expensive, and programmes run without clean-core rules. | Deep customisation that turns the annual version upgrade into a project of its own. |
| 05AI available natively | Agentforce agents, grounded in Data 360 and routed through the Einstein Trust Layer. | Joule, SAP Business AI scenarios and the generative AI hub on SAP BTP. | Digitisation of vendor bills and expenses, plus the AI features of newer releases. |
| 06Where we usually begin | A review of the existing org, or one service journey with a single tested agent. | A readiness check and a migration route for S/4HANA, timed against the end of ECC mainstream maintenance in 2027. | A module map and a fixed first phase, usually accounting, GST and inventory. |
| 07How it combines with the others | Front end for customers, reading orders and invoices from SAP or Odoo through events and APIs. | Core of the group, with Odoo in smaller entities and Salesforce facing customers. | ERP of a subsidiary or unit, sending its figures to the SAP core of the group. |
| View Salesforce | View SAP | View Odoo |
- Role in your landscape
- Relationships with customers, dealers and partners, their service requests and the portals around them.
- Where it is usually found
- Banks, insurers, NBFCs, consumer brands and B2B sellers with high volumes of customer contact.
- What it does well
- Request handling, self-service portals, quick changes by administrators and a wide partner ecosystem.
- Risks to manage
- Licence cost per user, platform limits and flows that multiply without an owner.
- AI available natively
- Agentforce agents, grounded in Data 360 and routed through the Einstein Trust Layer.
- Where we usually begin
- A review of the existing org, or one service journey with a single tested agent.
- How it combines with the others
- Front end for customers, reading orders and invoices from SAP or Odoo through events and APIs.
- Role in your landscape
- The record of money, materials and production for a business group and each of its entities.
- Where it is usually found
- Business groups, large manufacturers and PSUs with several legal entities and demanding audits.
- What it does well
- Finance, procurement, production and plant maintenance in depth, with segregation of duties built in.
- Risks to manage
- Modifications that make every upgrade expensive, and programmes run without clean-core rules.
- AI available natively
- Joule, SAP Business AI scenarios and the generative AI hub on SAP BTP.
- Where we usually begin
- A readiness check and a migration route for S/4HANA, timed against the end of ECC mainstream maintenance in 2027.
- How it combines with the others
- Core of the group, with Odoo in smaller entities and Salesforce facing customers.
- Role in your landscape
- A single modular ERP for an MSME, a new business unit or a subsidiary abroad.
- Where it is usually found
- MSMEs, distributors, exporters and the smaller companies inside a larger group.
- What it does well
- Many business functions on one database, a modest entry cost and an open-source core.
- Risks to manage
- Deep customisation that turns the annual version upgrade into a project of its own.
- AI available natively
- Digitisation of vendor bills and expenses, plus the AI features of newer releases.
- Where we usually begin
- A module map and a fixed first phase, usually accounting, GST and inventory.
- How it combines with the others
- ERP of a subsidiary or unit, sending its figures to the SAP core of the group.
Connected, not copied
Few organisations run a single platform. Next to Salesforce, SAP or Odoo there are in-house applications, a data platform, the IRP for GST e-invoices and, for groups with European entities, Peppol. What matters is how they cooperate: a single owner for each record, events in place of overnight batch copies, and AI that reads across systems while respecting each system’s permissions.
Our platform consultants agree integration contracts with our colleagues in Integrations & APIs, Data & Analytics and AI Engineering & GenAI. A field changed in SAP reaches Salesforce through a defined event, and an agent working in Salesforce can touch an Odoo invoice only under rules your finance team has approved.
- 01
One owner per record
Every type of record has a single system of record; the other platforms subscribe to its changes.
- 02
A shared integration layer
APIs and events pass through one governed layer, monitored from source to target.
- 03
Data that AI can use
Records reach the data platform with their business meaning and the purpose for which personal data was collected.
- 04
AI within your roles
Agents act across platforms only with rights you grant, approval by an authorised officer and a full log.
- Salesforce
- SAP
- Odoo
- Data platform
- AI services and agents
- In-house applications
- Identity
- IRP, Peppol and other networks
Read the diagram as text
Across the top, Salesforce, SAP and Odoo each hold the records they own.
Each platform connects to a shared integration layer made of APIs and events.
Under that layer are the services all three use: the data platform, AI services and agents, in-house applications, identity, and external networks such as the IRP for GST e-invoices and Peppol for European trading partners.
Where platform work connects to our other services
- Integrations & APIs
Interface contracts, events and monitoring between your platforms, the IRP and other systems.
- Architecture & Consulting
A documented decision on which platform owns which process.
- AI Agents & Automation
Agents with maker-checker controls that work across your platforms.
- All services
Everything we design, build and operate for clients.
- Our delivery model
Discovery to operation, with named deliverables at every stage.
India
Platform rules for organisations in India
Several Indian rules now reach into platform design. Under GST e-invoicing, businesses above the turnover threshold report their B2B and export invoices to the Invoice Registration Portal (IRP) and keep the Invoice Reference Number (IRN) it returns, so the ERP and the IRP must stay in step every day.
The Digital Personal Data Protection Rules, 2025 bring notice, security safeguard and breach intimation duties for Data Fiduciaries from May 2027; they shape consent records in the CRM and log retention on all three platforms. The CERT-In Directions of 28 April 2022 already require listed cyber incidents to be reported within six hours, which depends on usable logs from the integration layer.
For groups with entities in the EU, the switching and data access rights of the EU Data Act belong in each platform contract, and NIS2 sets the security bar for the integration layer. Each of these is settled during platform selection and architecture, not left to an audit after go-live.
- GST e-invoicingGST e-invoicing: B2B and export invoices registered on the Invoice Registration Portal (IRP) to obtain an IRN (opens external site)
- DPDP Rules 2025Digital Personal Data Protection Rules, 2025, brought into force in three steps over eighteen months (opens external site)
- CERT-In Directions 2022CERT-In Directions of 28 April 2022 under s. 70B(6) of the IT Act: reporting of listed cyber incidents within 6 hours, log retention, time synchronisation (opens external site)
- Data ActData Act, Regulation (EU) 2023/2854 (opens external site)
- NIS2NIS2 Directive (EU) 2022/2555 (opens external site)
Common questions on platforms
How do we decide between Salesforce, SAP and Odoo?
Begin with the business requirement, not the product. High volumes of customer or dealer interactions and service requests point to Salesforce. A group ledger with complex finance, production or many legal entities points to SAP. An MSME or a subsidiary that needs one affordable ERP points to Odoo.
Many groups need two of them. Before any licence is bought, we write down which platform owns which data and which process.
Will you take over a platform implemented by another partner?
Yes. We first assess the configuration, custom code, interfaces and open tickets, and give you a written view of what to retain, correct or decommission before we accept responsibility for it.
Are these the only platforms you work on?
They are the three where we hold partner status and keep dedicated platform consultants. Around them we build custom applications, cloud and data platforms and AI systems, so a requirement the platform cannot meet still has a home.
How is AI connected to these platforms without weakening controls?
Only through each platform’s released APIs and its own role model, never around them. Every AI action has bounded rights, a maker-checker step where money or records change, and a complete log. Output is tested against agreed criteria before and after go-live, and doubtful cases go to a person.
What public-sector experience do you bring to platform work?
Our public-sector platform work is European: 600+ projects for European public administrations, completed and ongoing. What carries over to a ministry, a State department or a PSU in India is the discipline those projects demand: answering each clause of a bid document, building to WCAG 2.1 level AA as GIGW 3.0 asks of government websites, and keeping a trail for every change. See Government & public sector.
Unsure which platform should own which process?
Share your current landscape and the decisions ahead of you. We will help you take the platform, integration and AI questions in a sensible order.