01
Admin and back-office tools
The screens your team lives in, designed with the same care as anything customer-facing.
What you need
Software for the people who work for you.
Internal tools are where design quality quietly pays for itself. A customer might use your product weekly; your staff use their tools every hour of every day. Ten seconds saved on a task done two hundred times a week is real money.
Why it matters
The short version.
Internal tools are the clearest return on design investment anyone can make, and they are consistently the last thing funded. The logic that starves them is understandable — customers generate revenue, staff do not — and it misses that staff use these tools for hours every day, where customers might use yours for minutes a week.
Do the arithmetic once and it stops being an argument. Ten seconds removed from a task performed two hundred times a week by six people is roughly forty hours a year. That is a person-week, recovered annually, from one interaction. Most internal tools have a dozen such interactions.
There is a second, quieter cost. People route around bad tools. They keep private spreadsheets, batch work up to avoid the slow screen, or skip the optional field that would have been useful later. Your data quality is downstream of how pleasant your tools are to use.
Your data quality is downstream of how pleasant your tools are to use.
Is this you?
You probably need this if…
- Your team copies data between systems by hand
- Onboarding a new staff member takes weeks because the tools are confusing
- People keep private spreadsheets because the official tool is slower
- Simple questions need a developer to run a query
What's involved
The actual work.
No two engagements are identical, but this is the shape of it.
02
Workflow and approvals
Routing, sign-off and status that reflect how decisions really get made in your organisation.
03
Reporting for non-technical staff
Answers without needing SQL or a developer's afternoon.
04
Bulk operations
Because doing something to four hundred records one at a time is not a workflow.
What goes wrong
Mistakes worth
avoiding.
Named plainly, because most of them are easier to avoid than to undo.
-
Assuming staff will tolerate anything
They will, and they will also find workarounds that quietly corrupt your data. Compliance is not the same as adoption.
-
Designing from the database outward
Tools shaped like the data model force people to think like the database. The screen should match the task, not the schema.
-
Never watching anyone use it
The gap between how a tool is meant to be used and how it actually gets used is where all the improvement is.
How it runs
Start to finish.
Each phase ends in something you can open, click or read.
-
01
Observe
We watch people do the job. What they do and what the manual says rarely match.
-
02
Prioritise
Frequency multiplied by friction — the highest-value fixes are often unglamorous.
-
03
Build
Starting with whatever is costing the most time right now.
-
04
Measure
Confirming the time actually got saved, not just that it feels nicer.
Deliverables
What you walk
away with.
Yours to keep, whatever happens next.
Tools your staff prefer to their workarounds
Permissions and audit trails appropriate to the data
Faster onboarding for new hires
Source code and documentation you own
Questions
Worth asking.
Anything else — email hello@haddon.software and a human replies the same business day.
This is where the return is clearest. Staff use these tools constantly, so friction compounds daily — and unlike customers, they cannot leave, which means the cost shows up as slowness and errors rather than churn.
Usually. Most business systems expose an API, and where one does not there are other routes. We will confirm feasibility before quoting rather than after.
Involving them in the design is the single most effective thing. People who were asked what they needed tend to adopt the result; people handed a finished system tend not to.
Time-and-motion on the two or three most repeated tasks, multiplied by the people doing them. It is usually a shorter payback period than the customer-facing work competing for the same budget, and it is easier to measure afterwards.
Frequently, yes, and it is cheaper. A lot of internal tool pain is a handful of screens and a missing bulk action. We would rather fix those than sell you a rebuild you do not need.
Related
You might also need…
Want to talk it through?
The first call is free, runs about thirty minutes, and you'll get a straight answer about whether we're the right fit — including when we're not.