Is the persuasive narrative tender dead?

How to inject compelling messages into data-driven and AI-shaped RFP formats

Lately I’ve been working on tenders where the RFx requirements feels almost… like it was created by a robot.

Instead of a flowing proposal document, the process increasingly looks like this:

• dozens (sometimes hundreds) of structured questions

• strict character limits

• spreadsheet uploads

• drop-down compliance fields

• submissions through procurement portals with limited formatting.

Many of these RFPs are clearly designed with data extraction and structured evaluation in mind.

It raises an obvious question.

Is the persuasive tender narrative dead?

Traditional proposals often relied on narrative.

You could build a story through:

• a strong executive summary

• a clear explanation of the client’s problem

• examples of how your team solved similar problems

• a description of your approach and why it works.

Modern RFPs often break this apart.

Instead of a flowing narrative, the response is fragmented across dozens of short questions and compliance tables.

But the persuasive narrative is not dead.

It has simply changed shape.

Why so many RFPs now look like databases

Another trend I’ve noticed recently is the growing appetite for reams of structured data, particularly from incumbent providers.

Procurement teams are increasingly asking for detailed operational information such as:

• volumes of matters handled

• turnaround times

• staffing ratios

• cost breakdowns

• service levels

• performance metrics.

In some cases the requests go much further, with incumbents being asked to provide years of historical operational data.

Why?

Because many organisations are starting to feed that information into the maw of analytics tools and AI systems.

The goal is often to:

• benchmark supplier performance

• model service delivery scenarios

• compare bidders using consistent metrics

• identify opportunities for cost reduction or process improvement.

In other words, the tender response is not just a proposal anymore.

It is increasingly treated as a structured data source.

That explains why so many RFP formats now feel highly structured. The procurement process is being designed so information can be easily extracted, compared and analysed.

But numbers alone rarely tell the whole story.

They still need context.

They still need explanation.

And they still need to connect to the outcomes the client actually cares about.

Procurement formats have changed, but evaluators haven’t

Even the most structured procurement process eventually comes down to human judgement.

Evaluators are still trying to answer the same questions they always have:

• Do these people understand our problem/s?

• Can they actually deliver the work?

• Are they better than the other bidders?

• If we choose them will we get a good return on our investment?

A spreadsheet of answers rarely resolves those questions on its own.

What evaluators are really looking for is confidence.

Confidence comes from clear explanations backed by credible evidence.

Years ago I wrote that strong tenders are built on compelling stories supported by concrete evidence.

That principle still applies.

The difference today is that those stories often need to be delivered in smaller, sharper fragments.

The real shift: narrative to structured persuasion

Traditional tenders often allowed a firm to develop a persuasive case over several pages.

Modern RFP formats increasingly break that narrative into pieces:

• describe your methodology (400 words)

• provide a relevant example (250 words)

• outline governance arrangements (table format)

• upload policies and supporting documents.

The narrative still needs to exist.

But now you have to carry the persuasive thread across multiple short answers rather than one flowing document.

This requires a different discipline.

Think of it as structured persuasion.

Four ways to inject persuasion into data-driven RFP formats

1. Start with the message, not the background

When space is tight, many teams begin responses with background information.

Instead, start with the main message.

Weak opening:

Our firm has extensive experience delivering investigations for government clients.

Stronger opening:

Our investigations model reduces case resolution time by an average of 28 percent while maintaining evidentiary standards required for litigation.

The same principle applies across professional services.

A law firm responding to a litigation panel tender might say:

Our commercial litigation team resolves more than 70 percent of disputes before trial through early strategic intervention.

An accounting firm responding to an audit tender might say:

Our audit approach identifies material risk areas within the first two weeks of fieldwork, allowing issues to be addressed well before reporting deadlines.

Each example starts with a clear outcome or benefit, not background.

2. Use micro-stories rather than long narratives

Where a traditional proposal might include a lengthy case study, many RFP questions now allow only a few hundred words if you’re lucky.

You can still tell a persuasive story using a simple structure:

Problem
Action
Result

Investigation services example:

A national insurer faced a backlog of more than 400 suspected fraud matters.
Our investigation team implemented a triage model combining surveillance, digital investigation and rapid reporting.
Within six months the backlog reduced by 63 percent and the insurer recovered more than $4 million.

Law firm example:

A government agency faced a complex class action involving multiple jurisdictions.
Our litigation team coordinated a national strategy across three courts and resolved the matter through mediation within nine months, avoiding prolonged litigation.

Accounting firm example:

A regional council struggled with delays in finalising its annual financial statements.
Our audit team redesigned the audit timetable and introduced earlier risk identification meetings with finance staff.
The following year the audit was completed three weeks earlier than the statutory deadline.

These examples demonstrate experience, judgement and outcomes, even within tight word limits.

3. Let evidence carry the narrative

Structured RFP formats favour measurable information.

Rather than resisting that, use it.

Numbers often communicate capability more clearly than paragraphs.

Examples might include:

Investigation firm:

• 1,200 investigations completed in the past five years

• average report turnaround: 14 days

• 92 percent of reports accepted without further clarification.

Law firm:

• 450 litigation matters handled over the past three years

• 68% resolved through negotiated settlement

• 23 specialist litigators across key jurisdictions.

Accounting firm:

• audits completed for 60 public sector entities

• 97% delivered within statutory reporting timeframes

• average partner involvement of 20% of engagement hours.

These metrics tell a punchy story about performance and reliability (without lengthy explanations).

4. Maintain a consistent message across the response

Even when an RFP is fragmented into many questions, the submission should still feel cohesive.

Your core messages should repeat consistently across sections:

• methodology or service plan

• team capability

• case studies

• governance

• implementation.

Without that consistency, the response becomes exactly what many procurement platforms encourage:

a collection of disconnected answers.

The real risk: undifferentiated responses

One side effect of highly structured RFP formats is that they make it easier for submissions to look identical.

Everyone…

• answers the same questions.

• uploads similar policies and documents.

• describes similar systems and processes.

• Before long, evaluators are looking at a sea of submissions that feel interchangeable.

In other words, organisations risk becoming just another undifferentiated fish in the sea in a crowded professional services market.

The role of a bid team today is not simply to answer the questions.

It is to ensure the answers still communicate what makes the organisation distinctive and credible.

And remember: eventually a human will read your bid

Despite all the structured fields, procurement platforms and emerging AI tools, one thing has not changed.

At some point, a real human will read your submission.

They will assess it.
They will score it.

If you make the shortlist, they may also:

• meet you at the beauty parade (or Zoom shortlist interview)

• engage with you in a round of BAFO negotiations

• or begin imagining what it would actually be like to work with your team.

Most tenders also ask you to provide client referees.

When those referees are contacted, they are not reading from a spreadsheet.

They are telling the story of what it was actually like to work with you.

They may describe:

• how your investigation team handled a sensitive case

• how your lawyers managed a difficult dispute

• how your auditors helped them navigate a challenging reporting issue.

Those conversations are entirely human.

They are about experience, judgement and trust.

Which is another reminder that even the most structured procurement process ultimately comes down to people deciding whether they want to work with you.

Bottom line

Structured RFP formats are likely here to stay.

But persuasion has not disappeared from tendering.

It has simply become more disciplined.

The strongest responses today combine:

• clear compliance

• credible evidence

• concise explanations

• consistent messaging.

Because even in the most data-driven procurement process, the goal remains exactly the same.

To help a human evaluator conclude: These are the people we want to work with.

Happy bidding!