Three categories of business software —
and the quiet shift underway.
Top management still asks the wrong question. It isn't "should we buy SAP or Oracle." It's which category of software fits our company at all — and which one our workforce will still be operating in 2030.
When SME boards in Singapore and the region debate operational software, the conversation usually orbits a single vendor name — SAP, Oracle, Microsoft Dynamics. The names carry weight. They sound serious. They sound safe. But SAP, OutSystems, and Jodoo aren't three vendors competing for the same job. They sit in three entirely different software categories, each engineered for a different size of company, a different operating model, and — increasingly — a different generation of workforce. Understanding the categories before choosing the vendor is what separates a strategic technology decision from an expensive accident.
Cloud ERP Suites — the giants.
SAP, Oracle, and Microsoft Dynamics 365 belong to the category Gartner formally calls Cloud ERP for Product-Centric Enterprises and Cloud ERP for Service-Centric Enterprises. These are pre-built suites of enterprise modules — Finance, Supply Chain, HR, Manufacturing, CRM — built on rigid data models that reflect a vendor's view of best practice.
You buy the suite. You configure it. Any deviation from the vendor's model requires customisation in proprietary languages — ABAP for SAP, X++ for Dynamics, PL/SQL for Oracle. Implementation is typically led by a Big Four or Tier-1 system integrator and stretches across 18 to 36 months. Total cost of ownership for a 200-user deployment runs S$3M–S$15M over three years.
This category is engineered for one buyer: the large, multi-national, regulated enterprise.
Low-Code Application Platforms — for builders.
OutSystems, Mendix, Microsoft Power Apps, Appian, ServiceNow and Salesforce belong to Low-Code Application Platforms (LCAP) — a Gartner Magic Quadrant category in its tenth year.
Unlike ERP suites, low-code platforms come with no pre-built business modules. You're not configuring an existing accounting system; you're building a custom application from scratch, but faster than traditional coding. Visual development handles the bulk of the work; professional developers drop into actual code for complex logic, integrations, and custom interfaces.
The buyer here is the enterprise with an internal IT team that needs to ship many bespoke applications faster than their developers can hand-write them.
No-Code Platforms — for everyone else.
Jodoo, AppSheet, Airtable, Bubble, and Glide belong to the emerging category Gartner now formally tracks as Citizen Automation and Development Platforms (CADP). There is no dedicated Magic Quadrant yet — the category is still maturing — but Gartner addresses it directly in its LCAP commentary and forecasting research.
No-code platforms eliminate code entirely. Business users — operations managers, accountants, production planners — build forms, workflows, databases, and dashboards by configuring rather than programming. The output is a working operational system that any trained staff member can modify the next morning when the business rule changes.
The buyer here is the SME or department that doesn't have an IT team and never will — but whose operations are still unique enough that off-the-shelf SaaS doesn't fit. This is the segment ERP suites price out and low-code platforms cannot reach.
Where the three sit on a single map.
Gartner publishes its Magic Quadrants within categories, never across them. To compare the three categories themselves, the more useful axes are speed of change — how fast can you deploy and adapt — and operator: who can actually run and modify it.
Side-by-side, on the dimensions that decide.
Fifteen dimensions, grouped by what top management asks first — identity, people, time, cost, adaptability, fit. The pattern is consistent throughout: each category sits in a different operational world.
| Dimension | Cloud ERP SuiteSAP · Oracle · MS Dynamics | Low-Code PlatformOutSystems · Mendix · Power Apps | No-Code PlatformJodoo · AppSheet · Airtable |
|---|---|---|---|
| Identity | |||
| Gartner category | Cloud ERP Suite | Low-Code Application Platform (LCAP) | Citizen Automation & Development Platform (CADP) |
| Pre-built modules | Yes — full enterprise suite | None — build from scratch | None — build from scratch |
| People & code | |||
| Who builds it | Certified consultants + internal IT | Professional developers | Trained business staff |
| Coding required | ABAP / X++ / PL-SQL | Yes — for complex logic | None |
| Time | |||
| Time to first module | 6–18 months | 2–6 months | 2–4 weeks |
| Time to full deployment | 18–36 months | 9–18 months | 3–9 months |
| Cost | |||
| Typical implementation cost | S$500K – S$10M+ | S$100K – S$1M+ | S$10K – S$100K |
| 3-year TCO (200 users) | S$3M – S$15M | S$800K – S$3M | S$50K – S$300K |
| Cost of every change request | High — consultant hours | Medium — dev sprint | Near-zero — staff edits live |
| Adaptability | |||
| Time to adapt to a process change | Weeks to months | Days to weeks | Minutes to hours |
| Vendor / SI dependency | Very high | Medium | Low |
| Data portability | Proprietary, hard to migrate | Standard DB, exportable | Standard formats, exportable |
| Risk & fit | |||
| User scale | Tens of thousands | Thousands – tens of thousands | Hundreds – low thousands |
| Project risk profile | High — big-bang go-live | Medium | Low — module-by-module |
| Best-fit business size | 1,000+ headcount enterprise | 200–5,000 with IT team | SME, 10–500 headcount |
Why no-code becomes infrastructure.
In 1985, a small fraction of office workers used computers — typing pool secretaries and specialists in accounting departments. By 2005, every white-collar professional was expected to operate Word, Excel, PowerPoint, and Outlook without thinking about it. The skill ceased to be a skill. It became infrastructure — the assumed baseline on which all knowledge work runs.
of new enterprise applications
will be built using low-code or no-code technologies by 2026 — up from less than 25% in 2020. By the same year, citizen developers will outnumber professional developers four to one.
What the rest of the data says
Three forces converging
This shift isn't a fashion. Three structural forces are driving it simultaneously, and none of them reverse.
The developer shortage is permanent
The world will be short 85 million software engineers by 2030. No country's training pipeline can close that gap. Companies that depend on hiring specialists to maintain their operational systems will lose to companies whose own staff can do it.
The incoming workforce expects to build its own tools
Generation Z grew up with computational thinking embedded in K-12 curricula. They will not tolerate waiting six weeks for IT to add a field to a form. They will build it themselves, or they will leave.
AI is collapsing the cost of building software
Microsoft reports that 30%+ of its own code is AI-generated. The bottleneck of software development is shifting from writing code to describing what you want — a skill every business user already has.
Put together, these forces produce a single conclusion: the ability to configure operational software will become a baseline workplace skill, much as spreadsheet competency did between 1990 and 2005. The companies that build that capability into their own teams now will compound a structural advantage for the next two decades. The companies that lock themselves into systems only specialists can modify will be paying tomorrow's premium for yesterday's architecture.
What this means for SME top management today.
For a 30-person Singapore manufacturer or a 150-person regional trading firm, the strategic calculation is unusually clean. The cost gap alone tells most of the story.
The cost gap is not a tradeoff — it is a category boundary.
You will not be hiring a five-person IT team to support a Tier-1 ERP. The cost is wrong; the talent isn't available; and even if it were, it isn't what your business needs. The category was not engineered for you.
You will not be running a low-code platform either. Low-code requires the very developer talent the market is short on. It is a platform for companies whose problem is "we have developers; they're not fast enough" — not "we don't have developers."
What an SME actually needs is the same thing it has always needed: a system that fits the unique way your operation runs, that can be changed by the people who run that operation when reality changes, and whose total cost matches the scale of the business it serves.
That is the no-code category. Not a fashion. Not a tradeoff. The structural fit.
A closing perspective.
Top management debates over enterprise software usually start with vendor names. They should start with category fit. The right category, badly executed, still beats the wrong category executed perfectly — because the wrong category is built for someone else's company.
For SMEs, the next decade's competitive line is being drawn now: between companies whose teams own and evolve their own operations, and companies whose operations live inside a system nobody in the building can change without a quote from outside.
The first group will compound. The second will pay rent on every change, every year, forever.
The category your SME is actually in.
Velo Working engineers SME operations on Jodoo — Asia's leading no-code workflow platform. If you're trying to figure out whether your company belongs in the no-code quadrant, we'll walk you through it honestly.