Software3 min read
Custom Software vs Off-the-Shelf: How to Actually Decide
Buy by default. Build when the way you work is the thing that makes you competitive. Here’s how to tell the difference.
Read article →Build — Custom Software
Software built around your business.
Off-the-shelf software is the right choice more often than software companies admit. Custom becomes worth it when the way you work is the thing that makes you competitive — and bending it to fit someone else’s product costs you more than building your own.
Build
- We start with the process, not the feature list
- Architecture you can maintain, extend and hand to someone else
- You own the code, the data and the decisions
When custom software makes sense
Usually it’s not one dramatic reason. It’s several small ones that have quietly become expensive.
Your core process lives in spreadsheets that only one person fully understands
You pay per seat for a tool where your team uses fifteen percent of it
Two systems hold the same data and neither is trusted
Every new client or product means more manual setup work
The workaround has become the process
The thing you do better than competitors is the thing no product supports
What we build
Internal tools
The unglamorous applications a team lives in all day: intake, scheduling, approvals, quality checks, operations.
CRM & sales systems
When a generic CRM can’t model your pipeline, products or partner structure — or when the data matters more than the interface.
Dashboards & reporting
One place where numbers from several systems agree, refresh automatically and can be trusted in a meeting.
Customer portals
Give clients a place to see status, documents, history and invoices instead of emailing you for updates.
Workflow platforms
Multi-step processes with roles, permissions, states and an audit trail — the things spreadsheets can’t do.
SaaS products
Multi-tenant products with billing, onboarding and access control, built to be extended after launch.
From problem to working software
The first phase is deliberately about understanding, because the most expensive software mistakes are made before any code exists.
- 01
Problem
What actually goes wrong today, how often, and what it costs. Sometimes this phase ends with 'don’t build this’ — and that’s a good outcome.
- 02
Requirements
The real rules of your process, including the exceptions everyone forgot to mention. Written down and agreed.
- 03
Architecture
Data model, integrations, permissions, hosting and the decisions that are hard to reverse later.
- 04
Development
Built in slices you can see and use, so feedback happens while it’s still cheap to act on.
- 05
Testing
Automated tests where they earn their keep, plus real people doing real work in a staging environment.
- 06
Launch
Migration, training, a rollback plan, and someone available when the first unexpected thing happens.
- 07
Improvement
Software that’s used changes. We keep improving what creates value and resist adding what doesn’t.
What you should expect to own
A custom system you can’t take elsewhere is a liability. From day one, the code lives in a repository you own, in a stack a competent developer can pick up, with documentation that explains the decisions and not just the syntax.
We’d rather be the team you keep working with because the work is good than the team you can’t leave.
- Source code in your repository, under a normal licence
- Your data in your database, exportable
- Infrastructure in your accounts where practical
- Documented architecture, environment setup and deployment
- No obscure proprietary layer that only we understand
Questions people ask
How much does custom software cost?
Enough that it should be a business decision, not an impulse. The honest answer is that cost tracks scope: number of user roles, integrations, business rules and edge cases. We scope in stages — a short discovery phase produces a specification and a realistic range, and you can stop there and take it elsewhere if you want.
Can we start small?
Almost always, and we’d encourage it. A first version that solves the single most painful part of the process teaches you more than a year of specification. We design the architecture so version one doesn’t have to be thrown away to build version two.
What if we already have a system that half works?
That’s common. Sometimes the answer is to extend it, sometimes to build around it and migrate gradually, occasionally to replace it. We’ll look at what exists before recommending a rewrite — rewrites are expensive and frequently reintroduce problems the old system had already solved.
Who maintains it afterwards?
We can, under an ongoing arrangement, or your own team can. Either way you get the code, documentation and access. Maintenance isn’t a hostage situation.
How do you handle security and data protection?
Access control, encryption in transit and at rest, sensible secret management, audit logging where the process needs it, and hosting in a region that fits your obligations. If you handle personal data under GDPR, we design for data minimisation and deletion from the start rather than retrofitting it.
Often combined with
Most projects touch more than one of these. Here’s what usually sits next to custom software.
Worth reading first
Background on the decisions behind this kind of project.
Software3 min read
When Should a Business Build Custom Software?
Not ‘is custom software good’ but ‘is now the moment’ — and how to build the smallest thing that proves it.
Read article →Business3 min read
How to Choose a Software Development Company
Portfolios and price tell you less than you’d think. These questions tell you a lot.
Read article →Discuss a software project
Describe the process that’s costing you time. We’ll tell you whether software is the answer — and roughly what it would involve.
No specification needed. A description of the problem is enough to start.