How to outline a proposal around the customer's actual requirements
A proposal outline connects a customer's problem to a defined approach, scope and next step. It is useful before investing time in detailed copy or a finished commercial document.
Start with the right material.
- What you provide
- an opened client brief plus user-supplied scope and prices.
- The intended result
- Create a non-binding proposal outline with unresolved scope clearly marked.
How the workflow works.
Map each supplied requirement to a proposed section and identify the evidence or input that section needs. Keep deliverables, exclusions, responsibilities and pricing assumptions easy to find.
What to check in the result.
Review the outline with the people who would deliver the work. Attractive wording should not turn an optional service, an estimated date or an unconfirmed capability into a contractual commitment.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.