Process

How the plan, the goal and the investment are agreed

You know what the team will build, what it should achieve and the investment before each stage starts. A project with Mavrin Labs begins with one conversation about one task that repeats. You and the team put the goal in writing first, and the investment for each stage is agreed in writing before it begins. The team plans nothing until it has seen the work.

Read this first if you run a small business or a nonprofit and want the AI project scope settled before you commit.

Key takeaways from this page:

  • Three things go in writing before any build: the scope, the result it should reach, and the investment.
  • The workflow assessment is the first paid stage, and it ends in a written proposal for one build.
  • Advertising, and answering your calls or enquiries, sit outside every project.

How does a project start?

A project starts with a first conversation, which the firm also calls the strategy session. You ask for one by sending an enquiry from this site. You bring one task that repeats and annoys someone every week. The team asks how it runs today, how often, who does it and what happens when it goes wrong.

For a cleaning firm, that task might be copying each new booking from email into the calendar. You leave with a clear view of whether a build is worth it, and you commit to nothing. If the hours in that task do not justify a build, the team will say so. That beats a project neither side can defend later. The contact page covers what happens after you send an enquiry.

What gets agreed in writing before a build?

Three things get agreed in writing before any build begins: the scope, the result and the investment. You approve each one, and the team builds nothing until all three are settled. The list below says what each one holds, in plain words, so you know exactly what you are agreeing to.

The scope
A plain list of what the team builds, which tools it touches, which steps a person approves, and what waits until later.
The result
How long the task takes today, the goal in hours back or revenue, how you will measure it, and the date you review it together.
The investment
Agreed with you directly, in writing, for each stage: the workflow assessment first, then the build against its written proposal.

Before you approve a scope, check that it says each of these:

  • What the team builds, in plain words.
  • Which of your tools it touches.
  • Which steps a person approves before anything goes out.
  • What waits until a later stage.

The page on how a result is agreed and checked explains the result agreement in full. It covers what no builder can control and what happens at the review.

Ownership goes in writing too. Under U.S. copyright law, a commissioned work counts as made for hire only in nine listed categories, and only with a written agreement both sides sign (Circular 30 from the U.S. Copyright Office, checked Monday, November 16, 2026). So the agreement states that you own the custom work once it is paid for, and all of your data.

How is the investment set?

The investment is set one stage at a time, and each one goes in writing. The first conversation is about one task. If the first conversation finds a project worth doing, you agree the investment for the workflow assessment, the first paid stage. Its investment is credited in full to a build that begins within thirty days of its report. The assessment ends in a written proposal for one build, and you agree the build's investment against that proposal.

The page on the workflow assessment says what the first stage looks at and what its report contains.

The facts this page states about the firm itself, such as the team and its base in Sarasota, are listed with their basis and the date each was confirmed in the register of evidence behind the site.

Before that first conversation, the questions worth asking any AI firm help you judge the answers you get, from Mavrin Labs or anyone else.

In what order does an engagement run?

An engagement runs in the same order every time. It starts with a first conversation about one task, then moves through three stages: the workflow assessment, the build and the care plan. Each stage closes, with your approval in writing, before the next one opens, so you always know which stage you are in.

  1. First conversation

    One task that repeats; you commit to nothing.

  2. Workflow assessment

    The Assess step, ending in a written proposal you approve or decline.

  3. Build

    Design, Build and Launch, against an agreed design plan and acceptance tests.

  4. Care plan

    The Support step, with monitoring, fixes and improvements.

  5. Review

    The same measure taken again on the agreed date.

What the review shows sets the next step, and the next round starts from there.

The order of a Mavrin Labs engagement: a first conversation, then the three stages, then the review. Outlined squares are where you approve in writing before the next stage opens.
  1. Workflow assessment

    The Assess step, a close look at how your chosen tasks run today. The team times each one as a starting point, shows where time could come back, and hands you a written proposal for the first build. You approve it or say no.

  2. Build

    The Design, Build and Launch steps. First you agree a written design plan, which says how the system will work, and acceptance tests, the checks it must pass before you accept it. The team then builds on your current tools, tests it against those checks and takes it live in stages you choose. The people who will use it get training.

  3. Care plan

    The Support step, the ongoing care after launch. It covers monitoring, fixes and improvements. On the agreed review date the team takes the same measure again, and the next step comes from what it shows.

How a build runs, step by step explains the five steps in detail, with what you provide and what you get at each one.

What does an engagement not include?

An engagement does not include advertising, answering your calls or enquiries for you, or open-ended work with no agreed result. Those sit outside every project on purpose, and it is fairer to say so here than for you to find out later. The table below compares what a project covers with what it leaves out.

What does an engagement not include?
What a project covers What it does not cover
Building and connecting tools your own people run Running ads or buying placement of any kind
Systems that log, route and draft a reply for a person to approve Answering your enquiries or calls for you
The same people through the assessment, the build and the review A handover to someone who has never seen the system
A written scope that says what the first version includes Open-ended work with no agreed result or review date

The right-hand column is there because the firm would rather turn down work that does not suit it. A project nobody can defend at the review helps no one. The page on the team behind the work covers who does what.

Every project rests on three written agreements: the scope, the result and the investment. The team builds nothing until you approve all three. The first step is to start a conversation about one task that repeats every week.

Frequently asked questions

What should we bring to the first conversation?

Bring one repeated task, a rough idea of how often it runs, and the role of whoever does it today. You do not need a detailed brief or a list of tools. The conversation works well as a walk through a real week. The lost hours hide in the handoffs that nobody writes down until someone asks about them.

Who do we work with once an engagement starts?

You work with people from Mavrin Labs' own team, chosen for the work, for the whole project. The people who first look at your task also write the scope and build the system. They launch it and measure the result too. Nobody has to learn your business from scratch halfway through. No account manager sits between you and the people doing the work.

Can we start with one workflow instead of a whole program?

Starting with one workflow, meaning one task that repeats, is the normal way in and usually the wise one. One task gives you a real starting point, a result you can read, and a fair sense of how working together feels. You see all of that before anyone commits further. If it pays off, the plan for the next piece builds on what the first one measured.

What happens if priorities change in the middle of a build?

Priorities that change in the middle of a build wait for the end of the current step. Every step ends with something you can see and approve. That is the right moment to stop, change the order, or rewrite the rest. The team explains what a change affects before anyone acts on it, and puts the new plan in writing.

Does an engagement include advertising or answering our enquiries?

An engagement includes neither advertising nor answering your enquiries, and the written scope says so. The systems Mavrin Labs builds can log an enquiry, send it to the right person and draft a reply. A named person at your business then decides what goes out, so your own staff stay in charge of every reply.

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