Custom software development is the work of designing, building and running software around one organisation's way of working, instead of buying a packaged product and configuring it to fit. The case for it starts with a specific problem. It might be a quoting process held together by spreadsheets, customers chasing your team for updates, or two systems that only agree because someone re-keys data between them every morning.
This guide covers when to build, the main types of custom software, how a project should run and what it costs. It also covers how to judge a supplier, and when a standing engineering team suits you better than a project. The checklists work with any supplier.
If you already know you need a build, our bespoke software development service has the fixed price and delivery terms.
What custom software development is
Custom software is designed and built for a single organisation's processes, data and users. Packaged software (a CRM, an accounting system, a project tool) is built for a market, and you configure it as closely as it allows. Custom software development covers its whole life, from working out what it needs to do to building, testing, launching and maintaining it.
Custom software does not have to replace the packaged systems a business already runs. It can fill the gaps between them, or sit in front of them. A broker portal that writes quotes to the CRM is custom software, and so is an integration that keeps finance and sales looking at the same numbers.
Custom or bespoke?
They mean the same thing, and this guide uses both. Our own service page uses "bespoke".
What it is not
Configuring a packaged product, even heavily, is different work, because you are still shaping someone else's product. In staff augmentation, the supplier places developers inside your team and you manage them. A chain of workarounds and brittle middleware connects tools without anyone owning the result. Each of those can be the right answer to a given problem.
When to build, when to buy, and when to keep configuring
A mid-market firm has three options: buy a packaged product, build custom software, or extend the system it already runs.
Buy, or keep what you have, when
- A packaged product already does most of the job. If the gap between what it does and what you want is a matter of habit, configure it and spend the money elsewhere.
- Your volumes are small. A spreadsheet and a disciplined team can outperform a custom system that you then have to maintain.
- The process is still changing. Automating something that will change next quarter means paying to build it twice.
- Your compliance and security needs are standard. Established vendors carry that load across thousands of customers, and you benefit from it.
Build when
- The process is how you win. If the way you quote, schedule, onboard or report gives you a competitive edge, packaged software will tend to flatten it into everyone else's version.
- Manual handling has become a cost line. Re-keying between systems, chasing missing data and fixing the errors that follow show up in staff time and lost revenue.
- The process is stable and the tools are not. Workarounds and brittle middleware are holding the process together, and each one adds risk.
- Customers or partners need self-service you cannot buy. A vendor does not sell a portal, quoting tool or reporting platform built around your own data and rules.
In the enquiries we see, clients who choose a build tell us they want control over how the system works and to own it, without paying for features they do not need. They also value our expertise in the systems involved and our knowledge of their business.
Custom software usually costs more to maintain per user than a packaged product, because no vendor is spreading the cost across thousands of customers. Build only where the advantage is real, and design for maintainability when you do.
Keep configuring, or extend, when
Your core system can be extended without a separate application. Many CRMs and ERPs support custom objects (record types you define), custom cards in the interface, coded workflow steps and APIs (the interfaces other software uses to read and write their data). For a HubSpot customer, a custom HubSpot development project such as a custom card or a coded workflow action can close the gap faster than a standalone build. Whatever you run, ask whether it can be extended safely, and whether the extension will survive the vendor's next release.
If you are not sure which of the three applies, a short diagnostic reviews your systems, processes and data and gives you a prioritised plan. It can recommend configuring what you have instead of building something new.
Five types of custom software
Custom software is a wide category. These are five of the main types a mid-market firm might commission.
Customer, partner and member portals
A portal gives customers, partners or members a secure place to see their own information, submit requests, download documents and track progress without phoning your team. Our guide to customer portals for mid-market B2B compares the routes to a portal and what one costs over three years. If a self-service front end is what you need, our customer portal service is a fixed-scope package with its own price and delivery guarantee.
Internal tools and operational platforms
These are scheduling, case management, approvals, reporting and job tracking systems built around the way your team works. They often replace spreadsheets and shared inboxes that grew up because no packaged product fitted.
Quoting, pricing and product configuration
Where pricing depends on many variables, regulations or product combinations, a quoting engine or configurator can produce accurate quotes and pass clean data to the CRM and finance system. These builds sit close to revenue, so a mistake in the pricing logic costs money directly.
Integration platforms and APIs
These are governed data flows between systems such as a CRM, finance system, e-commerce platform or warehouse, with monitoring and error handling designed in. Our integrations page covers the systems we connect to HubSpot, from Sage and Xero to legacy systems. When we checked on 16 Nov 2026, our Integration Library listed 99 HubSpot integrations with notes on how each one works.
Applications with AI built in
Document processing, quote drafting, classification and agent workflows can be built into the software, so the model does one defined job inside a process that your code controls. We build these under our AI implementation service, which has separate pages for Claude, for Grok, Cursor and Grok Bot and for OpenAI.
How a custom software project should run
Use these stages as a checklist. Each one should give you something to show your IT or procurement team before you decide to continue.
- Paid discovery. A short, paid piece of work before anyone quotes for the build. The supplier interviews the people who do the work, audits the systems and data, and tests whether the idea is feasible. You come away with a written problem statement and scope, an architecture recommendation and data model, a risk register, and a fixed price and date for the build. Ours takes one to two weeks.
- Architecture and technical design. Language, framework, database, integrations and hosting are chosen for your case, and you can see why. The design should say where your data will live, because hosting jurisdiction matters for UK GDPR and for some customer contracts.
- A fixed-scope contract. Price, delivery date, intellectual property and data processing terms are agreed and written into the contract before the build starts. You should also know what happens if the date is missed.
- A sprint-based build. Development runs in sprints, fixed blocks of work of the same length, with working software you can review at the end of each one.
- Testing and acceptance. Automated tests check each component and how the components work together, and end-to-end tests run through the software as a user would where the project needs them. You sign off a formal user acceptance stage before release.
- Handover. Technical documentation, a walkthrough for your team, and repositories, hosting accounts and credentials in your name.
- Go-live and warranty. A defined period after launch in which defects are fixed at no charge. Ours is 30 days.
- Support and evolution, if you want it. A named contact, an agreed response time and an allowance for fixes and small improvements, priced against the system that was built and possible to cancel.
What a fixed date depends on
In our experience, what puts a delivery date at risk is clients changing their minds about a feature once they see it working, which is natural. We encourage clients to launch with the smallest set of features that can go live, then plan the rest as later iterations (an agile approach: improving the software in short, planned rounds).
The date also depends on fast access to the systems the software must connect to and feedback in days instead of weeks. Discovery surfaces those dependencies before they can hold up the build, which is one reason it is worth paying for.
Ownership, data and security
Settle these four points before you sign.
Who owns the code
Under the Copyright, Designs and Patents Act 1988, the author of a work is the first owner of its copyright, and an employer owns work its employees create in the course of their employment. An outside supplier's engineers are not your employees, so unless the contract says otherwise the supplier owns the code you paid for. An assignment of copyright is only effective in writing, signed by or on behalf of the owner. Make sure the contract includes the assignment and says when it takes effect. At SpotDev, intellectual property in the software we build is assigned to the client outright on final payment. This is general information. Take legal advice on your own contract.
Who holds the keys
Ownership on paper means little if the supplier holds the repository, hosting account and passwords. Ask for all three to be in your name from the start. If your governance requires more, ask for source code escrow, where an independent third party holds a copy of the code for release to you if the supplier cannot continue. We offer it on request.
How personal data is handled
If the software processes personal data, UK GDPR applies and you need a data processing agreement (the contract setting out how a supplier handles personal data for you) with any supplier who handles it. The Information Commissioner's Office publishes a guide to controllers and processors that sets out who is responsible for what.
How security is tested
Certification shows whether someone independent has tested a supplier's security controls. SpotDev holds Cyber Essentials Plus, the UK government-backed certification in which an independent assessor tests the controls rather than taking our word for them.
How AI is changing delivery, and how we use it
AI coding tools have changed how software is written. For a buyer, what matters is how the output is checked and under what terms your code is handled.
Cursor is our development platform, with Anthropic's Claude Code and OpenAI's Codex used alongside it. Every line that ships is reviewed by a SpotDev engineer, covered by automated tests and delivered under the same warranty as code written by hand. These tools run under commercial terms that do not permit your code to be used for model training.
When the software itself uses an AI model, the choice of model depends on the job, the data, the controls and what you already run. The vendor bills model and subscription costs to you directly, on your own contract, so the running cost stays visible in an account you control.
If your team has built an application with an AI coding tool, we can review it and sign off a version fit to run. We can also set your team up to keep building safely.
What a build costs, and what moves the price
No single price covers custom software, because a two-screen internal tool and a multi-user partner platform are different jobs. A supplier should explain what moves the price and stand behind its quote.
What moves the price
- Scope. The number of user types, screens, workflows and business rules.
- Integrations. How many systems the software must talk to, and whether they have usable APIs.
- Data. The volume, quality and complexity of the data, including any migration or clean-up.
- Compliance. Sector rules, audit requirements, data residency and security review.
- Support. Whether you need the system kept patched, monitored and improved after launch.
How suppliers charge
Suppliers usually charge in one of three ways. With day rates you pay for time, and any overrun is yours. With a fixed price after paid discovery, the supplier carries the risk of overrun, which is why it needs discovery before it can quote. With a subscription team you pay a monthly fee for a standing team that works through a backlog.
Our published prices
SpotDev does not sell day rates. These are the prices published on our service pages, all excluding VAT.
| Service | Price | Terms |
|---|---|---|
| Technical discovery | £5,000 | Credited in full against the build if you proceed within 60 days. The output is yours either way. |
| Fixed-scope build | From £15,000 | Price and delivery date fixed in writing, with 20% back if we miss the agreed date. |
| Customer portal | From £15,000 | Live within 30 days of contract signing, with a written delivery guarantee. |
| Engineering team subscription | From £5,000 a month | A standing team for ongoing work. |
Hosting, software licences, AI model usage and support continue after launch. Ask for them to be estimated during discovery, so you know the total cost of ownership before you commit.
How to judge a supplier
Ask each supplier you speak to these questions.
- Who will write the code, and can we meet them? Find out whether the engineers are the supplier's own staff or subcontractors.
- Who owns the intellectual property, and where does that say so? It should be in the contract, with a clear point at which ownership passes to you.
- Is the price fixed, and what happens if the date is missed? Look for a written consequence, such as money back.
- What security certification do you hold, and who tested it?
- What do we receive at handover?
- How do you use AI in the build? Ask who reviews the output and whether your code can be used for model training.
- Can you show us something similar you have built? Named client case studies count for more than a list of technologies.
- What do independent reviewers say? Look for reviews on a platform the supplier does not control.
SpotDev builds with an in-house, fully remote engineering team. On 16 Nov 2026 it held an average rating of 5.0 from 42 reviews on HubSpot's Solutions Directory.
A project or a subscription team?
A fixed-scope project suits a defined outcome, such as a portal or a quoting engine. You agree what will be built, by when and for how much, and the project ends at handover.
Some needs do not have an end date: a standing backlog, a system that needs continuous upkeep, software a departed developer left behind, or a product with no team to run it. These suit a subscription engineering team. Ours gives you a named solutions consultant, project manager, designer and full-stack developer, with our QA (testing), DevOps (deployment and hosting) and security tooling behind them, working in two-week sprints. Plans start at £5,000 a month for the equivalent of one engineering day a week. There is a three-month minimum and then 30 days' notice, and a two-week trial sprint is available before you commit. Unlike staff augmentation, the team works on our stack and to our process.
The two can work together. A fixed-scope project gets the system live, and a subscription keeps it secure, current and improving afterwards.
Software we have built
Most of this work was built on or around HubSpot, and we say so where it applies.
- For Peregrine Finance, an asset finance broker, we built a standalone web application with a proposal builder, a regulated and unregulated quote calculator, lender-ready PDFs and a governed sync into HubSpot. Our bespoke software page describes how it runs on Node.js and PostgreSQL, with HubSpot as one of the systems it talks to.
- For Superior, we built a scheduling system and secure portal that coordinated thousands of equipment-upgrade appointments for bank customers during US bank mergers. It uses HubSpot custom objects, workflows and serverless functions (code that HubSpot runs on demand). The Superior case study describes it as launching a new business unit for Superior.
- Wolsey Hall has two customer portals, one for parents and one for partner schools, integrated with its CRM. As the Wolsey Hall case study sets out, they serve families and schools in more than 130 countries.
- Icon Solutions has a learning management portal for the technical teams that use its payments framework. The Icon Solutions case study shows how it automates enrolment, course progression, exam booking and certificate management.
- Abbott Laboratories' BMI tracker portal, hosted on HubSpot, let users log their measurements and track progress over time. According to the Abbott case study, it became the central asset in campaigns across several countries.
- L&DI's corporate membership portal lets corporate members add and remove their own people. The L&DI case study explains how billing connects across HubSpot, Stripe and Sage 50. Sage 50 has no native API, so we built middleware that runs on the machine hosting Sage 50 and gives it an API.
About SpotDev
SpotDev is a software engineering firm with deep AI capabilities and deep HubSpot platform expertise, working with mid-market companies whether or not they run HubSpot. SpotDev is a HubSpot Diamond Solutions Partner, an OpenAI Select Partner, Certified in the Claude Partner Network, and a SpaceX Super Intelligence Transformation Partner.
Frequently asked questions
What is custom software development?
It is the design, build, testing and support of software made for one organisation's processes, data and users. For mid-market firms that usually means portals, internal tools, quoting engines, integration platforms or applications with AI built in, connected to systems the business already runs.
Is custom software the same as bespoke software?
Yes. UK buyers use the two terms interchangeably, and the engineering behind them is the same.
How much does custom software development cost in the UK?
At SpotDev, technical discovery is £5,000, fixed-scope builds start from £15,000, customer portals start from £15,000, and an engineering team subscription starts from £5,000 a month. All prices exclude VAT. The price of a build is fixed in writing after discovery.
How long does a custom software project take?
Discovery takes one to two weeks. The build timeline depends on the scope, and should be set during discovery and written into the contract. Our customer portal package goes live within 30 days of contract signing.
Who owns the code when a supplier builds custom software?
Under UK copyright law the author of a work is its first owner, so a supplier owns the code it writes unless the copyright is assigned to you in signed writing. SpotDev assigns intellectual property to the client outright on final payment.
Do we need to use HubSpot to work with SpotDev?
No. Many of our clients run HubSpot and want software that extends it. We also build for companies that do not use HubSpot at all, and the engineering process is the same.
When should we buy off-the-shelf software instead?
Buy when a packaged product covers most of what you need, your volumes are small, the process is still changing, or your compliance needs are standard. Configuring an existing product is then usually cheaper and lower risk than a custom build.
Should we commission a project or subscribe to an engineering team?
A fixed-scope project suits a defined outcome with a clear finish, such as a portal or an integration platform. A subscription team suits ongoing work, such as a backlog or software inherited from a previous developer. You can also start with a project and move to a subscription after launch.
How do you use AI when building custom software?
Our engineers work in Cursor, with Anthropic's Claude Code and OpenAI's Codex. A SpotDev engineer reviews all AI-assisted code before it ships, and it carries the same automated tests and warranty as hand-written code. The tools' commercial terms rule out training models on your code.
What should a custom software contract include?
A defined scope, a fixed price and delivery date, and the consequence of missing that date. It should also cover assignment of intellectual property to you, a data processing agreement where personal data is involved, testing and acceptance, what you receive at handover, and the warranty after go-live.
Next step
Start by describing the problem you want to solve. We will reply within one business day with a view on whether custom software is the right answer and what discovery would cover. Our bespoke software development page explains how discovery leads to a fixed-price, fixed-date proposal.
Get new articles by email
Practical guides from the SpotDev team, when we publish them.
By submitting this form, you consent to us sending you emails with our latest content. Privacy Policy


