How much does a custom web application cost?

Your team is moving information between spreadsheets, messages and several tools. You want a platform that puts one important workflow in the same place, but “build an app” is too broad to price usefully.

Start by describing the job it must do. Who signs in, what they need to see and which action should take them from the beginning to the end?

Aruno budgets below exclude VAT and are indicative. The written agreement sets your scope, payment and ownership terms; this is general information, not legal or tax advice.

How much does a custom web application cost at Aruno?

A focused first version gives you a more useful budget than a wish list for a complete business system.

At Aruno, a custom platform's focused first version is typically €3,000 to €6,000 excluding VAT. The starting scope is login, a dashboard and one main workflow. This range depends on the agreed rules, screens and connections to other services.

Plan the build and ongoing responsibilities separately.

Cost area	Indicative Aruno budget, excluding VAT	Scope boundary
Focused first version	€3,000 to €6,000	Login, dashboard and one main workflow
Custom-platform maintenance	€100 to €250 per month	Updates, monitoring and bug fixes within 2 hours of hands-on work monthly
Hosting and paid services	Agreed separately	Accounts, subscriptions and usage costs
Later features	Separately quoted	New workflows, screens and integrations

Use the first row to define what can launch, then identify which other costs your platform will need.

This range doesn't cover a marketplace or several departments' processes. Our Aruno services include simpler sites and stores if those already do the job.

Already have a first version built with an AI tool? If it's custom code, cleaning up and finishing that MVP may cost less than starting over. We'd quote it once we've seen what can be kept.

What counts as one main workflow?

A workflow should have a clear starting point, action and result.

For example, an illustrative request portal might let someone sign in, submit a request, see its status and let a staff member approve or decline it. The dashboard shows the relevant requests. The quote still needs to name the roles, fields, status changes and notifications.

Adding payments, several approval layers or external records would widen that illustrative scope.

Write the normal path first. Then list the likely exceptions: missing information, an unauthorised person, a duplicate request or a failed notification. Those cases affect how safe and useful the platform is when people use it beyond a demonstration.

Decide what the dashboard helps someone do. Pending requests may be enough; add charts or exports for known decisions.

Name what's excluded from version one. A “later” list keeps the launch scope steady while leaving room to learn before building more.

Which features change the price most?

Business rules and connections often create more work than the visible number of screens.

These are useful details to include in your brief.

Requirement	Why it affects scope	Detail to provide
Different account roles	Each role can see or change different information	Roles, permissions and approval rules
External integrations	Other systems have access rules and failure cases	Service names and available documentation
Existing data	Records need mapping, cleaning and checking	Sample data and what must move
Payments or billing	Failed payments and changed subscriptions need handling	Charging rules and provider
Reporting	Calculations and exports need precise definitions	Which decision each report supports

Use real examples to explain these rules. “Managers see requests from their own branch” is easier to scope than “advanced permissions”.

Specify who invites people, removes access and views private records. For personal or sensitive information, get advice on your obligations and include those requirements in the brief.

For integrations, provide account access and decide what happens if the external tool is unavailable: should the request wait, retry or show an error?

How do you keep the first version focused?

Choose the smallest complete journey that your team can actually use.

It must work from start to finish, including important failure states. A screen that can't save isn't usable; building every possible report delays feedback.

At Aruno, design is approved before development. You can review the proposed screens and steps while they're easier to change. The design stage includes two revision rounds; new scope and additional rounds are quoted separately.

A focused platform usually takes 1 to 2 months, with the schedule agreed around scope, access and feedback. Choose someone who can answer business-rule questions and approve decisions promptly.

Judge the first version by whether someone can complete the task and understand the result. Test mobile journeys too; our guide to slow mobile websites explains problems that can interrupt them.

If you have one workflow worth replacing with a custom platform, we can discuss a focused first version. Bring the steps, account roles and a sample of the data involved so we can talk about the build scope. Book a free intro call with no commitment, or reach us at hi@aruno.studio, on WhatsApp or Telegram @mihaipostelnicu.

What should you ask before signing a platform quote?

A platform quote should describe working behaviour and the responsibilities after launch.

Confirm roles, screens, steps, migrated data, integrations and completion checks. A low quote without those details can leave both sides picturing different products.

Aruno payments are normally 50% upfront and 50% on completion by bank transfer. Custom deliverables transfer after full payment under the contract; third-party accounts need separate access and billing arrangements.

Our builds include 30 days of bug fixes after launch. Continuing maintenance is typically €100 to €250 per month excluding VAT, covering dependency and security updates, monitoring and bug fixes within a shared two-hour monthly hands-on allowance. Extra work is agreed and quoted first; new features are separate.

Agree backups, recovery and response expectations separately from monitoring. Name who restores important records and what happens beyond the allowance.

Test notifications through to the recipient, not just the confirmation screen. Our guide to forms that don't send emails explains that distinction for enquiries; the same question matters when someone relies on an approval email.

Frequently asked questions

These answers help you keep the budget tied to a usable first release.

How much does a custom web application cost at Aruno? A focused first version is typically €3,000 to €6,000 excluding VAT for login, a dashboard and one main workflow. More roles, integrations or workflows need a wider scope.

How long does a custom platform take to build? A focused Aruno platform usually takes 1 to 2 months. The agreed schedule depends on the rules, data, access and timely feedback.

Is a custom platform worth it? It can be when a repeated business process needs rules or connections that existing tools don't handle well. Compare the build and upkeep costs with the time, errors and limitations of your current process.

Does the price include ongoing maintenance? No. Continuing maintenance and running costs are separate from the build. Aruno's maintenance range is €100 to €250 per month excluding VAT with a shared two-hour hands-on allowance.

Can more features be added after launch? Yes, they can be scoped as later development. Keep the first release's boundaries clear so new ideas don't change the delivery target halfway through.

Describe one workflow from the first action to the final result. That gives your platform budget something specific to buy.