Internal tools
We replace the spreadsheets, side chats and workarounds holding your operation together with one tool built around how the work really happens - the thing your team opens every morning.
Start a projectThe service
Norex builds the custom software a company actually runs on - orders, jobs, approvals and stock in one place.
We map the work before building anything, design adoption in from the start, and connect the tool to the systems you already pay for.
The replacement
Every colour-coded, six-versions-deep, only-Dave-understands-it file gets replaced by one tool with one source of truth. The data moves across deliberately, with checks, before the old files are switched off.
The fit
Screens, steps and statuses match the way work really moves through your business - including the exceptions. Nobody bends their day to fit a product built for a company in Ohio.
The rollout
The tool is fast, simple and built with the people who will use it, tested against real work as we go. It wins because it is easier than the workaround, not because of a memo from the top.
The connections
Accounting, inventory, email and the rest feed in automatically. We agree which system owns each record, so nobody retypes anything and the numbers always match.
When this matters
The business runs on files only two people understand, and both of them are on leave in January.
Answering a simple question about an order or a job means opening four tabs and ringing one person.
The software you pay for makes the team work its way, so the real process lives in side chats and memory.
Nobody can see what is stuck, what is late or who is overloaded without a meeting about it.
What becomes possible
One place holds the status of every order, job and decision, so answers stop depending on who is in the room.
The steps that existed only to serve the spreadsheet disappear, and the day gets shorter.
The team actually uses it, because it was built with them and beats the workaround it replaced.
How the work moves
We follow the process as it actually runs - the spreadsheets, the judgement calls and the exceptions that never made it into any document.
Output: A map of the workflow, the roles and the friction points
We redesign the path around the outcome and remove the steps that only existed to serve the workaround, before any screen is drawn.
Output: A target workflow and a prioritised scope for the first release
The people who will use the tool test it as it is built, and we connect it to the systems that already hold your data.
Output: A working tool with permissions, reporting and links to your systems
Data is moved across with checks, the team is trained in a working session, and the old files are retired on an agreed date.
Output: A controlled rollout, an operating guide and an improvement backlog
Make the right investment
If one person owns it and mistakes are cheap, keep the spreadsheet. Build when several people depend on it, errors cost money, or you need live status, permissions and history.
If an existing product covers most of the workflow and bending your process to fit costs you nothing, that is the cheaper path. We will say so when it is.
The case for a custom tool is strongest where your way of working is the advantage. Generic steps stay in generic software; the tool covers what makes the operation yours.
Questions
Related services
Start a project