Frequently asked questions
These are the questions SME owners ask us, including the cost questions. The answers cover bespoke software, CRM, integration and AI readiness.
Browse the answers
Clutch.
5.0 / 5 · 9 client reviews on Clutch
Over 30 years' experience between the founders.
AI-native delivery today.
A small, senior team.
Direct access to the people building your system.
- How much does bespoke software cost in the UK?
- For the SME systems we build, most projects land between £15,000 and £80,000, with phased delivery so you see working software early. The biggest cost drivers are the number of distinct workflows, integrations with existing tools, and reporting depth. We publish our approach to pricing openly — see the pricing page — and every project starts with a fixed-scope analysis phase so you know the full number before committing to the build.
- How long does a bespoke system take to build?
- A first working release typically ships in 8–12 weeks. We deliver in phases: the workflow that hurts most goes live first, then the system grows around it. The founders' experience building business systems has taught us that a six-month big-bang launch fails more often than a six-week first phase.
- Why build a bespoke CRM instead of using Salesforce or HubSpot?
- If an off-the-shelf CRM fits how you sell, use it — we say so in our comparison guide. A bespoke CRM earns its keep when your sales process, quoting, or fulfilment does not fit the standard pipeline model, or when per-seat licensing across a growing team exceeds the one-off cost of owning your system. We have replaced spreadsheet-plus-inbox setups and licence-heavy CRMs alike; the deciding factor is fit, not fashion.
- What goes into building a bespoke CRM system?
- A bespoke CRM starts with mapping your actual sales and enquiry process, then builds the system around it rather than the other way round. Typical scope includes migrating existing customer and contact data out of spreadsheets or a legacy system, connecting your website's enquiry forms so new leads land directly in the CRM, automated routing of enquiries to the right person or team, integration with the email platform your staff already use, and reporting tools your own team can configure rather than waiting on IT. Which of these apply to your business is decided during the fixed-scope analysis phase, alongside cost and timeline.
- What kinds of systems can you integrate?
- Most modern business tools — payment gateways, accounting packages, CRMs, email marketing platforms, booking and ticketing systems, and social or review platforms — publish an API that lets other software talk to them securely. If the tool you use has one, we can normally connect it to your bespoke system, whether that means pulling stock levels from a warehouse system, pushing customer data into your accounts package, or syncing a booking calendar with the tools your team already uses. The main constraints are the quality of the third-party API and how much reporting or automation you need layered on top.
- How will my business benefit from a bespoke software solution?
- Bespoke software is built around how your business actually works, not the other way round. You get one system holding the truth about orders, customers, and stock, rather than several tools that disagree with each other. In practice that means fewer manual re-entries, faster reporting, and a system that flexes as your process changes rather than forcing you to change your process to fit someone else's software.
- Why might my company need a bespoke software solution?
- There are a few consistent signs. Your team relies on spreadsheets to track things a proper system should own; getting a straight answer means pulling information out of multiple systems; an unsupported legacy system is still doing the heavy lifting; parts of the process run manually, on paper or in someone's memory; or staff struggle to access the information they need when they are out of the office. Any one of these is survivable. The trouble starts when they combine: nobody has a clear overview of what is going on in the company at any given time, and decisions get made on stale or contradictory information. A bespoke system fixes this the only way that lasts — one system built around how the business actually runs, holding a single point of truth for the whole company, rather than a system the business has to work around. If several of those signs sound familiar, that is usually the point at which bespoke software starts paying for itself.
- How much does a business website cost?
- A content-managed business website typically costs between £5,000 and £15,000, with the range driven by design complexity, the number of page types, and how far it needs to integrate with other systems. A straightforward brochure site — homepage, about, services, case studies, blog, and a contact form — sits at the lower end, usually with a template-based design and standard hosting. Costs climb once you add gated content, multi-step enquiry forms, bespoke design work, or a live connection to a CRM or booking system; at that point you are closer to a lightweight bespoke system than a website, and the number moves toward the upper end of the range or beyond it. We price website builds the same way as everything else we build: a fixed-scope analysis phase up front so you know the total before work starts, not an estimate that grows once development is underway.
- What is bespoke software?
- Bespoke software is built to fit one business, rather than adapted from a template built for thousands. Off-the-shelf tools ask you to reshape your processes around their design; bespoke software is shaped around your processes instead. It can start small — a single workflow — and grow as the business grows, rather than locking you into a fixed feature set from day one.
- Can you integrate bespoke software with our legacy systems?
- In most cases, yes. If the legacy system has an API, integration is usually straightforward — we connect to it the same way we would any modern system. Without an API, it takes more work: options include database-level integration, or building a thin service layer that talks to the old system on one side and your new tools on the other. We assess this during the analysis phase of every project, so you know which route applies and what it adds to the cost before the build starts.
- Is bespoke software only worth it for large companies?
- No. Advances in modern programming languages and frameworks mean bespoke software can now be developed at a price point that is viable for even the smallest company. For smaller businesses the return is often more visible, not less: a single automated workflow can free up a meaningful share of someone's week, and on a small team that shows up quickly. It is also one of the ways smaller firms compete directly against larger ones — with systems fitted to how they actually work.
- What is digital transformation?
- Digital transformation is the improvement of a business's activities through a mix of integrated digital technologies — in plain terms, replacing manual or disconnected ways of working so information flows between teams without being re-typed from one place to another. In practice it often means moving to cloud-based systems, which reduce deployment and maintenance costs and give everyone in the company seamless access to the same information, wherever they are working. Done well, it is not one big project but a series of specific process changes: how orders are captured, how stock is tracked, how customers are followed up. Each change should be measurable on its own, which is why we deliver transformation in phases rather than as a single system-wide rollout. The founders' experience building business systems has shown that the phased route succeeds far more often, because each step proves itself before the next one is committed to.
- How much does digital transformation cost?
- There is no single figure, because digital transformation covers everything from automating one manual workflow to rebuilding how an entire company operates. The cost is different for each business, and it is driven by three things: the size of the company, the number of distinct business processes that need to be transformed, and the complexity of those processes — including how many existing systems need to talk to each other and how much reporting the result has to support. What we can be precise about is how the number is arrived at. Every project starts with a fixed-scope analysis phase, so you know the full cost before committing to a build. Delivery is then phased: the first phase tackles the process causing the most pain, and later phases are priced and agreed on their own once you can see what the first one actually saved you. You are never committed to the whole spend up front.
- Is digital transformation worth it for my company?
- Usually, yes — but the value shows up in specific, measurable places rather than as a general improvement. The gains we see most consistently: time-consuming manual tasks get automated; the business becomes available from anywhere, at any time, so staff work the same way in or out of the office; systems that used to disagree with each other are integrated, giving one version of the truth; reporting happens in real time instead of at month-end; and security and accountability improve because actions are recorded rather than lost in inboxes and spreadsheets. Customers notice too — faster responses and fewer errors feed directly into satisfaction, and staff spend their time on work that needs judgement rather than re-keying data. Together those add up to a genuine competitive advantage. The businesses that get the most out of transformation are the ones that pick one painful process to fix first, measure the result, and let that set the pace for the rest.
- What does digital transformation mean for a small or medium-sized business?
- For an SME, digital transformation rarely means adopting an enterprise platform wholesale. Every company, big or small, has developed its own unique business processes over the years — often informally, held together by habit, spreadsheets, and a few people who know how everything works. Transformation means taking those processes and making them run through software instead of memory: digitising the paper-based steps, automating the repetitive ones, and connecting the tools that currently do not talk to each other. The result is a better experience for the people using those processes — both clients and staff. The businesses we work with around Dorking and the wider South East usually start with the one process costing the most time or causing the most errors, fix that, and use what they learn to plan the next step. It is a lower-risk route than a single company-wide system, and it delivers a noticeable improvement much sooner.
- What is an API?
- An API (Application Programming Interface) is the agreed set of rules that lets two pieces of software exchange data and instructions without a person moving information between them by hand. It defines what data is available, how to request it, and what format it comes back in. APIs are what let your website talk to your accounting package, or your CRM pull stock levels from your warehouse system, without anyone re-typing numbers from one screen into another.
- What is automated deployment?
- Automated deployment is the practice of moving code and database changes from a development environment onto other servers — test or live — through a repeatable, scripted process, effectively at the push of a button, rather than copying files and running updates by hand. The point is reliability: manual deployments are where mistakes creep onto live production servers, and a scripted process runs exactly the same way every time. It also changes how software is delivered. Because each release is quick, efficient, and low-risk, changes can go live in small, frequent increments instead of one large and riskier update every few months. For the businesses using the system, that means fixes and improvements arrive steadily rather than in disruptive batches — and if a change does not behave as expected once it is live, it can be rolled back just as quickly as it went out.
- What is open source software?
- Open source software is developed on a model of transparency and collaboration: the source code, documentation, and APIs are published and made freely available to the global developer community, under a licence that grants anyone the right to use, study, change, and distribute the software for any purpose. For a business buying bespoke software, the relevance is practical. We build on well-maintained open-source frameworks and libraries rather than writing everything from scratch, which means faster delivery because solved problems stay solved, code that has been reviewed and tested by a global community of developers rather than a single team, no licence fee attached to the framework itself, and — because the technology is widely known — no lock-in to a single supplier to maintain your system in future. What stays bespoke is the part that actually matters: the workflows and logic specific to your business.
- What is an AI harness, and why does it matter?
- An AI harness is the software that sits around an AI model or agent and controls how it works inside your business. It decides what information the agent can see, which tools and systems it can use, which actions need a person's approval, and it records everything the agent does. The model supplies the reasoning; the harness supplies the control. Once AI agents move beyond answering questions to taking actions, such as updating records, sending emails or raising orders, the harness becomes the most important part of the deployment, because it is what keeps those actions within your business rules.
- Can we change AI model or provider later?
- Yes, if the harness is designed for it from the start, which is how we build them. AI models improve and prices change quickly, so we keep your workflow logic, approval rules and audit trail in a harness you own, separate from any single model or provider. Swapping in a better or more cost-effective model, or using different models for different tasks, then becomes a configuration and testing exercise rather than a rebuild. Platforms tied to one provider make that switch far harder, and the rules you have built up inside them rarely come with you.
- How do you keep a person in control of what AI agents do?
- By building approval points into the harness as code, rather than writing them as instructions the AI is asked to follow. Instructions, rules and skills given to a model are open to interpretation; a coded approval step is not. If an action such as a payment, a customer communication, or a change to a contract or a price needs sign-off, the workflow stops at that point until a named person approves it, and that approval is recorded in the audit trail alongside everything the agent did before and after it.
- Do we need to be AI-ready before you can help with AI?
- Not necessarily, but it shapes where we start. AI produces results worth trusting when it works from clean data and a defined process. If the workflow you want to improve already runs through a system, we can usually add AI to it directly. If it still lives in spreadsheets, inboxes or someone's memory, the honest first step is to turn it into a system, with AI added once there is something reliable to build on. Our AI readiness framework sets out how to tell which applies to you, and the fixed-scope analysis phase confirms it before any commitment to build.
What could work better
in your business?
You don’t need a finished brief to start a conversation.