Verdicts are derived from methodology and sourced evidence — not for sale. CoDomain never adjusts a verdict based on commercial relationships. Companies can pay for representation, distribution, and depth — not for analytical outcomes.
The Four Verdicts
| Verdict | What it means |
|---|---|
| Validate | The pattern is real, but field conviction has not yet confirmed the spend signal. Validate before scaling. |
| Scale | Spend and field sentiment both support expanding into this pattern. |
| Refine | The pattern has traction, but scope or positioning needs narrowing before expanding. |
| Pivot | Structural evidence suggests the current positioning is not viable. A directional change is warranted — not iteration. |
Guidance by Verdict
Validate
The capital signal is present but the practitioner field hasn’t built conviction yet. This is a Capital ahead pattern — money is moving faster than operators have validated. The pattern isn’t broken; it’s unproven at scale. For a founder building here: You are likely earlier than the funding activity suggests. The spend signal is real, but the absence of field validation means buyers may be harder to land than the market activity implies. Run structured discovery. Find the practitioners who are experiencing the problem the pattern claims to solve. Build conviction from the field before scaling investment. For an operator evaluating a deployment: The technology or approach you are evaluating may not have enough real-world deployment evidence behind it. Pilot before you commit. Ask vendors for practitioner references outside their marketing materials.Scale
Both signals are aligned and both support expansion. Field conviction and capital deployment are reinforcing each other. This is the pattern’s highest-confidence state. For a founder building here: The structural conditions support growth. Capital is available, practitioners are engaged, and the pattern has field validation. The primary risk shifts from whether the market exists to whether you can execute and compete in a space that others are also scaling into. For an operator evaluating a deployment: This is the strongest entry signal CoDomain produces. Practitioners are buying in, capital is committed, and the space has real-world validation. The risk to manage here is vendor selection and implementation quality — not market viability.Refine
The pattern has traction — there is real signal in both capital and field sentiment — but the scope or positioning is too broad, too narrow, or misaligned. The pattern works somewhere, but not everywhere it’s being applied. For a founder building here: Don’t scale the current positioning. The market is telling you the pattern is real but your aperture is off. Look at which sub-segments of the pattern are generating enthusiastic field sentiment versus cautious or skeptical. Narrow your ICP, your use case, or your integration surface before expanding. For an operator evaluating a deployment: Be specific about what you are deploying and why. Generic implementations in this pattern are underperforming. Operators who are succeeding here are doing so with tightly scoped deployments. Define the workflow, the integration surface, and the success criteria before you start — not after.Pivot
The structural evidence suggests the current positioning is not viable. This is not a signal to iterate — it is a signal to change direction. Either capital has moved on, field sentiment has turned negative, or the technical infrastructure cannot support the deployment ambition the market was funding. For a founder building here: This is a hard signal and it is meant to be. Pivoting is not failure — continuing to scale a structurally weak positioning is. Identify which element of the positioning is breaking down: is it the customer segment, the use case, the architecture, or the go-to-market? The Pattern section of the frame will give you the mechanism language. For an operator evaluating a deployment: Do not deploy into a Pivot-verdict pattern without significant additional diligence and a clear thesis for why your specific context is different from the structural trend. The evidence suggests that most deployments here are not delivering at the level the market initially projected.Reading Direction and Verdict Together
Direction tells you the structural state of the pattern. Verdict tells you what that state implies for action. Neither is complete without the other. Here is a practical example of how they combine:Read the direction label
The frame shows Capital ahead. Capital is committing to this pattern faster than practitioners have validated it. The gap between spend and field sentiment is material.
Read the verdict
The verdict is Validate. The structural state — capital ahead of field conviction — implies you should validate before scaling. The spend signal is real but unconfirmed by the field.
Apply the combined read
Together: the market is being funded, but practitioners haven’t caught up. If you are a founder, this means the opportunity is real enough to pursue but too early to scale without field validation. Run discovery first. If you are an operator, pilot before you commit — the vendor landscape is active but real-world deployment evidence is thin.