We'd like to use analytics cookies to see how people use this site. They stay off unless you accept. Privacy policy Cookie policy

HandBuiltBrands

Insights / AI in your business

How we build your AI system, step by step

By Matt Marquart · November 12, 2026

Every build runs in four phases. We map the workflow and put a value on each fix. We make the first fix, as light as it can be. We set the numbers that prove it works and tune it against them. Then you see the benefits.

Four phases, and the first one is the AI Assessment

  1. Map the workflow and assign value. We write down how your operation actually runs and put a value on every possible fix.
  2. Make the first fix. We build the fix at the top of the list: an automation, an agent, or whatever fits the problem.
  3. Design the feedback loop, set the KPIs, and fine-tune. We agree the numbers that prove the fix works and tune it against them.
  4. You see the benefits. It works within a couple of weeks. Running on its own takes a few months more.

Phase 1: Map the workflow and assign value

You can’t fix a process nobody has written down, and you can’t choose a fix without knowing what it’s worth.

What we look at

Four things. The business: how it makes money, where the margin is, and where the bottlenecks are. The people: who makes the decisions and who lives with them. The workflows: what actually happens, next to what the process says should happen. The software and data: what you have, where it lives, and whether it tells you what you need to know.

What we write down for every step

Who or what does it. Which software it runs in. Where someone has to approve before it moves on. And how much of it a machine already does, on a five-level scale: a person does it by hand; a person does it with an AI tool; a machine drafts it and a person approves; a machine acts on its own inside written limits, with every action logged and reversible; or a scheduled job runs it with no judgment involved.

First, should this step exist at all?

Some steps were built for a problem that’s gone. Some exist because nobody stopped doing them. Those get deleted before anyone automates them.

How we assign value

Each possible fix gets scored on four things. How often the step happens. How many hours it takes each time. What it risks: the errors and the stalls. And how ready a fix is, because a fix that already works somewhere else is cheaper and safer to build. Then we put a rough value on each, in the terms your business uses.

What you do

Lead the first conversations. Make time for the people we need to talk to. Give us a look at the software, read-only where that’s possible. Supply the numbers only you know, such as what an hour of a given role costs. Sign the mutual NDA.

What you get

A map of how your operation runs today, and a list of fixes in order of value, including what to delete and what isn’t worth building.

This phase is the AI Assessment.

Phase 2: Make the first fix, as light as it can be

It’s better to delete a step and add it back later than to bolt on a system you didn’t need.

The lightest thing that works

We start with the simplest fix that could solve the problem. Every system you add is one more thing your team has to run, pay for and keep working, so we add one only when nothing lighter will do. Often the first fix is removing a step.

What a fix can be

Whatever fits the problem. An automation that moves work from one step to the next without anyone retyping it. A connection between two systems you already run, so they stop disagreeing. An agent that does one defined job, such as turning every meeting into notes with an owner on each action item, or answering the routine requests that land on your operations team and sending the rest to a person.

The rules every fix follows

Every fix gets a written job. It gets written limits, agreed with you before it starts: what it handles alone, and what always goes to a person. Every action it takes is logged. Anything that reaches a customer, or can’t be undone, waits for a person. That’s how we run the agents in our own business.

Built around what you already run

We build around your workflows, your software and the words your team uses. If your team says work order, so does the fix.

Getting your team to use it

A tool your team won’t use is an expense. Every fix includes the change to how people work, and we train the people who will use it inside their real work.

What you do

Name an owner on your side. Approve the fix before it goes live. Use it, and tell us where it’s wrong.

What you get

A first fix working inside your business.

Phase 3: Design the feedback loop, set the KPIs, and fine-tune

A fix you can’t measure is a guess.

Set the numbers first

We agree with you on the few numbers that show the fix is doing its job: hours saved, requests answered, errors caught, or whatever the value in phase 1 was based on. We record where they stand before the fix goes live, so there’s a before to compare against.

Build the loop

We set up how those numbers come back to us and to you, so nobody has to go looking for them.

Tune against real work

Plans meet real work and change. We test the fix against how the business actually runs and adjust it until the numbers move the way they should. Sometimes the business teaches us something and the target itself changes.

Go back to the map when you need to

When the numbers show something a tune won’t fix, we go back to phase 1. What looked like a workflow problem often turns out to be a data problem once the numbers are clean.

What you do

Agree the KPIs. Read the results with us.

What you get

KPIs you can see, and a fix that keeps getting better against them.

Phase 4: You see the benefits

Fast to work, slower to run on its own.

Within a couple of weeks

The fix works. The routine work it was built for starts coming off people’s desks.

Over the next few months

We keep tuning until it runs on its own. That takes at least a couple of months, usually about six, depending on the problem.

Then the next fix

We go back to the list from phase 1 and take the next one, with better numbers than we had the first time.

What owners ask about how a build runs

Who on our side has to be involved?

The owner, or whoever can say yes to what we find, for the first conversations. Then the people who do the work we’re mapping. Then one owner on your side for each fix.

Do we have to change our software?

No. We build around what you already run, and we’d rather remove a step than add a system. If the map shows a system is the problem, it says so, and the call is yours.

What if the best fix is no software at all?

Then that’s the fix. Deleting a step or changing who does it often pays more than anything we could build.

How long until it works?

A couple of weeks. Running on its own takes at least a couple of months, usually about six.

Do you work on our marketing too?

That’s a separate offering. If the map shows growth is where the business is falling short, we’ll say so.

Start with the step that costs you the most

Tell us where the hours go and what you’d fix first if you could. We’ll tell you whether an Assessment is the right next step. See how the AI Assessment works, or read what we built for our own business.

Questions about your own situation? Request a call with Matt.