Market and Competitor Intelligence Automation: Every Competitor Named, Typed and Structured

A consultant researching a client's market rarely lacks information about competitors — the problem is almost never a shortage of knowledge, it is the shape that knowledge takes. One competitor gets a detailed paragraph because a recent conversation surfaced it; another gets a single bullet point because nobody had time to dig further; a third is mentioned only in passing as "also worth watching." Comparing them later means re-reading unstructured prose each time, with no consistent set of questions answered for every competitor and no clear label distinguishing a genuine head-to-head rival from a company that only competes for the same customer's attention in a much broader sense.

Structuring competitive research properly — typing every competitor consistently, answering the same seven questions for each one, keeping the market-level context in its own separate record — takes deliberate discipline that a busy engagement schedule tends to erode first. It is also easy to conflate "we discussed competitors" with "we have a usable competitive record," when in practice the former produces meeting notes and the latter requires someone to sit down and fill in the same structured fields for every single name that came up. And without any mechanism connecting the depth of that research to the engagement's own measured quality, a thin competitive section carries no visible cost — it just quietly stays thin.

A project's market study is a single record, upserted by project id rather than created fresh each time, carrying eight fields — market name, region, category, consumer behavior, seasonality, trends, barriers and sources — each one optional but each one contributing to a completeness score computed as the fraction of those eight fields actually filled in. Every write first checks that the acting user actually belongs to the organization the project is scoped to, rejecting the request outright otherwise. Competitors are a completely separate, unbounded list: each one is created with a required name (at least two characters) and an explicit type chosen from exactly four options — direct, indirect, substitute or reference — never left ambiguous or unlabeled. Every competitor then carries the same seven structured fields regardless of type: channels, positioning, value proposition, strengths, weaknesses, offers and threats, each one free text but each one consistently present across every competitor in the list, so comparing two competitors means reading the same seven questions answered twice, not two differently-shaped writeups. A competitor can be updated in place (matched by its own id and the project's organization) or removed outright, with the delete operation checked against every organization the acting user actually has access to, not just the one named in the request. Separately, Oracle's own overall project quality score — the same mechanism that already tracks briefing completeness, diagnostic coverage, branding, journey and offer completeness elsewhere in the engagement — pulls in both the market study's completeness score and the raw count of competitors tracked as two of its contributing categories, confirmed directly in the scoring module's own source. A market section left mostly empty, or a competitor list with only one or two entries, shows up as a specific, named gap in that overall score rather than staying an invisible blank spot nobody's attention was drawn to.

A consultant has thoroughly filled in a client's 11-block diagnosis, branding and offer sections, but the market study has only two of its eight fields filled in — category and region — and only one competitor has been entered, typed as "direct," with just a name and no other field completed.

Reviewing the project's overall quality breakdown, the market and competitor categories stand out as the clear weak points relative to everything else that has been thoroughly documented — not a vague sense that "something feels incomplete," but a specific, named category with a specific, low score. The consultant goes back to the market study and fills in consumer behavior, seasonality and trends, then adds two more competitors: an indirect one offering a different approach to the same underlying need, and a substitute the client's own sales team keeps hearing about from prospects. The next time the quality breakdown is checked, both categories have moved, and the gap that used to be invisible is now closed.

Comparing two competitors stops requiring a re-read of two differently-shaped paragraphs, because every competitor answers the same seven structured questions. A distant substitute stops getting silently conflated with a genuine head-to-head rival, because the type is an explicit, required choice on every record. And a thin or missing competitive section stops hiding in plain sight, because it shows up as a specific, named, low-scoring category inside the engagement's own overall quality measurement rather than staying an unmeasured blind spot.

A team hoping the system will find and research competitors automatically will not find that here — every market-study field and every competitor record is entered directly by the consultant; there is no web-crawling or AI-assisted research step behind this feature. The value is in the structure and the connection to the rest of the engagement's quality measurement, not in doing the research itself.

A folder of meeting notes about competitors can hold the same underlying information, but nothing forces a consistent type label, nothing guarantees the same seven questions get answered for every competitor, and nothing connects a thin competitive section to any measurable consequence. Centriu Oracle's structure adds exactly those three things, and ties the result directly into the same quality score already tracking the rest of the engagement.