How approaches differ
Not all automation advisory work starts from the same place
The approach taken at the start of an engagement determines much of what follows. This page lays out what the common approaches involve and where they differ from how Yorozu works.
Back to homeWhy this comparison matters
The framing shapes the findings
When an organisation engages an advisor on automation, the way that advisor starts the work tends to determine what they find. A vendor-affiliated consultant begins by knowing which tools they can sell. A generalist consultant begins by mapping processes at a high level. Both produce recommendations — but those recommendations are shaped by where they began.
Yorozu begins by observing what your people actually do, task by task, with time and frequency figures collected directly. Only after that observation is complete do we consider which approaches, if any, would genuinely affect the work.
What follows is a comparison of these starting positions. It is not a criticism of any particular provider — most operate in good faith within the logic of their model. It is an account of how different starting positions produce different outputs, and why that matters for your organisation.
Side by side
Vendor-led advisory vs. observation-first advisory
Vendor-led / product-first approach
Starting point: the tool
The engagement begins with a product suite or platform. The assessment then identifies which parts of your work fit it.
Assessment methodology: high-level mapping
Process mapping tends to happen at a departmental or workflow level rather than task by task. Detail that would reveal misfit tends not to appear.
Scope of recommendation: broad automation
The output tends toward a recommendation to automate as much as the platform can handle. Narrower conclusions are structurally disincentivised.
Risk assessment: tool-centric
Risks that fall outside the vendor's platform tend to receive less attention. Tasks where automation would introduce fragility are often not flagged.
Contract terms: vendor-standard
Data ownership and exit provisions reflect the vendor's interests. These terms are rarely surfaced prominently during the sales process.
Yorozu — observation-first approach
Starting point: the actual tasks
The engagement begins with direct observation of recurring tasks in your departments. No tool is assumed at the outset.
Assessment methodology: task-level census
Each recurring task is recorded individually — its frequency, duration, variability, and the judgment it requires. This granularity is what makes the output proportionate rather than promotional.
Scope of recommendation: proportionate
The output distinguishes clearly between tasks suited to automation, tasks partly suited, and tasks where a person is the more reliable option. We include all three.
Risk assessment: task-specific
Risk analysis is conducted at the task level. Tasks where automation would introduce more fragility than it removes are explicitly noted and excluded from recommendations.
Contract terms: reviewed for your interests
In vendor selection engagements, we surface data ownership and exit provisions as standard review items — before you sign, not after.
What distinguishes this approach
The methodology behind the difference
The task census as a starting artefact
Most assessments produce a process diagram. We produce a task register — a row for each recurring task, with frequency, duration, variability and judgment figures. That register is what makes proportionate comparison possible. It is also something you keep and can use independently of any future engagement.
No commercial alignment with vendors
We receive no fees, referral payments, or platform commissions from tool providers. This is not a claim most advisory firms can make. Our revenue comes from the client engagements themselves, which means our conclusions are not shaped by what a provider needs us to find.
Manual override retained throughout
When we implement scheduling or other automated systems, the responsible person retains the ability to intervene at any point. Systems that remove human judgment from the loop are, in our view, not ready to operate without supervision — and we do not build them that way.
Parallel running before cutover
For implementation engagements, we include a parallel period where automated and manual processes run alongside each other. Differences are reviewed before any transition is finalised. This reduces the risk of problems that only become visible once the old process is gone.
Effectiveness
What different approaches tend to produce
Assessment accuracy
High-level process mapping tends to overestimate the proportion of tasks suited to automation, because task-level variability is not visible at that scale. Task-by-task observation surfaces constraints that process diagrams do not.
Figures reflect typical ranges observed across comparable engagements.
Implementation stability
Systems built without a parallel running period typically encounter issues during the transition that were not anticipated during design. The parallel period adds time to the engagement but reduces the frequency and severity of post-implementation problems.
Based on patterns observed across scheduling and back-office deployments.
Vendor contract risk
Data ownership clauses and exit provisions in vendor contracts vary significantly. Engagements that include structured contract review before signing surface terms that may otherwise only become visible when an organisation wants to change provider.
Proportion of engagements where problematic terms were identified before signing.
Investment perspective
What the comparison looks like in practice
Short-term cost view
Vendor-led advisory engagement
Often subsidisedInitial advisory cost may be low or absorbed into the software contract. The full cost becomes visible only once the platform is deployed and subscription fees begin.
Task Review (Yorozu)
¥30,000A fixed engagement cost that produces a task register you own, whether or not you proceed to implementation. The cost of the review is not recovered through a software sale.
Vendor Selection Advisory (Yorozu)
¥34,000Five weeks of structured evaluation using your own material, ending with a written matrix and notes on what each provider answered indirectly.
Long-term cost view
Avoiding over-automation
Tasks automated beyond their actual suitability produce recurring errors that require manual correction. The cost of those corrections is rarely visible in initial ROI projections.
Vendor lock-in and exit costs
Contracts that do not address data portability clearly can make switching providers significantly more costly than anticipated. This is why contract review before signing is part of our advisory work.
The value of not proceeding
If a task review concludes that automation would not materially benefit a department, that is a useful finding — and one a vendor-aligned advisor has no incentive to reach. The ¥30,000 cost of a review can prevent a much larger commitment that would not deliver its projected return.
Working experience
What the engagement actually looks like from your side
Typical vendor-led engagement
-
01
Initial demo of the platform, with examples from other industries used to illustrate potential.
-
02
Discovery workshops identify which parts of your work the platform could handle. The output is a fit assessment written around the platform's capabilities.
-
03
Proposal for implementation is produced. Timeline and cost reflect the platform's standard deployment model.
-
04
Implementation proceeds. Gap between projected and actual performance becomes visible post-deployment.
Yorozu engagement
-
01
Initial conversation about your departments, current processes, and what you are hoping to understand. No commitment follows.
-
02
Four weeks of observation alongside your teams — not in a separate room with a questionnaire. Task register built from what is actually seen and timed.
-
03
Findings presented with three categories: suited, partly suited, and not suited. You receive the register whether or not you proceed.
-
04
If implementation or vendor selection follows, it is built around the findings — not around a pre-selected platform. Manual override is retained throughout.
Over time
How results hold up beyond the initial deployment
Artefacts you retain
The task register produced during a review engagement is yours to keep. It can be used in future vendor conversations, internal planning, or subsequent reviews — independently of any ongoing relationship with Yorozu.
Systems that can be maintained
Scheduling systems built around documented constraints — contractual hours, skill coverage requirements, override logic — are maintainable by your own team. We document what we build so the knowledge does not leave with us.
Vendor flexibility
Organisations that enter vendor contracts with a clear evaluation matrix and reviewed exit provisions are better placed to change provider when their needs shift. Avoiding lock-in is a long-term consideration that is easier to address before signing than after.
Common questions
Things worth clarifying before engaging any advisor
"All automation consultants do essentially the same thing."
The methodology used at the assessment stage determines the shape of what follows. A high-level process map, a vendor fit analysis, and a task-level census produce different findings from the same starting material. The starting point is worth asking about before agreeing to an engagement.
"An advisor with a vendor relationship will still give neutral advice."
Advisors with commercial relationships to vendors are subject to structural incentives that are difficult to neutralise through individual intent. This is not a question of honesty — it is a question of how incentive structures shape conclusions. Asking whether an advisor receives fees from vendors is reasonable due diligence.
"Automation is always the right direction for back-office work."
Across the engagements we have observed, a significant proportion of back-office tasks are more reliably handled by a person than by an automated system. Tasks with high variability, tasks that require contextual judgment, and tasks where errors have downstream consequences beyond the immediate process are candidates for keeping with a person. A proportion tool does not assume the answer before looking at the work.
"A longer engagement means more value."
Our task review engagements run for four weeks. That is long enough to observe recurring tasks across their actual frequency cycles and short enough not to impose unnecessary cost. The value is in what the observation produces — a usable register — not in the length of time spent on-site.
Summary
Why some organisations choose this approach
For organisations that want to understand their own work before committing to a tool or a vendor, an observation-first assessment produces findings that are grounded in what actually happens rather than what a platform is able to support.
For organisations evaluating vendors, independent advisory that carries no commercial alignment with any provider produces an evaluation matrix that reflects your requirements rather than a preferred outcome.
This approach is not for every situation. If your organisation has already completed a thorough internal process review and simply needs implementation support, a vendor-aligned partner who specialises in a particular platform may be a more efficient choice.
Where we are most useful is at the stage before that decision is made — when the question of what automation could actually affect in your specific work is still open.
Next step
If you are at the stage of deciding whether and how to engage with automation advisory, a conversation is a reasonable place to start
There is no commitment involved in reaching out. We can talk through your situation and, if there is a fit, explain what an engagement would involve and what it would produce.
Get in touch