Automation · Deep dive 04
Custom Internal Tools
Admin panels, dashboards, operator consoles — built for your people, not for the general market. Low-friction UX, role- aware, scoped to the job.
What this is
When Retool + Airtable stops scaling and Salesforce is overkill, we build the tool fit to your team. Usually React + API, occasionally on Retool / Appsmith when their primitives fit cleanly. Designed for the ops team, not the sales demo.
Does this sound familiar?
-
Support spends 15 minutes per ticket in 4 different tools instead of one.
-
You bought a tool to handle X and the team still does X in spreadsheets on the side.
-
Operators have asked for a 'refund and re-ship in one click' button for two years.
-
The existing admin panel is a read-only mirror of the DB that nobody wants to use.
-
Your top operator knows things that should be in software.
The customer payoff
What you get
What you feel once it’s running.
Tooling shaped to the actual job — not to a vendor's feature menu.
-
Hours saved per rep per day (measurable from the day it launches).
-
Reduced error rate because the software enforces the steps that matter.
-
Happier operators — it sounds soft, but it shows up in retention.
Phases
⏱ 6–12 weeks typicalHow Custom Internal Tools actually runs.
-
01
Shadow
A full day with each operator role. What they click, what they copy, what they have to ask a colleague about."
-
02
Sketch
Wireframes with operators in the room. Iterating on paper beats iterating in code."
-
03
Ship
Weekly releases to real operators. They tell us what's broken within 24 hours; we fix it."
-
04
Harden
Role-based access, audit trail, rate limits, admin-proof destructive actions. The unglamorous layer that matters once someone tries to mass-update."
The hand-off
In the build
What lands in your hands — every artefact, nothing hidden.
-
Production internal tool on your infra
-
Role-based permissions with a simple admin UI
-
Audit log for every state-changing action
-
Bulk operations where they save operator time
-
Basic reporting + CSV exports
-
Handover with written operator guide
The usual questions
-
Q·01 Retool vs custom React?
Retool when the primitives fit and you want non-engineer maintenance. Custom React when design polish, performance, or workflow specificity matter. We'll tell you honestly which is right for your scope."
-
Q·02 Who maintains it after launch?
Your team can. We build on common stack (React + Node + Postgres) and document it. Optional retainer for the first 90 days."
-
Q·03 How do we handle access?
SSO through your existing identity provider (Google, Azure AD, Okta). Roles defined in our system, mapped to groups in yours."
-
Q·04 Can this integrate with our existing admin?
Yes — usually it sits alongside existing admin panels at first, then replaces the parts it supersedes. Gradual migration is standard."
-
Q·05 What about mobile?
Internal tools are usually desktop-first. If your operators work on iPads or phones, we design for that specifically — but we don't bolt mobile on after the fact."
Ready to start
Build the tool your team deserves.
Day with the operators, honest scope, fit-for-purpose build. Start with whoever's got the most tabs open right now.
Start an internal toolThe wider map
Every service page at a glance.
Each link below opens a dedicated page on that specific piece of one of our four service pillars. Jump sideways — different service, same way of working.
Digital Product Strategy
Service overview →Web & Mobile Development
Service overview →Business Automation
Service overview →- 01 Workflow Automation
- 02 AI-Assisted Operations
- 03 Process Digitisation
- 04 Custom Internal Tools — you’re here
- 05 System Integration & APIs
- 06 Data Pipelines & ETL