Process
Scope first. Test before trust. Hand over properly.
Every engagement follows the same six steps, whether it is a workspace setup or a single workflow. Three of them end with a decision that belongs to you.
Assess
A first conversation about fit and one candidate team or workflow.
We look at the repetitive work, the tools and plans you already have, and who would own the result. The outcome is a recommendation — including “not yet” when that is the honest answer.
- You provide
- A short description of the repetitive work and the tools involved
- You receive
- A recommendation: workspace, workflow, both in sequence, or not yet
Scope
A written scope with tasks, sources, applications, caps, exclusions and price.
Everything that defines the fixed price is written down: the three uses or the one workflow, the sources, the users, what is excluded and what would count as new scope.
Decision point: You approve the scope
- You provide
- Answers about plans, permissions, volume and exceptions
- You receive
- A written scope with caps, exclusions and a fixed price
Configure or build
Set up in accounts your company owns, with named users and limited permissions.
No shared passwords and no consultant-owned accounts. We organize approved material, write instructions, or build the workflow with duplicate prevention, alerts and a pause switch.
- You provide
- Account access via named users; the approved documents or process details
- You receive
- A configured workspace or a built workflow in your own accounts
Test
Representative cases, including missing, conflicting and out-of-scope information.
For a workspace, around twenty real examples form the acceptance exercise. For a workflow, test runs cover the normal path and each exception. You see the results before anyone relies on it.
Decision point: You review the test results
- You provide
- Real examples, including awkward ones; time to review results
- You receive
- Test results: what passed, what did not, and what was changed
Train and hand over
Training sessions, a recorded walkthrough, a short guide and named ownership.
Your team learns the agreed tasks; one person becomes the owner of the reference material or workflow. The handover documents how to update, pause and check it.
Decision point: Handover accepted
- You provide
- The people to be trained, and one owner
- You receive
- Training, a recording, a short guide and a handover document
Optional care
Bounded monthly support if you want it. Never required.
A small monthly allowance for adjustments and checks on what we delivered. New uses, new workflows and rebuilds are scoped separately.
- You provide
- A decision, if and when you want it
- You receive
- A bounded monthly allowance — or nothing further, by your choice
—Principles
What stays the same in every engagement.
- Your accounts. Everything is built in subscriptions your company owns, with named users and no shared passwords.
- Written scope. The caps, exclusions and price are agreed before work begins. Larger or unusual work is assessed separately — or declined.
- People decide. Consequential or ambiguous situations go to a named person. Missing information is flagged, not guessed.
- No dependency. The handover gives your team what it needs to update, pause and check the setup without us. Care is optional.
Next step
Start with one conversation about one piece of work.
An Automation Assessment is a first conversation about fit: what your team does repeatedly, which tool you already use, and whether a workspace setup or a single workflow is the sensible first step. If neither fits, we will say so.