Unsolicited Bid Strategy¶

Scope¶

This file covers the methodology for initiating and executing unsolicited bids -- proposals that the provider creates without a customer request, RFP, or formal procurement process. Unsolicited bids leverage the provider's existing knowledge of the customer's environment, pain points, and strategic direction to propose a solution before the customer asks for one. Distinct from RFP responses (customer-initiated, defined scope, competitive evaluation) and renewals (existing contract renegotiation). For general pursuit methodology, see general/pursuit-methodology.md. For commercial framing, see patterns/private-cloud-as-a-service.md.

Checklist¶

Opportunity Identification¶

[Critical] Is there a non-optional trigger driving the customer to act? (Lease expiration, licensing cliff, end-of-support, compliance deadline, acquisition/divestiture) Unsolicited bids without a forcing function are easily deferred -- the customer says "interesting, we'll think about it" and nothing happens.
[Critical] Does the provider have a pre-existing operational relationship? (Currently managing the environment, operating adjacent systems, or deep account knowledge) Without insider knowledge, an unsolicited bid has no advantage over a cold proposal.
[Critical] Is the timing aligned with the customer's decision cycle? (Budget planning periods, board meeting schedules, contract renewal dates, fiscal year boundaries) A perfectly crafted bid presented at the wrong time gets shelved.
[Recommended] Is the competitive landscape assessed? (Is the customer likely to receive competing proposals? Is there an incumbent who might be displaced? Could the customer use the unsolicited bid as leverage for competitive pricing without awarding?)
[Recommended] Is there an internal champion at the customer? (Someone who would benefit from the proposal and will advocate internally) Without a champion, the bid enters the organization with no sponsor.

Leveraging Incumbent Advantage¶

[Critical] Is the provider's operational data used to build the proposal? (VM inventories, utilization data, incident history, capacity trends -- data the customer hasn't shared because the provider already has it) This is the #1 differentiator of an unsolicited bid from an incumbent.
[Critical] Is the "we already run it" narrative articulated? (No discovery phase needed, no learning curve, no surprises. The provider's analysis was built from operational data, not a questionnaire.)
[Recommended] Is work-in-progress leveraged? (If the provider is already migrating workloads, modernizing infrastructure, or driving improvements, the bid extends and formalizes existing momentum rather than proposing something new.)
[Recommended] Are operational metrics cited as evidence? (Uptime achieved, incidents resolved, capacity managed, migrations completed -- verifiable facts, not marketing claims.)

Win Themes¶

[Critical] Are win themes specific and verifiable? ("We manage 12,082 VMs across your 5 sites today" is verifiable. "We have deep expertise in datacenter migrations" is not.)
[Recommended] Is the "why now" narrative clear? (What makes this moment the right time? Lease expiring, licensing costs increasing, technology debt growing. The urgency must be real and documented.)
[Recommended] Is the "what happens if you don't act" scenario articulated? (Lease expires with no plan, VMware licensing costs double under Broadcom, hardware reaches end-of-support with no replacement) This creates urgency without being alarmist.
[Recommended] Is the "why us" differentiated from the "why now"? (We should do this now because leases expire. You should do it with us because we already operate the environment, we have the data, and the migration is already underway.)

Proposal Construction¶

[Critical] Is the proposal based on real data, not assumptions? (Use operational data the provider has access to. Every number should be sourced. This is the credibility advantage of an unsolicited bid.)
[Critical] Are assumptions explicitly documented? (Where data is incomplete, state the assumption and its impact if wrong. Unsolicited bids often have data gaps that an RFP process would have filled.)
[Critical] Is the proposal structured at the right level? (NBIE-level for initial pitch, not detailed SOW. The goal is to get the customer interested enough to engage, not to deliver a final contract.)
[Recommended] Are discovery questions included? (The bid acknowledges what it doesn't know and provides a structured list of questions for the customer to answer. This demonstrates thoroughness and sets up the next engagement step.)
[Recommended] Is the proposal free of tooling or methodology attribution? (No "generated by AI", no tool names, no methodology branding. Professional documents from a trusted partner.)

Competitive Defense¶

[Recommended] Is there a strategy for preventing the customer from using the bid as leverage? (Customer takes the unsolicited bid to a competitor: "match this price." Mitigation: relationship depth, proprietary operational knowledge, work-in-progress that a competitor cannot replicate.)
[Recommended] Are switching costs articulated? (If the customer went to a competitor, what would they lose? Operational continuity, in-progress migrations, institutional knowledge, no ramp-up period.)
[Optional] Is the bid structured to be difficult to comparison-shop? (Bundled services, unique operational model, proprietary automation -- elements that a competitor's proposal cannot directly replicate.)

Risk Management¶

[Recommended] Is the risk of rejection planned for? (The customer may say no. Is the pursuit cost justified by the probability and size of the opportunity? Typical unsolicited bid win rate: 20-30% for incumbents, lower for non-incumbents.)
[Recommended] Is the relationship risk assessed? (Could the bid be perceived as overstepping? Is the customer relationship strong enough to absorb a "thanks but no thanks"?)
[Optional] Is a fallback position defined? (If the full bid is rejected, is there a smaller scope that the customer might accept? Partial migration, advisory engagement, or extended managed services?)

Why This Matters¶

Unsolicited bids from incumbents win at significantly higher rates than cold proposals because the provider has three advantages no competitor can match: operational data, institutional knowledge, and relationship trust. However, these advantages are only valuable if the bid is built on real data (not generic capabilities) and timed to a customer trigger (not provider convenience).

The most common failure: proposing without a forcing function. The customer agrees the idea is interesting but has no urgency to act. Without a lease expiration, licensing cliff, or compliance deadline, the bid sits in a drawer. The forcing function is what makes the customer read past page one.

The second most common failure: treating the unsolicited bid like an RFP response. RFP responses answer the customer's questions. Unsolicited bids must create the narrative: here is your problem, here is when it becomes urgent, here is what we propose, and here is why we are the right partner. The provider defines the scope, not the customer.

Common Decisions (ADR Triggers)¶

Bid scope -- full transformation vs phased approach vs advisory; determines investment level and customer commitment required
Pricing strategy -- competitive pricing to prevent shopping vs premium pricing justified by incumbent advantage; affects margin and win probability
Proposal depth -- NBIE-level (get the conversation started) vs detailed SOW (close the deal); early-stage bids should be NBIE-level
Discovery question strategy -- include questions to demonstrate thoroughness and set up next engagement vs answer everything with assumptions; questions create next steps