We build internal software for small businesses in fourteen days at a fixed price: an app for your team on iPhone and Android and a dashboard for the office, built around how your operation actually runs. Most businesses over a certain size are held together by a spreadsheet one person understands. This replaces it.
What internal software costs
| Route | Typical cost | Fits when |
|---|---|---|
| Off-the-shelf software | A monthly fee per user | Your process matches the product and the team is small |
| Simple internal tool, UK agency | From about £10,000 | One job, few users |
| Staff portal or admin system | £8,000 to £25,000 | Several roles and permissions |
| Standard bespoke business build | £15,000 to £30,000 | Integrations, reporting, several teams |
| Full business system | £30,000 to £80,000 | Runs most of the operation |
Per-user pricing is the cost people underestimate. Twenty staff at £30 a user a month is £7,200 a year, every year, and it rises each time you hire. Custom software you own has running costs too, but they do not grow with headcount.
We are not one of those rows. We build one fixed scope in fourteen days for £999 or £1,999, with a full refund any time before we start. A single workflow with a dashboard fits the Starter App. Several roles, approval chains or complex rules usually need the Advanced App. More detail in what internal tools cost.
When this is worth doing
Count the hours. If someone spends four hours a week copying information between systems, that is around 200 hours a year of a paid person doing data entry. Put your own cost on those hours and compare it to a one-off build you own outright. In most cases the arithmetic is not close.
The other trigger is per-seat pricing. Off-the-shelf software that charges per user punishes exactly the thing you want to do, which is grow.
What we build
- Job and work managementWhat needs doing, who is doing it, what state it is in.
- Data capture in the fieldOn site, in a vehicle, on a shop floor. Offline where it needs to be.
- Stock, assets, and materials
- Timesheets and scheduling
- Compliance and inspection recordsStructured, searchable, and retrievable years later.
- Dashboards and reportingSo the office can see what is happening without phoning to ask.
Every build also includes user accounts, push notifications, testing on real devices, store submission, accounts in your name and 30 days of support. The full list is on what's included.
What's not included
Who this suits, and who it doesn't
It suits businesses where the process is specific enough that off-the-shelf software does not fit, and repetitive enough that the manual version is costing real money: field teams, workshops, distributors, service firms.
It does not suit a business whose spreadsheet genuinely works, or one where an off-the-shelf tool does 90% of the job at a reasonable price. Buy that instead. Custom starts winning when the 10% it does not do is the part that matters, or when per-seat pricing has become punitive. Off-the-shelf or custom, compared.
How the fourteen days work
- Day 1
Kick-off and scope
We go through your goals, your users, and the one job the app has to do. Everything that is not that job goes on a version-two list.
- Days 2 to 3
Design
Screens, flows, and the look of the thing. You review and revise until you sign off. Nothing gets coded until you have.
- Days 4 to 10
Build
Front end, backend, accounts, notifications, admin dashboard. You see working builds as they land rather than a reveal at the end.
- Days 11 to 12
Test and fix
Real devices, real data, edge cases. This is where most of the unglamorous work happens.
- Days 13 to 14
Submit and launch
Store listings, screenshots, privacy details, and submission to the App Store and Play Store. Then 30 days of support while your first users arrive.
Day one is spent with the people who do the work, not just the person who wants the report. The full process is on how we work.
The thing that decides success
Adoption, not features. Internal tools fail when they make the day longer for the person using them so that somebody else can have better data. Build for the person doing the work, and the reporting arrives as a by-product. Why teams refuse the software you bought.
Common questions
How much does internal business software cost in the UK?
Published UK pricing puts a simple internal tool from about £10,000, a staff portal or admin system at £8,000 to £25,000, and a standard bespoke business build at £15,000 to £30,000. We build one fixed scope in fourteen days for £999 or £1,999.
How do I know a custom tool is worth it?
Count the hours. If someone is spending four hours a week moving information between systems, that is roughly 200 hours a year. Put a cost on those hours and compare it to the build. The decision usually makes itself.
Is custom internal software worth it for a small business?
Often more than for a large one, because a small team feels every wasted hour and every per-seat licence. It is worth it when the process is specific to you and repeated every day. If an off-the-shelf tool fits, buy that instead.
Will our team actually use it?
Only if it is faster than what they do now. That is the design brief, and it is why we build for the person doing the work rather than for the person who wants the report.
Can it connect to Xero, Sage, or our existing systems?
If they have an API, yes. Older systems often do not, and the practical answer there is a scheduled export rather than live sync. We establish which on day one rather than discovering it on day nine.
Do we own it?
Yes. The code, the database and the accounts are in your name. There is no per-seat licence, so adding staff costs nothing.