Inevitable / The platform

Build what makes
you different.

Your methodology is the product. Evidence, reasoning, execution, and application services are the machinery beneath it. Connect the capabilities you need instead of rebuilding the foundation.

See how it fits together Build with us
Your application. The capabilities underneath.
platform architecture svgA distinct customer application composes four selectable capability groups. Connections do not imply a shared database.YOUR DIFFERENTIATIONMethodology + experienceDomain rules · Integrations · Your brandGoverned dataReasoningExecutionApp servicesCOMPOSE WHAT THE PRODUCT NEEDSplatform architecture svg mobileA distinct customer application composes four selectable capability groups. Connections do not imply a shared database.YOUR DIFFERENTIATIONMethodology + experienceDomain rules · Integrations · Your brandGoverned dataReasoningExecutionApp servicesCOMPOSE WHAT THE PRODUCT NEEDS

01 / Governed data

Keep the answer.
Keep its origins.

Connect documents, business systems, and public sources. Reconcile what they say without losing the evidence behind the chosen value.

A canonical value serves the product. Source-specific values, transforms, confidence, and conflicts remain in its lineage. Geography is resolved through a governed read path rather than silently rewritten into the source record.

Inside data infrastructure
An operational value and its evidence.
platform evidence svgSource claims and geographic evidence feed reconciliation. The operational value is separate from all retained source contributions, conflicts and lineage.Source claimsGeographic evidenceReconcile + validateChosen valueProduct read pathSource lineageValues + conflicts

Origination data infrastructure

Discover the sources.
Build in your cloud.

Over a million data sources tagged by geolocation and subject matter.

Our discovery engine finds the sources. Ingestion proxies through our resolution engine to identify geographic tags. You host and operate the data infrastructure in your own cloud.

02 / Reasoning

Find the drivers.
Explore the consequences.

A conclusion is more useful when you can inspect what drives it. Explore assumptions, causal relationships, and alternative scenarios across every relevant driver.

Different perspectives test the framing. Causal models examine mechanisms and interventions. Evidence and disagreements stay connected to the analysis.

Explore causal reasoning
18causal models

Change the drivers.
See the decision move.

Illustrative / Relationships, not one score.
platform causal svgAdoption and price affect revenue; cost affects delivery economics. They combine in unit economics with capacity feedback.AdoptionPriceCostoffer affects uptakeRevenueDelivery costUnit economicscapacity

03 / Task execution

Edit the work.
Follow what changes.

Research and analysis produce deliverables, not just a score. Edit a task’s output, keep its version history, and re-run the dependent work.

In the task executor, counterfactuals begin with deliverable edits. Change the analysis or assumptions in the document itself. The workflow identifies which downstream deliverables need to be regenerated.

Inside task execution
Illustrative / One edit, explicit dependencies.
platform execution svgEdited pricing affects the market model and memo. The market model also feeds the memo; context is independent and version one stays in history.V1 retainedV2 editedPricing + economicseditMarket modelDecision memoContext

04 / Application infrastructure

Build the experience.
Reuse the foundation.

The intelligence needs somewhere to work. Shared application infrastructure supports the product around it: users, tenants, permissions, billing, and operations.

Keep your domain workflow and brand distinct. Connect the shared capabilities your product needs instead of rebuilding every supporting system.

Explore application infrastructure

Behind the customer experience

Identity & access
Users, roles, permissions, and tenant boundaries.
Commercial operations
Licensing, billing, usage, and administration.
Execution & integrations
Queues, connected systems, and domain workflows.
Operating visibility
Logs, audit trails, and observability.

05 / How it composes

Shared capabilities.
Distinct products.

A product draws on the parts it needs. Strategy intelligence and asset origination are separate experiences, with different workflows and evidence.

Strategy intelligence

From a business question
to a decision file.

Research markets, explore causal drivers, and build decision deliverables through a versioned task workflow.

  1. Evidence intake
  2. Reasoning & scenarios
  3. Task deliverables
Explore strategy intelligence

Asset origination

From geographic evidence
to an opportunity.

Evaluate sites, resolve owners and operators, and connect demand signals to ranked assets and an approach plan.

  1. Data infrastructure
  2. Origination analytics
  3. Opportunity workflow
Explore asset origination

Capabilities can become building blocks

Underwriting is a workflow.
It can also power another product.

Borrower acquisition and athletics financing combine their own domain operations with reusable underwriting and matching capabilities.

One capability supports distinct workflows.
platform reuse svgUnderwriting supports borrower acquisition and athletics finance with their own domain workflows.Underwriting& matchingBorroweracquisitionAthleticsfinance
Bring your product idea Explore the product types