Platform

Reads. Decides. Acts.
The system of decision.

Inversiq connects documents, data, models, decision logic, workflows and human control in one governed operating layer.

Inversiq PlatformGoverned execution

Connected inputs

Source documents
Operational data
Models
Decision policies

Inversiq operating layer

Evidence linked
Assumptions validated
Rules executed
Human review

Decision record

Preparing

Reading inputs into one governed decision record.

Architecture

One platform. One data model. End to end.

Evidence, models, rules, review and execution run on one governed operating layer.

The underlying engine is domain-neutral and designed to support multiple verticals. Commercial Real Estate is the first full vertical, and where the platform is applied most deeply today.

Documents & data

Documents, models, systems, records

Relationships

Entities resolved, sources reconciled

Risk & assumptions

Conflicts and gaps surfaced

Decision logic

Rules applied, rationale attached

Human review

Approval gates, accountability

Action

Workflows executed, outcomes logged

One governed operating layer — evidence to executed action.

Platform Architecture

One shared engine. Deep vertical products. Customer-specific configuration.

Inversiq separates reusable decision infrastructure from vertical logic and customer configuration, allowing each implementation to reflect how an organisation works without fragmenting the core platform.

Shared Engine

Execution, evidence, review, integrations, identity, audit and governance.

Vertical Layer

Domain objects, models, document types, rules, workflows and outputs.

Customer Configuration

Mappings, model structures, approval policies, terminology, templates and integrations.

Foundation

Security, reliability, observability and compliance readiness across every layer.

Platform Capabilities

The capabilities behind every governed decision.

Each capability works from the same connected sources, models, rules, permissions and audit trail.

One governed system
Connected sourcesModels & rulesPermissionsHuman reviewAudit trail
01 · Intelligence

Evidence Intelligence

Turn documents and data into structured, source-linked and reviewable evidence.

  • Documents, operational data and model inputs are read into one structured record.
  • Every value keeps the reference it came from, so a reviewer can go back to the source.
  • Anything that cannot be confirmed is raised rather than assumed.
Evidence workspaceReading sources

Raw sources

Source Documents
Operational Data
Model Inputs

Structured evidence · source-linked

Key assumption
Committed through 2029
SRC-014 · p.12Source linked
Model input
Escalation 2.5%
SRC-022 · Sheet 2Validated
Policy requirement
Approval threshold
SRC-007 · §4.2Confirmed
Material exception
Termination option · 2027
SRC-014 · p.31Confirmation required

Three records source-linked · one requires confirmation before it is used.

02 · Intelligence

Risk & Assumption Intelligence

Validate assumptions and surface material conflicts before they affect the decision.

  • Assumptions are tested against the sources they depend on.
  • Conflicts are stated in one line, with the requirement that contradicts them.
  • Materiality decides what reaches a person, so review effort follows the risk.
Assumption review
Testing assumption

Active assumption

Capacity is committed through 2029.

Supporting source

Commitment recorded through 2029.

SRC-014 · p.12Consistent

Conflicting requirement

Termination option effective 2027.

SRC-014 · p.31Conflicts
Materiality
LowModerateMaterial
Affects committed capacity from 2027.

Human review required — assigned to Process owner.

03 · Intelligence

Decision Intelligence

Explain what matters, why it matters and where human judgment is required.

  • Findings are synthesised into the effect on the decision, not just stored.
  • Source basis, applicable rule and rationale stay attached to the output.
  • The reviewer accountable for the judgment is named before anything proceeds.
Decision brief
Synthesising

What matters

Termination option conflicts with the capacity assumption.

Effect on the decision

Committed capacity ends in 2027, so the base case no longer holds on the original assumption.

Source basis
SRC-014 · p.31
Rule applied
Capacity assumptions must reconcile with active termination options.
Rationale
Evidence linked · assumption tested against source · effect stated

Required

Process owner

Accountable for the material judgment. Nothing proceeds until this review is complete.

Synthesised from linked evidence. The model states the effect; the reviewer makes the decision.

04 · Execution

Workflow Orchestration

Coordinate models, rules, reviews and approvals in one controlled workflow.

  • Intake, validation, model execution and review run as one governed sequence.
  • Exceptions interrupt the run instead of passing quietly to the next step.
  • No governed output is released while a review gate is still open.
Workflow run
Running
IntakePending
Documents and data received
ValidationPending
Inputs checked against rules
Model executionPending
Operating Model v4.2
ExceptionPending
Assumption conflict raised
Human review gatePending
Awaiting Process owner
Governed outputPending
Held until the review completes

Execution stops at the gate. No governed output is released while a review is open.

05 · Execution

Model Runtime

Run governed financial and operational models with reproducible outputs.

  • Models run at a known version, against connected and source-linked inputs.
  • Outputs are reconciled back to those inputs before they are used.
  • The same version, inputs and scenario reproduce the same run.
Model run
Queued

Version

v4.2

Scenario

Base case

Run

RUN-08

Connected inputs

