--- title: "Guides: software costs, ownership and rescues" description: "When owning software beats renting, what bespoke software costs to build and run, how to scope a build before you pay, and when a spreadsheet is the risk." canonical: https://www.clientflow.ai/guides language: en-GB --- # Guides When to own software, what it costs to build and run, how to scope one before you pay, and what to do when a build stalls. The numbers we quote, written down. 1. [Build or buy? What the software you already pay for really costs](https://www.clientflow.ai/guides/build-or-buy-software-uk): For a team of twenty, three mainstream tools at list price cost about £73,800 over three years before a single price rise, and software prices rose 13.2% a year in the latest index, nearly five times general inflation. A focused version one you own costs from £10,000 to build and about £800 a year to run, and nothing per seat. Renting still wins when the workflow is standard, the seat count is small and stable, or the process is still changing every month. Owning wins when the workflow is yours, the team is growing, or the data has to be in your name. The break-even question is simple to ask, and we will answer it for free on a twenty-minute call. Verified 4 September 2026; 12 dated sources. Markdown: https://www.clientflow.ai/guides/build-or-buy-software-uk.md 2. [What bespoke software actually costs in the UK](https://www.clientflow.ai/guides/bespoke-software-development-cost-uk): A focused version one of a bespoke system costs from £10,000 in the UK, and most of what established teams ask us to scope fits between £10,000 and £50,000. Five things move the price, and all five can be seen before anyone commits: integrations, data, complexity, user roles and compliance. Running it afterwards is a short list of services in your own name, priced by usage rather than by the size of your team, plus whatever support you choose. The right first step costs nothing: a twenty-minute blueprint call that ends in a firm range, or in the advice not to build. Verified 4 September 2026; 17 dated sources. Markdown: https://www.clientflow.ai/guides/bespoke-software-development-cost-uk.md 3. [What the software you own actually costs to run](https://www.clientflow.ai/guides/running-costs): A version one of a bespoke system costs about £800 a year to run at list prices: hosting, a database with sign-in, transactional email and error monitoring, every account in your name and none of it per seat. Over three years that is about £2,600 including the ICO fee, against the £2,700 to £4,500 a year the industry rule of thumb would predict for an £18,000 build. The rule comes from studies of large, long-lived systems in which three quarters of what was counted as maintenance was new features, which is work we scope and price separately. Support after launch is a fixed monthly fee and optional; ending it changes nothing about the software. Verified 5 September 2026; 14 dated sources. Markdown: https://www.clientflow.ai/guides/running-costs.md 4. [How to scope a build before you pay for it](https://www.clientflow.ai/guides/how-to-scope-a-software-project): Scoping a software project is the work of writing down what will be built, for whom, against which systems and at what risk, in enough detail that someone can put one price on it. UK suppliers have to publish a price to sell through the government’s G-Cloud catalogue, and the discovery services filed there run from £500 to £2,000 a person a day, with two fixed-price examples at £9,350 and £9,460, one of them costed openly as twelve consultant days. That matches the labour arithmetic: two weeks of a business analyst and a technical architect is £10,000 to £12,000 at UK contractor day rates. Under UK law the person who writes a document owns the copyright in it unless the contract says otherwise, so a buyer who pays for a scope and agrees nothing in writing may hold only a licence to use it for the purpose it was commissioned for. The test of a real scope is whether it decides what counts as a defect and what counts as a change. Verified 7 September 2026; 23 dated sources. Markdown: https://www.clientflow.ai/guides/how-to-scope-a-software-project.md 5. [When a spreadsheet stops being the right tool](https://www.clientflow.ai/guides/replace-a-spreadsheet-with-software): A spreadsheet stops being the right tool when the process needs a rule the file cannot enforce, when more than a handful of people edit it at once, when nobody can say who changed a number and when, or when only one person could rebuild it. Nearly nine in ten production workbooks contain at least one error, but the typical formula is right about 98 to 99 times out of 100, so the risk is concentrated in a few bad files rather than spread evenly. Most teams should keep the spreadsheet and add a named owner and a backup. The ones that should not can usually try a database tool at £10 to £45 a user a month before commissioning anything, and a bespoke system starts at £10,000. Verified 7 September 2026; 27 dated sources. Markdown: https://www.clientflow.ai/guides/replace-a-spreadsheet-with-software.md 6. [Stuck with a Lovable build? Here is what to do](https://www.clientflow.ai/guides/stuck-with-a-lovable-build): A stuck Lovable project ends one of three ways: fixed, built on, or started again, and which one fits is a question about the code and the database, not about what you have spent. The code is a standard React project you own; the database you may or may not own yet. Most projects stall in the same places: permissions, the data model and a fix loop that bills you per attempt whether or not the attempt worked. On a free twenty-minute call we say which outcome we think it is, then read the code and the database before we put a fixed price on it, and the AI bill for the work is ours, never yours. Verified 4 September 2026; 12 dated sources. Markdown: https://www.clientflow.ai/guides/stuck-with-a-lovable-build.md RSS: https://www.clientflow.ai/guides/feed.xml. All guides in one file: https://www.clientflow.ai/llms-full.txt.