Internal tools for engineering firms
I'm Hugo, a mechanical design engineer in London. I build the software a firm of 10 to 100 people uses every day to buy parts, keep procedures current, print labels and sign in visitors, made to fit how your team already works.
Detail A shows the approval flow I built for a battery R&D company. The names, suppliers, figures and requests below are fictional examples. Approve or reject them to see how the queue, budgets and audit log work.
Interactive example only. All records are fictional. Approvals, orders, emails and notifications are simulated in this browser; nothing is sent or saved.
Approval queue
- Anything over £1,000 goes to a director for a second sign-off.
- Budgets move the moment an order is raised, not at month end.
- Every step is logged with who did it and when.
Detail B: operations platform
Battery R&D company, name withheld. Not to scale.
Already running in a working lab. At a battery R&D company I built the operations platform the whole site now uses, and I still run it. Select a part to see what it replaced.
20staff use it every working day
NotesWhat I fix
The jobs that live in spreadsheets, inboxes and paper books because no off-the-shelf product fits a lab or a workshop.
- Purchase requests chased by emailPurchasing with approvalsRequests, sign-off limits and project codes that match your accounts, so finance stops guessing.
- Risk assessments saved as Word filesControlled documentsVersioned risk assessments and procedures, with review dates and a record of who read what.
- Labels typed out one at a timeOne-click printingSample labels, asset tags and forms printed from the record, on the printer they belong on.
- A paper visitor book at receptionVisitor check-inAn iPad at the door that signs people in, prints a badge and tells the host they have arrived.
- Customer notes in six placesA shared CRMOne list of contacts, quotes and conversations the whole team can see.
- The spreadsheet only one person understandsYour own odd processIf your team does it every week and it is slow, it can probably be a screen and a button.
ScheduleHow it works
- Step 1
Call
Free
30 minutes. You tell me what hurts, and I tell you honestly whether software is the answer.
- Step 2
Process review
£750
I sit with your team, map how the work really flows and write up what to build. Credited in full against a build.
- Step 3
Build
Fixed quote
One agreed price before I start. Working software in your team's hands, and you see it working each week.
Typically 2 to 4 weeks.
- Step 4
Support
Monthly
Fixes, small changes, hosting and keeping it running, for a set monthly fee.
Prices are agreed before any work starts. You own what gets built.
Tell me which job your team dreads every week.
Send a line about it and I will reply within a working day to set up a free call. If I can't help, I'll say so on the call.