How much does a custom business application cost?

What you pay for in a business application

The price of a business application mostly reflects time spent on design, development and testing. That time depends less on the number of screens than on the rules to follow: who can see what, what happens when information is missing, how a mistake gets corrected. Two applications that look alike in a demo can require very different amounts of work.

On top of that come go-live, onboarding the team and running costs over time: hosting, external services, AI model usage where relevant, and maintenance. These items continue after delivery. A serious proposal lists them separately from development, even when they are modest.

So the question “how much does an application cost?” first calls for another one: what work should it let you complete? Until that workflow is described, a figure does not tell you what you are buying.

What drives the cost of an application

Scope. The number of complete workflows to build matters more than the feature list. Receiving a request, handling it and keeping a record of it is one workflow. Every additional role, approval step and exception adds work.

Platforms. A web application used in the office, an iPhone and Android app for field work or offline access do not take the same effort. Targeting several platforms in the first version increases what has to be built and tested.

Data. Importing existing files often means removing duplicates, clarifying formats and deciding what to keep. This work is frequently underestimated, by clients and providers alike.

Integrations and maintenance. Connecting the application to invoicing software, a CRM or a third-party service depends on what those tools allow. Each integration then has to be monitored and maintained: maintenance grows with the number of parts that must work together.

Three example scopes, at €5,000, €7,000 and €15,000 excl. VAT

The amounts below are indicative examples, not a price list. They describe what a first version can contain at three budget levels, for a small business, a professional practice or a field team. Each project gets a fixed price, agreed before work starts, after a scoping discussion. The factors described in the previous section then move the amount: an extra platform, data to import or a difficult integration will raise it.

€5,000 excl. VAT: job tracking for a team of tradespeople. Requests come in by phone or text message, and the progress of each job is not recorded anywhere.

• First version: a web app that works on a phone to create a request, assign it to a technician, write the job report with photos, look up the history and export the list to a spreadsheet. A single user profile: the whole team has the same permissions.
• Out of scope: integration with other software, an app published on the App Store or Google Play, customer access.
• Indicative timeline: three to four weeks from scoping to go-live.

€7,000 excl. VAT: the same kind of tool, connected to existing software or assisted by AI. Job reports are entered, but the information is retyped into the invoicing software, or writing quotes takes too long.

• First version: the tracking workflow described above, plus one extension of your choice. Either an integration with a tool already in use, such as invoicing, the calendar or the CRM, through its API where one exists or through file import and export. Or an AI assistant that prepares a draft quote or job report from the team’s data; a person reviews and approves it before anything is sent.
• Out of scope: several integrations, two-way synchronisation, automatic sending without approval, an app published on the app stores.
• Indicative timeline: four to six weeks, depending on access to the software to connect or to sample documents.

€15,000 excl. VAT: a business application for the office, the field and customers. A service business or professional practice coordinates requests between the office, field staff and its customers, with several software tools that do not talk to each other.

• First version: three roles with their own permissions (office, field, customer), a web app and an iPhone and Android app for field work, two or three integrations with existing tools. An AI agent sorts incoming requests and prepares replies; the office approves before any action is taken.
• Support: go-live, onboarding for each role, documentation and a maintenance plan, with its recurring cost stated separately.
• Out of scope: replacing the accounting software or ERP, importing the full history beyond what is agreed, AI actions without approval.
• Indicative timeline: two to three months, with a demo at each stage.

In all three cases, the amount covers building the first version, its go-live and onboarding. Hosting, third-party services and AI model usage remain recurring costs, quoted separately. To place your project, describe the workflow to build: the scope and price are agreed together before work starts.

Fixed price or time and materials: two ways to charge

With time and materials, you pay for the time spent, usually by the day. This suits needs that keep changing, or a provider team working as an extension of yours. The risk of overrun stays with you: if the work takes longer than planned, the invoice follows.

With a fixed price, the price is set for a defined scope. The risk moves to the provider, who must therefore define precisely what is included. A fixed price is only worth something if the scope and acceptance criteria are written down. Without them, every disagreement becomes a negotiation.

A fixed price per version combines both approaches: a fixed price for a useful first version, then a new proposal for each following stage, decided on the basis of actual use. You do not commit the whole budget to assumptions that have not yet been tested.

Why set a fixed price for a first version

At ClairAI, the proposal covers a useful first version: a complete, testable business workflow defined with you, for example creating a case, attaching its documents and tracking its status. The price is set before work starts, together with the acceptance criteria, go-live and onboarding.

This approach forces the scope to be defined before building. Deferred features are named, expected recurring costs such as hosting, third-party services or AI model usage are listed separately from development, and later changes are covered by a new agreement. No single price is published, because each proposal depends on the workflow to build.

SquareTally illustrates this kind of scope: starting from a PDF floor plan, measuring the rooms and preparing a materials quote, with a draft in the invoicing software already in use. The tool targets one specific job rather than running the whole business. To see how a project unfolds, read about our custom application service.

Comparing quotes and spotting warning signs

To compare application development quotes, bring them back to the same basis: which workflow will be usable at delivery, by whom, on which platforms and with which data. The guide to preparing and comparing a business application quote lists the questions to ask each provider.

Some signs deserve a question before you sign:

• A price without a written scope: the figure says neither what will be delivered nor how delivery will be accepted.
• No mention of running costs: hosting, third-party services and maintenance will still have to be paid for.
• An estimate given without seeing your data or your tools: integrations and file imports are often where costs slip.
• Vague ownership terms: you need to know how you will recover the code, the accounts and the data.

A lower quote may cover a narrower scope or leave items out of the price. If off-the-shelf software already meets your need, start there: the guide to choosing between off-the-shelf and custom helps you decide.