Service 03 — Vendor Selection Advisory
When competing providers are sending proposals and your organisation is not well placed to evaluate them against each other, outside support can be useful. This service provides that support: requirement definition, structured evaluation, trials against your own material, and a review of contract terms — without any commercial relationship with any vendor under consideration.
What this delivers
After five weeks, your organisation will have a structured evaluation matrix comparing the vendors under consideration against requirements that you defined and agreed — not requirements shaped by what any provider chose to emphasise in their proposal.
The evaluation includes notes on the questions each provider answered indirectly or not at all, because those gaps are often as informative as the answers that were given. It also covers contract terms — data ownership, exit provisions, and pricing structures that may not be prominent in the initial materials.
The output is a document. The decision remains yours. We do not make a recommendation in the sense of selecting a vendor for you — we give you the structure and information to make that decision more clearly.
What you can expect
Requirements defined before evaluation begins
Your actual requirements — not a generic feature checklist — documented and agreed before any vendor is assessed. This is what makes the evaluation comparable across providers.
Trials using your own material
Where trials are possible, they run against your organisation's actual data and use cases — not the demo scenarios vendors use to show their tools at their best.
Notes on indirect answers
A specific record of which questions each vendor answered indirectly, partially, or not at all during the evaluation process — often a more useful signal than the answers that were given clearly.
Contract term review
A plain-language summary of data ownership provisions, exit conditions, pricing change mechanisms, and other contract terms that affect your organisation's position after signing.
Why vendor selection is difficult to do well
01
Vendors structure proposals around their strengths — which means the features that matter most to your organisation may not appear prominently in any of the materials you receive. Comparing three proposals that use different frameworks produces a picture that is hard to act on.
02
Product demonstrations use scenarios selected to show the tool working well. The scenarios your organisation would actually use the tool for — including the edge cases and exception conditions — are rarely in the demo. That gap is where implementation surprises tend to originate.
03
Data ownership provisions, exit clauses, and pricing change mechanisms tend to receive less attention than features during evaluation — partly because they are less prominent in proposal materials, partly because the focus is on what the tool does rather than on the terms under which you use it.
Our approach
The advisory begins with requirement definition — a structured conversation with the people who will use the tool and the people who will be responsible for it, to produce a specific list of what the tool needs to do and what conditions it needs to meet.
Those requirements become the evaluation criteria. Every vendor is then assessed against the same criteria, in the same way — so the comparison reflects your requirements rather than the shape of each provider's proposal.
Where structured trials are possible, they use your organisation's own material: actual data, actual use cases, actual exception conditions. The trial protocol is agreed with your team before vendors are approached, so the same conditions apply to each.
The contract review phase examines each vendor's standard terms — and any proposed amendments — for provisions that affect your data, your ability to exit the agreement, and your exposure to pricing changes after the initial contract period.
The evaluation matrix — how it works
The evaluation matrix is built from your requirements, not from a generic feature list. Below is an illustrative structure — the actual criteria depend on what your organisation needs.
Requirement
What the five weeks look like
Week 1
Requirement definition
Structured conversations with the people who will use and be responsible for the tool. Requirements documented in specific, testable terms. Evaluation criteria agreed before any vendor contact begins.
Weeks 2–3
Structured evaluation
Each vendor assessed against the agreed criteria. Where trials are possible, they run using your material under conditions agreed in advance. Questions put to vendors are the same across all providers.
Week 4
Contract review
Standard terms from each vendor under consideration reviewed for data ownership provisions, exit conditions, pricing change mechanisms, and liability terms. Plain-language summary produced for each.
Week 5
Findings and presentation
The written evaluation matrix and contract notes delivered and presented. Questions addressed. The document is yours to use in further negotiations or internal decision-making.
Effort panel — your team's time
Who needs to be involved
The people who will use the tool day to day — their operational requirements are the primary input to the definition phase
A manager or senior contact who can confirm organisational priorities when requirements involve trade-offs
A legal or procurement contact to receive and review the contract term summary
Investment
A fixed fee for the full five-week engagement: requirement definition, structured evaluation against up to three vendors, structured trials where applicable, contract review, and the written findings presentation.
If you are evaluating more than three vendors, or if your procurement situation requires engagement with more than one set of contract terms in parallel, we discuss scope and a revised fee in the initial conversation.
Two weeks of follow-up support are included after the findings session — for questions that arise during internal discussions or negotiation with the vendor you select.
What is included
Requirement definition session — your actual requirements in specific, testable terms
Comparable evaluation of up to three vendors against the same agreed criteria
Structured trials using your organisation's own data and use cases where possible
Written notes on questions each vendor answered indirectly or not at all
Plain-language contract term review covering data ownership, exit provisions, and pricing terms
Written evaluation matrix and findings presentation, plus two weeks of follow-up support
What the evaluation covers
Functional assessment
Core capability against requirements
Does the tool do what your operation needs it to do — not in general, but against the specific requirements your team defined in week one? Each requirement is assessed as met, partially met, or not met, with a note explaining the basis.
Performance under trial conditions
How the tool performs when given your organisation's actual data and use cases — including the awkward cases, the exceptions, and the scenarios that do not appear in the demo. Trial results are recorded and compared across vendors.
Integration with your existing setup
What the tool requires from your existing systems, and where the integration points are. Includes a practical assessment of what implementation would involve on your side.
Indirect and unanswered questions
A specific log of questions put to each vendor during evaluation that received indirect, partial, or no response. The pattern of avoidance is often as informative as the direct answers.
Contract and commercial assessment
Data ownership provisions
Who owns the data processed by the tool, what the vendor can do with it, and what happens to your data if you end the contract. These provisions vary considerably across providers and are rarely prominent in proposal materials.
Exit conditions
What the exit process looks like in practice: notice periods, data export procedures, termination fees, and any provisions that affect your ability to move to a different provider. Exit provisions are often clearer before signing than after.
Pricing structure and change terms
What the pricing looks like beyond the initial contract period, and under what conditions the vendor can change it. Volume-based pricing changes and unilateral price adjustment rights are common and worth understanding before signing.
Liability and support terms
What the vendor is and is not responsible for, and what support terms apply during and after implementation. Plain-language summary, not legal advice — but flagging terms that may warrant specific legal review.
Our commitment
Yorozu holds no commercial relationship with any software vendor or automation platform — no referral arrangements, no partner programmes, no revenue share of any kind. This is not a policy that applies to most vendors while excepting others; it is a structural position we maintain consistently.
The evaluation this service produces is shaped entirely by your requirements and the evidence gathered during the assessment. Where a vendor performs well against your criteria, we say so. Where a vendor performs poorly, we say that too — and we explain why, in terms you can verify independently.
If, at any point during the engagement, we identify a reason why this advisory is unlikely to give your organisation useful information — for instance, if the vendors under consideration are too similar to differentiate on the criteria that matter to you — we will raise that and discuss what to do. The initial conversation carries no commitment on either side.
Start with a conversationHow to proceed
Step 1
Write to info@domain.com or use the contact form. Tell us what kind of tool you are evaluating, how many providers you are considering, and where you are in the process. We respond within two business days.
Step 2
We discuss the selection in more detail — what you are trying to accomplish, what you already know about the options, and what would make the evaluation useful for your decision-making process. This also lets both sides confirm there is no commercial relationship between us and any vendor under consideration.
Step 3
If both sides want to proceed, we confirm the vendors in scope, the people from your team who need to be involved in requirement definition, and the start date. The five-week engagement then begins with requirement definition in week one.
Vendor Selection Advisory
This service gives your organisation a structured basis for comparison built around your requirements, with no commercial interest in which provider you choose.
Get in touchOther services
Service 01
If you are evaluating automation tools but have not yet established which tasks in your departments are suited to automated handling, this review produces that picture first — so the vendor evaluation is grounded in a specific, accurate account of your work. Four weeks.
Service 02
If vendor selection leads to a scheduling implementation, this service handles the deployment — built around your actual constraints, with a parallel period before handover and manual override retained throughout. Ten weeks.