A good proposal often contains the clearest explanation of what a buyer needs to decide. It may show why a delivery date depends on approval, why two similarly named outputs take different work, or what the customer should prepare before an assessment. Bring those explanations onto the website when they answer a question other buyers face. Rebuild them around the current service and leave negotiated terms in the proposal.
Start with a question that has come up more than once. Find the part of the proposal that helped the buyer understand the answer. Then confirm which part is a normal service rule, which depends on circumstances and which belongs to that client alone. The useful material is usually the reasoning behind the answer.
Disclosure. AI Visibility is published by Lunasol, which offers GEO and AEO services. The proposal examples below are fictional. The guide uses public sources and does not reproduce client material. About AI Visibility
Find the explanations that change a buying decision
Ask the team which sections buyers return to during a proposal review. Look for a question whose answer affects service choice, preparation, timing or the scope of work. A passage about a client's background may be important to that document. A paragraph explaining which files a customer receives may help many buyers before they ever request a quote.
Group candidate passages by the underlying question. One buyer asks whether the finished video can go on two channels. Another asks what the supplier means by “two versions.” These may share a decision about how outputs are counted. Keep that decision in the content brief and remove project-specific details from the working example. Use enquiries or a conversation with the service owner to confirm that the issue recurs.
The UK Office for National Statistics' content guidance recommends grounding user needs in evidence such as research, existing material and input from people who work with the audience. A proposal library can provide one part of that evidence. A polished explanation alone tells you little about whether prospective buyers need it. Record the question it answered and how you know that question comes up elsewhere. ONS guidance on designing content for user needs
Separate the general rule from the agreed deal
Mark the passage in three parts. Identify the explanation that applies to the normal service, the conditions that make it vary and the terms agreed for this particular client. Verify the first two with the operational owner. Retain the third in the private record. A negotiated turnaround, concession or extra round of work can sound like a standard promise when the surrounding deal disappears.
Australia's business.gov.au quote guidance lists scope, itemised costs, variations and expiry among the items a written quote can include. That is a useful example of how much specific material a quote may carry. When adapting the underlying explanation for a service website, preserve conditions that affect a buyer's choice and write a fresh example where the original depended on a private deal. Business.gov.au guidance on preparing quotes
| Proposal passage | Public question to answer | Treatment |
|---|---|---|
| Several formats and one project-specific delivery date | What counts as a distinct output? | Explain the unit and keep the private date out |
| A discounted line for an extra service | Which work needs a separate quote? | Confirm the ordinary scope and leave the negotiated figure private |
| A named customer approval and sign-off deadline | When does the delivery schedule start? | Explain the triggering event with current operating conditions |
| A bespoke exception for a single venue | What happens if a site needs special access? | State the normal requirements and explain how exceptions are assessed |
Check the source before describing a condition as standard. The proposal writer may have used a project-specific workflow to make one deal work. Ask the delivery team to identify recent ordinary cases that follow the same rule. If the answer varies across service lines, restrict the public explanation to the one you can verify or explain how the team confirms it during scoping.
Rewrite the explanation for someone without the proposal
Open with the buyer question, then explain the condition and the action. A private passage might read, “Two further edits are included in the package above.” A public reader has no package above and may interpret “edit” as either another revision or another delivered file. Define the word and tell the reader when the team agrees the number of outputs and revision rounds.
Lunasol's public video quote comparison guide distinguishes outputs by their intended use and by the work needed to create them. It contrasts resized exports with more substantially edited versions in a worked brief. That is an example of a public explanation that can help a buyer describe what they need before asking for a proposal. The public article is a related-party example. It provides no evidence about how a particular private proposal was reused. Lunasol's video quote comparison guide
Test whether the public sentence can stand on its own. Replace references to earlier emails, annexes and named parties with what the reader needs to know. If a price, time or inclusion depends on a condition, put the condition beside it. A verified official Brewing Gadgets Instagram post offers a simple analogy. Its caption describes a UAE promotion on selected Compak grinders with a stated end date of 9 November 2026. A summary that drops “selected” or the date changes what the offer appears to cover. Keep the same care when moving a qualified explanation from a proposal to a page. Official Brewing Gadgets Instagram post
Choose the page where buyers need the answer
Place a decisive inclusion on the service page, where buyers are checking fit. Put an explanation of approvals and timing on the process page if it helps customers recognise their stage. Add a prompt to an enquiry form if the answer changes what the buyer needs to supply. A guide is useful when the question calls for a fuller comparison or worked example.
Check for an existing answer before adding a new page. The best passage may improve a short section that customers already reach. Keep one maintained explanation of the operational rule and adapt the surrounding context to each page. If a short version needs a link, name the destination so readers know whether they will find scope, preparation instructions or the process after approval.
Consider a fictional printer whose proposals explain why proof approval affects the ready date. A public process page could say that the production schedule is confirmed after the customer approves the correct proof, assuming the operations owner confirms that rule. The service page could add a brief link near delivery information. The enquiry form could ask whether the buyer has a fixed opening date. Each placement serves a specific moment in the purchase without publishing any client's proof or schedule.
Try the conversion in a short workshop with one salesperson and one person who delivers the service. Give them the same extract and ask each to mark the sentence they would want a new buyer to read. Compare their choices. Sales may choose the reason two options cost different amounts, while delivery may choose the required input that makes one option possible. Both can be useful if they answer distinct questions and lead the reader to the right page.
Capture the evidence for each public sentence while you have both people in the room. The scope statement may come from a current service specification. A timing condition may need an owner to confirm how the team handles missing inputs. The proposal passage tells you what was explained to one buyer. The operating record tells you what the business can say to the next one.
When the proposed change is small, compare the page before and after in the same buyer scenario. Can the reader distinguish a revised file from an additional deliverable? Can they tell which deadline they need to share before asking for a date? Record the sentence that changed their answer. That gives the next editor a reason to keep the explanation when the page is redesigned.
Check for private clues in the final package
Read the candidate material for names, addresses, prices, attachments and distinctive combinations of details. Rewriting a sentence can still preserve a recognisable project when it carries an unusual location, exact date and deliverable. Use a fresh illustrative example when the lesson does not depend on the original case. Label the example so readers understand what it represents.
Review assets and previews as well as the main copy. A screenshot of a quotation may show a hidden email address, revision history or file name. A copied table may still contain a client-specific scope note. Build a new public table from approved material and inspect the version a reader will see. Keep the source mapping in the restricted editorial record so the writer can verify the wording without including that source in the public page.
If a specific client example is essential, use the applicable release review before publication. Separate permission to use a project name from permission to use figures, quotes or images. If approval is limited, explain the general rule or use a different example. The public explanation should work for a buyer who has never seen the underlying proposal.
Check that the website and proposal tell the same story
Use the same labels for the main service, outputs and approval stages. When the website explains what determines a quote, the proposal should show those decisions for the individual buyer. When the site explains who supplies an input, check that the proposal assigns it to the right party. If a business makes an exception, record it as an exception in the private document so the public rule remains intelligible.
Proposal explanation publication record
- Recurring buyer question and where it arose
- General rule, conditional factors and private terms
- Operating owner and current evidence for the public wording
- Destination page and related proposal wording
- Public example and any release approvals
- Preview, language versions and contact path checked
- Review date and trigger for an update
Ask someone unfamiliar with the source proposal to read the public paragraph and apply it to two situations. One should fit the standard case. The other should need a clarification or an exception. Then ask the sales and delivery teams what they would tell those buyers. If the public reader expects a promise the staff would not make, revise the wording and repeat the check.
After release, record the questions that still recur. A new paragraph may resolve one issue while exposing another, such as who supplies assets or when a new version counts as extra work. Review the conversations where the explanation was used and update the maintained page when the underlying rule changes. The website can answer common buying questions early, while the proposal remains the place to agree the particular job.



