Backed by Relevance Lab· previously known as Kaman.aiInsightsWhitepapersTrust centreCareersContactSign in
Try it now

Home / Platform / Use cases

Use cases

Agents that run your processes. Every flow, every format, every platform.

21 use cases across seven end-to-end flows and six industries. Agents and deterministic workflows over structured and unstructured data, with your models, your systems and a person in charge of what matters.

Domain · Flow · Crew · Anchor · Edition

Every use case is packaged along the same five dimensions, so you find the one that fits.

Built once. Yours to own.

Installed in your organisation, on your platform, under your rules.

Five dimensions

One engine. Knowledge packaged five ways.

The engine is the same for every customer. What we add on top is knowledge, organised along five dimensions. Every use case below is one intersection of them.

Domain

Whose world

Industry entities, terms and rules: financial services, energy, life sciences, manufacturing, public sector, technology.

Flow

Which process

APQC end-to-end flows: issue to resolution, order to cash, record to report, procure to pay and more.

Crew

Who it serves

Engineering, operations, ideation and design, customer support.

Anchor

Where it runs

The platform you already own: SAP, ServiceNow, Salesforce, Oracle Fusion, Dynamics, Snowflake, or standalone.

Edition

How deep

Ready as it is, Configured to your rules, or Tailored only for you.

Building blocks

What every use case is built from.

Not a chatbot, and not RAG on a folder. A platform where agents, workflows and data work together, governed end to end.

Agents

Agents that reason, use tools and act, built by describing them to Kai.

Deterministic workflows

Fixed steps, arithmetic in code, retries and approvals. Agents only where judgement is needed.

Scenarios

Data questions saved and scheduled, so the same question is asked the same way every month.

Structured and unstructured

Tables federated in the lake engine, and documents, drawings, images and audio in the knowledge base. Text-to-SQL and RAG.

Vision, voice and speech

Image understanding, OCR in 12 writing systems, camera feeds, and agents on your phone lines.

Knowledge graph and ontology

Your business in your words, so agents follow real relationships instead of guessing.

Digital twins

Live models of plants, fleets, networks and cities. Try the change on the copy first.

Bring your own models

OpenAI, Anthropic, Google, AWS Bedrock, Azure or open models on your own servers. Choose per agent.

Tools and integrations

105 integrations ready to use: SAP, ServiceNow, Salesforce, Snowflake, Jira, NetSuite and more. Add your own API in minutes.

Governance, lineage and proof

Access policies, maker-checker, lineage from source to report, and a signed record of every action.

Use cases by flow

21 ways customers put Camaan to work.

Each one names its five dimensions, the building blocks it uses and the outcome it delivers.

Flow

Issue to Resolution

From the first signal to the problem solved: incidents, claims, faults and alerts. 7 use cases.

DomainTechnology and MediaFlowIssue to ResolutionCrewOperationsAnchorServiceNowEditionReady

The L1 engineer that never sleeps

“P2 on the payments API, and the SLA breaches in 40 minutes. What's wrong, and who owns it?”

L1 queues fill with the same twenty incidents every week. Engineers copy fields between screens while the SLA clock runs.

  • An agent reads the incident, the CMDB, past resolutions and the runbooks
  • A deterministic workflow classifies, routes and watches the SLA clock
  • The fix is drafted, a person approves, the ticket is updated and the owner notified
AgentsDeterministic workflowRAGHuman approvalSigned audit
60%of L1 tickets resolved without a hand-off
2 minfrom new ticket to triaged
0SLA clocks left unwatched

In the marketplace: Incident Triage & SLA Breach Watch

DomainTechnology and MediaFlowIssue to ResolutionCrewEngineeringAnchorServiceNowEditionConfigured

Provisioning that fixes itself

“The VM build for the trading desk failed at 2 a.m. Fix it before they log in.”

A failed build becomes a ticket, the ticket waits for the morning shift, and a whole team waits for a machine.

  • The failure raises a ticket, and an agent reads the logs and diagnoses the cause
  • Approved runbooks re-run configuration management, verify the machine and resume the order
  • Anything new is escalated, and every fix writes a root-cause report to the lake
AgentsDeterministic workflowScenariosHuman approvalSigned audit
Minutesto recover, not a morning
80%of known failures fixed without a person
Every fixwith a root-cause report

In the marketplace: Failed Provisioning Remediator

DomainEnergy and UtilitiesFlowIssue to ResolutionCrewCustomer SupportAnchorZendeskEditionReady

Every customer, every language

“Show me every call this month where a customer threatened to leave over billing.”

Customers call in their own language at all hours, and quality teams can only listen to two calls in a hundred.

  • Voice agents answer on your existing lines, in the caller's language, and hand over with the full context
  • Speech-to-text runs inside your perimeter, and every call is indexed by topic and promise made
  • Answers jump to the exact second in the recording that proves them
