For research firms
AI drafts the note.
An analyst signs it off.
Get every AI-drafted note signed off by the analyst or research director whose name goes on it, before it reaches a subscriber and without chasing them for it. The agent stops to ask them — on their phone or from an email — and goes on when they answer. Subscribers then open the approved note at one address, entitled per client, with the figures refreshed in place.
No card required · Approvals on every plan · Secure by default
What you get
What Deliverd changes for research firms.
The research director's sign-off, without the chasing
The agent asks the analyst or director who puts their name on the note and carries on with their answer — approve, correct a figure, or send it back with a reason.
How: Your AI asks before it acts ↓Subscribers get the note that was signed off
Nothing reaches subscribers until someone with the authority has said so, and each client opens it at one address that knows who they are.
How: Sign-off before it leaves ↓A thesis that keeps its thread for weeks
The objective and where the work stands live apart from any one session, so the next draft — in another tool or another model — starts where the last one stopped.
How: The work keeps its objective ↓The situation
What this looks like today
The agent drafted it; the analyst has to stand behind it
A note goes out under an analyst's name with a model's first draft inside it. Without a step where the agent stops and asks, the only review is whoever happens to read it before it is sent.
The list is the only access control
Entitlement lives in whoever maintains the distribution list. A client who churned last quarter is one stale row away from still receiving the work they stopped paying for.
The numbers age faster than the analysis
The argument holds for a quarter; the figures underneath it are stale in a week. Reissuing the whole note to update a table means it goes back through review for no good reason.
How it works
Deliverd for research firms
Everything below ships today. Where something needs a paid plan, it says so.
Your AI asks before it acts
An agent that needs a decision puts it to a named person and waits: what it wants to do, why, how risky it is, and what to read first. They approve, approve with changes, reject with a reason, or ask the agent a question — on the page, from an email link, in Slack or Teams, or from a push notification on a phone — and a colleague can cover their approvals while they are away. It can also ask for a review, or for information it is missing, the same way.
Sign-off before it leaves
A publishing rule can hold work for a partner's approval: the version is stored and scanned, the client sees nothing until someone with the authority says so, and the decision is on the record. Off by default; switch it on for agent publishes, for anything addressed outside the firm, or both.
An address, not an attachment
The work lands on a URL you can send. It stays put, so the link you shared at the kick-off still opens today's version rather than a copy of what it looked like in March.
Numbers that refresh without reissuing
A published report can hold its own dataset, updated over the API on whatever cadence you choose. The narrative stays fixed and reviewed while the figures underneath it stay current.
The work keeps its objective
A task holds what the work is for apart from the conversation doing it, with a short state — where it stands, the next action, what is in the way — that any agent reads when it resumes. Side tasks take a bug or a piece of research out of the main thread and come back with a result. Switch tool or model and the next one picks up where things stand instead of starting over, and only a person changes the objective.
Included in Team, Business Starter, Business and Enterprise
A record of who opened it
Views, versions, access changes and share links are written to an audit trail you can export — which is the difference between believing a client saw something and being able to show it.
Opened with the client's own sign-in
Readers authenticate with the identity their organisation already uses, including SAML and OpenID Connect single sign-on. Nobody gets a password to remember, and nobody gets a file to leave with.
Every version kept, one URL
Reissuing updates the address and keeps what was there before. You can see what changed between two drafts and roll back if the new one is wrong.
External readers, verified by one-time code
A reader outside any directory gets a link that emails them a code before it opens. Links can be restricted to named email domains, so a forwarded one does not become an open one.
Inside the client's own intranet
Allow a SharePoint site by origin and a report can be framed on a page there. It is still served and access-checked here, so the page shows the report to the people who may open it and a sign-in link to everyone else.
Questions
Research firms and Deliverd.
Can the agent ask an analyst or the research director to sign off before a note goes out?
Yes. The agent asks the named analyst or research director with request_approval and waits for the answer — approve, correct a figure, reject with a reason — from a phone or an email link. A publishing rule can also hold every publish for approval, so nothing reaches subscribers until someone with the authority says so.
How do the numbers update without republishing?
A report can carry its own datasets, written over the API on whatever schedule you like, and read by the report when a reader opens it. The reviewed narrative does not change; the figures it draws are current.
Does that mean an old version shows old numbers?
No, and this is worth knowing before you rely on it: a version is immutable but its data is not, so rolling back to an earlier version renders that version's wording against today's figures.
Can we see which clients are actually reading?
Yes. Views are recorded per report and surfaced in analytics on the plans that include it, and the underlying trail is exportable.
Can an agent write the note and publish it?
Yes — over MCP, the REST API or the CLI. An agent identity can be scoped to a single workspace and can never grant public access, so an automated pipeline cannot widen distribution.
The analyst's name is on it. The analyst should have said so.
Let the agent draft the note, put the sign-off in front of the analyst, and send subscribers an address that knows who they are.