Custom internal tools
When the process doesn’t fit one system, we build the layer it runs on.
Henswick builds the operational layer your team actually works in: role-based views, shared status, approvals and exceptions, sitting on top of the systems you already run.
Requester
Procurement coordinator
Submitted. Checks are running.
With the approver. Nothing else is needed from you.
Approved. Being applied to the supplier record.
Applied. The supplier record is updated.
What you provided
Approver
Finance controller
Waiting for the checks to finish.
Your decision is needed.
Approved by you. Reason recorded.
Applied to the supplier record.
Operations lead
Owns the queue
Open supplier changes
Nothing is applied until the approver decides.
Where it breaks
The same request, in four places.
A supplier asks to change its bank details. The request lands in an inbox, gets copied into a spreadsheet, is queried in chat and tracked in a ticket. Nobody can say who has it now, or who approved what.
Inbox
Re: Updated bank details
Please use our new account from next month. Letter attached.
Who has this now?Spreadsheet
Team chat
Has anyone called Alderwick back?
Not sure. I thought Sam did.
Was it checked?Ticket
Change supplier bank details
Waiting · no assignee Who approved it?Each place holds a piece. None of them holds the case.
The layer
One case, one set of rules, and clear ownership at every state.
Henswick writes the process down as states, roles and rules. It shows who can move a case, where it can go next and where a person has to decide.
Requester
Supplier, new details and the supporting letter.
Next: 2Rules
Format checks, a call-back record and differences flagged. Routed by rule.
Next: 3, or hold (B)Operations
Something is missing. An owner is assigned and the case waits.
Back to 2 once resolvedApprover
Old and new side by side. The approver approves, sends back or escalates.
Approve: 4 · Send back: A · Escalate: CRequester
Returns to the requester with the reason. Nothing is applied.
Back to 1Operations
A second approver is asked, then it returns to the decision.
Back to 3Rules
Written to the supplier record only after approval.
Next: 5Operations
Who decided, why and when stays attached to the case.
Visible to OperationsOnly the approver role can approve. Operations can hold and reassign, but not approve. The requester cannot approve their own request.
What gets built
Four places your team meets the same rules.
Not four app types. Each surface is built around a real operational problem, a role and a decision, and each sits on top of systems you already run.
Request intake
IllustrativeRequests arrive complete, or they don’t leave the form.
The requester sees where a request will go before sending it, and what is still missing.
New starter equipment request
A needed-by date is required before this can be routed.
Where it will go
A preview until the form is complete.
Decided by the line manager, then Finance.
Exception workspace
IllustrativeExceptions land with their context and an owner.
Each held item shows why it stopped, what to check and who has it. Releasing one needs a reason.
Invoice differs from purchase order
The invoiced quantity is higher than the order. Check the delivery note before paying.
Decided by the buyer or the approver, with the reason recorded.
Cross-system record
IllustrativeOne view of the customer, without copying the data.
The view reads from each system and labels every field with its source. Where a field can be changed here, the change is written back to that system.
Marlowe Dental Group
Account owner and stage
R. Nasser · Renewal discussion
Invoices
One overdue
Support
One case open, waiting on the customer
Decided by the account manager.
Operations console
IllustrativeThe queue, the owners, and what is blocked and why.
Operations sees work by owner and by state. Summaries go to the places the team already looks.
Needs an owner
New starter equipment
Operations
Supplier query
Finance
In progress
Contract renewal check
Legal review pending
Month-end handoff
Finance to Operations
Blocked
Supplier change
Waiting for a second approver
Access request
Missing manager sign-off
Operations reassigns and holds. Approvals stay with approvers.
What your team receives
A working tool your team owns, with the rules in plain sight.
Not a black box. Your team gets the tool, the rules it runs on and a record of every decision, all sitting on top of systems that stay yours.
The working tool
A workspace for each role
Each person sees the cases and actions their role allows.
The rules, readable
Supplier bank-detail change
Process owner: Finance operations lead
Changes to these rules need approval.
Permissions and record
Who can do what, and what was done
Audit trail
Your ERP, CRM and finance systems stay the systems of record. The layer reads from them and writes back only what the rules allow.
Show us the process your team runs on spreadsheets.
We start with three questions: who touches it, where it gets stuck, and what must never happen without approval.
A simple, single-screen helper may fit a ready-made tool. Anything with several systems, rules, roles or approvals is custom workflow territory.