T Bruce Studio practical guide · Proposal quality control · Reviewed 2026-10-30
A credible proposal should help the reader answer four questions: What problem are we solving? What exactly will be delivered? What does it cost? What happens next? More pages do not automatically make it more convincing.
1. Open with the client's problem—not your biography
Use two or three sentences to restate the client's goal in specific language. Avoid claiming you have researched their market unless you actually have. For example: “Your team is copying sales totals between three spreadsheets each Friday. The goal is one reviewable weekly report with fewer manual steps.”
2. State the desired outcome clearly
Replace vague aims such as “improve efficiency” with a deliverable the client can evaluate, such as “an editable report template and a documented handover procedure”. Separate the thing you will deliver from any wider business outcome you cannot guarantee.
3. Define what is included
Name the exact files, number of rounds, data sources and types of changes. A useful scope might say:
4. State exclusions explicitly
List what is not covered: new research, legal or compliance certification, external integrations, extra rounds of revision, additional languages or changes to other documents. Clear exclusions protect both the buyer and the provider.
5. Separate supplied facts from assumptions
If a claim includes market share, return on investment, savings or third-party statements, identify its source or mark it as an assumption. Do not invent success statistics, testimonials, customer names or citations to make a proposal appear stronger.
6. Give the price and what triggers extra work
Say whether the fee is fixed or estimated, what currency applies and what happens if the project grows. Avoid hiding important commercial conditions in a footnote. If tax treatment or local legal terms matter, confirm them appropriately.
7. Specify dependencies and a realistic sequence
What must the client provide? What constitutes a complete brief? What will cause a pause? Explain the order of work and whether delivery depends on feedback, access or validated source material. Do not promise a turnaround you cannot support.
8. Set acceptance criteria
Describe how both sides will know the work is finished. For example, “all supplied sections preserved; editable document delivered; headings consistent; numbers not changed without evidence; one revision for errors within the agreed scope.”
9. Finish with one unambiguous next step
Specify whether the reader should approve a fixed scope, provide missing information, sign a contract or open a secure checkout. A good proposal does not force someone to guess how to proceed.
The final five-minute quality pass
- Read only the headings. Do they tell a coherent story?
- Find every number and named claim. Is it supported or clearly qualified?
- Remove repeated promises and unnecessary technical jargon.
- Check that scope, deliverables, price, exclusions and acceptance are consistent throughout.
- Open the document on a phone and on a laptop if possible; check tables, page breaks and links.
- Confirm the attachment is the correct version and contains no internal notes or tracked changes meant to remain private.
Run the existing draft through the free Document Clarity Checker for a first-pass structure and readability review. The tool does not check factual accuracy or replace professional judgement.
If your existing proposal needs a professional edit and is within scope, Document Finish · R1,490 provides a bounded editing service with one included revision. It is not a new research or professional-certification service.