“Which campaigns wasted spend last week?”
A ranked finding with the reporting period, spend and revenue definitions, supporting rows, and a proposed follow-up Task.
Agent
Use Vendo’s Agent or connect Claude and Codex through subscriptions your team already has. Agents investigate, create reports, and run Automations. People review important Approvals.
Inside the workspace
The Agent keeps the answer, evidence, proposed next step, and human review together instead of ending at a block of generated text.

No SQL, no waiting on an analyst. The Agent answers from your Vendo data, respects your access rules, and asks when a business definition is unclear.
Ask about attribution, spend, revenue, LTV, jobs, and data quality in plain language — get answers, not exports.
The Agent prepares options grounded in your data and documents, with the evidence attached so you can judge them fast.
Refresh data, build reports, investigate results, and run Tasks through conversation. Each Agent only sees the data and tools you allow.
Describe the result you need and the Agent drafts the query, model, or report. You review it before it ships.
Practical workflows
Vendo maps a business request to the underlying data, definitions, tools, and controls required to complete it.
A ranked finding with the reporting period, spend and revenue definitions, supporting rows, and a proposed follow-up Task.
A source-aware investigation covering freshness, attribution, conversion delivery, and the assumptions behind the comparison.
A reusable group definition, estimated size, exclusions, destination requirements, and an Approval before delivery.
Refreshed models and charts, a drafted narrative, visible caveats, and the activity trail for every completed step.
Assign work to a person, the Vendo Agent, Claude, or Codex. Every handoff, status change, review, and result stays in one activity trail.
Assign a Task to a teammate, the Vendo Agent, or a connected client such as Claude or Codex.
Move work from planned to in progress, review, and complete without losing the brief or evidence.
See who created, assigned, changed, reviewed, and completed the Task — person or agent.
Schedule repeatable checks, report refreshes, and customer-group updates with every run recorded.
Agents prepare the recommendation, evidence, and next step. A person approves, rejects, or asks for revisions before anything becomes an outbound change.
A Task or question surfaces a finding from your data.
The item lands in your queue with the evidence and context attached.
A person approves, rejects, or requests changes. Approved items can continue into execution.
The work runs and records its status, so you always know what happened and when.
Recommendations land in one queue with their evidence, owner, and status — ready for a person to review.
Choose what happens next, reject what does not fit, or send the work back to the Agent with feedback.
Save context once — your goals, naming rules, quirks — and the Agent remembers it in every later conversation.
A recommendation cannot become an outbound change until a person approves it.
Built for trust
Check any answer against your workspace definitions, source freshness, permissions, and job history — the evidence is one click away. The same Foundry tools and workspace controls provide the evidence — and you make the call.
Answers use your shared metric definitions, and every answer shows which definition and time range it used.
See the recency, volume, and structural checks behind the data — so you know the inputs are solid.
The Agent works from your tools, prepared tables, documents, and saved Memory — always within your permissions.
Agents prepare and recommend. A person decides whether to approve, reject, revise, or act.
Vendo exposes its tools over MCP, so Claude, Codex, and other MCP clients can use the same Insights, Automations, and Approvals — always scoped to the permissions you grant, never more.
FAQ