Home Work

The systems we build.

Three solution blueprints, described end to end — the problem they solve, how they're put together, and what changes in the business once they're live.

Clients

Who we work with

Consulting
Luxury retail
Home retail

Solution blueprint 01Finance operations

Invoice to ledger, without the re-keying

Challenge
Invoices arrive as email attachments in a dozen different layouts. Someone opens each one, types it into the finance system, matches it against a purchase order, and chases whatever doesn't line up. Volume rises every quarter; the team doesn't.
Approach
Extraction reads the document whatever its layout, rather than depending on a fixed template per supplier. Matching logic reconciles it against the order and the ledger. Confidence is scored on every field, and anything below the threshold stops and waits for a person — with the source document, the extracted values and the reasoning shown side by side.
Integration
Reads from the shared mailbox, writes to the accounting system through its API, and posts exceptions into the channel the finance team already works in. No new tool to log into.
What changes
The finance team moves from processing to reviewing. Month-end stops depending on how much of the backlog someone managed to clear, and supplier queries get answered from a record that's already current.
Document in, reconciled entry out

Arrives as

Invoice Any format
Read & match PO · ledger

Two paths

Posted
Held for review

Confidence is scored on every field. Anything uncertain waits for a person.

Solution blueprint 02Customer operations

An agent that owns the first response

Challenge
Inbound enquiries arrive through three channels and queue overnight. A large share are routine — order status, documentation, a question already answered on the site — but they sit in the same queue as the genuinely complex ones, and everything waits.
Approach
An agent classifies each enquiry, retrieves the relevant record from the CRM and order system, and either resolves it directly or prepares a full handover. It's allowed to answer and to look things up; it is not allowed to issue refunds, change contract terms or make commitments, and it knows to escalate rather than guess.
Integration
Sits in front of the existing support desk rather than replacing it. Every action is logged against the ticket, so an agent can see exactly what was said and done before they picked it up.
What changes
Routine enquiries get answered immediately, at any hour. The complex ones reach a person sooner, with the context already gathered, and the team stops starting every morning behind.
Triage, resolve, escalate

Channels

Email
Web form
Chat
Agent Classify · retrieve

Two paths

Resolved now
To a person

It answers, or it hands over properly. It never guesses.

Solution blueprint 03Commercial reporting

One version of the numbers, every morning

Challenge
Sales, operations and finance each report from their own system. The figures never quite agree, so the weekly meeting starts by arguing about whose spreadsheet is right instead of deciding anything.
Approach
A pipeline pulls from each source on a schedule, applies one agreed definition for the contested measures, and flags records that can't be reconciled rather than silently dropping them. Reporting is built on top of that single view, split into an operational board for the day and an executive board for the quarter.
Integration
Feeds the dashboard tool the business already licenses, and delivers a scheduled summary into email and chat so the numbers reach people who never open a dashboard.
What changes
Meetings start from a shared set of figures. Nobody spends a day assembling a pack that's already stale, and disagreements move from the data to the decision.
Three sources, one agreed view

Separate today

Sales
Operations
Finance
One definition Reconciled daily

Built on top

Operational board
Executive board

Records that cannot be reconciled are flagged, never silently dropped.

Engagement

Three ways projects usually start

You don't have to know which one you need. The first conversation usually settles it.

01

Assessment

A short, fixed-scope piece of work. We look at the process and the systems and come back with what's worth building, what it would take, and what we'd do first. It ends in a recommendation, and you're free to take it elsewhere.

02

Build

A defined solution, designed, engineered, integrated and handed over. Scope and success measures are agreed up front, and you see working software early rather than at the end.

03

Ongoing partner

We stay with the system after launch — tuning it against real usage, extending it where it's earning its place, and picking up the next opportunity when it's ready.

Recognise your process in any of these?

Tell us where the time goes in your business. We'll tell you which of these patterns fits, and what it would take to build it for you.