Custom web application development covers an enormous range of scope and complexity, which means the cost range is equally wide. If you have asked for quotes and received wildly different figures, that is not necessarily a sign that something is wrong. But understanding what drives the cost helps you evaluate what you are being offered.
The primary drivers of cost in custom development are complexity of the data model, number of integrations with external systems, number of user roles and permission levels, volume and complexity of business logic, requirements for real-time data, and the expected scale of concurrent users. Each of these adds development time. Beyond the core functionality, things that are often underestimated include authentication and security requirements, testing, documentation, and the time needed to deploy and configure a proper hosting environment.
Regardless of the size of the project, certain things should be consistent. You should receive a clear specification before any code is written. You should own the code at the end of the project. The codebase should be documented well enough that another developer could work on it without the original developer. You should have access to source code through a version control repository. Hosting and deployment should be handled in a way that does not create lock-in to a specific provider or individual.
A significantly lower quote for the same stated scope usually means one of three things. The developer has found a way to deliver the scope more efficiently, which is possible. The developer has made optimistic assumptions about the requirements, which tends to result in scope creep and additional costs during the project. Or the quote reflects a lower quality of output, which may manifest as poorly structured code, absent documentation, or an application that works on day one but becomes increasingly difficult to maintain. Not all cheaper quotes are problematic, but it is worth understanding which of these categories applies.
A custom application requires ongoing maintenance. PHP and its dependencies require updates. Security patches need to be applied. Hosting needs to be managed. Business requirements change, and the application needs to change with them. These ongoing costs should be factored into the investment decision from the outset, not discovered after the build is complete.
The most important thing you can do before asking for a quote is to define what you need as clearly as possible. Not in technical terms, but in business terms: what the application needs to do, who uses it, what data it handles, and how it connects to other systems. A developer who asks detailed questions before giving a price is a better sign than one who quotes quickly from a brief description. The questions are how the complexity is understood, and complexity is what drives the cost.
Custom software development has a higher upfront cost than buying a subscription to an existing tool or adding another plugin to your CMS. That cost is often the reason businesses do not pursue it. But in the right circumstances, the return on a bespoke application is clear, measurable, and often much faster than expected.
Most business websites are built on content management systems. That makes sense for most situations. But there are cases where a CMS is the wrong tool, and the gap between what a CMS can do and what a business needs it to do creates ongoing friction, cost, and limitation. Knowing when a bespoke solution makes more sense is a useful thing to understand.
Most clients come to us when their site has started to feel like a risk rather than an asset. Whether the agency relationship has ended, an upgrade has been delayed, or the site has simply grown beyond what it can handle, a conversation costs nothing.
Get in touch with KarlTrusted by established businesses and growing brands across the UK
Expression 37 works with a small number of clients at any one time. These are some of them.
Karl founded Expression 37 in 2007 and has worked exclusively with ExpressionEngine and Craft CMS ever since. He does not take on work in other platforms and does not hand work to other developers. Expression 37 is deliberately small, because the kind of support that matters to clients with business-critical sites is specific to their site, not something that scales in the conventional sense. If you work with Expression 37, you work with Karl.
Find out how we workKarl was very helpful in providing us with essential insights into the inner workings of our ExpressionEngine driven site. His knowledge level with the ExpressionEngine platform is very impressive and we look forward to dealing with Karl again in the future.
Tim Cullum - Digital Comms Media
David H. Murdock Research Institute