How FIGJAM Mobile delivers ERP integrations without a dedicated API team.
FIGJAM is a SaaS platform that helps distribution and logistics businesses manage field sales and van operations. Its mobile and web apps replace paper-based processes with real-time orders, stock management, and reporting. Serving customers across Africa and beyond, FIGJAM's value depends on reliable integration with the ERPs its customers run, and the ability to deliver those integrations without tying up its own core developers.
Every new customer needed an ERP integration, but there was no API team to build them
FIGJAM needed a Sage Evolution integration early on but could not justify the cost of Sage's developer license or the internal effort to build and maintain custom integrations from scratch. The business had no dedicated API integration team, and tying core developers to long, brittle integration projects was not viable.
ERPs and SDKs evolve. Any hand-coded integration would require ongoing maintenance every time an underlying system changed, a perpetual burden that would scale poorly as FIGJAM grew its customer base across Africa and into new regions.
Flowgear as the integration toolkit, built by support staff, not developers
FIGJAM selected Flowgear primarily for its Sage Evolution connector, and over time it became the default platform for all ERP and API integrations. Support and implementation staff now build and adjust Flowgear workflows themselves, using out-of-the-box nodes rather than writing thousands of lines of code. Where no dedicated connector exists for a less common ERP, generic web request nodes handle API-based integration.
FIGJAM uses Flowgear for Sage Evolution most frequently, but also for SAP Business One, Acumatica, and other platforms encountered in East and Central Africa. As ERPs release SDK updates and new API endpoints, Flowgear keeps pace, removing the re-engineering burden from FIGJAM's team.
Faster integrations, fewer headaches, and core developers freed
With Flowgear in place, time to integrate with customer ERPs is significantly shorter than building from scratch. Support and implementation staff handle the bulk of integration work, and the team can see inside workflows via logs, troubleshoot independently, and escalate to Flowgear support when needed. The result is that new customer integrations do not become a bottleneck for product development.
- Time to integrate with customer ERPs significantly reduced versus custom builds
- Support staff build and maintain integrations, core developers stay on the product
- Workflow logs give the team full operational visibility and self-service troubleshooting
- Flowgear keeps pace with ERP SDK changes, removing ongoing maintenance burden
- Default first question for any new ERP: can we do it in Flowgear?
“We don't have to put devs on long integration projects. Our support team can build Flowgear workflows instead. It's more like Lego than writing 10,000 lines of code.”
New ERPs, data pipelines, and AI-assisted workflows
FIGJAM is expanding into Microsoft Dynamics 365 Business Central and ERPs common in East Africa and India such as Tally. The team also plans to use Flowgear for moving data between FIGJAM's systems, customer ERPs, and data warehouses alongside tools like BigQuery.
FIGJAM is also exploring Flowgear's MCP server and AI-assisted workflow building to prototype and simplify flows faster, particularly for recurring tasks like data extraction and report generation.
More customer stories
TreasuryONE
Saves at least 5,000 hours a month, RPA fully replaced, no extra headcount.
Read the story
Dunlop Tyres South Africa
If Flowgear is switched off, no sales flow. It is the integration layer for both commercial and production operations.
Read the story
Bidvest Noonan
Salesforce and Aggresso integrated in four weeks, the internal team now owns and manages enterprise integrations themselves.
Read the storySystems connected in this story
Could this be your integration story?
Start building free for 90 days, or book an Integration Assessment for a prioritized roadmap first.