Operational data set
ConnectedSRC-031
Rate assumption
Source linkedSRC-022 · Sheet 2
Policy constraint
AppliedSRC-007 · §4.2

Key outputs

Projected outcome
12.4%
Coverage ratio
1.38×
Downside case
−8.2%
Validation
Outputs reconciled to connected inputs · no unresolved differences

Same version, same inputs, same scenario — the run reproduces.

06 · Execution

Integrations

Connect documents, data and enterprise systems through governed integrations.

  • Document libraries, model files and operational systems are connected in scope.
  • Access follows the permissions of the connected system, not a second set of rules.
  • Outbound actions stay behind an approval boundary.
See connected systems
Connections
Connecting

Connected sources

Microsoft SharePoint
Document library · read
Microsoft Excel
Model files · read
Operational system
ERP / CRM records · scoped

Access context

Identity
Existing identity and access controls
Permissions
Inherited from the connected system
Scope
Customer tenant · configured workspaces

Inbound

Approved import · 12 documents, 1 model

Outbound

Actions require approval before execution

Availability depends on implementation scope — systems are connected with the access each environment permits.

07 · Governance

Human Review & Controls

Route exceptions, approvals and overrides to the right people.

  • Material exceptions are routed to a named accountable role.
  • Approvals, conditions and overrides are recorded with the reviewer's reasoning.
  • The material judgment stays with a person, not the model.
Review queue
Routing
Material exception

Termination option conflicts with the capacity assumption.

Assigned to
Process owner
Reviewer note
Capacity assumption revised from 2027. Condition attached to the approval.
Decision
Approved with condition
Accountable owner
Process owner
Written to decision record REC-2291 with the reviewer's reasoning attached

Overrides are recorded the same way — with the reason, the reviewer and the accountable owner attached.

08 · Governance

Governance & Auditability

Keep every material decision explainable, reproducible and traceable.

  • Source reference, model version, rule applied and human decision sit in one record.
  • The state before and after the decision is kept, not only the outcome.
  • A readable event trail shows who did what, and when.
Decision record
Assembling

Record

Source reference
SRC-014 · p.31
Model version
Operating Model v4.2
Rule applied
Capacity reconciliation
Human decision
Approved with condition · Process owner

State change

Before

Capacity assumption unverified

After

Assumption reconciled · condition attached

Audit events

09:41
Evidence linked
System
09:44
Model run v4.2
System
10:02
Exception raised
System
10:26
Approved with condition
Process owner

Every material step is reproducible from the record — source, version, rule, reviewer.

09 · Governance

Security & Compliance

Protect access, tenant data and governed operations.

  • Access is enforced by role, workspace and tenant scope.
  • Requests outside that boundary are not served, and the outcome is recorded.
  • Architecture and current assurance status are shared during the security review.
View security overview
Access & controls
Resolving access

Access context

Role
Reviewer
Workspace
Programme workspace
Tenant scope
Customer tenant · isolated
Permission boundary
Role and workspace scope

Protected resource

Source document · restricted
View linked evidencePermitted

Within role and workspace scope

Configure workflowNot served

Outside the permission boundary

Control event
Actor, action and permission outcome recorded

Architecture documentation and current assurance status are shared during the security review.

Integrations & Governance

Governed integrations. Governed operations.

Model Runtime executes financial and operational models with reproducible outputs. Governed integrations connect documents, data and systems, with permissioned access, audit trails and human review built in.

Connects with

Financial & operational models

Spreadsheet and structured models, run with reproducible outputs.

By implementation scope

Documents & data rooms

Investment memoranda, leases, reports and diligence material.

By implementation scope

Microsoft SharePoint

Document libraries and sites connected within implementation scope.

By implementation scope

Google Drive

Shared drives and folders connected within implementation scope.

By implementation scope

ERP, CRM & operational systems

Enterprise records and workflow systems connected by implementation scope.

By implementation scope

Integration availability depends on implementation scope. Enterprise systems of record are connected as part of implementation, using the connectors and access each environment permits.

Governance & Auditability

Permissioned accessAudit trailsHuman review by designTenant isolation

The Decision Agent

An AI agent that coordinates the work behind every decision.

It reviews information, works across models and workflows, involves the right people and carries out approved tasks — with every action controlled and recorded.

Inversiq Agent
Ready

Connected to

Documents & data

Documents and records reviewed

Models & rules

Assumptions and policies evaluated

Workflow state

Current stage and blockers understood

People & permissions

Tasks routed to authorised colleagues

Enterprise systems

Approved actions executed through integrations

Instruction

Review the decision inputs, resolve material conflicts and coordinate the required follow-up.

Issue detected

A model assumption conflicts with an active source requirement.

Coordination

Assign review task
Request input from Operations
Draft clarification message
Prepare approval request

Human control

External request awaiting approval

Approve action

After approval

Request sent
Workflow updated
Task assigned
Audit event recorded

The agent prepares and executes approved work. The material decision stays with the accountable reviewer.

See the platform in your workflow.