A small client, such as a ten-person company or a local service business, usually decides on a proposal in a few minutes between other tasks. A long document with a company history, a methodology chapter and three pricing tiers tends to sit unread. A single page that answers four questions gets a reply: what will you do, what will it cost, when will it be done and what happens next.
This article describes a simple structure for that page. It suits marketing and web work such as a new landing page, an email set-up or a lead-handling routine, but the same layout works for most small projects. It is a working template, not legal advice; if the job carries real legal risk, have a contract reviewed separately.
Before you write: one conversation
A one-page proposal depends on a short call or meeting first. Ask three things and write the answers down in the client's words:
- What problem are you trying to solve, and how will you notice it is solved?
- What have you already tried, and what must not change?
- Who decides, and by when do you need to start?
The proposal then opens by repeating the problem in one or two sentences. This shows that you listened and lets the client correct you before any money is discussed.
The page, section by section
1. Scope: what you will do
Write three to six bullet points, each describing a result rather than an activity. "A landing page with a contact form that sends enquiries to your shared inbox" is better than "web development". Use the client's vocabulary, not yours.
Then add a short line headed Not included. This is the most useful line on the page. Typical entries: copywriting beyond two pages, photography, ongoing advertising spend, changes after the final approval. Most disputes on small jobs come from an unspoken assumption, and this line brings it into the open.
2. Price and terms
Give one price for the scope above, in one currency, and say whether tax is included. Small clients rarely want a menu; if you offer an option, offer at most one, clearly marked as optional.
Add the terms in plain sentences:
- when you invoice (for example, half at the start and half on delivery);
- how many rounds of changes are included, commonly two;
- what happens to extra requests: a separate quote, or an hourly rate you state;
- how long the offer is valid, often 14 to 30 days.
If the price depends on something you do not control, such as the client supplying text or access to an account, say so. "The price assumes we receive the text and logo by the date below" is a fair sentence and avoids an awkward conversation later.
3. Timeline
Use calendar dates or "working days from start", not vague phrases like "a few weeks". Three to five milestones are enough: kick-off, first draft, client feedback, final version, live. Show who is waiting for whom at each step. A timeline that only lists your own tasks hides the fact that most delays are waiting for feedback.
4. What we need from you
This section is short and specific: the materials, access and decisions you need, each with a date. For example, "logo and brand colours by Monday", "one person who gives all feedback in a single message", "access to the website account". Name one contact on the client side. Without one person, feedback arrives in conflicting pieces.
5. What happens after yes
End with the exact next step. Make it small enough to do in one message: "Reply 'approved' to this email, and we will send the invoice for the first half and book the kick-off on the date shown." Add what the client will receive within one working day of saying yes, such as a confirmation, an invoice and a short start checklist.
This closing section is where many proposals fail. A reader who agrees but sees no clear step often postpones the reply. For a related habit on the sales side, see handling website enquiries in one working day.
A skeleton you can copy
Proposal: [project name] for [client] Date / valid until: [dates]
The problem: [1–2 sentences in the client's words]
Success looks like: [one measurable sign]
Scope: [3–6 result bullets]
Not included: [2–4 bullets]
Price: [amount, tax note]
Terms: [invoicing, rounds of changes, extras, validity]
Timeline: [4 milestones with dates and who acts]
We need from you: [items with dates, one contact]
Next step: [one sentence the client can act on today]
Keeping it to one page
If the page overflows, the project is probably two projects. Split it: a first phase with its own price and dates, and a short note that a second phase can follow. Cut background text before you cut the "Not included" line or the timeline. Put technical detail in an appendix only if the client asks for it.
Read the finished page as the client would. Can they tell in one minute what they get, what they pay, when it is ready and what to do now? If not, shorten it.
Sending and following up
Send the proposal in the body of an email or as a short PDF, not as a link to a portal the client must log into. Mention the validity date in the email. If you hear nothing, one short follow-up after three or four working days is normal; a calm question such as "Is there anything on the page you would like to change?" works better than a reminder. Once the client says yes, keep the page: it becomes the reference for the project, and it is much easier to point to a line everyone has seen than to a conversation everyone remembers differently.
If you are on the other side and reading a quote from a supplier, see reading a software quote: what to check and three warning signs. After the project starts, onboarding a new customer: a first-two-weeks checklist covers the first steps.
Common mistakes
- Describing activities instead of results. The client cannot tell whether they got what they paid for.
- Leaving out "not included". Unspoken assumptions become disputes.
- Several price options. Choice slows small clients down.
- A timeline without client dates. Delays then look like your fault.
- No next step. Agreement without an action is easily forgotten.
- Sending it without a call. You risk answering a question the client did not ask.
Summary
A one-page proposal for a small client has five parts: scope with a clear "not included" line, one price with terms, a dated timeline, what you need from the client, and one next step after yes. Hold a short conversation first, write in the client's words, and split the work if it will not fit on one page. The page is quicker to approve, and it gives both sides something clear to return to later.
Sources
- Common practice for scoping and quoting small service projects, offered as a practical guide. No client results or market figures are claimed in this article. Adapt the terms to your own business, and have a contract reviewed where the job carries legal risk.
