The verdict in three sentences
For a mid-market company that must automate 12 processes between a legacy ERP with no API and modern SaaS tools, the right answer is almost always hybrid. RPA (software robots that mimic clicks, EUR 5,000 to 15,000 per robot per year in licenses) is justified when the source application offers no interface, while API integration (EUR 8,000 to 25,000 per flow in development) becomes cheaper over 3 years as soon as an interface exists. The deciding factor is the breakage rate of robots at every screen update, which drives annual maintenance of 15 to 25% of the build.
What really separates the two approaches
An RPA robot (UiPath, Power Automate Desktop, Automation Anywhere) connects to the interface like a user: it reads the screen, fills in fields, clicks buttons. An API integration exchanges structured data directly between systems, without going through the screen.
| Criterion | RPA | API integration |
|---|---|---|
| Application prerequisite | None, the UI is enough | Documented API or database access |
| Setup cost per flow | EUR 4,000 to 12,000 | EUR 8,000 to 25,000 |
| Recurring license | EUR 5,000 to 15,000 per robot per year | EUR 0 to 3,000 a year (integration platform) |
| Annual breakage | 1 to 3 incidents per robot during screen updates | Rare, API versions announced in advance |
| Annual maintenance | 20 to 25% of build | 15% of build |
| Volume handled | Limited by UI speed | Thousands of transactions per minute |
| Implementation time | 2 to 6 weeks per process | 4 to 10 weeks per flow |
3-year comparison for 12 processes
The typical Berlin mid-market company, 600 employees, runs a production ERP installed in 2009 with no usable API, Salesforce CRM, a SaaS expense tool and a customer EDI platform. The 12 processes split as follows: 5 touch the legacy ERP (order entry, invoice matching, price list updates), 7 connect modern tools to each other.
| 3-year scenario | All RPA | All API (with ERP access layer) | Recommended hybrid |
|---|---|---|---|
| Build | 12 × 8,000 = EUR 96,000 | 12 × 16,000 + EUR 40,000 ERP layer = EUR 232,000 | 5 RPA × 8,000 + 7 API × 14,000 = EUR 138,000 |
| Licenses (shared robots) | 4 robots × 10,000 × 3 = EUR 120,000 | Platform 3,000 × 3 = EUR 9,000 | 2 robots × 10,000 × 3 + 9,000 = EUR 69,000 |
| Maintenance | 22% × 96,000 × 3 = EUR 63,400 | 15% × 232,000 × 3 = EUR 104,400 | 22% × 40,000 × 3 + 15% × 98,000 × 3 = EUR 70,500 |
| 3-year total cost | EUR 279,400 | EUR 345,400 | EUR 277,500 |
| Estimated breakage incidents | 25 to 35 | 3 to 5 | 10 to 15 |
| Overall timeline | 2 to 3 months | 5 to 6 months | 3 to 4 months |
These figures are 2026 order-of-magnitude estimates. The hybrid scenario costs about the same as all RPA, but cuts incidents by two or three, and prepares the future ERP replacement: the 7 API flows will stay in place.
How to decide process by process
Three questions are enough. Does the application have a stable API? If yes, API. Does the process handle more than 2,000 transactions a month? If yes, the API becomes more profitable even with heavier development, because a robot saturates. Will the application be replaced within 2 years? If yes, RPA is an acceptable bridge, paid back quickly, without investing in an access layer that will disappear.
An often neglected point: governance. An RPA robot acts with a user account, which raises traceability and segregation-of-duties questions for auditors. Plan dedicated service accounts, an execution log and an alert on failure.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Thomas, CIO of an industrial company in Berlin, estimates that the 12 processes take 2.5 full-time equivalents in data entry and matching, or 2.5 × EUR 58,000 = EUR 145,000 a year in loaded costs. With the hybrid scenario at EUR 277,500 over 3 years, or EUR 92,500 a year, and 80% of volume automated, the annual gain reaches EUR 116,000. Net savings approach EUR 23,500 a year, and above all free 2 people for financial control, a role he could not hire for. Moving to API flows in year 2 then cuts licenses by EUR 20,000 a year.
FAQ
Is RPA an outdated technology in 2026?
No, it remains the only option for applications with no programmable interface. But it should be seen as a transition solution, with an exit plan within 2 or 3 years for high-volume flows.
Why does a robot break during an update?
It locates fields by their position or on-screen identifier. A new button or a moved field is enough to stop it, hence 1 to 3 incidents per robot per year depending on update frequency.
Can we build an API on a legacy ERP?
Often yes, by reading and writing directly in its database through a dedicated layer. Budget EUR 30,000 to 50,000 and the vendor's agreement to keep support.
Do we need an integration platform (iPaaS)?
Beyond 5 flows, yes: Make, n8n, Boomi or Azure Logic Apps centralize monitoring and error recovery, for EUR 0 to 3,000 a year depending on the tool.
How long to automate all 12 processes?
In hybrid mode, 3 to 4 months, starting with the 3 costliest processes to get a first gain from the second month.
Let's scope your project. We analyze your 12 processes and systems to recommend RPA, API or hybrid, with a 3-year cost and a 2 to 6 month plan. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
