Velo Working / Field notes / Positioning Jodoo

Do you need an
IT department?

Before you choose between Cloud ERP, Low-Code, and No-Code, answer one question — who in your own building has to keep the system alive after launch? The honest test is the org chart you'd need to support each option.

Field notes Positioning May 2026 ~4 min read

Most SMEs don't pick an operations system off a feature list. They pick it on a hidden question they never quite say out loud: who in our own building has to keep this thing alive once the implementation partner leaves the room?

Cloud ERP needs an IT department and a system integrator on retainer. Low-Code needs an in-house development team. Only No-Code can be run, day-to-day, by trained operations staff. The org chart you'd need to support each option is a faster, more honest filter than any three-year TCO spreadsheet.

The framing
Resource demand  ×  Operational self-sufficiency
Organisational lens

Resource demand × Operational self-sufficiency.

X-axisResource demand (capital + people + time)
Y-axisOperational self-sufficiency once live
LOWER DEMAND → MORE SELF-SUFFICIENT → NEEDS DEPARTMENT NEEDS TRAINED STAFF Cloud ERP IT dept + SI partner Low-Code In-house developers No-Code Trained ops staff

"ERP needs an IT department. Low-Code needs developers. No-Code needs trained operations staff."

ERP

Needs an IT department.

A full-stack platform that assumes you have a system integrator on retainer and an in-house team to manage upgrades, integrations, and changes. Right answer for large enterprises — a tax on most SMEs.

Low-Code

Needs developers.

Faster than ERP, but every meaningful change still routes through a developer sprint. You've reduced the team to one or two builders — not eliminated the dependency.

No-Code

Needs trained operations staff.

Your own ops people, after a focused build phase, can configure forms, workflows, and dashboards. The system stops being IT's problem and becomes part of how the business runs.

What it means in practice

Three implications for SMEs choosing an operations system.

01

Match the system to the org you actually have.

The cheapest platform on paper is the wrong one if it demands a department you don't have. Start from your headcount, not the feature list — the system that fits your org chart is the one that will still be running in five years.

02

Self-sufficiency beats licence price.

An ops team that can configure their own forms, workflows, and dashboards is worth more, monthly, than any saving on subscription cost. Self-sufficiency is the strongest defence against vendor lock-in there is.

03

The platform is only half the answer.

No-Code unlocks the org-chart fit — but only if someone teaches your staff how to use the platform. The work is one part build, one part training. Both have to land for the system to belong to your team.

Velo Working · Official Jodoo partner, Singapore

Engineered with Jodoo. Owned by your team.

Velo Working engineers SME operations on Jodoo — Asia's leading no-code workflow platform — and hands the keys to your team. Fixed scope. Fixed fee. No subscription. No vendor dependency.