Demo gallery

Inspectable samples. No sales call required.

Three artifacts from real Deploris engagements, anonymised and on paper. Your engineer can poke at them before you talk to us.

RAG · retrieval with sources

What does a late signoff from Supplier X actually cost us?

Sample RAG answer over a corpus of contracts and email threads. Grounded answer, source citation per claim, principled non-answer when evidence is missing.

See RAG service →

query.jsonlSources: 3 docs, 7 passages

> How much does a late signoff from Supplier X cost us per month?

retrieval:
  [1] contract-supplier-x-v3.pdf §12.2
      "... delay penalty 1.8% of monthly invoice ..."
  [2] finance-ops/invoices-2026.csv row 142
      "Monthly invoice Supplier X: €84,300"
  [3] email/thread-9821.eml
      "... signoff landed on the 11th, 8 days late ..."

answer:
  ~€1,517/month in delay penalties (1.8% × €84,300), triggered every month for the last four, approximately €18,200/year of avoidable spend at the current signoff cadence. Sources [1][2][3].

confidence: 0.92
refusal_if_unsupported: true

Agent · production run trace

Analyse the reach of a lost opportunity

Trace of a production agent with four tool calls, one human-in-the-loop review, and one auto-generated CRM update. Every step logged, every write reversible.

See AI agents service →

agent://opportunity-recalltrace.jsonl

→ crm.getOpportunity(id=OPP-8421)

owner: alex@… stage: Closed-Lost value: $62k closed: 2026-07-14

→ email.search({"account":"OPP-8421.accountId", "last":"90d"})

found 23 messages across 5 threads

→ rag.query("why did we lose", scope=OPP-8421)

→ pricing mentioned 6× in last two threads; incumbent 15% below quote

→ calendar.proposeSlot(owner="alex", purpose="renewal nudge", window="next 10 days")

HUMAN REVIEW

Draft outreach to decision-maker + proposed talking points shown to alex@ for approval. Approved at 14:03 CET.

✎ crm.updateOpportunity(id=OPP-8421, nextAction="renewal-nudge", followUp="2026-10-18")

✓ run complete · 4 tool calls · 1 HITL gate · 1 reversible write

CRM · data model excerpt

Account hierarchy for multi-location sales

Slice of a custom CRM data model: account hierarchy, deal pipeline, activities with RBAC scopes. Editable, versioned, auditable.

See custom CRM service →

model Account {
  id            String   @id
  name          String
  type          AccountType  // HQ | SITE | FRANCHISE
  parent        Account? @relation("hierarchy")
  region        Region
  createdBy     UserId
  @@index([region, type])
}

model Deal {
  id            String   @id
  accountId     Account.id
  owner         UserId
  stage         DealStage
  value         Money
  currency      ISO4217
  expectedClose Date
  rbac          Scope[]   // who can read/write
}

model Activity {
  id            String   @id
  dealId        Deal.id
  kind          Kind       // EMAIL | CALL | NOTE | AGENT_WRITE
  author        UserId | AgentId
  body          Text
  at            Timestamp
  reversible    Boolean    @default(true)
}

Note: all data in the samples is synthetic. Real client data never appears in public material.

Inspectable samples. No sales call required.

Next steps