Internal business tool development

Not every build is a startup. A large share of the most useful software in the world is internal: the job tracker, the quoting tool, the stock sheet, the roster. It usually starts as a spreadsheet, and at some point the spreadsheet becomes the bottleneck — two people edit it at once, somebody deletes a column, and nobody can use it on a phone at a job site.

This is the lowest-risk category on the list, because the requirements already exist. You are not guessing what users want. There is a spreadsheet, and you can read it. The value is also immediate and measurable in hours saved per week.

A 48-hour internal tool is a genuinely good deal compared with the alternative, which is usually a per-seat SaaS subscription that does eighty percent of what you need forever, or a $30,000 custom quote.

The three features worth starting with

1. 1

   The records your business runs on

   Create, edit, search and list — jobs, quotes, clients, stock, whatever the spreadsheet holds today.

2. 2

   Team login and a mobile-friendly interface

   Your staff log in and use it on a phone in the field, not just on a desktop in the office.

3. 3

   The one automation that saves the most time

   The repetitive job worth removing: a generated PDF, an automatic email, a daily summary, a calculated total.

A worked example

The mistake to avoid

Trying to rebuild every quirk of the spreadsheet. Half those columns have not been filled in for two years. Build the workflow, not the artefact.

Common questions

Can you build a internal tool in 48 hours?

Replace the spreadsheet your business has outgrown with a proper web app — built and deployed in 48 hours for a fixed $3,500 AUD.

What features should a internal tool MVP start with?

The records your business runs on: Create, edit, search and list — jobs, quotes, clients, stock, whatever the spreadsheet holds today. Team login and a mobile-friendly interface: Your staff log in and use it on a phone in the field, not just on a desktop in the office. The one automation that saves the most time: The repetitive job worth removing: a generated PDF, an automatic email, a daily summary, a calculated total.

What is left out of a internal tool MVP?

Fine-grained role permissions beyond staff and admin; Integrations with Xero, MYOB or QuickBooks (real work, worth a second build); Offline use on site with no signal; Migrating years of messy historical spreadsheet data (a one-off import can be quoted separately). Each of these is deliberately deferred to a later build rather than half-finished in the first one.

What is the most common mistake when building a internal tool?

Trying to rebuild every quirk of the spreadsheet. Half those columns have not been filled in for two years. Build the workflow, not the artefact.