Scoped pilot / Not the data-agent fleet
Not just more data.
A better understanding.
Your workflow needs more than a pile of files. It needs the facts, the rules you have approved, and what happened the last time work was done. The upload is an identifier-only CSV. Drafts wait for you. Nothing sends.
01 / Context layer
Source facts
Customer records and transaction summaries, with the export date and original source record kept in view.
02 / Context layer
Business meaning
Your definition of a dormant customer, minimum history, exclusions and other approved operating rules.
03 / Context layer
Approved knowledge
How your business describes itself. The team uses the version you approve, not an invented company profile.
04 / Context layer
Working context
The current workflow run, its evidence and drafts, and the decisions that still need your attention.
05 / Context layer
Decision history
What changed, what was approved or rejected, and the version of the work that decision applied to.
06 / Context layer
Recorded outcomes
Observed transactions and their references, distinct from unproven claims about incremental revenue.
A memory you can inspect and correct
Keep facts, interpretations
and approvals distinct.
In the pilot, updating a source, definition or business description creates a new saved revision and clears the current workflow. An edited draft must be approved again. Stale sources block new work. Previous private-workspace artifacts remain available in the archive.
This is versioned context and workflow history, not a claim that an AI model retrains itself or that every stored statement is true.
Private / Per workspace
Your business context
Customer records, approved knowledge and decisions remain in the workspace you are authorized to access. They are not pooled into other customers' workflows.
Reusable / Source-aware
The context library
Public and appropriately licensed external data can support a defined task. The current public-source infrastructure is retained separately, with its source health and evidence links.
Inspect the supporting sources →Reusable / Not your records
The methods
Connectors, mappings, validations, workflow recipes and evaluation cases can improve across implementations. Reusing a method does not mean reusing another customer's confidential data.
One offering / Three clear responsibilities
The team. The mind.
The expertise behind both.
LucidAgent is where the pilot runs. LucidAgentMind is its business context. LucidDataMind handles implementation, complex data integration and exceptional support.
You do not need separate hosting, model API keys, or three subscriptions to request the quoted pilot. Your Mind lives inside the same workspace as the workflow.
FAQ
Upload, sending, and buying
- What do you upload?
- An identifier-only customer-summary CSV: opaque customer IDs and the fields needed to apply rules you approve. Do not include names, email addresses, phone numbers, passwords, or sensitive documents. The pilot accepts up to 2,000 rows, 384 KB, in USD.
- Does the pilot send messages?
- No. It prepares drafts. You approve, edit, or reject each one. Nothing sends, and the pilot does not write to your source systems.
- How does buying work?
- The pilot is quoted. This page does not start a subscription, and self-serve checkout stays paused. Fleet access, Watch seats, and a Team API are not for sale on this site.
Direct CRM connections, document search, scheduled execution and automatic external enrichment are later capabilities, not active features of this release. Private pilot access requires explicit provisioning and passing isolation checks.