Spreadsheets are a prototype, not a system
Spreadsheets are where most business processes start, and that’s fine. The trouble begins when the spreadsheet becomes the system:
- forty tabs
- formulas nobody dares to touch
- three people editing at once
- no record of who changed the number that cost you money
An internal tool turns that prototype into software. Your rules are enforced in code. Everyone gets the right view for their role, every change is logged, and the copying between systems happens automatically.
Built around how your team actually works
The most important part of an internal tool is not the technology. It’s fitting the workflow. Before writing code, I sit with the people who do the work, and I usually find:
- Duplicate data entry across tools that can be synced automatically.
- Hidden rules, such as “this building is always priced 10% higher on weekends”, that belong in the system.
- Approval steps that happen over chat and should be explicit, logged and auditable.
Examples from production
- Pricing engine for a rental operator.
- Tiered pricing with cascading overrides and a multi-month calendar.
- Rate pushes to five channels, previewed before they go out.
- An audit log where every change can be reverted.
- Utility-bill operations dashboard.
- Around 30 screens covering scrape runs, reconciliation, an email inbox, an Excel viewer and owner report approvals.
- Used by a finance team handling more than 735 units.
You can try mock-data versions of both on the demos page.
What makes a good internal tool
Speed, clarity and trust. Pages load instantly, the next action is obvious, and the data can be trusted because the tool checks it on the way in. If your team hasn’t asked for the old spreadsheet back within a month, the tool is doing its job.
How a typical project is priced
Most internal tools land between $6,500 and $25,000. The range depends on four things:
- how many distinct workflows the tool covers
- how many systems it has to integrate with
- how complex the permission rules are
- how messy the existing data is to migrate
A single-workflow tool, such as a pricing calendar or an approvals queue, sits at the lower end. A multi-team operations platform is delivered in phases, each with its own fixed price, so value arrives early and budget stays under control.
Every project finishes with a parallel run. The old spreadsheet and the new tool run side by side for a short period until the numbers match and the team is confident. Only then is the spreadsheet retired.
Security and access
Internal tools often hold your most sensitive operational data, so they’re built with:
- Proper authentication, with SSO where you need it.
- Per-user permissions, not shared logins.
- Audit logs of every change, plus encrypted backups.