Internal tools

    Internal tools your team opens at 9am and trusts by 9:05.

    Most operations run on a spreadsheet, a phone and someone's memory. We replace that with an internal tool built for the job: a live dispatch board, automatic invoicing on completion, searchable records, and a dashboard that tells the manager what is happening right now. Not a no-code app that hits a wall at the first unusual rule, and not a general-purpose builder your team has to maintain. Software written for your process, running on infrastructure you own.

    The software your staff open at 9am.

    The back-office software a business actually runs on. Dispatch boards, inventory and invoicing, admin panels, and a live view of what is happening today.

    1
    Person running a dispatch board that took three
    Live
    Hardware and real-time integrations in production
    CSV / Excel
    Export on every build
    StackNext.js·React·TypeScript·Node.js·PostgreSQL·Supabase
    The problem

    Where teams get stuck

    The business runs on a spreadsheet only one person fully understands

    Jobs get missed and invoices go out late because dispatch and billing never talk

    Nobody can answer what is happening right now without ringing three people

    The work

    What we actually build

    Operations dashboards

    Live job status, revenue and inventory in one view, instead of four tabs and a phone call.

    Scheduling and dispatch

    Drag-and-drop boards that assign work to people and vehicles, with the whole day visible at once.

    Inventory and invoicing

    Stock that decrements when work happens, and invoices raised automatically on job completion.

    Admin panels and audit trails

    Configure rates, zones and rules without a developer, and see who changed what, when.

    The path

    How we get you there

    A tight, low-risk path from first call to something running in production.

    01

    Shadow the work

    We watch the current process before proposing anything to replace it.

    02

    Scope it tight

    Nail down what to build, and just as importantly what to skip.

    03

    Build in slices

    Small increments, in front of the people who will use it every day.

    04

    Hand it over

    Documentation and a deployment runbook, with the repository signed over.

    Included

    In every build, not as an extra

    Automated tests on the paths that matter

    Auth, billing, and anything touching money. Those fail in CI, not on a customer's invoice.

    Documentation and a real handover

    Architecture notes, setup instructions and a deployment runbook. Written, not promised.

    Reporting and CSV/Excel export

    Because ops teams always need the data out, and always need it sooner than you planned.

    Full source-code ownership from day one

    In your repository, from the first commit. No license, no lock-in, no hostage situation.

    The decisions

    What makes an internal tool survive its second year

    Internal tools rarely fail at launch. They fail eighteen months later, when the person who commissioned it has moved on and the business has changed shape around it.

    Configuration, not code

    Rates, zones, statuses, approval thresholds and email templates belong in a settings screen an operator can reach. Every one of those that lives in code becomes a support ticket and a deploy, and the tool slowly turns back into something only a developer can change, which is where you started.

    An audit trail from day one

    Who changed what, when, and what the value was before they changed it. Retrofitting this is unpleasant, because the history you want is the history nobody recorded. It costs almost nothing at the start and it is the first thing anyone asks for the day an invoice is disputed.

    Permissions that survive a re-org

    Model roles against what the business does rather than against the current org chart. A tool built around five named people needs rewriting the first time somebody changes job, while one built around dispatcher, manager and finance keeps working when the names underneath them move.

    Exports on every screen

    Operations and finance will always need the data somewhere else, and if you do not give them CSV they will build a shadow spreadsheet to get it. That spreadsheet then becomes a second source of truth, which is the exact problem the tool was commissioned to put an end to.

    A way in for other systems

    Accounting, telephony, payment terminals, and the next tool nobody has bought yet. An internal tool with no API becomes an island, and prying the data back out of it later reliably costs more than a thin documented endpoint would have cost at the beginning.

    Someone can run it locally

    A README that works on a clean machine, seed data, and a deploy that repeats. This is what decides whether the next developer can help you in an afternoon or spends their first week reconstructing an environment out of somebody else's memory.

    Questions

    Answered before you ask

    What exactly counts as an internal tool?

    Anything your staff use to run the business, rather than anything your customers see. Dispatch and scheduling, inventory and invoicing, admin panels, approval workflows, reporting dashboards. If the permissions and the audit trail have to hold up, it is our kind of work.

    How is this different from Retool or Airtable?

    They are good at the first eighty per cent and expensive at the last twenty. They hold until you hit a rule they were not designed for, or a per-seat bill that grows with headcount. A custom tool costs more up front and then stops costing, and nobody can deprecate it under you.

    Our spreadsheets mostly work. Should we replace them?

    Spreadsheets fail in a specific way. They scale until two people need the same row at the same time, or until the person who built it leaves. If that is not biting yet, keep them, and we will say so. When it is biting, the fix is not a bigger spreadsheet.

    How much does a custom internal tool cost?

    One price, agreed at discovery before anything starts, and a first production version typically takes four to eight weeks. A single integration, a report, or a fix to something already running sits well below that. Cost is driven by how many distinct roles need their own permissions.

    Can it talk to our existing hardware or software?

    Often, yes. We have built a billing system driven by live weigh-scale hardware, and a dispatch platform running seven third-party integrations at once. Existing databases, accounting tools, payment terminals and telephony are all fair game.

    What happens after the tool goes live?

    You get a real handover: architecture notes, setup, deployment runbook, and the code in your repository, so you are never dependent on us. Most clients keep us on for support anyway, and some have been with us over a year, but that is a choice rather than a requirement.

    Can it run on top of our existing database?

    Yes, and often that is the cheaper route. If your records already sit in Postgres, MySQL or an accounting system with an API, the tool reads and writes there instead of starting a second source of truth. Two systems holding the same records is the problem you are trying to leave.

    Tell us what it has to do.

    Describe what you’re building, what it has to do and when it needs to be live. You’ll get back the architecture we’d use, the trade-offs, and a realistic timeline, before anything is signed.