Internal Tools Development
The tool that replaces the spreadsheet your operations actually run on — with permissions, history and no broken formulas.
Map your workflow ↗
What counts as an internal tool?
An internal tool is software only your staff use — an operations console, an approvals queue, a reconciliation screen, a bulk-import job. Nobody markets it and no customer sees it, which is exactly why it tends to end up as a shared spreadsheet with colour-coded rows and one person who understands the macros.
The signal it’s time to build something is rarely elegance. It’s when two people edit the same cell, when a wrong number reaches a customer, when onboarding a new hire takes a fortnight of shadowing, or when you can’t answer who changed a value and why. Those problems are about permissions, validation and history — the three things a spreadsheet can’t give you.
What an internal tool includes
Process mapping first
We sit with the people doing the work and record what actually happens, including the workarounds. The documented process and the real one are never quite the same.
Roles and permissions
Who can see, edit, approve and export, modelled explicitly. Most internal tools leak because everyone was given admin on day one.
Audit trail
Every meaningful change stored with who, when and previous value, so questions about a record have answers instead of theories.
Validation at entry
Rules enforced where data is typed rather than cleaned up in a monthly report. Bad data is cheapest to stop at the keyboard.
Spreadsheet migration
We import your existing sheets, reconcile the duplicates and inconsistencies, and keep a read-only export so nobody feels cut off.
Bulk actions and search
The unglamorous features that decide adoption — filtering, keyboard entry, editing fifty rows at once, and pasting from Excel.
How an internal tool build runs
Shadow the work
A few days watching the current process end to end, timing the painful steps so we can tell which ones are worth automating and which aren’t.
Agree the smallest useful tool
One process, one team, one screen set. Internal tools fail when they try to be the whole operating system on day one.
Build with the users in the room
Weekly sessions where the actual operators click the thing. Their objections in week two are worth more than any specification.
Migrate and run in parallel
The tool and the spreadsheet run side by side for a week or two, so discrepancies show up before the sheet is retired.
Retire the spreadsheet
Switch over, train the team, and hand across documentation plus a short list of the next processes worth absorbing.
Internal Tools Development FAQ
Most single-process tools land between $8k and $30k, which is often less than the annual cost of the manual work they replace. We’ll help you do that comparison honestly before committing, including the case where the answer is not to build.
The tools we build with
Internal tools live for years with small budgets, so we favour a plain stack any developer can pick up over anything clever we’d have to explain.
Interfaces
React
Next.js
TypeScript
TailwindServices & data
Python
FastAPI
PostgreSQL
PrismaAccess control
Keycloak
Auth0OAuth 2.0Reporting & ops
Metabase
Docker
GitHub Actions
SentryRelated work
Related reading
Which spreadsheet is holding you together?
Send us the sheet and tell us who touches it. We’ll come back with a scoped tool, a migration plan, and an honest view on whether buying beats building.