Custom internal tools and bespoke back-office software
The tool your team needs, built around your process.
Custom internal tools development means building the back-office software your team uses every day around the way you actually work: purchase approvals, supplier onboarding, job planning, quality checks, a bespoke CRM or any process that now lives across emails, folders and spreadsheets. This page helps you decide whether you need one, how Retool and other low-code platforms compare honestly with a custom build, and when an off-the-shelf package is the better answer.
If any of these sound familiar, we can help.
- 01The process lives in five tools that don't talk to each other.
- 02Manual steps that depend on a single person.
- 03Generic software that forces you to work its way.
What's included
We agree the exact scope with you in the proposal.- Administration
- Purchasing
- Human resources
- Operations
- 01
Workflows
Statuses, approvals and clear owners.
- 02
Roles and permissions
Each person sees and edits what's relevant to them.
- 03
History
Who changed what and when.
- 04
Reports
Lists and exports ready to use.
A back office to manage supplier onboarding, approvals and documentation.
One place for the whole process, with automatic alerts at every step.
Signs a process needs its own internal tool
Most businesses run a few processes that no standard package quite covers. They survive on goodwill, inboxes and a spreadsheet with too many tabs. The usual signs that this has become a problem:
- Approvals happen by email, and nobody can later show who said yes, or when.
- To find out where something stands, you ask in Teams or walk over to someone's desk.
- A report is assembled by hand every Monday from three different exports.
- New starters take weeks to learn a process that exists only in people's heads.
- A customer audit or ISO 9001 review means digging through months of emails for evidence.
- A spreadsheet holds the process together; if that sounds familiar, see also convert Excel to a web app.
What bespoke back-office software includes
Bespoke back-office software starts from a model of your process: the things you track (orders, jobs, suppliers, assets), the stages they go through and who acts at each one. Screens, rules and documents are then built for each role, rather than one generic screen everyone has to adapt to. Typical pieces:
- A clear record for each item, with every document, comment and decision attached in one place.
- Business rules enforced by the system: a purchase above a set amount cannot skip a second approval.
- Generated documents: purchase orders, job packs or inspection reports from your templates.
- Connections to what you already run: the ERP for prices and stock, Microsoft 365 for sign-in and email.
- MI dashboards built on live data instead of weekly exports.
- Imports from the old way of working, so history is not lost on day one.
Bespoke CRM or HubSpot, Pipedrive and the like
If your sales process is the standard one (leads, deals, pipeline stages, emails), a standard CRM is almost always the right answer, and we will say so. A bespoke CRM makes sense when the sale itself is unusual: a site survey before the quote, prices calculated from technical rules, long contracts with renewals and service visits, or a need to show ERP data such as balances and order history next to every account.
The same logic applies to so-called custom ERP software. Our advice is usually to keep Xero, Sage or Business Central for the accounts and build the operational piece around it, connected through ERP integration services, instead of replacing a finance system that already works.
Retool vs custom build: an honest comparison
Retool, Power Apps and similar platforms are good at one thing in particular: putting screens over a database you already have, quickly. Retool is a developer tool, so someone technical still builds it. It charges per builder and per internal user each month, meters external users on some plans and offers self-hosting only on its Enterprise plan. Microsoft's UK page lists Power Apps Premium at £15.40 per user per month, paid yearly, excluding VAT (November 2026).
Neither is the wrong choice for a simple admin panel used by a small team. The picture changes as users, external access and logic grow, or when you need the tool to outlive the platform.
| Criterion | Retool or Power Apps | Custom build |
|---|---|---|
| First working version | Very quick for screens over existing data | Slower: needs design and development |
| Cost as you grow | Rises with every builder and user | Mostly fixed: project price, then hosting and support |
| Customers or suppliers logging in | Extra licensing or metered users | Part of the design |
| Complex rules and user experience | Possible, but you work within the platform | Whatever the process needs |
| Leaving later | The app lives in the platform's format | Standard code in your repository |
How we would build your internal tool
An engineering firm could start with purchase approvals alone and add supplier records and job costing once the team trusts the tool. Each step is designed with the people who do the work, shown as a working demo every two weeks and delivered under one fixed price per project, with the code in a repository in your company's name. How scope changes and support work is set out on our page about fixed price software development.
Frequently asked questions
See all FAQs →Can we start with just one part of the process?
Yes, and it's what we recommend. We start with whatever takes up most of your time and expand from there.
Who can see and edit each thing?
We define roles and permissions per person or department. Every change is logged.
Is training needed?
A short session is usually enough, because the tool is designed around how you already work.
Does a custom internal tool replace our ERP or work alongside it?
Usually alongside it. The ERP keeps the accounts, stock and invoicing; the internal tool handles the process the ERP does not cover and reads from or writes to it through its API. Replacing the ERP is a much bigger decision and rarely the first step.
Would Retool or Power Apps be enough for this?
For a simple tool used by a few internal people, often yes, and it will be quicker. If customers or suppliers need access, the rules are complex or you want to avoid per-user costs that grow with the team, a custom build usually works out better over time. We tell you which fits on the first call.
Can another supplier maintain it if we stop working together?
Yes. The code is yours, in a repository in your company's name from the first day, written in mainstream languages and documented. If you prefer another team, everything is handed over documented.
What does a bespoke CRM do that HubSpot or Pipedrive doesn't?
It follows your sale rather than a generic pipeline: technical surveys, rule-based quotes, contract renewals or ERP data on every account. If your process is standard, it does nothing they don't, and you should buy rather than build. The guide on how much custom software costs helps you weigh it up.
You might also be interested in
- Web platformsDashboards and MI reportingYour key business numbers on one screen, updated automatically.
- Web platformsERP and CRM integrationYour systems pass data to each other automatically, no copy-and-paste.
- Mobile appsDelivery and proof-of-delivery appsRoutes, deliveries and proof of delivery from the driver's phone.
Tell us about your project.
We'll reply within one working day. We start by understanding the problem, not by selling you a solution.