PolicyOS

Whose logo is on your quote?

Your team put real work into that quote. Someone chose the markets, compared the coverage, checked the limits and wrote a recommendation the client can act on. Then the quote leaves the building as a PDF attached to an email.

So here is a practical question for anyone who runs policy operations: when your client opens that quote, whose logo do they see?

What the client actually sees

An emailed PDF does not open in your agency. It opens in a reader. Usually that is Adobe's. If the quote goes out for signature, it may be DocuSign's.

Either way, the window around your quote belongs to someone else. Their name sits in the frame. Their toolbar runs along the edge. And now there is one more thing on screen: their AI button, placed right on top of your document.

Your logo is still there, somewhere on page one. But the client's experience of the quote is wrapped in another company's brand from the moment they open it to the moment they close it.

The button on top of your quote

The logo question matters on its own. The AI button is where it starts to cost you.

Clients have questions about quotes. That is normal, and it is good. "What does this exclusion mean?" "Why is this deductible higher than last year?" "Do I need this endorsement?" Those questions are where a quote turns into a conversation, and where a conversation turns into a bound policy.

When the quote is a PDF with an AI button on top, the easiest place to ask that question is the button. The client asks the reader's assistant about the PDF, gets an answer of some kind, and moves on.

You never hear the question.

You do not know it was asked. You do not know what answer came back. You do not get the chance to explain why you recommended what you did, because the conversation happened in someone else's tool, under someone else's name.

That is the core of the "Your quote. Their AI." problem: the PDF hands your client to the reader's AI, and the questions that should come to the agent go somewhere else.

It is tempting to treat this as a design issue. Put the agency logo in the header, pick the right colours for the PDF template, and the job is done.

But the client does not experience a quote as one page. They experience a sequence of screens:

  • The quote itself, where they read what you are offering.
  • The questions they have while reading it.
  • The signature, when they agree to go ahead.
  • The payment, when they make it real.

Each of those screens is a moment where the client decides, quietly, who they are dealing with. If the quote is in Adobe's frame, the signature is in DocuSign's frame and the questions go to an AI assistant in a toolbar, the agency has shown up on a few pages of a document and nowhere else.

What PolicyOS does instead

PolicyOS sends the quote as a link under the agency's name, not as an attachment that opens in someone else's reader.

When the client follows that link, they see the agency's name and colours. Not a reader's chrome. Not someone else's toolbar. And that holds on every screen the client touches:

The quote. The client reads the quote on a screen that carries your agency's name and colours, from the first line to the last.

The questions. When the client has a question about the quote, it comes to the agent. Not to an assistant bolted onto a PDF reader. The person who built the quote is the person who hears what the client is unsure about.

The signature. Signing happens on a screen with your agency's name and colours, not in a separate tool's frame.

The payment. Payment happens under your name too, so the last step of the process looks like it belongs to the same agency as the first.

The point is consistency. One agency, one look, from the quote to the payment, with no point along the way where the client is handed to another brand.

Why the questions matter most

Of those four screens, the questions are the one most agencies underestimate.

A question about a quote is a signal. It tells you what the client cares about, what they do not understand, and what might stop them from going ahead. An agent who hears that question can answer it with context: the client's history, the reasons behind the recommendation, the trade-offs between options.

A question that goes to a reader's AI is a signal you never receive. Multiply that across every quote your team sends, and it adds up to a lot of conversations that never happen.

PolicyOS is built so that those questions come back to the agent, under the agency's name.

A quick check you can run today

You do not need new software to see the problem. Take the last quote your team emailed and open it the way a client would.

  1. Count the logos. How many belong to your agency, and how many belong to the tools around the document?
  2. Find the AI button. Is there one on screen? Where would a client's question go if they clicked it?
  3. Follow the signature. Whose name is on the screen where the client signs?
  4. Follow the payment. Whose name is on the screen where the client pays?
  5. Ask who hears the question. If the client is confused by a line in the quote, what is the easiest path for them to ask about it, and does that path end with your agent?

If the answers point to other companies more often than they point to yours, your quote is carrying someone else's brand.

Keep the quote, and the conversation, under your name

The quote is your work. The client relationship is your business. Neither should be framed by someone else's software, with someone else's AI waiting on top.

PolicyOS shows the agency's name and colours on every screen the client touches, and sends the questions to the person who can actually answer them.

See how it works, and why emailed PDFs are losing agencies the conversation: https://policyos.io/dont-lose-quotes-to-ai