What a winning business proposal must contain
A winning business proposal follows a recognizable anatomy: an executive summary that restates the client's problem in their own words, the context and objectives of the mandate, the proposed approach, a precise scope with named deliverables, a realistic timeline, the responsible team, and an investment stated plainly. Seven blocks, in that order, because each one answers a question the client is already asking: was I understood, how will the work be run, what exactly do I get, when, from whom, at what price. The proposals that win aren't the longest ones — they're the ones where none of those seven questions is left without a written answer.
The executive summary is the most-read section, and often the least polished. It should name the client's problem before presenting the solution, ideally in the vocabulary used during the interview or in the tender documents. Among Québec municipal bodies, one of the open award procedures — the deferred-price-disclosure system — scores the quality of bids first, and only the price of bids that scored at least 70 % on the quality criteria is then considered, per the Gouvernement du Québec. Wherever a scoring grid exists, a summary that opens with a corporate introduction spends its first lines on material no criterion measures.
A poorly defined scope describes an intention rather than a delivered object: 'change management support', 'help with the rollout', 'process optimization'. A well-defined scope names the object, its quantity and its boundary: three half-day workshops, a twelve-page communication plan, two revision cycles, an envelope of 87 to 102 hours. The difference isn't cosmetic: the first wording opens an argument about what's included once the mandate has started, the second closes it before signature. The test fits in one question: would two readers counting the deliverables separately arrive at the same number?
The vocabulary of Québec public tenders is worth adopting even outside the public sector, because buyers already use it. Under the municipal contracting regime, a Québec municipal body must run an open procedure, published in the Système électronique d'appel d'offres (SEAO) and in a newspaper circulated on its territory, above a threshold set at $139,000 until December 31, 2027, those rules being written into its contract management by-law (Gouvernement du Québec). The notice published on SEAO is the avis d'appel d'offres, the package handed to bidders the documents d'appel d'offres, mid-process clarifications are addenda, and the first check is administrative compliance, before anyone reads the content. A private proposal that carries the same markers — file number, issue date, validity period, list of attachments — reads faster because it reads like the others.
A decision made by a committee changes what a proposal must contain. In the municipal deferred-price-disclosure system, the quality criteria are set at the start of the contracting process by the municipal body, then scored by a selection committee formed to assess the compliant bids received (Gouvernement du Québec). The reader doesn't have to be charmed: the reader has to be able to assign points, usually alone, usually in an hour. Every section should therefore map to a named criterion — understanding of the mandate, methodology, team experience, timeline — rather than run as one continuous pitch. A brilliant passage that matches no criterion on the grid earns nothing.
The investment section states amounts before tax, and that is the convention to follow. In Québec, GST at 5 % and QST at 9.975 % each apply to the pre-tax amount, neither one computed on top of the other, and both are collected at invoicing, not in the offer. A proposal showing a tax-inclusive total makes bid comparison harder and ages badly the moment a rate moves. The useful wording is short: total fees, the note that taxes (GST/QST) apply on top, and the validity period of the offer, written out rather than implied. The calculation itself belongs to the billing document, as how GST and QST are calculated on a Québec invoice sets out.
The terms of a professional services mandate group into a small number of stable contract blocks. The set OffrePro drops pre-filled into a new proposal has eight: offer validity, payment terms, exclusions, confidentiality, intellectual property, limitation of liability, termination, governing law. The starting values are geared to professional services — offer valid thirty days, fees payable net thirty days, confidentiality for twenty-four months, fourteen days' written notice for termination, final deliverables becoming the client's property on full payment while pre-existing tools, methodologies and know-how remain the property of their author, engagement governed by the laws of Québec. These are editable starting points, set per proposal, not legal advice. On what gains from being standardized and what must stay bespoke, automating business documents without losing your voice goes further.
A repeatable template shortens the sales cycle without flattening the content that matters: the structure stays fixed from one mandate to the next, only the content of each section changes. OffrePro writes six named sections — executive summary, client context, proposed approach, scope, timeline, team; the investment, for its part, comes from the priced line items — at the end of a six-step path: context, services, phases, responsibles, terms, preview. The timeline is the exception: its figures are computed from the selected phases and never handed to the model, because they are quasi-contractual. The preview allows every section to be reread and edited before it goes out, and a section edited by hand is never rewritten by a later regeneration. Content and prices freeze on send, and reopen only when a change is requested. On how much room to give the model in such a path, where to start with generative AI in an SMB sets the frame.