What happens in a Model Transfer Evaluation

A Model Transfer Evaluation is a fit check, not a sales call. It turns your brief into a go/no-go decision, tells you exactly what you receive, and treats a direct no-go as a useful result.

Who this is for

This memo is written for owners and partners preparing their first evaluation brief. It sets expectations before scope and commercial terms are confirmed.

The pathway is fixed: brief review, fit call, then a validation sprint or a clear stop.

What must be true

The evaluation runs on a small, explicit contract. Each side knows what goes in and what comes out.

| Stage | What it is | | --- | --- | | Input | A structured brief | | Review | 2–3 business days | | Output | Go / no-go | | Next | RECON or stop |

1. Evaluation is scoped, not a free discovery call

A Model Transfer Evaluation is a paid or scoped engagement. It begins after brief review, and only when fit looks plausible.

The job of the evaluation is to turn your thesis into something testable. Four elements get pinned down:

• The reference model
• The market gap
• The advantage
• The proof point

If those four cannot be named, there is nothing to evaluate yet.

2. What you receive

The output is a decision package, not a deck. It contains:

• A fit assessment against model, market, and partner criteria
• A named proof point and the fastest kill factor
• A recommendation: validation sprint, adapt the thesis, partner, or stop
• A clear commercial scope if RECON is warranted

Every recommendation maps to one of four moves. There is no "let's keep talking" outcome.

3. No-go is a valid outcome

A brief no-go protects capital and attention. It usually means one of four things:

• The model is not legible
• The market is crowded
• The advantage is vague
• The proof point cannot be named

A fast no is cheaper than a slow maybe. And the boundary holds after the decision.

We do not run chase sequences after a no-go.

Ready to test the next move?

Use this note to tighten the model, market, advantage, proof point, bottleneck, or target outcome. Then send the right brief. The evaluation works when these conditions hold:

• There is an existing business, product, workflow, or proven model to improve
• The market, process, or customer journey is underserved, fragmented, or underperforming
• You bring decision authority, market access, distribution, domain insight, or capital
• You can describe the customer or workflow problem and what would prove progress
• Scoped services, a JV, building together, or aligned advisory is realistic if evidence clears
• You are ready to move in weeks, not exploratory quarters

If most of these are true, start the evaluation brief. If the work is client systems rather than a venture thesis, start a services brief instead.

Read next

• Is this model worth transferring? A checklist for scoring model, market, edge, and proof before sending a brief.
• RECON before roadmap. Why validation comes before any build plan.