Generic SaaS was built for a flat year, and Edinburgh's year has a wall in August
Custom software in Edinburgh generally costs £60,000 to £180,000 over four to ten months, depending on scope. Build when generic SaaS forces your festival, finance, or fintech operation into a shape it doesn't fit, especially around the August spike or regulated workflows. Buy off-the-shelf when your process is standard and a configured product covers it.
Most SaaS is designed for a business with a flat, predictable year. Edinburgh businesses rarely have one. A festival operator's demand triples in three weeks, a fintech's workflow is shaped by regulation, and an asset manager's process is built around discretion and multi-entity reporting. Generic SaaS handles the average case and quietly breaks at the edges, which for these firms is exactly where the value and the risk live.
The usual result is a stack of SaaS tools stitched together with integrations that mostly work, plus a layer of spreadsheets and manual steps that absorb everything the products can't. It functions until August, until an audit, or until growth, and then the seams show. At that point the cost of the workarounds, in time and risk, starts to rival the cost of building software that fits the business as it actually operates.
- Generic SaaS forces a process that doesn't match how you operate
- Your spreadsheet-and-integration workarounds have become load-bearing and risky
- The August spike or a regulated workflow is central and unsupported off the shelf
- The software is a genuine competitive differentiator, not a commodity function
- Your process is standard and a configured SaaS product covers it well
- You need something live quickly and the off-the-shelf gap is minor
- You lack the internal ownership to specify and steward a custom build
- The function is a commodity where bespoke offers no real advantage
- Software shaped around your real process, not a vendor's average customer
- The August spike modelled as a first-class design constraint, not an edge case
- Regulated workflows built to compliance requirements from the start
- A single coherent system replacing a brittle stack of integrations and spreadsheets
- A competitive edge competitors using the same generic SaaS can't copy
- Higher upfront cost and longer timeline than configuring a SaaS product
- You own maintenance, security patching, and future development
- Specifying bespoke software demands real internal time and clear ownership
- A poorly scoped build can become its own expensive workaround
The honest cost picture for Edinburgh
| Project scope | Typical cost | Timeline |
|---|---|---|
| Focused custom application replacing a key SaaS misfit | £60,000 to £100,000 | 4 to 6 months |
| Multi-workflow platform with integrations and compliance | £100,000 to £180,000 | 6 to 10 months |
| Maintenance, security, and ongoing development | £12,000 to £36,000/year | ongoing |
Feature priorities for Edinburgh teams
What we build under custom software in Edinburgh
Digital Heroes builds the full custom software stack for Edinburgh teams. Typical engagements cover systems integration, microservices, database design, bespoke software development, SaaS development and web application development.
Exactly what you get
Software built around your real operation: the festival surge, the regulated workflow, or the multi-entity process, with the integrations that retire your spreadsheet layer. You get a coherent system instead of a stitched stack, designed to hold through August and stand up to an audit. It typically connects to or replaces parts of your ERP (Enterprise Resource Planning), CRM, accounting, and booking tools so the whole stack pulls in one direction.
How to choose a developer in Edinburgh
Look for a team that spends real time understanding your process before proposing anything, and that has shipped software for seasonal or regulated businesses. Ask for a reference where a custom build replaced a failing SaaS stack. Edinburgh's market rewards discretion and quality, so favour a developer who scopes carefully, communicates clearly, and commits to maintenance rather than disappearing at launch.
Timeline: what happens, and when
- !They start with technology, not your process; ask them to map your August workflow first
- !No compliance discussion for regulated work; ask how they'd handle an audit trail
- !They under-scope discovery; ask how they'll avoid building the wrong thing
- !No maintenance plan; ask who patches security after launch
- !They can't show a comparable build; ask for a reference solving a seasonal or regulated problem
Most Edinburgh teams pricing custom software end up comparing notes on website, inventory management, warehouse management too; the systems share one data spine.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
When is custom software cheaper than SaaS plus workarounds?
When the workarounds become load-bearing. Once the time, risk, and lost margin from spreadsheets and brittle integrations rival the SaaS licence cost, a custom build that fits the process often pays back, especially for Edinburgh's seasonal and regulated firms.
How do you design for the August spike?
By treating it as a primary constraint, not an edge case: modelling peak load, scaling the architecture for it, and testing against tripled demand. Generic SaaS averages your year, which is exactly why it struggles in the three weeks that matter most.
What's the risk of building the wrong thing?
It's real, and it's why discovery matters. A rushed or vague scope can produce software that becomes its own workaround. A disciplined developer invests in understanding the process first, which is the single best protection against an expensive miss.