How a project runs

Five stages. You can stop after the first.

You know what you are getting at the end of each one, and nothing is built before you have approved what it is allowed to do.

01

We watch how you work

Typically two to four weeks

We sit with the people doing the job. Not a survey, not a workshop. We map what actually happens, where the time goes, where the errors come from, and where a system would help versus where it would just add another thing to maintain.

What you get: a written plan naming exactly what we would build, what it would cost, and how long it would take.

The Intake Audit. After the first conversation and before any design work, you complete a structured Intake Audit form. It captures how the work actually flows, which documents and systems are involved, who touches what, where the time goes, and what happens when something goes wrong. Your answers are what the system design is built from. Skipping it means designing from assumptions, so we do not skip it.

Worth saying plainly: if we do not find enough here to justify the cost, we will say so. That is a real outcome and it happens.

02

We design it and you approve it

Runs inside stage one

Before anything is built, you see the rules. What it can do. What it cannot do. Who is allowed to use which parts. What happens when it hits a question it should not answer.

What you get: a design document you sign off on. Nothing gets built until you do.

03

We build it and try to break it

Typically four to eight weeks

We build it against your real work, connect it to the systems you already use, and then deliberately try to make it fail. We feed it bad inputs, edge cases, and questions it should refuse. If it fails, we fix it and try again.

What you get: a working, tested, documented system. It does not go live until it passes.

04

We train your people

At launch and again after

Owners and managers on one track. Staff on another. Then written procedures so it survives turnover.

What you get: trained people, written SOPs, and reference materials your firm keeps.

05

You run it, with or without us

Optional, monthly

Some firms keep us on to monitor quality, update the system as their work changes, and review how it is being used. Others take it in-house after training. Both work.

What you get: if you keep us on, a monthly review of how the system is performing and what needs attention.

06

What it costs

How we price it

The price is not a rate card. It comes out of a financial analysis of the specific work we would be building around.

We document what the work costs you today

Hours per cycle, cycles per year, the loaded cost of those hours, and what a delay or an error costs when one happens. That gives a defensible annual figure for what this work is costing your firm right now.

Our fee is 15 percent of the documented savings

Your firm keeps 85 percent. If the analysis does not show savings that justify a build, we tell you and you do not build it. That is a real outcome and it happens. Savings figures are estimates produced by the analysis, not a guarantee of results.

Design is a flat $3,000

That covers the financial analysis, the intake audit, and the complete system design. The design is yours to keep and use whether or not you build with us.

Build typically falls between $5,000 and $50,000

Where you land is set by what the analysis shows you will save and how complex the build is. A single workflow sits toward the lower end. A connected operating system sits toward the upper end.

Read those two figures as a range, not as prices. They are not a floor and not a ceiling. No engagement is quoted from them. Your number comes out of your own savings analysis and can fall outside the range in either direction.

No per-person and no per-use charges

Your bill does not go up because your team used it more than expected, and you never have to ask staff to ration it.

Monthly support is recommended, not binding

We recommend it because a system nobody maintains slowly stops earning what you paid for it. It is not a condition of the build, there is no multi-year lock-in, and you can cancel at any time.

Why it works this way

A number quoted before anyone has looked at your work is a guess, and you would be right not to trust it. Pricing off documented savings means we only get paid more when the thing we built is worth more to you.

The five rules, on every system we build

These are not add-ons and there is no version of our work without them.

01
It reads your files only.
Not the open internet. It is built to keep your firm's and your clients' confidential information out of data mining and public AI training.
02
It shows its sources.
Every answer carries a citation to the document it came from.
03
A person approves everything.
No system we build sends, files, or decides on its own. Your team provides the incremental and final approval on every output.
04
It stops when it is unsure.
You approve the limits before we build. Outside them the system does not guess. It routes the question to the named person at your firm who owns that decision.
05
You keep what we build.
Once the build is paid for, the system, documentation, and training materials stay with your firm for its own use.

Start with one conversation about one workflow.

Pick the piece of work that annoys you most. Twenty minutes. We will tell you whether it is worth doing.

Start here