VoiceAgentsSpeechRAGHuman approval
24/7answered in the customer's language
100%of calls searchable, not 2%
To the secondcitations into the audio

Camaan Voice In the marketplace: Multilingual Service Line

DomainFinancial ServicesFlowIssue to ResolutionCrewOperationsAnchorStandaloneEditionConfigured

Claims that read themselves

“Which open motor claims have photos that don't match the reported damage?”

A claim arrives as a pile: photos, a scanned form in Hindi, an email chain with six attachments. Handlers retype it before anyone can decide.

  • Vision describes every photo and flags what doesn't fit the story
  • OCR in 12 writing systems turns forms and notes into structured fields
  • An agent triages, a handler approves, and both are signed into the record
VisionOCRAgentsHuman approvalSigned audit
Minutesto triage, not days
12writing systems read
Everydecision signed and auditable
DomainEnergy and UtilitiesFlowIssue to ResolutionCrewOperationsAnchorSAPEditionConfigured

The field engineer's copilot

“The pump at substation 14 is vibrating again. What fixed it last time?”

The fix is in a manual, a photo from 2019 and the head of a technician who has moved on. The crew on site has a phone and a deadline.

  • Searches manuals, past work orders, site photos and voice notes at once
  • Answers on a phone in plain language, with the page or photo that proves it
  • Raises the work order in SAP once the supervisor approves
RAGVisionSpeechAgentsHuman approval
35%higher first-time fix rate
Secondsto find the last fix
Every visitfeeds the knowledge base

In the marketplace: Process Deviation Responder

DomainEnergy and UtilitiesFlowIssue to ResolutionCrewOperationsAnchorStandaloneEditionConfigured

A live twin of the plant

“What happens to pressure in zone 4 if we take pump 2 out for maintenance tonight?”

Operations data sits in a dozen systems, and how the assets connect lives in people's heads. You find out what a change does after you make it.

  • A digital twin models every asset and connection in your ontology, fed live by sensors and systems
  • Alarms fire on limits and on learned normal behaviour, with history to look back through
  • Try the change on the twin first; agents watch it and raise proposals for a person to approve
Digital twinAgentsScenariosOntologyHuman approval
What-ifon the copy before the real thing
Livestate and history of every asset
Minutesto plan an outage, not days

Camaan Twins

DomainPublic SectorFlowIssue to ResolutionCrewOperationsAnchorStandaloneEditionTailored

Eyes on the ground

“Smoke near tower 3. Where exactly, and which patrol is closest?”

Hundreds of cameras, a handful of people in a control room, and the one frame that matters arrives at 3 a.m.

  • Vision models watch camera feeds and flag smoke, fire, intrusion or a fault
  • Each alert is placed on the map and on a digital twin of the site
  • A person confirms before anyone is sent, and the dispatch is recorded
VisionDigital twinDeterministic workflowHuman approvalSigned audit
24/7watch on every camera
Secondsfrom detection to the control room
Every alertconfirmed by a person

Flow

Idea to Market

From an idea to something shipped: software, designs, plans and research. 5 use cases.

DomainTechnology and MediaFlowIdea to MarketCrewEngineeringAnchorJiraEditionConfigured

Software that ships with proof

“Ship the new onboarding screen, and prove it works before anyone merges it.”

Coding agents write changes faster than teams can review them, and nobody can prove a change works the way a user will see it.

  • Every change starts as a journey: what a user does and should see, drafted from the ticket
  • Builder and reviewer agents code on your own machines, with the model of your choice
  • A real browser test runs, screenshots land in the journey, and a person decides what merges
AgentsDeterministic workflowBrowser proofBring your own modelHuman approval
100%of changes proven in a real browser
2xmore changes shipped per sprint
1,875proof screenshots behind Camaan itself

Camaan Fletcher In the marketplace: Test Automation Generator

DomainEnergy and UtilitiesFlowIdea to MarketCrewEngineeringAnchorStandaloneEditionConfigured

Ask the drawing office

“Which drawings use valve V-204, and what changed in revision C?”

Forty years of drawings, three generations of CAD and a bill of materials nobody trusts. Engineers spend a day a week finding the right revision.

  • Reads DWG and DXF natively: title blocks, layers, tags and every label
  • OCR on scanned legacy drawings, linked to the asset register in a knowledge graph
  • Every answer cites the sheet, the revision and the tag
RAGOCRKnowledge graphAgents
10 sto find the right revision
70%less time spent searching
1 graphdrawings, assets and specs
DomainFinancial ServicesFlowIdea to MarketCrewEngineeringAnchorIBM iEditionTailored

Mainframe, mapped

“If we change the interest calculation, which COBOL programs, tables and reports are affected?”

