Internal Tools and Dashboards

What counts as an internal tool?

An internal tool is any application only your own team uses. A dashboard that pulls sales, jobs and invoices from three systems into one screen. A quoting tool that stops staff re-typing prices from a PDF. A job board that replaces the whiteboard, a stock count that replaces the spreadsheet, an approval queue that replaces the email chain. The common thread is that the users sit in your business, the data already exists somewhere, and the manual process is costing hours a week.

Because the users are staff rather than customers, the build is shorter and the stakes are lower than a public portal. That is what puts the starting price at $8,000 + GST rather than the $12,000 + GST of a web app or client portal. The engineering standard does not drop with the price.

How does an internal tools build start?

Every build starts with the discovery and prototype sprint, which runs two to three weeks and costs from $4,500 + GST, credited against the build if it proceeds within 30 days. For an internal tool the sprint is mostly about the existing process: who does what, in which spreadsheet, and where the data actually lives. The prototype is put in front of the staff who will use it, because they know where the current process breaks and they are the only people whose opinion of the tool matters.

The sprint ends with a fixed-price quote. It itemises the tool, any integration it needs, every third-party platform and API fee, and the maintenance plan as a separate line from 15% of the build cost per year.

What is included in every internal tools build?

Test automation and release assurance are built into the price of every build above the discovery sprint. They are never an optional line, and they are not trimmed because the tool is internal. An internal tool is the build most likely to be extended by someone else in two years' time, and the handover suite is what makes that safe. Every build includes:

• An automated end-to-end test suite in Playwright, handed over with the code
• API contract tests against every integrated service
• Load and rate-limit testing with K6 where third-party API caps apply
• Failure-mode coverage: token expiry, webhook retry, partial failure, duplicate delivery
• Security checks for backend-only credential handling and per-record access
• A CI pipeline on GitHub Actions with the test suite gating deployment
• Test documentation the next developer can actually run

The security checks matter even when the tool never faces the public. An internal dashboard usually holds API keys for your accounting system or CRM, and those keys stay on the server, never in the browser.

How does the tool connect to the systems we already use?

Most internal tools exist to read from or write to something you already run. A dashboard reads from your accounting system; a quoting tool writes to your CRM; a job board pulls bookings from a scheduling platform. That connection is scoped and priced with the tool rather than discovered halfway through.

Where the tool needs custom code to talk to one system in one direction, the work is scoped as a standard integration from $3,500 + GST, with contract tests against the system's API. Where no custom code is needed, a connector-level integration on Zapier, Make or n8n from $850 + GST is cheaper, and you own the automation account. The sprint decides which applies.

Two costs are named in every quote. Third-party API usage bills by volume after launch, and the quote states what the systems you connect to charge and who pays. And where the tool handles personal information, a business turning over more than $3 million a year, or handling health information, has Privacy Act 1988 obligations that add 10–40% to a build depending on the data type. Both are on the quote, not in a variation.

What does the build cost and what do you own?

Builds are priced from $8,000 + GST. A single dashboard with one read-only connection and one user role is the starting price. A tool with several roles, write access to a business system, scheduled reports and an export path sits above it. The price is fixed after the sprint and does not move unless the scope does, in writing.

You own everything: the repository, the test suite, the CI configuration, the hosting accounts and the runbook. The documentation is written for the person who maintains the tool after us, whether that is your own developer or someone we have never met. A tested tool is cheaper to change, and a client with the tests is never dependent on the people who wrote them.

The app maintenance plan is quoted as a line item from 15% of the build cost per year, as a monthly fee with named inclusions and no lock-in. It covers dependency updates, monitoring and the small changes a tool needs as the business around it changes.