Our work
Three engagements, described start to finish
Each one below follows the same shape: what the business was dealing with, what we actually built, and what changed once it was running. No jargon, and no numbers we cannot stand behind.
These are representative engagement scopes rather than accounts of named clients. Client names and commercial figures stay confidential unless a client has agreed in writing to be referenced.
Technology company · 4 weeks
Collections reporting, from six spreadsheets to one dashboard
The problem
Each branch sent a weekly collection file. Consolidation took a full day and the totals rarely matched the ledger, so the weekly figure was always argued over before it could be used.
What we built
One combined view of product, subscription, support, and delivery data, a dashboard that refreshes every morning, and a short list of records that need a person to check them.
The result
Consolidation effort removed, and overdue items visible the next morning instead of the following week. The weekly argument about whose number was right stopped.
Distribution business · 5 weeks
Supplier invoices read and routed automatically
The problem
Two staff keyed supplier invoices into the accounting system by hand, and approvals were chased over email. Nobody could say quickly where a given invoice had stalled.
What we built
Software that reads each invoice, checks it against the purchase order, and sends it to the right person to approve, with a record of who approved what and when.
The result
Manual keying limited to exceptions, with a reviewer confirming anything above the agreed threshold. The two staff moved to work that needed their judgement.
Software firm · 3 weeks
Revenue and cloud cost in one view
The problem
Billing sat in one tool and cloud spend in another, so nobody could say which customers were unprofitable. Pricing decisions were being made on instinct.
What we built
Billing, usage, and cloud cost brought together in one view, showing the margin on each customer and how recurring revenue moved month to month.
The result
Pricing conversations grounded in cost to serve, with the loss-making accounts named rather than suspected.
Is yours one of these, or something else entirely?
You do not need a specification to start. Describe what is slow, manual, or unreliable, and we will tell you whether it is worth fixing and roughly what it would take.