App development pricing: the price is scope, not a range
Before you ask for a quote, define what the app needs to remember, pass on and document.
In this article
An air conditioner technician answers the phone while already on the roof, and discovers he does not remember which model is installed at the customer's place. The detail exists only in his head. A few days later a quote arrives for building an app, with an orderly number, but without a clear explanation of what is included in it.
The price of building an app is not a range you choose from. It is derived from a scope defined in advance: what the system needs to remember, to whom it passes information and what happens when something goes wrong. When two suppliers price the same document, you can start comparing the quotes themselves.
Why the ranges on the first page do not help
A price range does not answer the question of what you will get. One number may refer to basic screens, and another to a system that also manages jobs, equipment, updates and faults. Without a written scope, the numbers describe different things.
The air conditioner technician has three vans, calls with customers and a WhatsApp thread for every job. The visit address may appear in a message, the air conditioner model in an old invoice, and the decision whether to bring a certain part stays in the business owner's memory. If a quote for an app arrives without detailing these things, it is not clear whether it includes them.
The same problem exists both in a business that still works with notes and files and in a business that has already purchased software. The first needs to define what moves from the head into the system; the second needs to clarify which gaps remained between the software and the actual work. A good scope document starts with what the business needs to manage, not with the name of the software.
Anyone who wants to see which parts a system for a business can include can look at custom business platforms. The principle stays the same: before asking for a quote for app development, define what it is supposed to do on a regular workday and also when the day gets complicated.
The price is a scope, not a range
The price is a scope, and the scope is what the app remembers. Every component in the quote needs to refer to the information the system holds, to an action it performs or to a transfer it enables.
If the app saves only a name and phone, that is one task. If it also links the customer to previous jobs, to equipment documentation, to the next visit and to an update sent to him, a different scope is required. If it passes a job to a specific technician and returns the result of the visit to the office, that path also needs to appear in the document.
Therefore the question "how much does it cost to develop an app" is premature before agreeing what "app" means for the business. You can read more about business app development: three doors to one room, but in the quote request itself you need to phrase the business outcome: what information enters, what is done with it and how you know the task is complete.
What the app needs to remember
The requirements document starts with three types of memory: customer details, job details and equipment details. After them, you define who the information passes to and when, and what happens if there is no answer or the system is unavailable.
For the air conditioner technician, the customer list includes contact details, address and entry preferences for the property. The job list records the fault described, the visit time, the technician who handled it and what was reported at the end. The equipment list links an address or job to the brand, model and technical detail required for another visit.
Memory does not end with storing information. You need to define who sees each detail, who can update it and when the service office receives the visit result. If the technician does not answer, you need to decide whether the job stays pending, moves to a manager or requires a phone call. These are operational decisions, not decorations for a screen.
A document with eight screens that does not explain what information they display does not give a good basis for a quote. Also the difference between a custom CRM and SaaS is examined against the way the business works: what the business needs to manage, and how many adjustments are required for the system to reflect the existing process.
Five steps to define scope before asking for a price
You can prepare an initial requirements document during the week, without starting with choosing a supplier. At each step you turn a detail the business holds in its head into a written decision that can be priced.
- 1Collect recent jobs
Write what had to be remembered in each job
- 2Map people and roles
Note who passes information and who receives it
- 3Define faults and transfers
Document exceptions and what is done after them
- 4Approve a shared document
Send it to every supplier in the same version
Building the scope from the work itself
Let's say the air conditioner technician asks to examine an app for managing his jobs. He goes over a sequence of jobs, writes down what was required to remember in each one, and then checks who needs to receive the information. At the end of the process he has a document that can be passed to suppliers.
1. Write the recent jobs and what had to be remembered
Open the list of recent visits and write next to each job what had to be remembered in order to handle it: who the customer is, what the fault was, what equipment was installed, which parts were required and what was said at the end of the visit. Use existing records, messages and invoices, without putting personal details into a document meant for distribution.
The result is a list of information that repeats across different jobs and of details unique to a particular case. For the technician, for example, it turns out that the air conditioner model and whether a part has already been replaced are not always in the same place. This is exactly a point that needs to be defined.
2. Split the information into customer, job and equipment
Take every detail from the list and assign it to the customer, the job or the equipment. If a detail relates to more than one, state the connection explicitly: a specific job at a specific address, with a specific model unit, handled on a specific date.
The result is an information structure that can be checked. The technician identifies, for example, that the equipment model should be accessible from the job details, but also kept for continued handling at the same address.
3. Mark who passes on and who receives each update
For every detail or action, write who enters it and who needs to see it afterward. State whether the technician updates from the field, whether the office schedules a visit, and whether the customer needs to receive a confirmation or a follow-up message.
The result is a short handoff map, not a general user list. For the technician, a job completion report should reach the office, so that billing or a further visit can be handled.
4. Write what happens when there is an exception
Choose situations in which the regular process stops: the customer does not answer, there is no suitable part for the vehicle, the job runs long or the technician cannot arrive. Next to each situation, write who decides what to do, to whom the handling is passed and which information must remain documented.
The result is a list of exceptions that can be included in the proposal. In the case of a missing part, for example, it must be decided whether the technician marks the job as waiting and who coordinates the next visit.
5. Prepare one scope page and ask for an answer on the same basis
Combine the memory list, the roles map, the work process and the exceptions into one document. Add what is not included, which data exists today and what is expected to remain outside the application.
The result is an application project scope that can be sent to every vendor in the same version. Ask each vendor to detail the work against the sections, mark assumptions and state what is required after go-live.
Question for the vendor: According to the attached scope document, which details, handoffs and exceptions are included in the proposal, and what remains outside it?
Line for a quote request: Please price the same scope document, and note separately assumptions, components not included and work required after go-live.
What costs money after the app is live
A quote is not complete if it describes only the build. Ask to know who handles fixes, adjustments when the process changes, software updates, backups, and faults that disrupt use.
In the case of the air conditioning business, the types of jobs may change, fields that must be documented, or the way the office passes a task to the technician. Ask whether such changes count as maintenance, an extension, or new work. Also ask to separate a fault that prevents use from a request for an additional feature.
You should also clarify what happens to the customer's data if the engagement ends, in what format it can be exported, and how long it remains available. These are questions about the scope of service and about the data, not about a promise that the system will never change.
If using AI built in is being considered, add to the document what is passed to the service, who approves an action before it is sent, and what is kept in the log. Systems can be built to support customer obligations under the Privacy Protection Law (Amendment 13) and the GDPR. This is not legal advice.
How to compare quotes that cannot be compared
To compare quotes, read each one against the same scope document and mark for each item whether it is included, missing, or priced as a separate discount. Comparing by the final number alone hides differences in the work and in maintenance.
| What to check | Question for the quote | What breaks without an answer |
|---|---|---|
| Customer details | Which details and relationships are kept? | Information stays outside the customer card |
| Job details | How are execution and outcome documented? | It is impossible to see what was done |
| Equipment | How is equipment linked to the address and the job? | Treatment history scatters |
| Information transfer | Who gets an update and at which stage? | A task gets stuck between people |
| Exceptions | What happens when a customer or technician is unavailable? | No role owner for continuing treatment |
| After go-live | What does ongoing treatment include and what is priced separately? | Maintenance is discovered late |
| Data | How and when can it be exported? | It is unclear what remains accessible |
- Shared document
Same processes and same exceptions for every vendor
- Answer for each item
Included or missing, discount or extension
- Maintenance after go-live
Fixes, changes and data export
Compare the scope, not just the bottom line
For the technician, one quote may include equipment documentation but leave the transfer of the job to the office out of it. Another quote can include the transfer, but assume the data will be entered manually. The two quotes may look similar at first glance, but they do not answer the same requirement.
Ask every vendor to return the document with an answer next to each item. Note their assumptions, the connections to existing systems, and what is not included. If the vendor proposes changing the process, ask them to explain what changes and why; do not mix a change in scope with a change in price without understanding the context.
In an existing system, also check whether the work requires a connection to other software or a data transfer. A question about business automation and when it becomes a burden can help identify whether the process relies on connections that need to be maintained. For a business still organizing its customer details, a CRM guide for small businesses deals with choosing a way to manage them.
What to answer when asked how much it costs
When asked how much it costs to develop an app, the accurate answer is that the price is set after defining what the system needs to remember and do. Without a shared document, a quote is a number with no basis for comparison.
You can answer: "We first define the customer details, the jobs and the equipment, who needs to receive updates and the exceptions. Then we ask each vendor to price the same scope and separate the build from the care that follows."
The price of app development starts with the business's decisions, not with a range that appears in a search result. alcyone14 builds businesses a system around the way they already work, with AI built in for routine work, and keeps running and improving it as the business changes. Anyone who wants to check fit can start by sharing one process and its scope document.
Frequently asked questions
How much does it cost to develop an app for a business?
You cannot derive a reliable price without defining the scope of work. Detail what the app needs to remember, to whom it passes information and what is required after launch, then ask for quotes on the same document.
What should a quote for app development include?
A quote should detail the processes and information included, assumptions, components not included and what is required for maintenance after launch. That way you can identify whether two quotes are actually pricing the same system.
How do you choose an AI vendor that does not keep our customers' information?
Do not assume anything in advance about how information is stored: ask the vendor to detail in writing what is sent to the service, what is stored, for how long, who can access it and when the information is deleted. Check the answers against the vendor's commitments and legal documents before feeding in real information.
What is the difference between a tailored app and ready-made software?
Ready-made software offers an existing process that can be adapted to a certain extent, and a tailored app is defined according to the process the business needs to manage. The decision depends on the gap between the business's needs and what the ready-made software allows.
What costs are there after the app goes live?
You need to clarify in advance what is required for maintenance, fixes, changes, connections to other systems and data export. Ask to separate handling a fault from developing a new capability.
A system that fits the way you work?
Let’s talk about the workflows, team and tools you want to connect in your business.
Let’s talk about your system