How to position a bid against an incumbent supplier

Positioning basis

Compete against the requirement, not an imagined version of the incumbent

Create a source ledger for every statement about the current service. Buyer-published objectives, performance data, known constraints, contract notices and clarification answers can be used within their stated scope. Sales impressions, former-employee comments, assumptions about technology age and guesses about buyer frustration cannot be presented as facts. Even a public failure from years earlier may be irrelevant to the present requirement. If the tender is silent, write to the risk inherent in any transfer, not to an alleged failure by the current provider.

State the challenger proposition in future-contract terms. Name the assessed outcome, the proposed difference, the proof that the difference exists and the transition control that makes adoption credible. For example: a unified service model may reduce handoffs, but the answer should identify the operating roles, common queue, performance measure and phased adoption. It should not claim the incumbent is fragmented. The buyer can credit a supported future strength without accepting a negative assertion about another bidder.

Keep eligibility and bid/no-bid reasoning out of the submitted argument. Once the decision to bid has been made, the evaluator needs a deliverable case, not the challenger’s internal view of incumbent advantage. Use the published criteria and weights. FAR 15.305, in its own US federal context, says proposals are assessed on the solicitation factors and that past-performance relevance depends on currency, source, context and trends. That is a useful discipline for any reference: explain why the evidence predicts performance here instead of treating reputation as proof.

Service protection

Show what remains stable while the supplier changes

Decompose the service into continuity domains: critical transactions, operating hours, support channels, security monitoring, regulatory controls, data retention, interfaces, reports, user communications, third-party commitments and key personnel. For each, define the minimum state through transition, the evidence used to establish the baseline and the gate before responsibility moves. Avoid assuming that “current process” is documented or desirable. Preserve the required outcome and control, not undocumented habits.

Then create a separate change register. Name each proposed improvement, reason, affected users, prerequisite, implementation point, rollback and measure. Some changes can be introduced during mobilisation; others should wait until stable service is demonstrated. Combining takeover and redesign may create value, but it also makes cause and recovery harder to isolate. Explain the sequencing decision. A challenger appears safer when it can distinguish essential continuity from deliberate improvement rather than calling all change transformation.

Use a transition architecture with parallel validation where proportionate: shadow reporting, sample migration, rehearsed cutover, dual-running of a control, staged region or cohort, and explicit entry and exit criteria. Do not promise zero risk or duplicate operations that the buyer has not funded. State residual risk and the authority that accepts it. The persuasive point is not that change has no cost. It is that the challenger has located the failure points and designed evidence before each irreversible step.

• Identify the services and controls that cannot be interrupted.
• Baseline the required outcome rather than undocumented custom.
• Separate takeover gates from improvement releases.
• Define entry, exit, rollback and acceptance authority.
• State residual risk without a “no-disruption” guarantee.

Takeover plan

Treat handover as a four-party operating system

Map activities across buyer, outgoing supplier, incoming supplier and material third parties. Include data and asset inventory, access, licenses, contracts, configurations, process records, service history, open incidents, security evidence, staff information where applicable, knowledge sessions, supplier introductions, test support and decision rights. Assign the deliverable, owner, required-by date, quality check, receiving owner and consequence of delay. A meeting called “knowledge transfer” is not a deliverable; an approved operating procedure and observed task demonstration are.

Do not assume the outgoing supplier will be hostile, cooperative or contractually obliged beyond the buyer’s documents. Ask the buyer to confirm exit provisions, available artifacts, handover governance and escalation. If details cannot be shared during competition, propose an early validation gate and show the commercial assumptions that depend on it. Keep contingencies proportionate: alternative data discovery, targeted reverse engineering, additional observation or replanning may be credible; a universal disclaimer that all dates depend on the incumbent is not.

The UK Sourcing Playbook says an exit plan should join the outgoing supplier’s exit with incoming mobilisation and cover activities, milestones, resources, roles, joint risks, interfaces, dependencies and transfers. The 2026 Contract Management Playbook likewise describes transition planning whether a service stays with the incumbent or moves, and notes the need for collaboration provisions. These are buyer-oriented UK guidance, but they support a challenger’s core message: the takeover succeeds through defined reciprocal obligations, not confidence alone.

Evidence and economics

Make the transition promise survive reference and price review

Choose reference projects that match the takeover difficulty, not merely the service category. Explain starting condition, service criticality, number of interfaces or locations, outgoing-provider involvement, role of the proposed organisation, transition duration, protected performance and measurable result. Identify problems encountered and corrective action where the procurement permits it. If the proposed key people performed the work, state their role. If not, show which method, artifact and governance capability transfers to the new team.

Attach proof to the relevant control: a redacted readiness checklist, reconciliation report, cutover runbook structure, early-life dashboard or reference contact. Do not overwhelm the answer with a long case study. One comparable detail that supports the gate is worth more than an unrelated success statistic. Where the challenger lacks a directly comparable takeover, reduce the claim, combine component evidence carefully and add stronger validation. Never re-label implementation work as incumbent replacement if it was not.

Reconcile the complete promise with the cost model. Price transition leadership, discovery, knowledge capture, data validation, rehearsals, dual activity, travel, third-party charges, contingency and early-life support as applicable. Map each narrative commitment to a work package, resource and approval. Check the contract for responsibility when inputs are late, baseline information is inaccurate or acceptance is delayed. The strongest challenger position is not the cheapest description of change. It is a future value case whose service protection, dependencies and economics remain coherent when the evaluator traces them into delivery.

• Match references to the takeover conditions and criticality.
• Show the proposed team’s actual role or transferable method.
• Place artifacts beside the control they prove.
• Cost discovery, rehearsal, contingency and early-life support.
• Reconcile narrative commitments with work packages and contract risk.