SOLUTIONS
Seven kinds of system we build most often, described by what they change rather than what they are made of.
SYSTEM OUTCOMES
Select an architecture below to inspect target outcomes, domain fit, and what we build.
The commercial layer of a software product — tenancy, subscriptions, roles, and self-service onboarding — built once, before the first ten customers make it permanent.
For a company that has proven demand for something it currently delivers as a service, and now needs to sell it as a product — where the first paying customer is real, the second one wants their own login, and nobody has yet decided what happens when the third asks for single sign-on.
Approval and case-handling processes moved out of inboxes into a system with states, owners, deadlines, and a record of every decision that was made.
For operations teams running approvals through email threads and a shared spreadsheet, where nobody can answer "who approved this and when?" without asking three people, and where the person who knows the exceptions is the reason the process works at all.
Automating the high-volume judgment tasks that rules alone cannot handle, with confidence thresholds, human review on the uncertain cases, and a full record of each decision.
For a team where several people spend a large part of the week reading documents, emails, or tickets and making the same category of small decision — routing, classifying, extracting, summarising — and where the decision itself is not hard, but there are several hundred of them a day.
A customer-facing account area that exposes status, documents, and self-service actions directly from your existing systems, reducing the questions that reach a person.
For a business whose support inbox is mostly the same six questions — where is my order, can I have a copy of that invoice, how do I change this detail, what is the status — asked by customers who would happily answer them for themselves if there were somewhere to look.
A reporting layer with defined metrics, traceable lineage, and refresh you can rely on, so the meeting argues about the decision rather than about whose number is right.
For a management team where two departments arrive at a meeting with different figures for the same month, both defensible, both produced by a spreadsheet somebody maintains personally — and where the first twenty minutes goes on reconciling rather than deciding.
Replacing a system that cannot be switched off, one component at a time, behind a boundary that lets every step be reversed.
For a business whose core system still works, still makes money, and costs more every year to keep alive — where a rewrite has been proposed twice and cancelled twice, and where the strongest argument against doing anything is that nobody is certain what would break.
Turning the spreadsheets and shared documents that run real operations into applications with proper data, permissions, and history, without losing what made them work.
For a team where something genuinely important — scheduling, stock, pricing, compliance tracking — runs on a workbook with fourteen tabs and a macro, maintained by one person, where the file is emailed around and everybody knows which copy is the real one only by asking.
Solution 01
SOLUTION · SAAS
A product you can sell, with billing, tenancy, and access control already solved.
For a company that has proven demand for something it currently delivers as a service, and now needs to sell it as a product — where the first paying customer is real, the second one wants their own login, and nobody has yet decided what happens when the third asks for single sign-on.
Solution 02
SOLUTION · OPERATIONS
Approvals that currently live in email, running as a system that can be audited.
For operations teams running approvals through email threads and a shared spreadsheet, where nobody can answer "who approved this and when?" without asking three people, and where the person who knows the exceptions is the reason the process works at all.
Solution 03
SOLUTION · AUTOMATION
The repetitive judgment work handled, with a record of why each decision was made.
For a team where several people spend a large part of the week reading documents, emails, or tickets and making the same category of small decision — routing, classifying, extracting, summarising — and where the decision itself is not hard, but there are several hundred of them a day.
Solution 04
SOLUTION · CUSTOMER
Customers self-serving the things your team currently answers by hand.
For a business whose support inbox is mostly the same six questions — where is my order, can I have a copy of that invoice, how do I change this detail, what is the status — asked by customers who would happily answer them for themselves if there were somewhere to look.
Solution 05
SOLUTION · DATA
One version of the numbers, available to everyone who needs them.
For a management team where two departments arrive at a meeting with different figures for the same month, both defensible, both produced by a spreadsheet somebody maintains personally — and where the first twenty minutes goes on reconciling rather than deciding.
Solution 06
SOLUTION · MODERNIZATION
The old system replaced in slices, while it keeps running.
For a business whose core system still works, still makes money, and costs more every year to keep alive — where a rewrite has been proposed twice and cancelled twice, and where the strongest argument against doing anything is that nobody is certain what would break.
Solution 07
SOLUTION · INTERNAL
The spreadsheet that runs a critical process, turned into software that can be maintained.
For a team where something genuinely important — scheduling, stock, pricing, compliance tracking — runs on a workbook with fourteen tabs and a macro, maintained by one person, where the file is emailed around and everybody knows which copy is the real one only by asking.
Tell us what you're working on. We'll tell you honestly whether we're the right team for it.
