The Tendering Survival Guide - Tip #3

08 Feb 2019
|

Battling for tenders can be a survival-of-the-fittest situation… well, the fittest and the most persuasive.

Continuing our PCPC series (position, comply, persuade, competitively price) this month we’re exploring how to write persuasive bids.

 

Tip #3: Persuasion

Now, when we say persuasion, we don’t mean hyped-up salesy documents full of jargon and self-flattery. We mean creating a compelling narrative that:

  1. Establishes that you completely understand the client and what matters most to them;

  2. Demonstrates you are perfectly suited for the job and ideally matched to the client and their needs;

  3. Inspires and connects with the client at a deeper level.

Put yourself in the shoes of the client. What keeps them awake at night? What inspires and excites them? And, with this at the forefront of your mind, ask yourself why you are suited, ahead of the competition, to do that job in that way for that client.

Ultimately, the tendering process is about matching problem-solvers (you) with people who have problems (your clients). So, your job when writing a persuasive bid is to clearly demonstrate that you best understand the client’s problem and have the best solution for that problem.   

 

Tender survival challenge for the month:

Think of a significant product or service you have purchased recently.  

What got you over the line?

What sort of language did their marketing material use to persuade you that theirs was the best solution to your problem?

How did they emphasise with your pain points or aspirations?    

 

With the right perspective and the right techniques you can write more persuasively. 
Let our experts teach you…

Become a Bid Master

| There’s a tender response workshop coming to a place near you. Master your tender writing process. Win more tenders! Book now >

Download the complete survival guide

Our Tendering Survival Guide provides a clear strategy to make sure your bid reponses are out-performing the competition.

Leave a comment

Fields marked * are required