Opportunity Formulation and Commercial Classification Quality Automation: "Sell More" Is Never a Registered Opportunity

An opportunity is easy to state vaguely and hard to state precisely — "sell more" costs nothing to say and commits to nothing specific, while a genuinely useful opportunity statement has to name a real situation, a real beneficiary, and a real cost of doing nothing. Under the pace of a client engagement, the vague version wins by default unless something actively pushes back on it. And a second, separate failure mode compounds the first: once an opportunity exists on paper, the temptation to call it "commercial" — something the sales team should chase right now — is strong, even when all that actually exists is a need the consultant perceived, not anything the client has said or done that shows they intend to buy.

Precise opportunity formulation takes more effort than a generic phrase, and under deadline pressure the generic phrase is what gets typed, unless a tool actively checks the text against specific required elements. And distinguishing a perceived need from actual buying intent requires a deliberate, separate judgment call that a simple checkbox for "is this commercial?" does nothing to enforce — the two get conflated exactly because nothing requires anyone to write down the evidence for the stronger claim.

Every opportunity statement is checked against eight required elements: the favorable situation that exists, the problem it solves, the value it creates, who benefits, over what period, under what condition, what doing nothing costs, and what the next validation step is — each needing real content before it counts as present. Separately, the exact title text is checked against seven specific generic phrasings named as inadequate on sight, including the literal "sell more," "use more AI," "build an app," "enter new markets," and "improve marketing" examples the underlying methodology calls out by name — a title matching any of them is flagged with the specific reason it fails to say anything actionable. On classification, the system enforces a rule directly in the save function itself, not just as UI guidance: choosing either commercial classification — for the client or for Centriu — throws a server-side error unless a written rationale accompanies it, describing specifically what the client said or did that indicates real buying intent, not merely a need the consultant identified. A separate, deliberately simple confidence calculation then scores the opportunity: each of the eight required formulation elements present is worth one point, and evidence linked back to the structured diagnosis is worth two — no hidden weighting, specifically so a consultant can explain, in front of a client, exactly why a given opportunity's confidence is where it is.

A consultant's first attempt at logging an opportunity reads simply "sell more to existing clients." The generic-phrasing check does not match this exact wording, but the formulation check flags five of the eight required elements as missing — no stated favorable situation, no named beneficiary group, no benefit period, no cost of inaction, no next validation step. The consultant revises: "Existing clients on the basic plan have grown their team size by 40% on average (favorable situation), but the plan's seat limit is starting to force manual workarounds (problem); upgrading unlocks per-seat features worth an estimated 15% productivity gain (value) for the 12 clients currently over 80% of their seat limit (beneficiaries) within this quarter's renewal cycle (period); the cost of not addressing this is those clients hitting a hard wall and churning at renewal (cost of inaction); next step is a targeted email to those 12 accounts with a seat-usage report attached (validation step)." This version passes the formulation check as "adequate." When the consultant tries to classify it "commercial for Centriu," the system requires a rationale — they cite the specific signal: three of the twelve accounts have already emailed asking about seat pricing, which is the kind of client action the rule requires, not just an inferred need.

An opportunity register stops filling with vague, unactionable phrases that sound promising and specify nothing. Sales stops being handed opportunities based on a consultant's inference alone — a commercial label now always comes with a stated, checkable reason grounded in something the client actually said or did. And a confidence score stays transparent and defensible enough that a consultant can walk a client through exactly why it is what it is, rather than presenting an opaque number.

A team that wants to freely brainstorm opportunity ideas with no structure enforced yet — a true blank-page ideation phase — will find this formulation gate premature; it is built for the moment an idea moves from brainstorm to a tracked, potentially client-facing opportunity record, not for open-ended ideation itself.

A freeform list accepts "sell more" as readily as a fully specified opportunity, and lets "commercial" mean whatever the person typing it felt at the time. Centriu Oracle instead checks the actual structure of every opportunity statement against eight required elements, rejects seven named vague phrasings on sight, and refuses a commercial label without a written, evidence-based reason — so what reaches a sales conversation was never just a consultant's hunch dressed up as demand.