What bespoke software development is, and who it is for
Bespoke software development is the design and build of software written for one business, to fit its own processes, rather than bought off the shelf and adapted. Evolve is a Bristol studio that builds it for UK companies of roughly 20 to 250 staff: the systems, portals and internal tools that no package quite fits.
Most businesses do not need bespoke software, and we say so on the first call. The ones that do usually share a symptom: a process that is the business, running on a tool that was built for a different one. A garage running its workshop on a program tied to one PC. A membership scheme tracked in a spreadsheet nobody dares sort. A recruitment desk coordinating everything by email because the six systems it pays for do not talk to each other.
What we build
The four systems below are real. They are described without the names because our clients did not hire us to be their marketing.
A cloud workshop-management system
Replaced a Windows desktop package licensed to a single PC. Bookings, job cards, parts, invoicing and MOT reminders, used by the whole team from a browser and a phone, with every historical record migrated and reconciled.
A membership site with billing and referral attribution
Paid membership through Stripe, a member dashboard, partner links that track which referral produced which sale, and an admin export the office runs itself. Built from a written spec in a single fixed-price phase.
An email-first coordination layer
For a marine recruitment firm whose real workflow ran in email and messaging, not in its six systems of record. Vacancy intake, candidate matching and chasing, sitting on top of the inbox rather than replacing it.
A travel operator's site, moved off WordPress and Elementor
Rebuilt with a CMS the office can edit, a lodge and itinerary uploader, and an assistant that reads incoming enquiries and routes them to the right person with the context attached.
Typical projects
Bespoke CRMs, customer and client portals, booking and scheduling, job and workshop management, internal dashboards, and the integrations between the accounts package and everything else. See bespoke systems for what each replaces.
The websites in front of them
Marketing sites rebuilt off templates and page builders, with the URLs and rankings carried across and a CMS the office uses without calling us. See website rebuilds.
When off-the-shelf is the right answer
If a package already does most of what you need and the rest is habit, buy the package and we will help you set it up. Accounting, payroll, email and a brochure website with no integrations are almost never worth building. Bespoke software earns its place when the process is the advantage, when the package has become the bottleneck, or when the real job is connecting systems that were never meant to meet.
Often the honest answer is a hybrid: keep the package, build the layer around it. We wrote up how to decide in plain terms.
Discovery before design
We do not pick the technology before we know where the time goes. Most builds open with the Workflow Audit: every member of staff documents their own repeating work, and the result comes back priced in pounds. That document becomes the build brief.
- 01
Listen
Everyone in scope documents their own routines, with the time and frequency attached. A census, not a sample.
- 02
Map
An explicit picture of how each workflow moves across people, systems, and decisions, drawn from what your team actually described.
- 03
Score
Every candidate opportunity scored on impact, feasibility, regulatory risk, change cost, and time to value.
- 04
Sequence
A phased roadmap that makes the order of work obvious. Quick wins first, strategic plays scheduled.
You leave with: full documentation of every process in the business, department by department, plus a prioritised opportunity register, recommended sequencing, and compliance notes. Board-ready, defensible, and yours to keep and use with anyone.
Learn how the Workflow Audit worksHow a project runs
Six steps, and you see working software from the second week of the build.
Discovery
The Workflow Audit for most builds. For a single site or system, a shorter scoping engagement: we sit with the people who do the work and write down what the software has to do.
Scope and fixed price
A written scope for the first phase and one number. If we got the number wrong, that is our problem, not yours.
Design
Screens and data model, checked against the people who will use them before anything is built. Cheap to change here, expensive later.
Build, with a demo every week
Working software on a staging address from week two. You use it, and what you say steers the next week.
Launch and parallel run
The old system stays until you say so. Cut-over criteria are agreed in advance, and there is a rollback path if something surprises us.
Handover
Repository, cloud account, documentation and training, all in your name. Support afterwards is optional and monthly, not a lock-in.
What it runs on
We build on a small, boring, well-supported stack, so that any competent developer can pick it up after us. That is part of what owning the code means.
Next.js and TypeScript
One codebase for the website, the portal and the admin screens. Server-rendered, so it is fast and search engines can read it.
Postgres
A standard relational database with a schema you can read and export. Hosted on Neon or in your own cloud account, with branching for safe migrations.
Vercel or Railway
Hosting billed to your account so you see every line item. Preview deployments for each change, and a production environment that rolls back in one click.
Stripe and Postmark
Payments, deposits and subscriptions through Stripe. Transactional email through Postmark. Both in your name, both with their own dashboards.
Claude, where AI belongs in the product
Enquiry routing, document reading, first drafts. Logged, reviewable and reversible, and only where the audit says it earns its place.
Your own accounts throughout
Repository, hosting, database, payments and email are opened in your name in the first week. Nothing sits behind an Evolve login.
What it costs
The honest answer is that it depends, so here is what it depends on.
- User types and screens. A system with one kind of user and six screens is a different project from one with customers, staff and managers each seeing something different.
- Integrations. Every system the software has to talk to, and whether that system has a usable API or needs a workaround.
- Data migration. How much history has to move across, how clean it is, and whether the old vendor will hand it over.
- Compliance evidence. Audit trails, retention, access controls and the documentation a regulator or an insurer will want to see.
- Hosting choice. A shared cloud account or your own private one, and what that means for security review.
- How much of the old process survives. Rebuilding everything at once costs more than replacing the bottleneck first.
Every phase is a fixed price agreed before it starts. We do not quote day rates. The audit gives us the scope, and the scope gives you the number. We wrote up what drives the cost in more detail.
Why an AI-native studio is cheaper and faster
Most of an agency's timesheet is mechanical work, and that is the part AI now does well. We use it heavily in the build and not at all in the decisions.
What AI does in our build
- Scaffolds the project and the data model from the agreed scope
- Writes the database migrations and the test suite
- Generates seed data and fixtures so demos run on realistic records
- Drafts documentation, help text and first-pass copy
- Reviews every change for regressions before a person does
That is where the weeks go on a traditional build, and where the saving lands.
What AI does not do
- Decide the requirements, or what not to build
- Choose the data model that will still make sense in five years
- Sign off a demo, or tell you a feature is a bad idea
- Talk to your staff about how the work actually runs
A person reads every line that ships. The judgement is ours; the code is yours.
Sectors we have built for
The method does not lean on knowing your sector; the audit finds the work wherever it is. These are the ones we know best.
Regulated professional firms
Where audit trails and access controls are part of the specification, not an afterthought.
Healthcare and medical training
NHS trusts, private providers and the manufacturers that supply them, with data handled to the standards they are held to.
- Healthcare
- Medical simulation and training equipment
Trade and workshop businesses
Garages, workshops and service businesses whose day runs on a diary, a job card and an invoice.
- Motor trade and MOT
- Job and workshop management
Hospitality, travel and marine
Bookings, memberships, enquiries and crews, where the coordination is the product.
- Hospitality membership networks
- Tour operators
- Yacht crew and marine recruitment
The work we do most often
Bespoke systems
CRMs, customer portals, booking and scheduling, internal tools, workshop and job management.
Website rebuilds
Off templates and page builders, with content, URLs and rankings carried across.
Legacy system modernisation
Rehost, replatform or rebuild, with reconciled data migration and a parallel run.
AI automation
Where the audit finds repeating work with clear rules, we automate it. Logged and reversible.
Questions people ask about bespoke software
What is bespoke software development?
Software designed and written for one business to fit its own process, rather than a package adapted to it. The business owns the result and decides how it changes.
How much does bespoke software cost in the UK?
It depends on scope, which is why we quote a fixed price per phase after discovery rather than a day rate. What moves the price is the number of user types and screens, the systems it has to connect to, how much data has to move across, and how much evidence a regulator will want.
How long does bespoke software take to build?
A first fixed-price phase usually goes live within eight weeks of sign-off. Larger systems are split into phases, and every phase ships something you can use.
Do we own the code?
Yes. The repository, the cloud account and the database are in your name from the first week. If you stop working with us, everything stays where it is.
Is bespoke better than off-the-shelf software?
Not always. If a package already does most of what you need and the rest is habit, buy the package. We will tell you when that is the case on the first call.
How do you use AI in the build?
For the mechanical parts: scaffolding, database migrations, tests, seed data and documentation. It never decides what to build, and a person reads every line that ships.
What happens after launch?
A documented handover either way, then optional monthly support if you want it. There is no lock-in and nothing that only we know how to run.
Do you work with businesses outside Bristol?
Yes. We are based in Bristol and work with businesses across the UK, in person across the South West and remotely everywhere else.
Tell us what the package cannot do
The first call is free and its job is to work out whether bespoke software is the right answer for you. If it is not, we will say so and point you somewhere better.