Workflow · Supplier Intelligence · Company Intelligence
Company Intelligence
Find a company and understand who they are, what they appear to do, what products and services are evidenced, and what remains unknown.
Who it is for — and what you will need
Buyers, analysts and diligence teams researching a supplier or counterparty.
- Industry and geography scope
- Product or service keywords
- Optionally: a specific company name or organisation number
Anything OrenAtlas already knows is prefilled with its evidence state — you are asked only for what is missing or unresolved.
How it works
6 stages. Save and resume at any point; each stage keeps its evidence attached to the exact item it supports.
Discover
Search the canonical company universe from official registry identity; deduplicated entities, small companies included.
Start a Company Intelligence case → (live today)Stage details
- What OrenAtlas already knows
- Saved and recent searches · Industry catalog scopes
- What you provide
- Industry & geography (required) — Scope the canonical company universe · Product/service keywords (if applicable) — Narrow to relevant activity
- Evidence used
- No evidence collected at this stage.
- What happens
- Scope resolves against the canonical industry catalog (fail closed on unknown keys)
- If something is missing
- Empty result states explain why and offer scope widening — never fabricated candidates.
- Done when
- A candidate company is selected.
- What comes next
- Selected candidate company (company_id).
Identity
Legal name, organisation number, status, address and entity type — each with source and retrieval date. Registered codes never imply actual products.
Browse companies → (live today)Stage details
- What OrenAtlas already knows
- Legal name, organisation number, status, registered address, entity type — each with source + retrieved_at
- What you provide
- Entity disambiguation choice (if applicable) — Resolve duplicate/ambiguous entities before deeper work
- Evidence used
- Official registry records. Reuse: Registry identity is reused across all workflows; freshness shown; re-retrieval only when stale.
- What happens
- Identity resolves to exactly one registry entity · Registered codes are never presented as proof of actual products
- If something is missing
- Unresolved identity becomes an explicit open question on the report — never guessed.
- Done when
- Identity is resolved (or the unresolved state is explicitly recorded).
- What comes next
- Resolved company identity with provenance.
Activity
Registered activity, observed signals and supplier-stated activity shown separately — never merged into one "verified activity".
in developmentStage details
- What OrenAtlas already knows
- Registered activity, observed activity signals, supplier-stated activity — three separate lanes, never merged
- What you provide
- Nothing — OrenAtlas assembles this stage.
- Evidence used
- Registry activity records, Observed signals with source, Supplier statements (labelled). Reuse: Signals reused with their source and date; supplier statements never promoted by reuse.
- What happens
- Each lane carries its own provenance · No merged "verified activity" field exists
- If something is missing
- Absent lanes state "no observed signals" honestly.
- Done when
- Activity lanes are displayed with provenance.
- What comes next
- Activity summary by source lane.
Products
Canonical product records with evidence, markets, review state and unresolved claims.
in developmentStage details
- What OrenAtlas already knows
- Canonical product records with evidence state, markets, review state
- What you provide
- Nothing — OrenAtlas assembles this stage.
- Evidence used
- Product evidence records, Supplier product submissions (labelled, review-gated). Reuse: Canonical products reused everywhere; unreviewed claims stay visibly unreviewed.
- What happens
- Products come from the canonical product model — no duplicate catalog
- If something is missing
- No products on file is an honest state with a supplier-task path.
- Done when
- Product list with evidence states rendered.
- What comes next
- Product + evidence-state list.
Evidence
Coverage summary: source-backed, supplier-submitted, pending, missing, expired, conflicting.
in developmentStage details
- What OrenAtlas already knows
- Compact coverage: n/m evidence items, gaps, stale — by category (Identity, Products, Credentials, ESG, Trade, Compliance)
- What you provide
- Nothing — OrenAtlas assembles this stage.
- Evidence used
- All existing evidence records. Reuse: Coverage computed from existing records; reuse never upgrades state.
- What happens
- Coverage counts derive from real records — never a generic "Verified ✓"
- If something is missing
- Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
- Done when
- Coverage summary computed.
- What comes next
- Evidence coverage summary.
Intelligence Report
Versioned Company Intelligence Report with identity, activity, products, coverage, freshness and open questions.
in developmentStage details
- What OrenAtlas already knows
- Everything assembled above
- What you provide
- Nothing — OrenAtlas assembles this stage.
- Evidence used
- No evidence collected at this stage.
- What happens
- Report is versioned; open questions listed; next actions present (no dead report)
- If something is missing
- Open questions appear in the report as such.
- Done when
- Versioned Company Intelligence Report generated with at least one next action.
- What comes next
- Company Intelligence Report (versioned) → hands company_id to Due Diligence / Compliance / Feasibility / Sourcing.
What you receive: Company Intelligence Report
A versioned result — not just a PDF. It preserves:
Current state
Partially live.
The operational case workflow is live for eligible signed-in buyer members: canonical discovery, identity, the three separated activity lanes, canonical products, evidence coverage and a versioned Company Intelligence Report (/workspace/company-intelligence/new; requires the case runtime to be provisioned). Registered codes remain classification signals — never proof of activity or products.
Where this hands off next
Your case context (company, product, market, requirement) travels with you — nothing is re-selected.
Due Diligence
Review a counterparty or case for a specific business purpose, with evidence, gaps and human review.
View workflow →Foundation — in developmentCompliance
Understand whether available evidence covers a defined requirement set — and exactly what to do about every gap.
View workflow →Partially liveFeasibility Study
Can this specific company × product × target market opportunity realistically move forward on available evidence, requirements and practical constraints?
View workflow →Partially liveSourcing Workspace
Move from a requirement to a documented sourcing decision: match, shortlist, close evidence gaps, negotiate in a controlled room, decide.
View workflow →