✦ Insights
Written for the person who has to make the decision, not for other developers. No invented statistics, no vendor spin, and we will happily tell you when off-the-shelf is the right answer.
Buying, cost and process
Systems mapping means putting every application your business runs on, how they connect, and where data actually flows, onto a single picture. Most businesses have never seen this drawn out, and it usually shows more risk than expected.
12 August 2026 · 9 min read
Buying, cost and process
Software outsourcing isn't a single decision. It's a set of choices about which parts of a project genuinely benefit from external delivery, which parts need to stay close to the business, and which location model fits the work you actually have.
12 August 2026 · 9 min read
Sector
Restaurant inventory management is really food cost control wearing a stock system's clothes. Counting deliveries in and stock on the shelf tells you what you've got, but not why your food cost percentage is drifting - for that you need recipe costing and yield tied to every dish sold.
12 August 2026 · 8 min read
✦ Buying, cost and process
Systems mapping means putting every application your business runs on, how they connect, and where data actually flows, onto a single picture. Most businesses have never seen this drawn out, and it usually shows more risk than expected.
Software outsourcing isn't a single decision. It's a set of choices about which parts of a project genuinely benefit from external delivery, which parts need to stay close to the business, and which location model fits the work you actually have.
Purchase order software exists to solve one specific problem: nobody can see where a request is stuck once it leaves someone's inbox. Here's what it should actually do, and what to check before you buy or build it.
An MVP development company is easy to find and hard to choose well. Portfolios all look similar; the differences that matter show up in how a team handles ambiguity, ownership and the awkward conversation about what to cut.
An inventory management system for retail has to do more than count boxes. It needs to know what's sold at the till a moment ago, what's still in the stockroom, what's on its way from another store, and what's simply gone missing.
Inventory management software for ecommerce has one job that matters more than any other: making sure the same unit of stock can't be sold twice across your website, your marketplace listings and any store you also run. Almost every ecommerce stock problem traces back to that one rule breaking down.
Cloud-based inventory management doesn't change how allocation or stock counting should work - it changes where the system lives, how it's paid for, and how much it depends on a working internet connection. Those are real differences, but they're not the ones most sales conversations focus on.
Business process improvement means looking honestly at how work actually gets done and fixing what's broken, before deciding whether new software is even the answer. Skip this step and software just makes a bad process faster.
Technical debt is the extra cost of maintaining and changing software because of shortcuts, ageing decisions, or a lack of investment in its design over time - not because the software is 'broken'. If your developer keeps using the phrase, it's worth understanding what it actually means before you agree to spend money fixing it.
A web app is software that runs in a browser rather than being installed, so anyone with a login and an internet connection can use it from any device. For most business systems - quoting tools, portals, internal dashboards - that's the format that causes the fewest headaches.
A software requirements specification is a written document describing what a system must do - its features, users, data, and the point at which each piece of work is considered done. It's the single most useful document you can bring to a first meeting with a developer, and this post is the template itself.
Software maintenance is the ongoing work of keeping a system secure, working, and useful after launch: bug fixes, security patches, hosting upkeep, and small improvements. It isn't optional for anything running in production, and it's usually priced either as a retainer or on an ad-hoc basis, not a fixed fee.
The software development life cycle is the sequence a piece of software goes through from idea to daily use: discovery, design, build, testing, release and ongoing support. Understanding it tells you what you're paying for at each stage and where a project usually goes wrong.
A software development contract should say, in writing, who owns the finished code, what happens if the supplier disappears, how changes to scope get priced, and what counts as acceptable work. Miss any of these and you're relying on goodwill rather than a contract. This isn't legal advice - get a solicitor to review the final document.
Professional services automation (PSA) replaces the separate timesheet spreadsheet, billing spreadsheet and resourcing spreadsheet that most firms accumulate, joining time, work-in-progress and staff availability into one place. It matters once those spreadsheets stop agreeing with each other.
Business process mapping is writing down how work actually moves through your business, step by step, before you change anything. Do it first and automation is cheap. Skip it and you automate the mess.
Agile vs waterfall is a choice about when you find out something is wrong. Waterfall plans the whole project up front and builds it in one pass; agile builds and shows you working software every couple of weeks so problems surface early. Most bespoke business software suits agile; some fixed, well-understood projects suit waterfall.
✦ Legacy systems and migration
Data migration is the craft of moving years of records from an old system into a new one without losing, duplicating or corrupting any of it. It's slower and more manual than most timelines assume, and it's where most system replacement projects actually go wrong.
The right Microsoft Access alternative depends entirely on how business-critical the database has become. For many businesses that's a modern hosted database or a low-code product, not a custom build - but the honest answer varies, and this guide walks through when each option fits.
A legacy system is software your business still depends on that is old enough, unsupported enough, or brittle enough that changing it, or even keeping it running, has become a genuine risk. Age alone doesn't make a system legacy - dependency without support does.
Legacy system migration doesn't have to mean switching everything off on a Friday and hoping the new system works on Monday. Moving slice by slice, with data reconciled at each step and a genuine way back, is slower on paper but far less likely to put the business at risk.
End-of-life software has stopped receiving security updates from its vendor. It usually still runs perfectly well, which is exactly why the risk goes unnoticed - the danger isn't that it breaks, it's that nothing is fixing the holes anymore.
✦ ERP and CRM
ERP implementation is where most of the risk in an ERP project actually sits - not in choosing the software. Here's the stage-by-stage plan that determines whether a system lands well or limps along for years.
MRP plans what you need to make and buy, and when. ERP does that plus finance, sales and stock across the whole business. Most mid-sized manufacturers eventually need both - the question is which to fix first.
ERP vs CRM comes down to what each system is the source of truth for. CRM manages the relationship with a customer up to the sale. ERP manages everything that happens once that sale becomes stock, an order and an invoice.
ERP system examples are more useful sorted by what a business actually does with each module than by vendor name. Here's what a manufacturer, a distributor and a services business each use ERP for, day to day.
ERP system cost is never one number. It's a licence or subscription fee, an implementation fee, data migration, training, and ongoing support, and the second one usually dwarfs the first. Here's what drives each up or down.
ERP for small business means one system holding stock, orders, purchasing and accounts instead of five spreadsheets that disagree with each other. Most small businesses need three or four modules, not the full suite a salesperson will show you.
A CRM system for small business should almost always be off-the-shelf to start with. The right question isn't which CRM is best in general - it's which one fits your sales process, and what to do when it eventually doesn't.
CRM implementation rarely fails because the software is wrong. It fails because of data, process and people decisions made - or skipped - before go-live. Here are the five that come up in almost every failed rollout.
✦ Sector
Restaurant inventory management is really food cost control wearing a stock system's clothes. Counting deliveries in and stock on the shelf tells you what you've got, but not why your food cost percentage is drifting - for that you need recipe costing and yield tied to every dish sold.
Inventory management for manufacturing isn't one stock figure - it's raw materials, work in progress and finished goods, each behaving differently, all linked by a bill of materials that determines what a finished item actually consumed to get made.
Construction payroll software has to run PAYE for employees and CIS deductions for subcontractors side by side, often for the same workforce on the same job, with hours that vary week to week and site to site. Generic payroll tools handle PAYE well and CIS poorly, or not at all. Here's the gap, and what to do about it.
Construction estimating software ranges from a well-built spreadsheet to a dedicated takeoff package to a bespoke tool tied into your job costing. Most contractors start with the first and grow out of it long before they admit it. Here's how to tell which one you actually need.
Construction cost management software should tell you a job is running over budget while there's still time to do something about it, not at month end when the CVR report lands. Most contractors only get the second version. Here's what the first one actually requires.
Construction accounting software has to handle retentions, applications for payment, CIS deductions, work in progress and job costing on top of the usual purchase and sales ledgers. A generic finance package can be made to do most of this with enough add-ons and workarounds. Here's where that approach holds up, and where it doesn't.
There are five types of manufacturing software most mid-sized manufacturers end up needing: planning (ERP/MRP), shop floor data capture (MES), quality, maintenance, and traceability. Few businesses need all five as separate systems on day one.
Time tracking software for construction has to do more than log hours - it has to allocate that time to the right cost code, treat CIS subcontractors and PAYE staff differently, and keep working when there's no signal on site. Here's what actually matters when choosing one.
Stock control software for a single warehouse just needs to count what's on the shelf. Add a second location and it has to track stock in transit between them, separate what's allocated from what's actually available, and stay accurate without a full annual stocktake.
Quoting software for manufacturing needs to build a cost from a routing and a bill of materials, apply your margin rules, and hand a won quote straight into production - without a second round of manual re-keying.
Production scheduling software plans what runs on which machine, in what order, given real constraints like changeover time and skilled labour. Most off-the-shelf schedulers assume constraints your plant doesn't have and miss the ones it does.
Job management software should follow a job from the first enquiry through to the invoice, without anyone re-typing the same details three times. Most field service businesses can buy this off the shelf - the trick is knowing exactly where your workflow stops matching the standard product.
Food traceability software has to link every batch you produce to the ingredient lots that went into it and the customers it was shipped to, and it has to prove that link in a mock recall - not just store the data somewhere.
Field service scheduling software has to match the right engineer to the right job by skill, certification and location, hold that against an SLA, and cope when a job runs long or an emergency call comes in. Most off-the-shelf tools handle the calendar view well and the constraints badly.
CVR in construction - cost value reconciliation - is the monthly comparison of what a job is worth against what it has cost, used to report margin honestly rather than by guesswork. Most contractors build it in Excel. Here's how it's actually assembled, and where that approach stops working.
Construction software for contractors isn't one product - it's six or seven categories that rarely talk to each other properly. Here's what each one does, which are safe to buy off the shelf, and where the gaps force you towards something built to fit.
✦ Integration
System integration is the plumbing that moves data between the separate systems your business already runs - CRM, finance, stock, a portal - so nobody re-types it. Done badly it's a tangle of one-off links; done well it's a small number of predictable connections.
Client portal software succeeds when it does two or three things customers actually want and does them well - not when it tries to mirror everything your staff can see internally. Scope creep, not technology, is what usually sinks these projects.
API integration is how two pieces of software exchange data without a person copying it between them. You don't need to write code to buy it well - you need to know what to ask a vendor before you sign the contract.
✦ Sales assets
Who owns the code isn't automatic just because you paid for it - under UK law, without a clear contract term, the developer who wrote it can retain the copyright. Here's exactly what to check before you sign, and this isn't legal advice.
What does custom software cost? Anyone who gives you a figure before understanding your process is guessing. What we can tell you honestly is what drives the number up or down, and how to compare two quotes that use different assumptions.
Web app or mobile app is usually decided by instinct - mobile feels modern - rather than by what the job actually needs. For most B2B tools, the honest answer is a web app, and this post explains why, and where the real exceptions are.
User adoption of new software usually fails quietly - people keep the spreadsheet running alongside the new system rather than raising an objection. Here's what actually drives adoption, and it starts well before launch day.
The cost of SaaS vs custom software looks like a clear win for SaaS in year one and often reverses by year four, once seats, growth and price rises compound. Here's the formula and the inputs - no invented figures, just your own numbers.
The right questions to ask a software development company aren't about their office or their tech stack - they're about what happens when something goes wrong. Here are ten, with what a good and a bad answer actually sounds like.
No code vs custom development isn't a contest - no-code is a genuinely good answer for a huge range of business tools. This post is about the five real ceilings where it stops working, so you can spot the moment before it costs you.
How to write a software brief comes down to one test: could two different suppliers read it and quote roughly the same price? If not, it's a wish list, not a brief. Here's the section-by-section outline that gets you a comparable, accurate quote.
Fixed price vs day rate isn't about which is cheaper - it's about who carries the risk when requirements change, which they usually do. Get this wrong and the commercial model works against you, not for you.
The custom software vs off-the-shelf question isn't about which is better - it's about whether your business is standard enough to fit a product, or unusual enough to need something built. Most businesses are more standard than they think.
Bring the messy version. Thirty minutes on a call is usually enough to tell you whether this is a build, a buy, or a spreadsheet that just needs tidying.
No pitch deck · We map your process · You own the software