Platform · Data agents

Agents that file their reasoning

A chatbot answers. An analyst shows their working. DataFact agents are built to do the second thing: plan the investigation, cross-check what they find, and hand back something you could defend in a review.

  • multi-step planning
  • cross-channel corroboration
  • SaaS or self-hosted

Anatomy of a run

You can read what it did

Every run is inspectable: the sub-questions it formed, which channel each step went to, how long it took, and the point where it reconciled two sources that disagreed.

When someone challenges the conclusion, the argument is about the evidence rather than about whether the machine can be trusted.

Run · margin investigationcompleted
  1. 01Decompose the question3 sub-questions
  2. 02Retrieve from documents9 chunks · 2 figures
  3. 03Query the warehouse2 queries · 1.2s
  4. 04Cross-check both sides1 conflict resolved
  5. 05Write up with sources4 citations attached

Capabilities

What separates a run from a reply

These behaviours are the difference between something people try once and something they route real work through.

01

Planning

The route is decided during the run

A causal question cannot be answered by one retrieval. The agent breaks it into sub-questions, and what it finds in the first step changes where it looks in the second — rather than following a chain fixed before it knew anything.

  • Question decomposed into sub-questions with their own retrieval
  • Later steps conditioned on what earlier steps returned
  • Work split across agents where the sub-questions are independent
02

Corroboration

Sources are checked against each other

When the report says one thing and the table says another, averaging them is the wrong answer. The run surfaces the disagreement, states which source it trusted, and says why.

  • Document findings cross-checked against warehouse results
  • Conflicts reported rather than smoothed over
  • Confidence tied to whether the channels agreed
03

Clarification

It asks when the question is ambiguous

Half the questions people type are underspecified — which region, which fiscal calendar, gross or net. Guessing produces a confident wrong answer. The agent asks, with the options it can see, then continues from your reply.

  • Targeted follow-up questions with concrete options
  • The run resumes from the answer without starting over
  • Skippable when you would rather it picked a default
04

Output

An asset, not a chat message

What comes out has data, charts, a written conclusion and a citation trail — durable enough to paste into a decision memo, and re-runnable next month against fresh data.

  • Charts generated alongside the narrative
  • Every claim carries its citation index
  • Scheduled re-runs for recurring reviews
05

Delivery

Wherever the question gets asked

An agent is published to the surfaces your people already use: the console, an embedded widget in your own application, an API for your systems, or a bot in the chat tool where the question would have been asked anyway.

  • Console for analysts
  • Embeddable chat widget for your internal apps
  • Native bots for DingTalk and Feishu — configured, not built
  • Open API to wire it into Slack, Teams or anything else you run

Agent types

Configured to the job, not one general chatbot

Different questions want different machinery. An agent is set up with the resources it needs and nothing more, which keeps both its answers and its permissions tight.

Knowledge

Document Q&A

Bound to selected document collections. Returns text, tables and figures with page-level citations.

Analytical

Query generation

Bound to a schema and an analysis model. Produces governed SQL, results and charts.

Investigative

Multi-source runs

Bound to both channels. Plans, splits and corroborates before writing a conclusion.

Assistive

No attached data

Prompt and skills only, for drafting and reasoning tasks that should not touch company data.

Bring a question nobody has time to answer question

The recurring investigation that takes an analyst two days. We will build the agent for it during the demo and show you the run.

SaaS subscription or private deployment · No data migration either way