Persuasive messages and proposals

Much of working life involves persuading people: convincing a manager to fund a project, a colleague to help, a customer to buy, a client to accept a proposal, a committee to change a policy. Persuasion in business is not manipulation. It is the honest work of showing people why an action is in their interest and making it easy for them to act. This lesson covers the foundations of persuasion, the AIDA pattern for persuasive messages, internal requests, sales messages and the structure of business proposals, including how to build and present a budget.

Foundations of persuasion

Aristotle identified three modes of persuasion more than 2,300 years ago, and they still describe how business arguments work. Ethos is credibility: the reader must trust the writer's competence, honesty and goodwill. Logos is logic and evidence: facts, figures, examples, comparisons and reasoning. Pathos is emotion and values: connecting the request to what the reader cares about, such as security, pride, fairness or the well-being of customers and staff. Strong business persuasion uses all three, with logos usually in the lead and ethos and pathos supporting it.

Research on influence, popularized by the psychologist Robert Cialdini, identifies principles that make people more likely to say yes: reciprocity (we return favours), commitment and consistency (we act in line with what we have already said), social proof (we follow what similar people do), authority (we defer to credible experts), liking (we say yes to people we like and who are like us), scarcity (we value what is limited) and unity (we favour people we see as part of our group). These principles are powerful, which is why they must be used honestly. Fake scarcity ("Only 2 left!" when there are hundreds) or fabricated testimonials are not only unethical but, in many cases, illegal.

The AIDA pattern

The AIDA pattern organizes persuasive messages in four steps: gain the reader's Attention, build Interest, create Desire and prompt Action. In practice, interest and desire often merge into one section that explains the benefits and supplies evidence. The pattern works for sales letters, fundraising appeals, internal requests to an uninterested reader and even cover letters (lesson 11).

Benefits, features and evidence

Features describe what a product or proposal is; benefits describe what it does for the reader. "256-bit encryption" is a feature; "your customers' card details are protected to banking standards" is a benefit. Lead with benefits and support them with features as evidence. Then strengthen the case with evidence the reader will trust: specific numbers rather than vague claims, independent sources, case studies, testimonials from real customers, demonstrations, free trials and guarantees. Anticipate objections and answer them before the reader raises them; addressing the strongest counterargument openly also builds ethos.

Persuasive requests inside the organization

Internal persuasion often goes upward (to a manager or committee) or sideways (to a colleague in another department who owes you nothing). For upward requests, managers want to know the problem, the proposed solution, the cost, the benefits, the risks and how the request supports the organization's goals. Present your case as a business case, quantify where you can and offer options. For lateral requests, emphasize shared goals and what the colleague gains, keep the request small and specific, and make it easy to say yes.

Business proposals

A proposal offers to solve a problem or meet a need, usually in exchange for money. Proposals may be solicited, written in response to a request for proposals (RFP), or unsolicited, offered on the writer's own initiative. They may be internal (asking your organization to fund a project) or external (offering services to a client). Solicited proposals must follow the RFP's instructions exactly: required sections, page limits, formats, deadlines and evaluation criteria. Many public-sector RFPs score proposals on a points system, so a proposal that ignores a required section can be disqualified regardless of its quality.

In Canada, federal government opportunities are posted on CanadaBuys, and provinces and municipalities run their own procurement portals; trade agreements such as the Canadian Free Trade Agreement set rules for open, fair tendering above set thresholds.

Persuading a resistant or sceptical reader

When the reader is likely to resist, open with common ground rather than the request: a goal you share, a problem you both recognize or a fact the reader already accepts. Then present the evidence, deal openly with the strongest objection and only then make the request, scaled so that saying yes feels safe. A small first step, such as a three-month pilot, a trial with one team or a review date, lowers the perceived risk and draws on the commitment and consistency principle. Offer options where you can, because people resist being cornered more than they resist change itself. Finally, respect the reader's right to say no: persuasion that leaves a decision-maker feeling manipulated wins one argument and loses the relationship. If the answer is no, ask what evidence would change it, and come back with that evidence later.

Honesty and the law in persuasive messages

Persuasive messages must be truthful. In Canada, the Competition Act prohibits false or misleading representations to the public, including misleading prices and drip pricing (advertising a price that cannot be obtained because of mandatory extra fees), and amendments in 2024 added rules on unsubstantiated environmental claims (greenwashing). The Competition Bureau can seek penalties, and the Act also allows private parties to seek orders in some cases. Commercial electronic messages are also subject to Canada's anti-spam legislation, CASL (lesson 12).

Beyond the law, persuasion depends on trust. Exaggerated claims may win one sale but lose the customer. A useful test is whether you would be comfortable if the reader later learned everything you knew when you wrote the message.

Portfolio task for lesson 6: write a one-page persuasive request to a decision-maker in an organization you know, asking for a resource (equipment, training, a process change). Use the AIDA pattern, include at least one calculation (savings, payback or cost per person) and answer one likely objection.