The people who wrote the core banking code have retired. Every change starts with weeks of archaeology.

  • Parses COBOL, SQL and scripts into a code-aware knowledge graph
  • Links each program to the tables it writes and the policies it implements
  • Agents propose the migration one program at a time, with tests
Knowledge graphAgentsDeterministic workflowLineage
90%less time on impact analysis
1 picturecode, data and policy
3xfaster modernisation sprints

In the marketplace: COBOL Migration Assistant

DomainLife SciencesFlowIdea to MarketCrewIdeation and DesignAnchorStandaloneEditionTailored

Research knowledge, connected

“Which past studies used this compound class, and what adverse events were reported?”

Twenty years of studies live in folders, lab systems and people's heads. New programmes repeat work that was already done.

  • Ontology Studio models compounds, studies, sites and outcomes in your scientists' words
  • The knowledge graph fills itself from documents and lab tables
  • Researchers ask across everything, and agents follow the links rather than guess
OntologyKnowledge graphRAGText-to-SQL
20 yearsof studies searchable in weeks
60%less time on literature reviews
1 ontologyshared by every team
DomainPublic SectorFlowIdea to MarketCrewIdeation and DesignAnchorStandaloneEditionTailored

Plan the city before you build it

“Where should the next three schools go, and what does each option do to traffic and travel times?”

Every department holds its own map and its own spreadsheet. A site study takes months, and the options are compared in a meeting.

  • A city twin brings land, roads, utilities and population onto one map
  • Agents compute and compare the options with spatial analytics
  • Planners see each option side by side and decide, with the working kept
Digital twinMapsAgentsScenarios
Weeks to daysfor a site study
Every optioncompared on the map
1 modelshared by every department

Camaan Twins In the marketplace: Smart Site Planning

Flow

Market to Order

From a prospect to a signed, onboarded customer. 1 use case.

DomainFinancial ServicesFlowMarket to OrderCrewOperationsAnchorSalesforceEditionReady

Onboard in a day, not a fortnight

“Is everything in for the new holding company account, and what's still missing?”

New clients send passports, registrations and statements in every format. Operations checks each one by hand while the deal waits.

  • OCR and vision read every document, in any of 12 writing systems
  • Deterministic checks compare them against the checklist and the CRM record
  • Gaps go back to the client automatically, and Salesforce is updated on approval
OCRVisionDeterministic workflowAgentsHuman approval
1 dayto onboard, not a fortnight
90%of checks done before a person looks
Everydocument traced to its decision

In the marketplace: Onboarding Document Checker

Flow

Order to Cash

From an order to the cash in the bank, with nothing leaking on the way. 2 use cases.

DomainManufacturing and CPGFlowOrder to CashCrewOperationsAnchorNetSuite and SAPEditionReady

Find the revenue that leaks

“What did we deliver last quarter that we never billed?”

Delivered but never billed. Billed below the contract price. Credited without a reason. Nobody notices, and it is revenue already earned.

  • An agent extracts the period's orders, deliveries, invoices and credit notes
  • The three-way match runs in code, so the numbers are the same every time
  • A model explains the root causes, finance approves, and recovery is raised natively
Deterministic workflowAgentsScenariosHuman approvalSigned audit
100%of order lines checked
1 to 3%of revenue typically recovered
0credits issued by an agent

In the marketplace: Order-to-Cash Revenue Leakage Monitor

DomainFinancial ServicesFlowOrder to CashCrewCustomer SupportAnchorSalesforceEditionConfigured

Collections that call

“Call every account more than 30 days overdue, agree a payment plan, and log it.”

Collectors reach a fraction of overdue accounts each day, and every call is written up by hand afterwards.

  • Voice agents place calls on your existing lines, in the customer's language
  • Payment plans are offered within the limits your rules allow, and anything else goes to a person
  • Every call is transcribed and logged against the account in the CRM
VoiceAgentsDeterministic workflowHuman approvalSigned audit
3xmore accounts reached per day
Every calltranscribed and logged
Same rulesas every other channel

Camaan Voice

Flow

Record to Report

From transactions to numbers a board and a regulator will sign. 3 use cases.

DomainManufacturing and CPGFlowRecord to ReportCrewOperationsAnchorSAPEditionConfigured

Talk to your numbers

“Why did gross margin in the south region drop in Q3, and which SKUs drove it?”

Every board question becomes a ticket to the data team. By the time the answer arrives, the meeting is over.

  • Text-to-SQL over a semantic layer built from your own business ontology
  • Federated queries across SAP, Snowflake and files, with no copy-and-load project
  • Saved as a scenario, so next month's board pack asks the same question the same way
Text-to-SQLScenariosLineageOntology
Secondsfrom question to chart
Zeronew data warehouses to build
100%of numbers traceable
DomainFinancial ServicesFlowRecord to ReportCrewOperationsAnchorSnowflakeEditionConfigured

Data you can defend

