Don’t just send a doc.
Relay the context and purpose behind it.
One command sends your doc to the person, and the reasoning to their agent.
Your AI writes the doc.
Their AI reads it first.
The file arrives, but the context doesn’t: why this price, what you ruled out, what’s still open. Relay gives their agent the context to explain your work, and a way to send decisions back to you.
How it works
One annual proposal, from Ana to Jordan and on to the CFO. An illustrative example.
Start with what you have.
Ask your agent to prepare the proposal and its context. You can also upload, write, or paste in Relay.
Review both before sharing.
Ana checks the doc, the context and the topics that must come back to Ana. Then Ana shares one link.
The “why” gets answered.
Jordan reads the doc in the browser and asks questions there or in their own agent. Answers draw on Ana’s approved context.
Decisions come back to you.
Routine questions get answered. Discounts and terms come back to Ana, and Ana’s reply returns to Jordan.
Works like a shared doc.
Jordan sends the link to the CFO. The CFO asks, Ana approves with one click, and the CFO’s agent has the full story too.
Ana, in Claude
Before it goes
For Jordan
Annual proposal
For Jordan’s agent
- Why tier 3 and not tier 2
- What the price includes
- Discounts and terms come back to Ana
Jordan, in their agent
Ana’s Relay
Could we do 20% off for a two-year term?
From Jordan, on Annual proposal
Why tier 3 and not tier 2?
Answered from your context
What if we add seats mid-year?
Answered from your context
Ana’s Relay
The CFO asked for access
Jordan sent them the link.
Anything that fits the sentence.
Their agent gets
Need something from them? ask Jordan to relay me their security requirements for the contract