Launched this week
You send a deck or doc. They ask their AI to read it. The AI sees what's on the page, but not the thinking behind it: why you made those choices, what you left out, or what's still open. Relay shares that context with your document, so they and their AI can understand it and ask questions. You choose what to share. Decisions that need your input, like a discount or a date, come back to you. Try a sample relay. No sign-up needed.









Free Options
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted




we send a lot of proposals at the agency and the first question back is almost always why the estimate is that high 😅 can the context include a cost breakdown that only shows up when someone asks about price
@eldarmiensutov Yes, this is exactly where context helps. Documents are usually high level and meant to be skimmed; the real heavy lifting is done by the context. It’s never shown on the page, and their AI uses it only when it’s relevant, so the cost breakdown comes up when they ask about price.
There’s plenty of room, so add the details, an FAQ, or links it can follow. Mark anything internal, like your margin, as must-ask and it comes back to you instead.
Here’s a sample proposal relay: https://relayto.ai/try/annual-proposal
@eldarmiensutov Eldar, have you got a client proposal going out this week? If you’re up for it, I’d like to help you add the scope and cost reasoning to one real relay and see what questions come back. We can start with an example you’re comfortable sharing.
we see this on websites too, a lot of pricing questions now come from someone's AI assistant. the must-ask list is the part I'd use most. does the sender set it for every relay, or can a team keep one default list?
@olia_nemirovski yup we see pricing as a frequent thing people use agents to ask about. At the moment, the questions & answers context is set for each relay so the sender knows exactly what goes out per relay - though we definitely see value in having an approved set of information that someone on the team can optionally include. And we'll add that in soon for supporting teams!