A no-code platform can get a working approval form to twenty people by Friday. Use that platform for 500 users, with data that must stay in one country and an ERP that has no API, and you are making a different purchase. This article shows where that line falls and how to tell which side of it your project is on.
DEFINITION
What Makes A Web Application An Enterprise Web Application
An enterprise web application is a browser-based system that runs a business process for many users across departments. It has role-based permissions, an audit trail, and connections to the company’s systems of record. All enterprise web applications are web applications. Most web applications are not enterprise web applications.
The difference shows in the requirements. A public website or a single-team tracker needs pages, a form and a login. An enterprise application needs to know who may approve a purchase over $10,000. It needs to record who changed a record and when, read stock levels from the ERP, and keep running when a thousand people open it at 8 am on a Monday. Common examples are operations dashboards that pull from several sources, approval and workflow engines, customer and partner portals, and integration layers that move data between systems that were never designed to talk to each other.
No-code platforms became the default way to build the first kind of app, and they are expanding into the second. Gartner forecast in 2021 that 70% of new enterprise applications would use low-code or no-code technology by 2025, up from under 25% in 2020 (InformationWeek). The question for a buyer is which of their applications belong in that 70%.
WHERE NO-CODE FITS
Three Cases Where A No-Code Platform Is The Right Choice
No-code is the better choice when the user count is small, the data is ordinary, and the process might be gone in a year. In those cases a custom build costs more and takes longer for no gain.
A Team Tool With A Short Life
An event registration tracker, an onboarding checklist for one department, or a survey for one quarter. If the app will be retired before a custom build would be finished, build it in the tool your team already licenses.
A Prototype To Test The Process
Building a rough version in no-code is a cheap way to find out whether people will actually use a new workflow. The prototype becomes the requirements document for a later build, which is worth more than a specification written from interviews.
Data That Lives Where The Platform Lives
If the records already sit in the vendor’s cloud and no regulation or contract restricts where they go, the platform’s own connectors do the integration work for you. There is nothing to move and nothing to approve.
THE LIMITS
Five Signs The Platform Has Reached Its Limit
A no-code platform reaches its limit when the cost, the data rules, the integrations, the permissions or the data volume grow past what the builder can handle. One of these on its own can usually be worked around. Two or three together are a strong signal to plan a custom build.
The User Count Grows Faster Than The App
Most enterprise no-code platforms charge per user. Microsoft Power Apps Premium is $20 per user per month, rising to $22 for new and renewed terms from 1 January 2027, and the 2,000-seat tier rises from $12 to $14 (Topedia). An app that started with 30 approvers ends up as a cost charged to every field supervisor who needs to see a single screen.
The Data Has To Stay In A Particular Place
Most no-code platforms run the application in the vendor’s cloud, and an air-gapped site cannot reach them at all. Where personal data is involved, each of these regimes sets its own test for sending data abroad: UK GDPR, Singapore’s PDPA with its Transfer Limitation Obligation, and the UAE’s PDPL. The ICO’s updated guidance from January 2026 sets out a three-step test for when a transfer to an overseas processor is a restricted transfer (Kennedys). A platform whose hosting region you cannot choose turns that test into an ongoing legal task.
The System Of Record Has No API
Connectors cover popular SaaS products well. A fifteen-year-old ERP, an on-premise database or a production line controller usually has none, so the work comes back to engineers anyway, now with a platform sitting between them and the data.
The Permission Model Outgrows The Builder
Separating records by business unit or by customer, multi-step approvals with delegation, and an audit trail an external auditor will accept can all be built in no-code. But they are built as layers of workarounds that nobody fully documents. When the person who built them leaves, the controls become guesswork.
Data Volume Reaches The Platform’s Query Limits
No-code platforms limit how much data a query brings back when the platform cannot pass the query to the database. In Power Apps that limit is 500 rows by default and 2,000 at most (Microsoft Learn). Reports that quietly miss rows above that limit are a serious problem in a compliance or finance dashboard.
COST
What Per-User Licensing Costs Over Five Years
Per-user licence costs grow with headcount. A custom build costs a fixed project fee plus maintenance and hosting. The table shows Power Apps Premium list prices only, before build effort, extra storage or a partner’s fees.
| Users | Per Year At Current List | Per Year From 1 January 2027 | Five Years At 2027 List |
|---|---|---|---|
| 50 | $12,000 | $13,200 | $66,000 |
| 200 | $48,000 | $52,800 | $264,000 |
| 500 | $120,000 | $132,000 | $660,000 |
| 2,000 (Enterprise Tier) | $288,000 | $336,000 | $1,680,000 |
ARSA’s custom web application projects typically run from $20,000 to $250,000 or more, with no per-user licensing fees. That comparison leaves out two costs. Annual maintenance is quoted as a percentage of the project value, agreed before the build. And if you host the system yourself, you pay for the hosting. At 50 users the platform usually wins. At 500 users on a process that will run for five years, the numbers deserve a proper calculation.
WHAT CHANGES
What A Custom Build Changes, And What It Leaves Unsolved
A custom build gives you control over where the application runs, how it connects to legacy systems, and how permissions are modelled. ARSA supports deployment on premises and in air-gapped environments. Most enterprise clients host the system themselves, and on-premise hosting is designed in from the first week. For a system with no API, the way to connect to it is worked out during the feasibility assessment, before any code is written.
What it does not change is time. ARSA delivers functional systems in 8 to 16 weeks, working in two-week sprints with a stakeholder demo at the end of each one. A no-code tool can deliver a first version in days. A custom build also cannot fix a process nobody has agreed on. If the approval rules are disputed, any software built on them will be disputed too.
ARSA’s own references include a restricted-area protection dashboard for Indonesia’s Ministry of Defense and PERCIK, the National Police’s vehicle registration physical check. In both, the data could not leave the client’s network, which is the same constraint that rules out most no-code platforms. Other engineering services are listed on the services page.
DECISION
How To Decide Before Committing Budget
Decide by writing down, before choosing a tool, five things: the data model, how many users the system will have over five years, where the data must stay, which systems it has to connect to, and who approves what. If all five fit inside the platform’s limits, build in no-code and review the decision when headcount doubles.
If they do not fit, ARSA’s feasibility assessment answers those questions in two weeks for $4,500. You get an operational diagnosis, a technical feasibility judgement, a cost model and a go or no-go recommendation. The fee is deducted from the project fee if you contract within 90 days. A no-go answer comes with its reasons, which is cheaper than finding out halfway through a build.
FAQ
Frequently Asked Questions
What Is The Difference Between An Enterprise Application And A Web Application?
An enterprise application runs a business process across many users and departments, and a web application is any software delivered through a browser. Many enterprise applications are delivered as web applications. What makes one enterprise grade is role-based access, audit trails, integration with systems of record, and support for an organisation’s full user base.
Is A No-Code Platform Cheaper Than A Custom Web Application?
For small teams and short-lived apps, yes. Per-user pricing grows with headcount, though. At $22 per user per month, 500 users cost $660,000 in licences over five years. A custom build has a fixed project cost plus maintenance and hosting, so the answer depends on user count and how long the system will be used.
Can An App Built In No-Code Be Rebuilt As A Custom Application Later?
Yes, and a working no-code version is often the best requirements document a custom project can start from. The screens, fields and approval steps show what users actually do. The data usually has to be exported and remapped, because no-code platforms store it in their own formats.
How Long Does A Custom Enterprise Web Application Take To Build?
ARSA delivers functional systems in 8 to 16 weeks, after one to two weeks of discovery and two to three weeks of design. Integration and testing add two to four weeks, and deployment with training one to two more. Projects that connect to legacy systems with no API sit toward the longer end.
Who Owns The Source Code Of A Custom Build?
For custom application code, the client usually does, agreed in writing before work starts. ARSA’s platform components and reusable libraries are licensed to the client and stay with ARSA.
Does ARSA Build For Companies Outside Indonesia?
Yes. ARSA’s list prices are in USD and invoicing is available in USD or EUR. Web application projects are delivered remotely in two-week sprints with a stakeholder demo after each one, and the system can be hosted on your own infrastructure in your own jurisdiction.
NEXT STEP
Scope The Build Before You Outgrow The Platform
If your application has passed two or more of the five limits above, set out the data model, integrations and permissions before anyone writes code. See how ARSA scopes and delivers Enterprise Web Applications, or contact ARSA to book a feasibility assessment.