Market Entry Versus Field Verification: Why Companies Need Both
One tells you whether the plan makes sense. The other tells you whether it is true.
A market entry assessment reasons about a plan and identifies what it depends on. Field verification establishes whether specific facts are true. Buying the first and expecting the second is the most common reason a company feels well-advised and still gets surprised on arrival.
Companies evaluating Venezuela regularly buy one of these products and assume they have bought both. They are different exercises, with different methods, different outputs, and different costs. This article sets out the difference so the right one gets commissioned at the right time.
The two products side by side
| Market entry assessment | Field verification | |
|---|---|---|
| Question | Should we enter, and what would it take? | Is this specific thing true? |
| Unit of work | A plan or an opportunity | A place, a route, or an organisation |
| Method | Documentary review, analysis, structured reasoning, targeted inquiry | Direct observation, photography, physical checking |
| Output | Assessment, dependency map, assumption register, decision matrix | Observation record with evidence and stated limits |
| Answers | What the plan rests on and what would break it | Whether a particular thing is as described |
| Cannot answer | Whether any specific assumption is actually true | Whether the overall opportunity makes sense |
| Best commissioned | Early — while the plan is still shapeable | Once the plan identifies what matters, and again close to commitment |
| Ages | Slowly — the structure of the problem is stable | Quickly — conditions change |
Why the assessment cannot substitute for verification
An entry assessment is an act of reasoning about available information. Done properly, it produces something genuinely valuable: an explicit list of the things the plan depends on, ranked by how badly the plan breaks if each is wrong.
What it cannot do is close those items. The assessment's most useful output is often a sentence like "the mobilization schedule depends on road access that has not been independently verified." That is a finding, and it is worth having. It is not a verified road.
Why verification cannot substitute for the assessment
Verification without a framing exercise produces confirmed facts about arbitrary things. A company can verify a site thoroughly and still miss that the binding constraint on the whole project was never the site — it was power, or a counterparty, or a corridor two hundred kilometres away.
The assessment is what tells you where to point the verification. Field work commissioned without it tends to check what is easy to check rather than what matters.
The efficient sequence is assessment first, then verification aimed by it — but only the top few items. In our assessment most plans have three to six load-bearing assumptions, and verifying those returns the great majority of the available risk reduction. Verifying twenty items costs several times as much and adds relatively little.
The sequence that works
- Assessment. Map what the plan depends on. Produce an explicit assumption register with consequence rankings.
- Triage. Identify the small number of assumptions that would change the decision if wrong.
- Verification, round one. Check those items on the ground. Record what was observed and what could not be established.
- Revise. Feed findings back into the plan. Some assumptions will have been wrong, and the plan changes shape.
- Verification, round two. Close out anything the revised plan newly depends on, and re-check condition-sensitive items close to commitment.
- Prepare and mobilize against what was actually found.
Step 4 is the one most often skipped. A verification finding that does not change the plan when it should have has been wasted.
Which to commission when
| Situation | Commission |
|---|---|
| Early exploration; no specific asset yet | Assessment |
| A specific opportunity, plan not yet built | Assessment |
| A plan exists and a decision is approaching | Assessment, then verification of the top items |
| One narrow factual question is holding up a recommendation | Verification only |
| Confirmatory diligence before close | Verification, aimed by the model's sensitivities |
| Approved project, mobilization approaching | Verification of condition-sensitive items, close to the date |
| Continuing operations | Periodic verification and monitoring |
Questions that reveal which one you actually bought
- Does the report distinguish observed facts from analysis?
- Did anyone physically go anywhere? When, and where?
- Is there a list of assumptions that remain unverified?
- Are the photographs dated and indexed to a question?
- Does the report say what could not be established?
- If someone acted on this and was wrong, which sentence would they have relied on?
A document that cannot answer those questions has done one job or the other, and it is worth knowing which.
What remains uncertain
Both products have limits worth stating. An assessment is reasoning under uncertainty and can be wrong about which assumptions matter. Verification is a dated snapshot under whatever access was available. Neither eliminates risk; both convert unknown risk into known risk, which is the only thing that can actually be managed.
Related capabilities
Not sure which one you need?
Describe the decision. We will tell you which product answers it, and what it would involve.