For research firms
You have subscribers.
Not a mailing list.
Recurring research is a product, and a product needs to know who is entitled to it. A PDF on a distribution list knows nothing — not who opened it, not who forwarded it, not whether they are still a client.
No card required · Unlimited readers · Secure by default
The situation
What this looks like today
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.
Nothing comes back
You cannot tell which notes were read, by whom, or which client is getting value — which is the conversation you need at renewal.
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.
What changes
Deliverd for research firms
Everything below ships today. Where something needs a paid plan, it says so.
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.
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.
Questions
Research firms and Deliverd.
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.
Your clients should not have to open an attachment.
Publish the work to an address instead, and let the people who need it open it with the sign-in they already have.