Notes

How to write a simple service proposal clients say yes to

A useful service proposal is not a performance or a long brochure. It helps a prospective client understand what you heard, what you recommend, what is included and how to proceed. Clarity makes a decision easier without pressuring anyone to say yes.

Start with the client’s actual problem

Before drafting, summarise the outcome the client wants in their own terms. A photographer might be asked for a set of staff portraits before a launch; a VA might be asked to organise recurring inbox and calendar work; a cleaner might be asked for a regular service with particular rooms included. Confirm the deadline, location, decision-maker and any constraints. If information is missing, ask rather than build a proposal on a guess. A proposal that begins with the client’s situation feels relevant because it demonstrates listening. Keep this section short. You do not need to repeat their entire conversation or make claims about what they must do.

A simple proposal structure

Use these headings: client and date; what you understood; recommended service; deliverables; what is included; what is not included; timing and dependencies; price and payment process; how to accept; and questions or assumptions. Keep the order logical, and use ordinary language. If there are options, present a small number with clear differences rather than a maze of add-ons. Make the recommended option easy to identify, but do not conceal what it costs. Save the proposal as a document or message that is easy to read on a phone. Give the file a clear name with the client and date so you do not accidentally send an old version.

Describe the scope precisely

Scope is the heart of a proposal. Replace “social media support” with the actual recurring tasks, frequency and agreed limits. Replace “photography” with session length, location, number or type of deliverables and delivery method where appropriate. Replace “regular cleaning” with the areas and tasks agreed. State what is excluded if a reasonable client might assume it is included. Use boundaries without sounding defensive: “This proposal covers the rooms listed above; inside appliances can be discussed separately.” Make dependencies visible, such as the client providing access, source content or approvals by certain dates. If the scope depends on a site visit or sample task, say so.

Make price and timing understandable

Present the price in the format that matches the work, and state what it covers. Explain any separate costs or choices before the client accepts. Avoid vague phrases such as “starting from” unless you explain what changes the amount. Set out the expected start date, milestones or delivery window, and note what client input is needed. Do not promise a turnaround that depends on an approval you have not received. If the client’s date is uncertain, offer a realistic range and name the point at which it can be confirmed. Payment terms should be written clearly and consistently with your normal process. Do not rely on a verbal explanation to fill gaps in the document.

A copyable one-page outline

Proposal for: [client]
Date: [date]
What I understand you need: [brief outcome]
Recommended service: [plain-language description]
Deliverables: [specific items and format]
Included: [tasks, quantity, frequency]
Not included: [relevant boundaries]
Timing: [start, milestones, delivery]
Client provides: [access, materials, approvals]
Price and payment process: [clear details]
To proceed: [reply, booking step or next meeting]
Questions: [contact method]

Keep the template reusable, but check each bracket before sending. Delete headings that are not relevant and add specifics that matter. A generic proposal with a client’s name inserted is not personalised. The client should be able to tell what happens next without searching through an email chain.

A practical example

Suppose a small business asks for help preparing a photo library for its website. A vague offer might say “branding shoot, full package”. A clear offer says what the session covers, where it takes place, what kinds of images are included, when the gallery is expected and what input the client must provide. It identifies whether extra locations or additional editing are outside the scope. The same principle works for admin support: name the recurring tasks, where requests go, expected response pattern and who approves outgoing work. Specificity does not make a proposal cold. It prevents a friendly yes from meaning different things to each person.

Send and follow up thoughtfully

Before sending, check the client name, date, arithmetic, scope, attachments and links. Read it once as a client: can you find the price, timing and next step quickly? In the email, summarise the proposal and give a reasonable date for questions or a follow-up. If there is no response, send one polite check-in rather than a string of messages. Ask whether they have questions or whether priorities have changed. If they decline, thank them and close your tracker. If they ask for a change, revise the document and label the new version clearly. Never leave two competing proposals both appearing current.

Make it part of your routine

Keep this process somewhere easy to reach and use it the next time the task comes up. The first version is a prompt, not a rule that must survive unchanged. Notice where you hesitate, what information you had to search for, and which step someone else might misunderstand. Update the note while the experience is fresh. A practical process is short enough to use on a busy day and specific enough to reduce avoidable decisions. It should support your judgement, not replace it. If a client’s circumstances differ, confirm the details rather than applying a generic template blindly.

Make ownership and the next action visible. A note that says “waiting” is hard to act on; add who you are waiting for and when you will check again. A checklist should distinguish a completed step from an assumption. If you use a digital tracker, keep only the fields that help you make a decision or remember a commitment. Review the process after a change in your tools, service or client expectations. Small edits keep a practical guide aligned with the work you actually do, rather than the business you imagined when you first wrote it.

Where to go from here

Choose one part of your current process and try the checklist on your next real job. Afterward, note one point that worked and one point that needs clarification. If you would rather start with ready-to-adapt materials, the Quote-to-Cash Kit offers a practical starting point, and the free five-SOP sampler lets you try a few templates first. Adapt any template to your own service and circumstances; these materials are not professional advice.