The structure clients actually read: their problem, your solution, exact scope, timeline, price and terms, in that order.
Proposals lose deals by burying the point: pages of company history before the client's problem appears. This template runs the order clients actually read, their problem first (proving you listened), the solution in plain terms, then a numbered scope that doubles as the contract's boundary, timeline, price, and only then your credentials, when the client is already persuaded. The scope section prints a 'not included' line on purpose: the most expensive sentence in freelancing is 'oh, I assumed that was included,' and this prevents it in both directions.
Keep proposals short enough to read in five minutes and specific enough to sign. The acceptance block turns the document into the agreement for straightforward engagements, for large or risky work, a proposal should feed a proper contract drafted or reviewed by a lawyer, not replace one. Pair it with the Invoice Generator and Receipt Template on this site and the whole engagement's paperwork is covered.
How long should a proposal be? For most small-business work: two to four pages. Long enough to scope precisely, short enough that a busy client reads every word.
Should the price be one number or a breakdown? A single clear total with a payment schedule converts best for fixed work; itemize when the client must compare options or approve parts separately.
Is a signed proposal a contract? For simple engagements it commonly serves as one, it states offer, scope and acceptance. Larger engagements deserve a dedicated contract; when in doubt, ask a lawyer once and reuse the answer.