The largest SEO opportunity is not automatically the best first investment. The easiest project is not automatically the best either.
Large demand estimates cannot compensate for weak execution.
ORBIT now exposes the complete rule: split Opportunity into Commercial Opportunity and Strategic Opportunity; calculate the Readiness floor from seven prerequisites; name the Binding Constraint; then use Information Speed and Turnback Cost to select Scale, Probe, Build, Harvest, Hold—or Review required.
Status: Evidence-first ORBIT V1.2 decision logic. Reviewer-agreement and post-publication outcome validation remain open.
The SERPIFAI ORBIT Portfolio Map
The map remains the article’s central instrument. Its axes are now reproducible: Opportunity is the higher of Commercial Opportunity and Strategic Opportunity, while Readiness is the lowest of seven required readiness components.
ORBIT V1.2 stands for Opportunity, Readiness floor, Binding Constraint, Information Speed, and Turnback Cost. Opportunity and Readiness position the initiative. The final three determine whether a low-readiness opportunity should be Probed or Built first.
The visible ORBIT equations
The workbook does not hide the scoring logic. The article uses the same equations.
| Output | Equation | Why this rule is used |
|---|---|---|
| Commercial Opportunity (CO) | CO = MEDIAN(Qualified demand, Customer value, Buyer relevance) | The median prevents one extreme commercial claim from dominating the position. |
| Strategic Opportunity (SO) | SO = MEDIAN(Strategic leverage, Authority leverage, Option value) | Strategic importance remains visible instead of disappearing inside one blended score. |
| Opportunity position (O) | O = MAX(CO, SO) | An initiative can be portfolio-relevant because its commercial or strategic case is high. A two-point CO/SO conflict requires an explicit mandate. |
| Readiness floor (R) | R = MIN(Evidence, Capability, Ownership, Measurement, Authority, Technical feasibility, Delivery capacity) | A critical weakness cannot be averaged away by strong non-blocking components. |
| Binding Constraint (B) | B = readiness component(s) equal to RSeverity = 5 − R | The model names what must change, how severe it is, and what evidence would clear it. |
Information Speed is the speed at which a bounded action produces decision-useful evidence—not the speed at which a team completes tasks. Turnback Cost is the cost of pausing, narrowing, reversing, or redirecting the initiative after new evidence appears.
Exactly how ORBIT selects an action
Rules are evaluated from top to bottom. The first matching rule becomes the output.
IF required input is missing
OR |CO − SO| ≥ 2 and the mandate is Unknown:
Review required
ELSE IF O ≥ 3 AND R ≥ 3:
Scale
ELSE IF O ≥ 3 AND R < 3
AND Binding Constraint is testable
AND Information Speed ≥ 3
AND Turnback Cost ≤ 2:
Probe
ELSE IF O ≥ 3 AND R < 3:
Build
ELSE IF O = 2 AND R ≥ 3:
Harvest
ELSE:
Hold| Priority | Condition | Action | Why the nearest alternative is rejected |
|---|---|---|---|
| 1 | Required input missing, or CO/SO differ by at least two points with no approved mandate | Review required | No automatic action is allowed from incomplete or unresolved evidence. |
| 2 | O ≥ 3 and R ≥ 3 | Scale | Probe is rejected because the weakest readiness condition is already executable. |
| 3 | O ≥ 3, R < 3, constraint testable, I ≥ 3, T ≤ 2 | Probe | Build is rejected because a fast, reversible experiment can reduce uncertainty. |
| 4 | O ≥ 3 and R < 3, but the Probe rule fails | Build | Probe is rejected because the constraint is untestable, evidence arrives too slowly, or reversal is too costly. |
| 5 | O = 2 and R ≥ 3 | Harvest | Scale is rejected because the opportunity is bounded; Hold is rejected because the initiative is executable. |
| 6 | All remaining classified cases | Hold | Harvest is rejected because readiness is low or the opportunity is negligible. |
What a score of 1, 2, 3 or 4 means
Ordinal scores are not scientific probabilities. Each score must carry evidence and a short rationale.
| Input family | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Opportunity component | Negligible or unsupported | Material but bounded | Large and decision-relevant | Strategic or category-level |
| Readiness component | Blocked or absent | Incomplete; material work remains | Executable and measurable | Proven at operating scale |
| Information Speed | More than 90 days | 31–90 days | 8–30 days | Seven days or less |
| Turnback Cost | Low; normal-workflow reversal | Manageable within one bounded tranche | High; multi-tranche rework | Severe or structurally difficult to reverse |
Opportunity Size × Execution Readiness
How to read it: select a checkpoint to isolate that part of the method. The canvas shows the relationship; the inspector explains what the checkpoint changes in the decision.
Executive comparison: why the first funding decision changed
The 70-page programme looked larger. The five-article pilot became the better first allocation only after every input and action rule was exposed.
| Attribute | 70-page overhaul | Five-article calibration | Decision effect |
|---|---|---|---|
| CO | 3 — large commercial scope | 2 — bounded direct commercial value | The overhaul wins on immediate commercial breadth. |
| SO | 4 — strategic library-wide leverage | 4 — creates the operating system for the library | Both remain strategically high. |
| O | 4 | 4 | Opportunity alone cannot decide the order. |
| R | 1 — Ownership clarity is the floor | 3 — Authority readiness is the floor | The pilot is executable; the overhaul is blocked. |
| Binding Constraint | Ownership and editorial operating standard | Authority proof remains incomplete but does not block execution | The overhaul requires prerequisite creation. |
| I / T | I=2, T=4 | I=4, T=1 | The pilot creates faster evidence at much lower reversal cost. |
| Rule applied | O≥3, R<3, Probe rule fails → Build | O≥3, R≥3 → Scale | Fund the calibration tranche first. |
Before and after ORBIT: the real 70-page decision
Before ORBIT
Fund the 70-page programme first because it affects the entire library.
After ORBIT
P1 = Build: CO=3, SO=4, O=4, R=1, Binding Constraint=Ownership, I=2, T=4.
P2 = Scale: CO=2, SO=4, O=4, R=3, I=4, T=1.
Why P1 is not Probe or Hold
- Probe rejected: the constraint was not yet testable, Information Speed was below 3, and Turnback Cost was above 2.
- Hold rejected: O remained 4, so the strategic opportunity was too large to abandon.
The observed result is operational, not a ranking claim. Four evidence-first pages were installed under transactional safety, while the broad programme remained protected from repeated uncalibrated errors.
Before and after ORBIT: AEO/GEO versus practical acquisition content
| Input | AEO/GEO expansion | Local competitor guide |
|---|---|---|
| CO / SO / O | 3 / 4 / 4 | 2 / 2 / 2 |
| R and Binding Constraint | R=1; Evidence and Measurement tie as constraints | R=3; executable floor |
| I / T | 2 / 3 | 3 / 1 |
| Rule | O≥3, R<3, Probe rule fails → Build | O=2, R≥3 → Harvest |
| Nearest alternative rejected | Probe is too slow and too costly to reverse at current maturity. | Scale is rejected because O<3; Hold is rejected because R≥3. |
The result is a parallel strategy: build evidence for the strategic emerging topic while harvesting a bounded practical acquisition opportunity.
How an initiative changes state
An action changes only when a published threshold changes.
- Build → Probe: the Binding Constraint becomes testable, I reaches at least 3, and T falls to 2 or below.
- Build or Probe → Scale: the Readiness floor reaches at least 3 while O remains at least 3.
- Probe → Hold: the test fails and the remaining opportunity/readiness profile no longer qualifies for another action.
- Harvest → Scale: O rises from 2 to at least 3 while R remains at least 3.
- Scale → Probe or Hold: a post-investment stop condition is reached.
This prevents “not ready now” becoming “never,” and “funded now” becoming irreversible.
Sensitivity: what single change moves an initiative?
| Initiative | Current | Single change | New action | Reason |
|---|---|---|---|---|
| P1 — 70-page overhaul | Build | Constraint becomes testable, I=3 and T=2 while R remains 1 | Probe | The Probe rule becomes true. |
| P1 — 70-page overhaul | Build | R rises from 1 to 3 | Scale | The Scale rule becomes true. |
| P3 — Internal links | Probe | T rises from 1 to 3 | Build | The Probe rule fails because reversal becomes too costly. |
| P5 — Local guide | Harvest | O rises from 2 to 3 while R stays 3 | Scale | The initiative crosses the high-opportunity threshold. |
When the large opportunity should win
ORBIT is not a small-project bias. The large initiative should move to Scale when the value pathway is material and delivery, evidence, ownership, and measurement are operational.
Monster India: Probe before Scale
Google’s published case describes Monster India testing JobPosting structured data and then expanding the implementation after positive performance. The case reports a 94% increase in organic traffic on job-detail pages and a 10% increase in applications. These are reported case outcomes, not a guaranteed result for another site.
Read the Monster India case on Google Search Central.
Wix: Scale with operating readiness
Google’s Wix case describes a platform-scale Search Console and Site Verification API integration. The case reports more than two million connected sites and observational performance differences for connected users. The portfolio point is that a large opportunity can justify Scale when the operating system already exists.
The five-option portfolio dataset
All component values, formulas, constraints and rejection reasons are available in the workbook. The table below exposes the decisive values.
| ID | Initiative | CO | SO | O | R | Binding Constraint | I | T | Action |
|---|---|---|---|---|---|---|---|---|---|
| P1 | Broad 70-page overhaul | 3 | 4 | 4 | 1 | Ownership clarity | 2 | 4 | Build |
| P2 | Five-article calibration | 2 | 4 | 4 | 3 | Authority readiness | 4 | 1 | Scale |
| P3 | Internal-link remediation | 3 | 3 | 3 | 2 | Ownership clarity | 3 | 1 | Probe |
| P4 | AEO/GEO expansion | 3 | 4 | 4 | 1 | Evidence + Measurement | 2 | 3 | Build |
| P5 | Practical local competitor guide | 2 | 2 | 2 | 3 | Evidence / Measurement / Authority | 3 | 1 | Harvest |
When several readiness components tie at the floor, all tied components must be recorded even though the workbook’s compact display returns the first matching column.
From ORBIT action to a bounded tranche
The map selects the next action. A bounded tranche turns that action into delivery with stop conditions, evidence requirements, and a review date.
The Green Book’s treatment of flexibility and real options is relevant here: uncertainty is easier to manage when investment can be staged, reviewed, and redirected.
Use ORBIT in fifteen minutes
- Score the three commercial inputs. Calculate CO with the median.
- Score the three strategic inputs. Calculate SO with the median.
- Set O = MAX(CO, SO). If CO and SO differ by at least two points, record the approved commercial, strategic or balanced mandate.
- Score all seven readiness components. Set R to the minimum and name every tied Binding Constraint.
- Record testability, Information Speed and Turnback Cost.
- Apply the ordered decision rules. Do not skip directly to a preferred action.
- Write why the nearest alternative was rejected.
- Define the single threshold change that would move the initiative.
Apply the complete ORBIT V1.2 decision workbook
The visible article shows the equations and ordered rules. The workbook expands them into component-level scoring, formula-driven classifications, nearest-alternative rejection, sensitivity tests, reviewer-audit rows, a software input schema, and a blank implementation template.
Use it when multiple SEO initiatives compete for the same budget or delivery window and different reviewers must be able to reproduce the same action.
What this article owns—and what it does not
| Page | Question it owns |
|---|---|
| Execution Readiness and Defensibility Gate | Can this one opportunity be executed responsibly now? |
| Opportunity Size vs Execution Readiness | How should several competing initiatives be sequenced? |
| Allocate Budget Across Technical SEO, Content and Authority | How should resources be distributed inside a selected initiative? |
| Post-Investment Review | Should a funded tranche continue, expand, pause, or reverse? |
Method, overrides and limitations
ORBIT adapts established portfolio, staged-investment and real-options principles to SEO evidence and delivery decisions. It does not claim that opportunity-versus-capability thinking is new.
An override is allowed only when the reviewer records the proposed action, the rule being overridden, the reason, the approver and the timestamp. Missing data never defaults silently to Hold.
The first-party dataset documents one SERPIFAI editorial portfolio. The external cases are provider-published and do not isolate every confounding factor. Ordinal scores support transparent comparison, not scientific probability.
Reviewer consistency is not yet empirically validated. A mature release must test inter-rater agreement, document disagreement causes and recalibrate ambiguous score anchors.
The final rule
Do not fund the largest opportunity automatically. Do not fund the easiest opportunity automatically.
Expose CO and SO. Use the readiness floor rather than an average. Name the Binding Constraint. Then apply the visible rules for Information Speed and Turnback Cost so another reviewer can reproduce—and challenge—the action.