“Where did line 4.2 of the regulatory return come from, and who changed the mapping?”

Regulators ask where a number came from. The answer lives in spreadsheets, emails and the memory of one analyst.

  • The lake engine federates every source, with lineage from source column to report line
  • Mappings change under maker-checker, and access policies decide who sees what
  • Returns are drafted by scenario, controls are tested, and evidence is packed for the auditor
Data governanceLineageScenariosHuman approvalSigned audit
Every numbertraced to its source column
Days to hoursto prepare a return
Maker-checkeron every mapping change

In the marketplace: Regulatory Return Drafter

DomainFinancial ServicesFlowRecord to ReportCrewCustomer SupportAnchorServiceNowEditionReady

The policy desk

“Can we onboard a corporate client from this jurisdiction, and which policy says so?”

Thousands of pages of policy, rewritten every quarter. Compliance answers the same question for the hundredth time.

  • Enterprise RAG over every policy version, including the legacy .doc and .ppt archive
  • Answers quote the paragraph and the version that applied on the day
  • Anything unclear escalates to compliance as a ServiceNow case, with the context attached
RAGAgentsHuman approvalSigned audit
80%of routine questions answered instantly
Paragraph-levelcitations
0answers without a source

In the marketplace: Policy Assistant with Escalation

Flow

Procure to Pay

From a supplier to goods received, graded and paid for. 2 use cases.

DomainManufacturing and CPGFlowProcure to PayCrewOperationsAnchorNetSuiteEditionReady

See supply shocks coming

“A port strike hits our tier-one supplier. Which orders, customers and revenue are at risk?”

When a supplier fails, it takes days of spreadsheets to work out who is affected, and the customers find out first.

  • A knowledge graph links suppliers, parts, purchase orders, sales orders and customers
  • The impact is computed in code from live ERP data, not guessed
  • Agents draft the alternatives and the customer notes for a buyer to approve
Knowledge graphDeterministic workflowAgentsHuman approval
Minutesto a full impact map
Everyaffected order and customer named
Daysearlier warning to customers

In the marketplace: Supplier Disruption Impact Analyst

DomainManufacturing and CPGFlowProcure to PayCrewOperationsAnchorStandaloneEditionTailored

Graded by vision, not by hand

“Grade this morning's intake by size and quality, and price each batch.”

Incoming produce and parts are sorted by eye, one tray at a time. Grades vary by shift, and so does the price paid.

  • Cameras on the line capture each tray, and a vision model finds and measures every item
  • A vision-language model checks quality the way an inspector would
  • A workflow records the grade, routes the batch and prices it for the supplier
VisionDeterministic workflowScenariosBring your own model
1,000sof hours of manual sorting replaced
Every traygraded the same way
Same daypricing for suppliers

Flow

Hire to Retire

From a new joiner's first day to their last. 1 use case.

DomainLife SciencesFlowHire to RetireCrewOperationsAnchorStandaloneEditionReady

Ready on day one

“A new analyst starts Monday in Pune. Get the laptop, accounts and induction sorted.”

Joining takes a dozen tickets across HR, IT and facilities, and the new hire spends their first week waiting for access.

  • HR describes the joiner app to Kai, and IT keeps it in git, previewed, tested and governed
  • A workflow provisions accounts through your identity provider, orders the kit and books the induction
  • Joiners ask the policy assistant anything, and access is granted only on approval
AppsDeterministic workflowAgentsRAGHuman approval
Day onelaptop, accounts and induction ready
Daysto build the app, not a quarter
0access granted without approval

Camaan Apps

Structured and unstructured

If your business keeps it, Camaan can read it.

Most AI stops at PDFs and Word files. The knowledge that runs a plant, a bank or a hospital lives in drawings, scans, recordings, tables and code.

Documents

Every office file, old and new

PDF, Word, PowerPoint with speaker notes, Excel, whole mailboxes, and twenty-year-old .doc and .ppt archives.

CAD

Engineering drawings

DWG and DXF read natively: title blocks, layers, tags, dimensions and every label on the sheet.

Images and video

Vision and OCR

Photos and camera frames understood, scans read in 12 writing systems, on your own servers.

Audio

Calls and voice notes

Speech-to-text inside your perimeter, with answers cited to the second of the recording.

Data

Tables and warehouses

Text-to-SQL across SAP, Snowflake, databases and files, federated in the lake engine, with lineage on every number.

Code

Systems, explained

COBOL, SQL, Python, JavaScript and scripts parsed into the knowledge graph, linked to the data they touch.

In numbers

Built for the estate you actually have.

Counted on the platform today.

105integrations ready to use
23ready-made offers in the marketplace
20+file formats, from PST mailboxes to DWG drawings
373user journeys tested end to end, every release

Pick a flow. Bring your data. We'll show you the agent running on it.

Book a working session