01
Connect sources
Link approved document stores and tools so the agent only retrieves from files your organisation already controls.
Drive, files, shared workspaceALPHAMATCH PRODUCT / Curiosity
Turn your company knowledge into answers your team can verify.
Curiosity connects approved documents and tools, then gives teams cited answers and useful next steps within the workflows they already use.
- Cited answers from your files
- Source-aware agent status
- Works with existing document stores
Agent workspace
Cited answers with sources your team can open.
Ask across approved files. Curiosity returns a verifiable answer, source chips, and an agent status your team can check before acting.
Workflow
How the work moves.
02
Ask and verify
Teams ask in natural language and receive cited answers with source chips they can open before they trust the output.
Cited answer panel03
Move work forward
Use the verified answer to draft the next artefact, hand off a task, or keep a background agent watching the same sources.
Agent status and next step Capabilities
Capability groups, not a feature dump.
Enterprise retrieval with citations
Answers are grounded in your documents, then shown with source chips so reviewers can check the original file.
Source list beside every answer
Shared document workspace
Keep institutional knowledge in one workspace so teams ask against the same approved set of files.
Organisation-level document sidebar
Background agents
Schedule follow-up work on the same sources instead of restarting every question in a blank chat.
Agent status: Ready / Needs review
Existing-system fit
Connect files where they already live rather than forcing a migration before the first useful answer.
Google Workspace and custom connectors
Control
Built around your control model
Curiosity is implemented against your document permissions, review checkpoints, and the rule that your files are not used to train models.
- Existing-system integration with approved document stores
- Organisation access controls on conversations and files
- Source and document permissions stay with your workspace
- Encryption in transit and at rest, with implementation support
- Your data is not used to train models
Evaluation
Where Curiosity is the better fit
Use this only when you are comparing a company-knowledge agent with a general chat tool or a manual search process.
| Capability | General-purpose tool | Existing process | Curiosity with AlphaMatch implementation |
|---|---|---|---|
| Answers grounded in company files | Depends on what was pasted in | Manual search | Cited sources from approved stores |
| Source verification | Not supported | Reviewer finds the file | Source chips beside the answer |
| Background follow-up | Not supported | Manual reminders | Configurable agents |
| Shared workspace control | Personal chats | Shared drives only | Organisation workspace with permissions |
Next
Bring one knowledge workflow to the conversation.
We will assess the document sources, permissions, review controls, and implementation work involved—then advise whether a product working session, pilot, or wider delivery plan makes sense.
Which knowledge workflow are you looking to improve?