Two quotes for "the same app" can be far apart without either developer cheating. They priced different assumptions. This post lists the decisions that move the price, with examples from systems I built and still run: a restaurant POS, a school payment platform, a delivery platform and a coffee roaster's ordering platform.
Why quotes for the same idea differ
A one-line brief ("a booking app", "something like Uber for our couriers") leaves the expensive questions open. One developer assumes a single admin and a web form; another assumes four roles, a mobile app and card payments. Both are reasonable readings. To compare quotes, answer the questions below first, so everyone prices the same thing.
1. User roles and permissions
Every kind of user adds screens, rules and tests. A customer, a member of staff and an owner see different things and may do different things, and every rule has to be enforced on the server, not only hidden in the interface.
The Lucas Coffee platform runs six interfaces on one TypeScript core, from the customer's ordering and loyalty app to a wholesale portal with company-specific prices, invoices and balances. Each interface is its own set of permissions over the same data.
2. Integrations with other systems
Every payment gateway, courier service, marketplace or accounting system is a small project inside the project. You depend on another company's documentation, test environment and support.
OkulSistem collects school fees through the 3D Secure flows of two banks, Garanti BBVA and VakıfBank. Paket X receives orders from restaurant websites, POS systems and marketplaces through a partner API and a WooCommerce plugin. When you list integrations, name the provider: "card payments" is vague, "VakıfBank 3D Secure" can be estimated.
3. Real-time updates
If a change on one screen has to appear on another within a second, the system needs a live channel and has to cope with dropped connections. In RentonSoft POS a waiter's order reaches the kitchen, bar and cashier screens at once through Socket.IO rooms per role. A report that updates when you reload the page costs far less to build.
4. Money moving through the system
Payments need more care than any other feature. A double tap must not charge twice, a refund must leave a trail and the totals must reconcile at the end of the day. RentonSoft POS uses transactional payments with idempotency keys, manager-PIN refunds and Z reports. OkulSistem never stores card data and has an approve-or-reject flow for bank transfers. If your software takes money, budget for this part on its own line.
5. Mobile apps
A web app runs wherever there is a browser. Native or cross-platform apps add store accounts, store review and release work on two platforms. The Apple Developer Program costs $99 a year and a Google Play developer account has a one-time $25 fee; the larger cost is the time spent on store review and testing on real devices. Ask whether a phone-friendly web app covers the first version.
6. One business or many (SaaS)
Software for one company and software sold to many companies are different products. The second needs sign-up, trials, billing and strict separation of each customer's data. In RentonSoft POS every business has its own PostgreSQL schema, and an expired trial turns read-only instead of being deleted. You do not need that work if the software only serves you.
7. Moving the old data
Most projects start with data somewhere: spreadsheets, an old system, paper. Importing it is a task of its own, with cleaning and checks. OkulSistem started from the school's Excel list of students and parents. Decide early what has to be in the system on day one.
8. Hosting, backups and maintenance
The build is not the whole cost. Software needs servers, backups, security updates and someone who notices when something breaks. I run what I build on my own servers with Linux, Docker, OpenLiteSpeed and Cloudflare, with backups and monitoring. Whoever you hire, ask who runs the software after launch and what that costs per month.
How to get a tighter estimate
Send a brief that answers the points above. Four lines are enough:
- The problem, in one or two sentences.
- Who uses it and where: staff on tablets, customers on phones, an accountant on a laptop.
- What exists today: designs, code, servers, spreadsheets.
- Timing and a budget range.
Then cut the first version down to one main flow for one or two roles. A small version in real use answers questions that a long specification cannot, and later features are easier to estimate once the core exists.
Frequently asked questions
Is an off-the-shelf product cheaper?
Usually, if it fits how you work. Custom software pays off when your rules are the point: your pricing, your approval steps, your integrations. Some of my products sit in between: the POS and the QR menu are ready products set up with your branding.
How long does a first version take?
It depends on the same eight points. One role and one main flow is a small project; each extra role, integration or app adds to it. Send the brief and I will tell you what a first version could include.
What does it cost to run after launch?
Servers, domain, backups and updates, plus per-transaction fees from payment or SMS providers and the yearly store fees if there are mobile apps. SSL certificates from Let's Encrypt are free.
Do I need a full specification before I get in touch?
No. A short brief is enough to start. The details are worked out in the first conversations, and the open questions become part of the estimate.