Weeks 1 to 2
Diagnose
Map the workflow, capture a baseline, pick one measure and agree the first build. Same rhythm as the Start diagnostic.
Approach
Diagnose, ship, then run and teach
We start with context, not code. You stay in control of what leaves your firm. We report progress every week.
Three stages
Fixed cadence. You always know which stage you are in and what happens next.
Weeks 3 to 6
Ship
Build the first workflow, often on Mashroo Desk, in draft mode first. Named approvers review anything external.
Week 7 onward
Run and teach
We operate, tune and hand skills to your team. Metrics stay visible. You decide what expands next.
Principles
Context before code
We read how work runs today before we propose tools or automations.
Ask before we build
We confirm scope, approvers and success checks with your sponsor in plain language.
People approve
AI drafts. Your named approvers send. Nothing client-facing goes out without them.
Measured every week
We track the measure you chose and review it with you on a fixed cadence.
Safety and control
Human approval
External messages and client updates wait for a named approver on your side.
Audit trail
Drafts, edits, approvals and sends are logged with time and user.
Your data, your rules
Access is limited to people on your account. We follow your instructions on retention and deletion.
No training on your data
We do not use your client data to train general models.
Disconnect when you ask
We revoke integrations and confirm what was removed.
See the Desk on sample data
The Desk demo uses fictional companies only. Charts and dashboards are labelled sample data.