Custom business systems built when off-the-shelf software doesn't fit




Six signs you need a bespoke build
You've trialled three or four SaaS products. Each one solved part of the problem but not all of it. Each one would require workarounds. The combined cost of the workarounds is worse than building once and owning it.
You're paying £300+ a month across multiple SaaS subscriptions to do something a custom system could do in one place. Over five years that's £18,000+ in subscription fees, with everything still locked in someone else's platform.
Off-the-shelf SaaS gives you what they decide to give you. Sometimes that's not enough for ISO, GDPR, ESFA, Ofsted, FCA or similar audit requirements. We design audit-grade systems where compliance is built in from day one.
The product is being deprecated. Pricing has tripled. New features go to enterprise tiers only. The export is incomplete. Sound familiar? Custom builds give you the exit they never wanted you to have.
Every business has bits where the workflow is different from the standard. A custom build leans into your uniqueness instead of forcing it through someone else's template.
An idea no off-the-shelf product solves yet. A new product line, a new service, a competitive edge that depends on the software being different. Custom is the only way to do that.
Real systems, real numbers, real production deployments
South Cumbria Skills Exchange. 23-day build. £260 hard cost vs £97k+ traditional. Four React dashboards, 31 REST controllers, ESFA-compliant.
Dottites. Two-app React food ordering platform with delivery slot management, WooCommerce payments and 26 database migrations. Production-grade.
Wicham Parish Council + Estuary View Escapes. Bay-level availability, DVLA reg lookup, season pricing, warden frontend. 12,000+ lines of properly-engineered code.
Lakeland Life Events. Multi-day events, supplier portal, ticketing, complex pricing rules. React frontend, PHP REST API, custom WordPress plugin.
A £97k system built in 23 days for £260 in hard costs
The client needed a regulatory-compliant LMS to replace spreadsheets and paper. Commercial alternatives — MAYTAS, Tribal, ProSolution — quoted £97,500 to £137,500 to set up and customise. The CIC couldn't justify that against its annual budget.
We built them what they needed instead. Four role-based dashboards in React: Admin, Tutor, Learner and Guardian. Nineteen custom database tables. Thirty-one REST API controllers. Full ILR compliance for DfE reporting. Grant-funded hour tracking. PDF invoice generation. Audit logs on every data write. Built in 23 calendar days for £260 in hard costs. In daily use today and has cut administrative time by more than half.
Everything is documented. Every milestone has a journal entry with a commit hash. The methodology is published in the book Building Without Code. The numbers are verifiable from the project journal.
Why we can build in weeks what teams take months to build
Every project starts with a Project File — a 1,000 to 3,000 line living specification that the AI reads at the start of every coding session. It includes the architecture, the data model, the business rules, the deployment process and the boundary cases. The AI never has to guess what to build because the Project File is its external memory.
We use sandwich prompts: Team Brief plus Task plus Restraints. The Team Brief gives the AI its role. The Task is the specific work for this session. The Restraints define what not to touch, what to avoid, and what to ask before assuming. This is how a junior team is run in practice — and AI agents respond to the same structure.
Every milestone gets a journal entry. Every code change is documented. Every API has authentication, capability and scope checks built in at the model layer. The discipline scales because it's encoded, not just discussed.
Weeks, not months — but not magic
What we will not tell you is that we can build any custom system in three weeks. Some systems genuinely need longer. We will quote a fixed price and a delivery range after the discovery call, both honestly scoped. If we think your project is 12 weeks we will tell you 12 weeks; we will not promise four and then slip.
What is consistent across every build: weekly progress on a staging URL, weekly demos, every milestone documented, full code ownership transferred on delivery. You never end up wondering what we've been doing for the last fortnight.
Fixed price quotes after a discovery call
The fixed price is set after a discovery call where we map the work in detail. From that point, you know what you are committing to. We invoice in milestones: a deposit on scope agreement, payment at agreed midpoints, balance on delivery. No hourly billing for vague work. No surprise additions. Scope changes during the build are quoted separately and approved before they happen.
For grant-funded or community organisations, we are willing to discuss flexible payment structures. Talk to us.
You own the code, the data, and the deployment
The complete source code is delivered to you in a Git repository — typically GitHub, but we can use GitLab, Bitbucket or self-hosted Gitea if you prefer. The code is documented to the level a competent developer could pick it up and extend it without us. The deployment instructions are written so anyone with reasonable WordPress experience can run it. The database schema is fully described in versioned migration files.
You can run the system on your own hosting from day one. We do not host it for you (though we can recommend hosts and help you set up if needed). You can engage another developer to maintain or extend the system. You can sell or transfer the code if you ever wanted to. None of that needs our permission because the code is yours.
We stay involved as much or as little as you want — ongoing support packages, change requests, or a clean handover and we walk away. Whichever suits you.
Being honest about where custom isn't the answer
If your need is a generic CRM with no unusual workflows — use Pipedrive or HubSpot. If your need is a generic e-commerce shop — use WooCommerce or Shopify. If your need is generic accounting — use Xero or QuickBooks. If your need is generic project management — use Asana, ClickUp or Notion. These are mature, well-supported products built by teams of hundreds. We can't beat them on cost or features for generic use cases, and we won't pretend otherwise.
Where we can win: when your need is genuinely different from the generic, when the SaaS subscriptions are adding up beyond the cost of a build, when compliance requires more than the off-the-shelf offers, or when you need to own the result. In those cases custom is the right answer — and we will be honest about that too.
Real production systems across six different sectors
Real users of systems we built from scratch
Three steps from discovery to delivery
60-90 minute structured workshop where we map your business, the system needed, the data model, the integrations, the compliance requirements. We come back with a written scope, an architecture document, and a fixed-price quote.
4-12 weeks. Staging URL from week one. Weekly demos. Every milestone documented with commit hashes. Every database change is a versioned migration. Every API endpoint has authentication, capability and scope checks.
Deploy to your hosting. Full code repository handed over. Documentation, deployment instructions, runbooks. 30-day bug-fix window included. Optional ongoing support thereafter — or a clean handover and we walk away.
Things prospects ask before signing a build agreement
What if my requirements change during the build?
Tell us about it. We will tell you honestly whether a custom build is the right answer, how long it would take, and what it would cost.
