RECON before roadmap

Why Exiid pressure-tests model, market, channel, and risk before turning a transfer thesis into a build plan. The roadmap comes second. Evidence comes first.

Who this is for

For: operators who want speed without letting roadmap momentum outrun evidence.

Useful when: you need to know what must be learned before a venture deserves build capital.

What must be true

The RECON sprint is a gate between a transfer thesis and a build plan. Its shape is fixed:

| Stage | What it is | | --- | --- | | Input | Transfer thesis | | Sprint | RECON | | Risk | Fastest kill factor | | Output | Decision |

The loop runs decode, adapt, test — then decide: build, adapt, partner, or stop.

01 — The roadmap is earned

A model transfer can look obvious when the reference market is mature. That is exactly when momentum is most dangerous. RECON exists to test whether local demand, trust, channel access, and economics survive contact with the target market.

A roadmap built before that contact is a guess with milestones attached. A roadmap built after it is a plan.

02 — Four questions drive the sprint

Every RECON sprint answers the same four questions:

• What exactly works in the reference model?
• Which parts must change for the local market?
• What proof point shows the transferred behavior is real?
• Which risk can kill the venture fastest?

Note the order. Decode the source before adapting it. Define the proof before chasing it. Name the kill factor before it names you.

03 — The output is a decision

A strong RECON sprint ends with one of four calls: build, adapt, partner, or stop.

Weak evidence is not failure. It is the system doing its job before capital and attention get trapped.

No-go is useful when it protects capital, time, and operator focus.

Read next

• Is this model worth transferring? — a checklist for scoring the thesis itself.
• What happens in a Model Transfer Evaluation — the memo that follows when RECON clears.