Research method

From observed behaviour to a controlled pursuit decision.

This public record explains how Achmed Esser's bidder and procurer perspectives inform the Bid Champions method, what the figures mean and how an observation is kept separate from a claim.

Public research position

A substantial practice-based record, described at the strength the record can support.

The figures below are owner-approved cumulative perspective counts from research personally undertaken by Achmed Esser. They are not presented as a probability sample of the entire procurement market, a peer-reviewed population study or a guarantee that one pattern applies to every pursuit.

3,000+Bidder perspectives
2,600+Procurer perspectives
30+Sector fields

Count boundary: “perspectives” describes the accumulated owner-reported research record. It should not be read as 5,600 statistically independent survey respondents unless a future underlying research register establishes that exact interpretation.

Observation ledger

Four kinds of input. No silent merging.

Participant experience, documents, practical work and interpretation can reinforce each other, but they are not the same evidence. The working method keeps their role visible.

01

Bidder perspectives

Recurring bidder decisions, operating constraints, evidence gaps and pursuit experiences across the owner-reported research record.

02

Procurer perspectives

How evaluators and procurement stakeholders describe usability, risk, evidence and confidence in competitive decisions.

03

Procurement artefacts

Requirements, evaluation structures, notices, clarification records, debrief themes and other lawfully available documents.

04

Live pursuit practice

Qualification, capture, response, review, commercial alignment, mobilisation and learning observed through practical work.

Controlled development loop

What has to happen before an insight becomes a method.

The loop is deliberately practical. It searches for a repeatable decision aid while preserving the need to test every recommendation against the actual procurement and bidder.

01

Observe

Capture the behaviour, document, decision or delivery condition without treating an isolated example as a universal rule.

02

Separate

Distinguish source evidence, participant perspective, professional interpretation and a proposed method.

03

Compare

Look for recurrence across bidder types, procurement roles, sectors, routes and stages of the pursuit.

04

Translate

Turn the recurring issue into a practical control, question, map, review lens or decision sequence.

05

Apply

Use the method against the live buyer, bidder, evidence, commercial route and delivery context rather than as a fixed template.

06

Learn

Capture feedback, award, mobilisation and delivery experience where available, then refine the working method.

How it changes a pursuit

Research becomes useful only when it changes a decision.

The practical output is not a claim that every buyer behaves alike. It is a stronger set of questions, evidence controls and challenge points for the situation in front of the team.

Working applications

  • Test strategic fit, access, evidence readiness, differentiation, delivery capacity and commercial exposure before committing.
  • Map procurement, technical, commercial, operational, user and mobilisation stakeholders rather than writing to one abstract “buyer”.
  • Connect each material claim to a source, owner, date, requirement, evaluator implication and delivery commitment.
  • Review whether the answer is specific and usable before improving its surface language.
  • Carry authorised promises and open risks into mobilisation and future learning.

Responsible interpretation

  • Use recurring observations as hypotheses and challenge prompts, not universal causal laws.
  • Do not convert anecdote, correlation or professional judgement into an unsupported numerical prediction.
  • Recheck the live notice, procurement documents, buyer instructions and applicable law.
  • Preserve confidentiality and anonymisation where participant or client identities are protected.
  • Record what remains unknown instead of filling gaps with invented precision.