Process

How the process turns an agreed result into a working system

You agree a clear goal in hours back or revenue before the build starts. Then the work runs in five steps, and you approve each one before the next begins. One team runs every step, so the people who time your task at the start are the people who hand it back working.

The page is for owners and nonprofit leaders weighing a first AI consulting project.

Key takeaways from this page:

  • The result goes in writing first: a baseline, a target, one measure and a review date.
  • The work runs in five steps inside three stages, and you approve each step.
  • People from one team do the work, from the first conversation to the review.

Why does more effort stall when your tools do not connect?

More effort stalls, as Mavrin Labs reads it, when your tools cannot pass work to each other. Adding a new app, a spreadsheet or an extra pair of hands just moves the jam. Each new part needs someone to keep it in step with the others. The hours vanish into the gaps between them.

Picture a small insurance office where staff type each new client into three programs. Hiring one more person only adds a fourth pair of hands to the same copying.

More tools
Each new tool keeps its own copy of the same facts, and someone has to keep every copy correct.
More effort
Work that depends on one person remembering fails the week that person is away.
More reports
A report rebuilt by hand each month tells you what happened, too late to change it.

What is agreed before the build starts?

The result is agreed in writing before the build starts, and that is what sets this apart from a quote for software. The agreement holds four things: a baseline, a target, one measure and a review date, each defined on the page about measurable results.

The agreement comes first. The technology follows from it.

Your risk drops because you agree the result in advance, rather than trusting a promise after the work.

The measurable results page explains each part of that agreement. It covers what happens at the review and what no builder can control.

When is a workflow worth building?

A workflow, meaning a task your staff repeat, is worth building when it comes up every week. It is a stronger case when people retype the same details between tools. It also needs a result you can name in hours or revenue. Those three signs give the Assess step something real to measure.

A workflow is better left alone when it runs a few times a year, changes shape every time, or already works well in one tool. The Assess step says so when that is the case.

Before you hire AI automation agency services at all, check whether a workflow is ready. The guide on how to hire an AI consultant lists the questions to put to any firm. Owners often ask one question first: What does an AI consultant do, and what stays with your staff?

How do the five steps run?

The five steps run inside the three stages of a project. Assess is the workflow assessment, a close look at how the task runs today. Design, Build and Launch make up the build. Support is the care plan, the ongoing care after launch. You approve each step before the next one begins.

The National Institute of Standards and Technology (NIST) also calls for monitoring an AI system after it is deployed (NIST AI framework core, checked Monday, November 16, 2026).

The table below compares the three stages: what you give, what you get and how each one is checked.

How do the five steps run?
Stage What you give What you get How it is checked
Workflow assessment (Assess) Time with the people who do the task, and a look at the tools it touches Timed baselines, the opportunities scored, and a fixed-scope proposal for one build You approve the proposal, or say no
Build (Design, Build, Launch) Approval of the design plan and of the acceptance tests The system on your own tools, tested, with staff training and a handover It passes the acceptance tests you approved first
Care plan (Support) A named person who reads the monthly review Monitoring, fixes, updates when a provider changes something and one improvement a month A monthly review sets the results beside the baseline

Assess and Design produce the written plan and the agreed result. The last three steps carry them out.

You approve what each step produces before the next one starts, so you always know where the work stands. No step carries a promised end date until the plan exists in writing. What happens when priorities change mid-build, and what to bring to a first conversation, are answered on how engagements work.

The five steps in order: Assess, Design, Build, Launch and Support, each filled as it is approved. The arc from Support back to Assess is the hand-back at the review, where the same measure is taken again and the next round starts from what it shows.
  1. Assess, step 1

    You walk the team through the task. The team times it, counts it and writes it down as the starting point. You learn whether the task is worth building at all.

  2. Design, step 2

    You decide which steps the system takes on and which ones a person approves. Using the starting point from Assess, this step produces the written plan. It names what the team will build and the result it should reach. You approve it before any build starts.

  3. Build, step 3

    You give access and real examples from your own week. Mavrin Labs builds on the tools you already have and shows you working parts as they arrive.

  4. Launch, step 4

    You choose when each part goes live. The team trains your staff on what changed and how to step in. The old way stays available until the new one holds.

  5. Support, step 5

    You keep using the system through the agreed period. On the review date, the team measures the same work again and tells you what it found.

Who does the work?

People from Mavrin Labs' own team, in mixed roles and chosen for the work, do the work. The same people stay with your project from the first conversation through to the review. You explain your task once, to the people who will build it. Those same people sit with you when you read the result together.

In practice, no handover loses what the team has learned about your tools, because no handover happens. The page on who builds the systems explains who is on the team.

Where to go next

Two pages carry the detail this overview leaves out. Each one answers the next question owners tend to ask.

  • How a result is agreed

    The page on how a result is written down explains the four parts of the agreement, what counts as a measurable result, and what happens at the review.

  • How engagements work

    The page on scope, the investment and what is excluded covers the business side. It shows how you settle the plan, how the investment follows from it, and what a project does not include.

The first step

Everything on this page comes back to one idea: an agreed result, built step by step, with your approval at each stage. To begin, start a conversation about the one weekly task you would most like back.

Frequently asked questions

Do we have to replace our current systems to work this way?

You do not have to replace your current systems to work this way. Mavrin Labs builds on the tools you already use and connects them. Replacing a tool that works would burn the very hours this work exists to save. If a tool cannot do what a task needs, you hear so in the Design step, and you choose what happens.

Who will we be working with?

You will be working with Mavrin Labs' own people, picked for the task, from the first conversation to the review. The people who look at your task first also design it, build it, launch it and measure it. You never have to explain anything twice. No account manager who has never seen the system stands in the way.

How is success measured at the end of a project?

Mavrin Labs measures success against the starting point recorded in the first step, using the measure you agreed before the build. The team times the task as it runs today. You set a goal in hours back or revenue. On the review date the same reading is taken again, and you can check the comparison yourself.

What do you approve at the end of each step?

At the end of each step you approve what that step delivered. After Assess, it is the starting point the team timed. After Design, it is the written plan and the result it should reach. After Build, it is the working parts. In Launch you choose when each part goes live, and in Support you read the review.

Does the system act without a person checking it?

The system acts on its own only where you say it may. In the Design step you decide which steps the system takes on and which ones a person approves, and that choice goes into the written plan. Anything outside those limits waits for a person, and you can change the limits at the end of any step.

Last updated

Reviewed by Mavrin Labs on

Enquiry form

Start with one workflow

Tell Mavrin Labs what is stuck and which systems it touches. A person at the firm reads every enquiry and replies by email.

Start a conversation

Fields marked with an asterisk are the ones a reply needs.

So a reply can address you properly.

The address the reply goes to.

Optional. Give one only if you would rather talk than write; the reply goes by email either way.

Optional, and useful when it says what the work has to fit around.

The result you want, and when you would want it working. Two or three sentences are plenty.

The task as it actually happens, roughly how often it runs, and which systems it touches. Two links at most, please.

Optional.

What you send goes to the Mavrin Labs inbox and is used to answer you, and a phone number, if you give one, is used for the same thing and nothing else.

A person reads it and replies by email.

If the form does not send, write to info@mavrinlabs.com instead; it reaches the same inbox.

Which hours would you take back first?

Name the one workflow that eats the most of your week. Mavrin Labs reads it, and the reply comes from the people who would build the fix.

Start a conversation