Approach Comparison
Two models.
Different things they actually deliver.
Understanding the structural differences between a retained advisory relationship and a project-based independent engagement makes it easier to choose the one that fits the situation.
← HomeContext
Why the comparison matters
Most companies that reach out to a business consultant are not short of options — they are uncertain which structure will actually answer their question. The fee model, the relationship length, and the nature of the output differ substantially between engagement types, and those differences shape what a company receives at the end.
This page sets out the practical distinctions between a retained advisory arrangement and a project-based independent engagement. Neither is presented as the correct answer for every situation. The intent is to give enough information to judge which fits the current need.
Two models compared on this page
Traditional / Retained Advisory
Ongoing relationship, typically monthly fee, broad advisory remit, relationship-centred delivery.
Project-Based Independent (Scope Lab Zone)
Fixed scope, defined fee, written deliverable, no ongoing commitment required.
Comparison Table
Traditional vs. Project-Based
| DIMENSION | TRADITIONAL / RETAINED | PROJECT-BASED (KADODE) |
|---|---|---|
| Engagement length | Ongoing, typically months to years with rolling renewal | Fixed — 4 to 6 weeks depending on assessment type |
| Fee structure | Monthly retainer, billed whether active work occurs or not | Single fixed fee agreed before work begins — ¥36,000–¥43,000 |
| Scope definition | Broad and flexible, shaped by the relationship over time | One-page scope note agreed and signed before any work starts |
| Deliverable | Advice given verbally or informally over time; varies by firm | A written document with sourced figures, handed over at end of engagement |
| Independence | May have referral relationships with vendors, staffing or implementation firms | No referral relationships. No downstream work follows from the engagement |
| Entry requirement | Usually requires signing a multi-month agreement upfront | Single engagement, no commitment beyond the current scope |
| What happens at the end | Relationship continues — exit may require notice period | Engagement closes. Client holds the output. No ongoing obligation |
| Best suited for | Companies needing ongoing strategic support across multiple functions | Companies with a specific question that needs an independent, documented answer |
Traditional
Ongoing, months to years, rolling renewal
Scope Lab Zone
4–6 weeks, fixed and defined
Traditional
Monthly retainer, billed continuously
Scope Lab Zone
Single fee, agreed before work begins
Traditional
Verbal advice, informal, varies by firm
Scope Lab Zone
Written document with sourced figures
Traditional
May have vendor referral relationships
Scope Lab Zone
No referral relationships of any kind
Distinction
What the project-based model makes possible
ACCOUNTABILITY
The output is the measure
In a project-based engagement, value is measured by what is produced — a written document that exists independently of the consultant. There is no ambiguity about whether the work was done. The deliverable is agreed upfront and either exists at the end of the engagement or it does not.
NO CONFLICT OF INTEREST
Nothing follows from the recommendation
Scope Lab Zone has no implementation arm, no software partnerships, and no staffing relationships. A recommendation to proceed or not to proceed has no financial consequence for the consultant beyond the fixed fee already agreed. That structure removes the most common source of bias in advisory work.
LOW COMMITMENT TO ENTER
One engagement, no lock-in
A company can commission a single assessment to answer a specific question, review the output, and decide independently what to do with it. There is no expectation of further work. If a second engagement follows, it is agreed on its own terms with its own scope.
CLEAR COST
The fee is known before any work begins
Each assessment type has a published fee. The scope note confirms the exact figure before any engagement starts. There are no hourly overruns, no scope creep billed at a day rate, and no charges for access to tools or platforms.
Outcomes
What each model tends to produce
Retained advisory tends to produce
- —
Broad strategic perspective across multiple functions, built over time through repeated interaction
- —
Relationship familiarity that can enable faster informal advice on emerging situations
- —
Access to a network the advisor has built, which may be relevant for certain introductions
- —
Continuity of involvement through implementation, which suits companies without internal capacity
Project-based engagement tends to produce
- —
A documented answer to a specific question, with the reasoning and figures set out clearly
- —
A view formed without institutional incentive to favour one outcome over another
- —
A defined cost that does not increase with the length of the relationship
- —
An output the client's own team can use, reference, and act on independently
Cost & Value
Investment in context
COST STRUCTURE
¥36,000–¥43,000
A single fixed fee per engagement. No time-and-materials billing, no monthly minimum, and no fee for access to tools or data systems.
WHAT IS PURCHASED
A document, not a relationship
The fee covers the time to conduct a structured assessment and produce a written output. That output belongs to the client entirely and has no expiry.
TYPICAL ALTERNATIVE COST
Months of retained fees
A retained arrangement to produce equivalent analysis would typically run for three to six months at a substantially higher cumulative cost, often without a written output as the endpoint.
Client Experience
What the engagement looks like day-to-day
In a retained arrangement
Contact tends to happen on demand — calls, meetings, and reviews as needed. The relationship develops organically, which can be productive but can also mean the engagement drifts in scope over time. What is being worked on and what it will produce are often undefined in advance.
The client's experience depends heavily on the individual advisor and how actively they pursue clarity. Some retained advisors are highly structured; others are responsive but reactive.
In a Scope Lab Zone engagement
The scope, the timeline, the required inputs, and the deliverable are agreed before any work begins. The client knows what is expected of them and when. Progress is shared at defined milestones, not at the end. The engagement ends when the written output is delivered.
There are no open-ended check-ins, no ambiguity about what is being produced, and no expectation that the client will drive the process. The structure is designed so that a senior contact who is busy can still participate without the engagement stalling.
Lasting Impact
What persists after the engagement ends
One structural consequence of project-based consulting is that the client owns the output. A working capital model, a segment definition built from transaction data, or a current-state operational map does not disappear when the consultant does. It stays with the client's team and can be maintained or built on.
This is intentional. The goal of an assessment is to leave the client's team better positioned to make a decision or run a function — not to create a dependency on continued external involvement.
What the client retains
- —The written assessment document, with sourced figures
- —Any working models handed to the finance or operations team
- —Defined decision points or criteria for revisiting the assessment
- —Complete ownership of all materials — no IP retention by Scope Lab Zone
Common Misconceptions
Clarifying what project-based consulting is and is not
"A short engagement can't go deep enough."
Depth depends on method, not duration. A four-week review that examines actual transaction records, interviews the right three people, and produces sourced findings will go further than a six-month retainer that never examines the underlying data. The scope note specifies exactly what will be examined.
"Without a long relationship, you can't understand our business."
The assessment type is chosen because it fits the question, not because the consultant already knows the company. The process of scoping an engagement surfaces the context needed. Companies with complex operations have found that a structured external examination uncovers things that internal familiarity had obscured.
"Independent means no follow-through."
An assessment that produces a clear written output and a defined decision point gives a company's own team what it needs to implement. Follow-through is a function of the quality of the output, not the length of the consultant's involvement. Scope Lab Zone can also be engaged on a subsequent project if implementation questions arise.
Decision Support
When the project-based model is a reasonable fit
The project-based model works well when the need is specific: a particular question that, if answered clearly, would allow a decision to be made or a direction to be confirmed. It is less suited to situations where a company needs ongoing strategic counsel across many functions simultaneously.
A reasonable starting point is to identify the question. If it can be stated in one sentence and would be answered by a structured assessment, a project engagement is likely appropriate. If the need is broader — managing through a significant transition, for example — a retained arrangement may be the better structure.
Consider Scope Lab Zone when there is a specific question, a defined timeframe, and value in having an output that your team can hold and use independently.
Consider a retainer when the need spans multiple functions, requires ongoing judgment over an extended period, or involves regular access rather than a defined endpoint.
Next Step
If there is a question that fits this model, the scope note will make that clear.
An initial enquiry is enough to confirm whether an assessment is appropriate and what the scope would involve. No commitment follows from making contact.
Get in Touch