For consultancies
It's your deliverable.
Not an attachment.
An engagement produces one thing a client keeps: the report. It leaves your firm as a file, gets forwarded, gets renamed, and by the steering committee nobody is certain which version is on the table.
No card required · Unlimited readers · Secure by default
The situation
What this looks like today
Version drift, discovered in the room
Two people open what they believe is the same pack and disagree about a number. The attachment is a copy the moment it is sent, so there is no way to reach the one somebody is holding.
Distribution is a judgement call every time
The client sponsor should see everything, the wider committee should see the summary, and a subcontractor should see neither. With files, that is a person deciding who to put on an email.
A year later, nobody can reconstruct it
When a decision is questioned, what you need is what was recommended, when, and who read it. What you have is a shared drive and a mail archive.
What changes
Deliverd for consultancies
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.
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.
It looks like your firm
Your name and logo, on your own verified domain, with notifications sent from your domain once it is verified. On the paid plans the reader sees your practice rather than ours.
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.
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.
A workspace per client
Segment who can reach what, so an analyst on one engagement cannot browse another. Access is decided per report and evaluated on every request, assets included.
Questions
Consultancies and Deliverd.
Can each client only see their own engagement?
Yes. Give each engagement a workspace and grant access per report. Access is evaluated on every request, including images and other assets, so nothing is reachable by guessing a URL.
What if the client's people are not in any directory we control?
They do not need to be. A share link can require the reader to verify an emailed one-time code before it opens, and can be restricted to their firm's email domains.
Does it carry our branding or yours?
Yours, on the paid plans: your name and logo, your own verified domain, and notifications sent from your domain once its DNS records are in place.
Can we prove what a client was shown?
Views, version changes, access grants and share links are all written to an audit trail you can export. Retention is configurable, and longer on the higher plans.
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.