Off-the-shelf SaaS was built for Bristol, and Cardiff's two languages and stadium swings break it
Custom software in Cardiff typically runs £60,000 to £200,000 over 4 to 9 months. You commission a bespoke build when generic off-the-shelf SaaS forces your team into workarounds for bilingual Welsh and English operation, public-sector reporting, or the event-driven demand that defines so much of the city's economy.
Generic SaaS is built for the median UK business, and Cardiff isn't median. The product assumes one language, so your Welsh Language Standards obligations become a manual translation queue. It assumes smooth demand, so your firm supplying the stadium and Bay events economy fights its forecasting every week. And it assumes private-sector reporting, so the Welsh Government framework you just won needs fields the SaaS has no place for.
Each gap on its own is survivable. Together they mean your team spends its days bridging software to reality with spreadsheets, copied documents and reminders to translate things. The SaaS subscription is cheap; the hours lost to its assumptions are not.
What custom software costs in Cardiff
| Project scope | Typical cost | Timeline |
|---|---|---|
| Focused single-domain tool | £60k to £100k | 4 to 5 months |
| Multi-module bilingual system | £100k to £155k | 5 to 7 months |
| Full platform with public-sector reporting | £155k to £200k | 7 to 9 months |
The fix: custom software built for Cardiff, not rented
Custom software is built around how Cardiff actually operates: two equal languages, demand that moves with the events calendar, and reporting that satisfies both commercial and public-sector contracts. It removes the daily bridging work, replacing copied documents and translation reminders with a system that does it natively. For a firm whose operation is genuinely shaped by the city, that's recovered hours and fewer errors, not just a nicer interface.
- Bilingual operation and public-sector reporting are core, not optional
- Your demand genuinely moves with the Cardiff events calendar
- Your team loses real hours bridging SaaS gaps with spreadsheets
- No off-the-shelf product fits without months of paid customisation
- A standard SaaS covers your process with minor configuration
- You're English-only with no public-sector reporting load
- Your demand is steady and predictable
- You can't fund a build or maintain it afterward
The capability list that earns its budget
Cardiff custom software: the full scope
Everything a custom software build here can cover: enterprise software, API development, cloud software, MVP development, legacy modernization, systems integration and microservices.
How long it takes, phase by phase
Exactly what you get
Software built around Cardiff's real operating conditions: native Welsh and English, demand logic that tracks the events calendar, and reporting that serves both Welsh Government frameworks and commercial contracts. It connects to your ERP, CRM and accounting software so it becomes the hub that ends the spreadsheet bridging your team does today, with UK GDPR-aligned data handling throughout.
How to choose a developer in Cardiff
Look for a partner who probes which of your problems are genuinely Cardiff-specific before quoting. They should talk fluently about bilingual data models, public-sector reporting and event-driven demand. A team that treats Cardiff like any English market will hand you generic software with a language toggle and call it custom.
- Built around bilingual operation so Welsh and English are native, not bolted on
- Models event-driven demand instead of fighting a flat-average assumption
- Handles public-sector and commercial reporting in one system
- Eliminates the spreadsheet bridges that erode SaaS time savings
- Designed to connect with your ERP, CRM and accounting software as a hub, not an island
- Higher upfront cost than a SaaS subscription, paid before you see value
- You own maintenance, security and uptime rather than renting them
- A long build means slower time-to-value than signing up for SaaS today
- If your operation isn't actually unusual, custom is over-engineering
- !They pitch a generic SaaS reskin. Ask what's actually bespoke versus configured
- !They skip the bilingual question. Ask how Welsh and English are stored and rendered
- !No public-sector reporting experience. Ask for a Welsh or UK government reference
- !They don't plan integrations. Ask how this connects to your existing ERP and CRM
- !They quote a fixed price before discovery. Ask what would move that number
Most Cardiff 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 worth it over SaaS?
When your operation is genuinely shaped by Cardiff-specific realities, bilingual obligation, public-sector reporting and event-driven demand, and you're losing real hours bridging SaaS gaps with spreadsheets. If a standard product fits with light config, stay with SaaS.
How long does a build take?
Most Cardiff custom builds run 4 to 9 months depending on scope. The bilingual core and public-sector reporting are the elements that extend timelines beyond a vanilla tool.
Can it integrate with what we already run?
Yes. Good custom software is designed to connect with your existing ERP, CRM and accounting software via API, becoming a hub rather than forcing a full replacement.
Who maintains it after launch?
You do, either with an internal owner or a support retainer with the developer. Unlike SaaS, uptime and updates are your responsibility, which is the trade for a system that fits exactly.
Is bilingual support really necessary?
For public-facing and public-sector work in Cardiff, the Welsh Language Standards typically require genuine bilingual delivery. Building it in once is cleaner and cheaper over time than a perpetual manual translation queue.