Enter workspace

Workflow · Trade Readiness · Feasibility Study

Feasibility Study

Can this specific company × product × target market opportunity realistically move forward on available evidence, requirements and practical constraints?

Start a Feasibility case →About this capability
Partially live

Who it is for — and what you will need

Exporters and buyers evaluating a concrete opportunity before committing resources.

  • Company + product + origin + target market
  • Opportunity description, volume and timeline
  • Route/corridor and commercial terms if known

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.

  1. Define opportunity

    Company, product, origin, target market, buyer type, volume, timeline, route and known terms.

    Start a Feasibility case → (live today)
    Stage details
    What OrenAtlas already knows
    Company identity (source-backed), known product evidence, credentials, market signals — shown as "what OrenAtlas knows", uncertain items never silently shown as fact
    What you provide
    Company / product / target market (required) — Establish case context — three fields, then Continue · Volume, timeline, buyer type, route, commercial context (if applicable) — Progressively requested only after context exists (inline "why we ask this": capacity, logistics and commercial evaluation)
    Evidence used
    No evidence collected at this stage.
    What happens
    Context triple resolves to canonical records
    If something is missing
    Unknown commercial details remain open assumptions, listed as such.
    Done when
    Opportunity defined; case created.
    What comes next
    Feasibility case (case_id).

  2. Requirements

    Buyer, product, market-entry and regulatory requirements resolved with required evidence/credentials.

    in development
    Stage details
    What OrenAtlas already knows
    Buyer, product, market-entry, regulatory and commercial requirements with required evidence/credentials — engine internals hidden
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Requirement sets carry versions
    If something is missing
    Unknown requirement areas stated as unknown — never invented.
    Done when
    Requirement picture assembled.
    What comes next
    Opportunity requirement set.

  3. Evidence

    Evidence Core reused — known documents never recollected. Supported / submitted / missing / expired / conflicting.

    in development
    Stage details
    What OrenAtlas already knows
    Evidence Core reused: supported / submitted / missing / expired / conflicting per requirement — known documents never recollected
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Evidence Core inventory. Reuse: Full reuse with re-validation of subject/market/freshness; reuse never upgrades state.
    What happens
    Every requirement has an evidence state
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Evidence coverage of the opportunity mapped.
    What comes next
    Coverage map.

  4. Constraints

    MOQ, capacity, delivery, logistics, Incoterms, lead time, pricing/payment context, partner dependencies.

    in development
    Stage details
    What OrenAtlas already knows
    Evidenced capacity, known logistics/route context
    What you provide
    MOQ, lead time, Incoterm, price/payment context, partner dependencies (if applicable) — Commercial and operational constraints — collected progressively, each with "why we ask this"
    Evidence used
    Capacity/logistics evidence where it exists, Statements (labelled). Reuse: Evidenced constraints separated from stated ones.
    What happens
    Stated vs evidenced constraints kept distinct
    If something is missing
    Unknown constraints recorded as open assumptions.
    Done when
    Constraint picture recorded.
    What comes next
    Constraints + open assumptions.

  5. Human assessment

    Conditional outcome: appears actionable · proceed with conditions · further evidence required · unresolved · not ready on current evidence.

    in development
    Stage details
    What OrenAtlas already knows
    Final-review screen: everything assembled, open issues highlighted
    What you provide
    Conditional assessment (required) — Appears actionable on available evidence · proceed with conditions · further evidence required · unresolved · not ready on current evidence — never a universal score, never a guarantee
    Evidence used
    No evidence collected at this stage.
    What happens
    Explicit confirm step; conditions recorded
    If something is missing
    Open items must be acknowledged in the assessment.
    Done when
    Human assessment recorded.
    What comes next
    Conditional assessment.

  6. Feasibility Report

    Versioned report with definition, requirements, evidence, gaps, constraints, risks, assumptions, conditions and next steps. No universal score, no guarantee.

    in development
    Stage details
    What OrenAtlas already knows
    Everything above
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Versioned; NEXT ACTION PLAN required (resolve blockers → Trade Rescue · prepare market entry → Market Entry · start sourcing → Sourcing · request evidence) — a Feasibility Report is never a dead end and never falls back to /match
    If something is missing
    Blockers listed with the Trade Rescue handoff carrying case context.
    Done when
    Versioned Feasibility Report + action plan generated.
    What comes next
    Feasibility Report (versioned) → Trade Rescue / Market Entry / Sourcing / Nordic Bridge, context carried.

What you receive: Feasibility Report

A versioned result — not just a PDF. It preserves:

opportunity definitionrequirementsevidencegapsconstraintsrisksassumptionsconditionshuman reviewrecommended next steps

Current state

Partially live.

The operational case workflow is live for eligible signed-in buyer members: create, save/resume, gated stages, authorized human assessment and a versioned report (/workspace/feasibility/new; requires the case runtime to be provisioned). Feasibility never routes to requirement matching (/match); that is a different question.

Where this hands off next

Your case context (company, product, market, requirement) travels with you — nothing is re-selected.

Foundation — in development

Trade Rescue

Unblock a stalled case: turn its blockers into an owned, dated action plan, resolve what can be resolved, and return the result to the originating case.

View workflow →Foundation — in development

Market Entry Readiness

For a selected market: what appears ready, what is missing and what remains unresolved — based on available evidence and the market’s known requirements.

View workflow →Partially live

Evidence Core

Understand exactly what evidence exists for a subject and what it supports.

View workflow →Partially live

Sourcing Workspace

Move from a requirement to a documented sourcing decision: match, shortlist, close evidence gaps, negotiate in a controlled room, decide.

View workflow →Partially live

Nordic Bridge Case

Take a Nordic company from identification to a managed international market-access case — on the shared platform, never a second system.

View workflow →