The workflow assessment, the first stage of every project
The workflow assessment is the first stage of every Mavrin Labs project, and the first paid one. The team studies the tasks you choose, times how long each one takes today and shows where hours could come back. It ends in a written proposal for one build on the tools you already use.
The assessment suits a small business owner or nonprofit leader who has named a task in a first conversation and wants to know, in writing, whether a build is worth it.
This page covers what the assessment looks at, who takes part, what its report holds and how its investment is agreed. The assessment times and scores the tasks you choose and proposes one build; it builds nothing itself.
An assessment is the right step when a task repeats every week and touches more than one tool. It is the wrong step for a task that runs a few times a year, changes shape every time, or already works well in one tool; the first conversation says so before any investment is agreed.
Key takeaways from this page:
- The assessment times the tasks you choose and records them as the starting point.
- It ends in a written, fixed-scope proposal for one build, which you approve or decline.
- Its investment is agreed in writing before it starts, as the investment section below sets out.
What does the workflow assessment look at?
The workflow assessment looks at the tasks you choose, as they run today. The team watches the work with the people who do it, looks at the tools each task touches and times every step. Those times become the starting point, or baseline, that the result of any build is measured against later. Each chance to give hours back is then scored, so the proposal starts with the one that matters most.
-
Watch
The work as it runs today, with the people who do it.
-
Time
Every step, recorded as the baseline.
-
Score
Each chance to give hours back, so the one that matters most comes first.
-
Proposal
A written, fixed-scope proposal for one build on your tools.
-
Your decision
Approve the proposal, or decline it.
The assessment is the Assess step of the five named steps. Design, Build and Launch make up the build that may follow, and Support is the care plan after launch.
Who takes part, and what do you provide?
Two groups take part in the workflow assessment: the people at your organization who do the task, and people from Mavrin Labs' own team. You provide time with the people who do the task and a look at the tools it touches. You do not need a detailed brief or a list of tools before it starts.
Mavrin Labs holds only the access the work needs, and you can remove it at any time. Your data is never used to train AI models, and you own all of it, as the page on how client data is handled sets out.
What does the written report contain?
The written report from the workflow assessment contains the timed baseline for each task you chose, the opportunities scored, and a fixed-scope proposal for one build on your existing tools. The proposal names what the team would build, the result it should reach and how you would check it. You approve it or say no. A sample workflow assessment report on made-up data shows the shape of one.
| Part of the report | What it holds |
|---|---|
| Baseline | How long each chosen task takes today, timed with the people who do it |
| Opportunities | Where hours could come back, each one scored |
| Proposal | One build on your existing tools, with a fixed scope, a target result and how it will be checked |
How is the investment agreed?
The investment for the workflow assessment is agreed in writing before it starts, after a first conversation about one task. That investment is credited in full to a build that begins within thirty days of its report. If you go ahead, you agree the build's investment against the written proposal. The build includes a written design plan, acceptance tests (written cases that say what goes in and what result you will accept), training and a handover.
The page on how each stage and the investment are agreed sets out the whole engagement, and the page on how a result is agreed and checked explains the baseline and the review.
The first step
The first step is an enquiry about one task that repeats every week. A person at Mavrin Labs reads it and replies by email within one business day, and the reply says what a first conversation would cover.
The question this page opened with, whether a build is worth it, gets its answer in writing at the end of the assessment. To begin, start a conversation about that task.
Frequently asked questions
Is the workflow assessment paid?
The workflow assessment is the first paid stage of an engagement. You agree its investment in writing before it starts, once a first conversation has found a task worth a closer look. If you go ahead with the build, the assessment's investment counts toward it, on the terms in the section of this page on how the investment is agreed.
Do you have to go ahead with the build?
You do not have to go ahead with the build. The assessment ends in a written proposal for one build, and you approve it or say no. Each stage closes, with your approval in writing, before the next one opens. If the hours in a task do not justify a build, the report says so.
Who carries out the assessment?
People from Mavrin Labs' own team, chosen for the work, carry out the assessment. The same people write the proposal, build what you approve and sit with you at the review, so nothing you explain is lost between stages. Our founder leads the team and stays accountable for the result.
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.
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