This page is the map. What each of the six actually is, which one we would put you on first, and the four things that hold whichever one you choose — ownership, your data, how scope is arrived at, and your right to be told not to go ahead.
No obligation · 30 minutes · no pitch. You talk to the people who would do the work — and you leave with the one task we would automate first, whether or not you work with us.
What you are actually getting
Each one is either software we build, or time in the room with your team.
The label on every card below tells you which, and it changes what you end up holding: a thing that runs when nobody is watching, or a decision you can act on and people who can act on it.Four of the six end with software running on your systems; two end with a person's work.
Software we build · four of the six
It runs every day without you
Agents, applications, data pipelines, rewired workflows. It is built inside the tools you already run, it works while nobody is looking, and it stops the moment a person is needed. What you own at the end is the software, its source and its accounts.
Your processes mapped in the room rather than from a questionnaire; your team trained on their own real work. What you own at the end is a written plan you could act on without us, and people who no longer need to be told what the tool is for.
03 strategy & roadmap · 06 enablement
The six
What each one is, in one paragraph.
No tiers, no bundles, nothing that only makes sense with something else attached. Each one is scoped, agreed and signed on its own — and each one names the part a person keeps.
01Software we buildStart here
AI agents & automation
the tireless teammate
Agents that pick up the repeating work — the tickets, the chasing, the copying between systems — and pass every judgement call to your team. They triage, draft, follow up and file inside the tools your people already use. We recommend starting here because it works on tasks your team already repeats daily, so there is something running before anyone has to believe a forecast.
A human keeps: anything involving financial records, a contract or a relationship. The agent stops there and asks.
The screens your people and your customers actually open, built to fit the way the work already moves. Web, mobile and AI applications specified, designed, built and launched end to end, connected to the systems your business already runs on — and handed over with the source code in your name.
A human keeps: the sign-off. Nothing goes in front of a customer until a named person on your side releases it.
Where AI belongs in your business, in what order, and what it would take to get there — in plain language, from your real processes rather than a questionnaire. You keep the map, the recommendation and the written list of things we think you should not do. When the honest answer is “not yet”, you get that in writing too.
A human keeps: the decision to go ahead — including the decision not to.
Your scattered data made readable, so the agents — and the people reviewing them — work from the same version of the truth. One source that agrees with itself, definitions written down once so reports stop contradicting each other, dashboards built around a decision, and the early warnings your data was already holding.
A human keeps: the reading. We show what moved; what it means for your business is your call.
Rewiring the workflow itself, instead of bolting AI onto a process that was already taking longer than it should. Paper and spreadsheet workarounds become connected digital steps — one stage live and settled before the next one starts, your team trained as each lands, and the old way kept available while people adjust.
A human keeps: the pace. We move to the next stage when you say you're ready — not before.
Training your team to run the floor without us: how to brief an agent, how to check its work, and how to know when to overrule it. Hands-on, on your real tasks rather than demo examples, with a short written policy for safe use — what to paste and what never to — and internal champions coached by name.
A human keeps: the expertise. Your people stay the ones who know the business — the tool never outranks them.
We expect most businesses need one of these, not six. We'll tell you which one — and if none of them fit your business, we'll tell you that too.Find out which one
Whichever one you choose
Four things that hold across all six.
These do not change with the service, so they are written here once instead of on every page. They are contract terms, not slogans — the wording below is the wording that goes in.
Every engagement · every servicein the contract
Ownership
You own it, not us
The code, the prompts, the accounts, the documentation — handed over to keep, not lent back, in your name, on standard tools any developer could pick up.
Your data
It never trains a model
What any system may see and store is agreed in writing before it is connected to anything. An NDA comes back signed before you send us a document or a login.
Scope
One scope, agreed before it starts
Nothing begins before it is written down and you have said yes to it. What makes a job bigger or smaller is scope, integrations and how ready your data is — all of it settled in a short written proposal after the call.
The no
We will tell you not to go ahead
When a simpler fix beats AI, we say so. When none of the six fit, we say that too — and you keep whatever we have already handed over.
Any industry · any size
All six are open to every industry, and to companies of every size.
There is no minimum and no ceiling. The only thing that decides whether we can help is whether work is being done by hand that shouldn’t be — which is as true of one person as of ten thousand. The work that wastes a week has the same shape in every trade, and the five phases below are about finding the first task worth automating, not about headcount. What changes with size is scope, not process.
Healthcare
Finance
Government
Retail
Logistics
Insurance
Education
Manufacturing
Legal
Real estate
Hospitality
Non-profit
Startups
and any trade not on this line
How an engagement runs
Five phases. Every service, every time.
The order never changes; only what happens inside each phase does. Nothing touches live work before the phase in front of it is finished — and you can stop after any one of them and keep what you have.
PHASE ONE
Listen
A 30-minute conversation, then we sit with your team and watch the real week — what actually eats the hours, not what the process document claims.
PHASE TWO
Map
We draw the floor: every task, who touches it, and where the routine ends and the judgement begins — then say plainly which lane makes the biggest difference first.
PHASE THREE
Build
One job first, inside the tools you already use, with its limits written down and its escalation rule agreed before anything goes near live work.
PHASE FOUR
Prove
It runs beside your people, in the open, on your real work — until what it produces is work you would have signed off yourself.
PHASE FIVE
Hand over
Keys, code, prompts and documentation are yours. We stay close — but we stay on only if you want us on.
No lock-in by design — every phase ends at a door you can walk out of.
Questions
Before you pick one, four answers.
These are the questions that decide which of the six you open next — settled here, in writing, so a first conversation can start further along than the brochure.
Q01Which one should we start with?
Agents and automation, unless one of two things is true. It works on tasks your team already does every day, so something is running and checkable early — you are not asked to believe a forecast.
Two cases where we'd start elsewhere. If nobody can yet say which task matters, start with strategy: a short piece of work that ends with a written recommendation you could act on without us. If your systems disagree about the same number, start with data & insight — an agent built on numbers nobody trusts inherits the mistrust.
Q02Can we take on more than one — or all six?
You can, and we would rather you did not start that way. Everything at once means everything half-proven and nothing running.
We would rather scope one service, then a second one the first makes obvious — the agent shows you which screens people are missing, or the map shows you the workflow has to change before anything can be automated. Nothing is bundled and nothing is a package: each one is scoped, agreed and signed on its own.
Q03Who actually does the work?
The people who would build it. Whoever answers your first email is on the team that sits with your people, maps the work, writes the code, and is still there when it needs changing. There is no account manager between you and the build.
That is also the honest limit, and the reason it is worth saying out loud: the people who scope the work are the ones who have to build it, which is what keeps the scope truthful. The work runs on your accounts rather than ours, and the code is written to be read by whoever comes next.
Q04What if none of the six fit?
We say so, in writing, and you are committed to nothing further. That is not generosity — a project that should not exist does far more damage abandoned later than declined now.
If a product off the shelf does the job, we will name it. If the real fix is a written procedure rather than software, we will say that too. You keep the map either way.
Thirty minutes · zero pitch
You don't have to pick one before you speak to us.
Thirty minutes with us. We look at your week, name the one thing worth doing first, and tell you plainly if AI isn't the fit.