This is the first question almost every business asks, and it's a reasonable one — you can't plan a budget around "it depends." But a single figure quoted without knowing your project would be a guess dressed up as an answer, so instead of one number, here's what actually determines the cost, and a practical way to estimate before you talk to anyone.
What actually drives the cost
Scope and complexity are the biggest factor by far. A tool that replaces one spreadsheet with a form and a table is a different project from a system that models approvals, exceptions, and role-based permissions across a whole department.
Integrations add cost in a way that's easy to underestimate — connecting to your accounting software, a payment gateway, or an existing database each brings its own quirks, rate limits, and edge cases to handle.
Data migration is often invisible in a project brief and expensive in practice. Moving years of records out of spreadsheets or a legacy system, cleaning them up, and making sure nothing is lost takes real time.
Timeline compression costs money the same way it does in construction — asking for a six-month project in ten weeks usually means paying for a larger team working in parallel, not just working faster.
How we actually price work
A defined, well-scoped project is quoted as a fixed price, so you know the number before anything starts. A longer build, or one where the requirements are genuinely expected to evolve as you learn from real use, runs as a monthly engagement instead — it keeps the roadmap flexible without renegotiating a fixed quote every time priorities shift.
Either way, you see the breakdown before committing to anything, and you own the source code and the data outright once the engagement ends.
A practical way to estimate before you talk to anyone
List the workflows the system absolutely has to handle on day one, separately from the ones that would be nice to have — that split alone usually cuts a project's apparent scope by a third.
Count the systems it needs to talk to. Each external integration is roughly its own small project, so three integrations is a meaningfully bigger build than zero.
Decide honestly whether version one needs to be complete, or whether a smaller version that proves the concept with real users is good enough to start. Most projects that try to ship everything at once end up costing more and taking longer than two smaller releases.
Questions worth asking any quote you receive
Who owns the code and the underlying data once the project is delivered? Is a support or maintenance period included, and what exactly does it cover? How are change requests after launch priced — per request, or as part of an ongoing plan?
A quote that can't answer these clearly is worth a second look before you sign anything.
Three shapes a custom project usually takes
A single-workflow tool replaces one spreadsheet or manual process with a focused application: a form, a table, a few reports. It is the smallest kind of custom project and often the best place to start.
A department system models how a whole team works, with roles, approvals and exceptions. It costs more because there is more to understand, design and test.
A multi-system platform connects several tools and audiences, such as staff, customers and suppliers, and usually grows in stages. Planning those stages is as important as building the first one.
Knowing which shape you are in makes quotes easier to compare. To see how we handle each, read about our custom software development service, or if you are weighing it against buying a product, custom software vs off-the-shelf software.
More factors that move the price
Clarity of requirements: a project whose rules are written down is cheaper and faster than one discovered halfway through.
User roles and workflows: each type of user, and each approval or exception path, needs to be designed, built and tested.
Database and data complexity: how much data, how it is structured and whether existing records have to be cleaned and migrated.
Reporting and dashboards: a few fixed reports are a different job from flexible reporting across many measures.
Security and access control: sensitive data, audit trails and strict permissions add design and testing.
Deployment and maintenance: where it runs, who monitors it, and how updates and fixes are handled after launch.
We explain how these combine into a quote in how we price projects, and you can discuss your software requirements with us at any stage.
This is how we approach custom software development projects.
Custom Software Development