Archive of Christian Ullrich

AI Reflex OS

Selling to the Military Reflex Area

2026-10-01

Selecting Military Markets and Customers
Understanding Military Buying Systems and Decision Structures
Understanding Military Needs, Requirements, and Demand
Navigating Defense Market Access and Eligibility
Discovering and Developing Military Opportunities
Qualifying Opportunities and Managing the Pursuit Portfolio
Building Customer Access and Stakeholder Support
Positioning Military Value and Building Evidence
Developing Capture Strategy and Competitive Position
Designing Teaming and Partnership Strategy
Navigating Formal Competitions and Bid Requirements
Developing and Reviewing Military Proposals
Pricing and Structuring the Commercial Offer
Managing Contract Risk and Negotiation
Transitioning From Award and Managing the Customer Relationship
Developing Follow-On Business, Recompeting, and Learning From Outcomes

Selecting Military Markets and Customers

Comparing Military Markets Before Committing Resources

Which military markets appear most attractive once demand, accessibility, competitive intensity, and likely economics are considered together?
What evidence supports the apparent attractiveness of each market rather than relying on headline defense spending or general strategic importance?
Which markets offer a realistic route from customer need to funded procurement for a company like ours?
How do the likely sales cycle, compliance burden, localization requirements, and cost of market entry differ across the markets being considered?
Where do we already possess relationships, evidence, partners, capabilities, or delivery infrastructure that materially improve our position?
Which uncertainties could change the comparison enough that we should investigate them before committing significant resources?
If we could pursue only a small number of these markets, which differences should drive the allocation of our limited time and capital?

Assessing Strategic Fit Between the Company and a Military Market

How closely does this military market align with the capabilities, technologies, services, and business models we are genuinely strong at delivering?
Which parts of our existing commercial or defense experience transfer credibly into this market, and which important gaps remain?
Does entering this market reinforce our long-term strategic direction or pull us toward work we would not otherwise choose to do?
What customer-specific engineering, certifications, security measures, support arrangements, or organizational capabilities would market entry require?
Could this market create reusable products, evidence, relationships, or capabilities that strengthen our position elsewhere?
What strategic dependencies or constraints could this market create for our product roadmap, ownership structure, partnerships, or future customers?
If the first contract in this market were successful, would we actually want the type of business that would likely follow?

Selecting Mission Areas and Capability Problems to Pursue

Which mission areas contain problems that our capabilities can materially improve rather than merely touch at the margins?
How important are these problems to the military organizations experiencing them, and what evidence shows that importance?
Which capability problems are receiving increasing operational, budgetary, or acquisition attention?
Where does our offering address an underlying military problem rather than only one requested feature or current implementation?
Which mission areas would require changes in doctrine, organization, infrastructure, or other conditions that reduce the commercial addressability of the problem?
Where do we possess credible differentiation, relevant evidence, or a plausible path to building it?
Which mission areas should we deliberately exclude because the problem, customer, competitive position, or delivery burden does not fit us well enough?

Prioritizing Military Customer Organizations

Which military organizations experience problems that match our strongest capabilities and evidence?
Which organizations have enough authority, funding access, acquisition activity, or institutional priority to convert those problems into business?
How accessible are the relevant users, requirement owners, acquisition organizations, and decision-makers within each customer organization?
Which customers have procurement mechanisms that a company of our type can realistically use?
Where would a successful first engagement produce the strongest references, learning, installed position, or follow-on potential?
Which customer organizations appear attractive but would require disproportionate resources, political capital, certifications, or local presence?
How should we rank these customers if market potential, ease of entry, probability of success, and strategic value point in different directions?

Comparing Geographic Markets for Entry

Which countries or regions have military needs that align most closely with our offering and demonstrated strengths?
How do procurement systems, defense budgets, industrial policies, security rules, export restrictions, and supplier eligibility differ across the markets?
Where can we participate directly, and where would market access depend on local partners, government-to-government channels, or other intermediaries?
How do local-content, offset, sovereignty, or domestic-industry expectations affect the commercial attractiveness of each geography?
Which markets would require customer-specific adaptation, local support, language capability, infrastructure, or legal presence?
What geopolitical, regulatory, currency, sanctions, or policy changes could materially affect our ability to pursue or deliver business there?
Which geography provides the best balance between meaningful demand and the practical ability to enter, win, deliver, and grow?

Estimating Accessible Opportunity Behind Headline Defense Spending

What portion of total defense spending is actually connected to the mission areas, capabilities, and products relevant to us?
How much of that spending is available to external suppliers rather than committed to personnel, sovereign capabilities, existing programs, or internal delivery?
Which relevant expenditures are already locked into incumbents, long-term contracts, closed frameworks, or government-to-government arrangements?
What eligibility, security, nationality, industrial-policy, or contract-vehicle restrictions further reduce the portion we can realistically pursue?
Within the accessible market, which opportunities are large enough and sufficiently aligned with our strengths to be genuinely winnable?
What assumptions are driving our market-size estimate, and which of them have the greatest risk of overstating the opportunity?
What is a more realistic estimate of supplier-accessible and potentially winnable demand after these constraints are applied?

Testing Market-Level Demand, Funding, and Urgency

What recurring evidence shows that this market has a real military problem rather than general interest in a technology category?
Which strategies, modernization plans, programs, budgets, experiments, or procurements demonstrate institutional demand?
Where is funding already available, programmed, requested, or plausibly reachable for the relevant capability area?
What evidence shows that the customer must act within a meaningful timeframe rather than treating the issue as a long-term aspiration?
Are multiple customer organizations acting on the same problem, or does apparent demand depend on a small number of enthusiasts?
How stable is the demand if current leadership, operational circumstances, or budget priorities change?
What additional evidence would materially increase or decrease our confidence that this is a durable market rather than a temporary wave of attention?

Assessing Competitive Openness and Incumbent Structure

Which suppliers currently serve this market, and what structural advantages do they possess?
How entrenched are incumbent systems, relationships, contract vehicles, interfaces, data rights, certifications, or support arrangements?
Are customers actively seeking new suppliers, alternative technologies, or competitive pressure against incumbents?
Do procurement methods and evaluation practices give new entrants a realistic opportunity to receive credit for meaningful differentiation?
Which parts of the market are open to commercial or nontraditional suppliers, and which remain dominated by established defense firms?
What would a challenger need to prove or provide to overcome the customer's switching, integration, or delivery risk?
Does the competitive structure leave enough realistic room for us to build a defensible position, or would entry depend on improbable incumbent displacement?

Deciding Whether to Enter Early, Wait, or Continue Watching

What advantage could we gain by entering this market before formal demand or procurement becomes mature?
What would we need to invest now in relationships, evidence, certifications, partnerships, or market learning to benefit from early entry?
Which uncertainties are likely to become clearer if we wait rather than committing immediately?
Could waiting materially weaken our future position by allowing competitors to build stronger customer understanding, establish relevant evidence, secure partners, or earn customer trust first?
What observable events would justify moving from monitoring to active market entry?
What is the minimum level of investment needed to remain informed and preserve future options while uncertainty remains high?
Given the current evidence, should we enter actively, maintain a watch position, or wait for a specific trigger before committing further resources?

Deferring or Exiting an Unattractive Military Market

Which original assumptions about this market have weakened or proven false?
Is the problem insufficiently important, insufficiently funded, inaccessible, or structurally difficult for us to win?
Have security, export, localization, competitive, delivery, or commercial requirements made the opportunity less attractive than expected?
What evidence suggests that additional investment is unlikely to improve our position materially?
Are we continuing primarily because of sunk costs, prestige, existing relationships, or fear of abandoning potential upside?
Would a different route, partner, timing, or narrower segment make the market worth revisiting later?
What specific conditions should cause us to defer, exit, or place the market back into passive monitoring?

Understanding Military Buying Systems and Decision Structures

Reconstructing How an Unfamiliar Military Customer Buys

How does this organization move from recognizing an operational problem to defining, funding, acquiring, and fielding a solution?
Which organizations or offices own each major step in that process?
What procurement mechanisms does this customer commonly use for offerings like ours?
Where do military users, civilian officials, acquisition organizations, and contracting authorities interact in the buying process?
Which parts of the process are formal and documented, and which important decisions depend on less visible institutional coordination?
What can previous procurements reveal about how this customer actually behaves compared with how the formal process is described?
Which remaining gaps in our understanding could cause us to pursue the wrong people, timeline, funding source, or acquisition route?

Distinguishing Users, Sponsors, Funders, Buyers, and Contracting Authorities

Who will actually use the capability, and what role do they play in creating or validating demand?
Who owns or sponsors the military need at the institutional level?
Who controls or influences the funding required to act on that need?
Which organization runs the acquisition or procurement process?
Who would actually contract with us, and would that be the military organization itself, a procurement agency, a prime contractor, an integrator, or another intermediary?
Where are we currently using the word "customer" to describe several people or organizations with materially different roles?
How should our engagement change once these roles are separated clearly?

Tracing Who Owns and Approves the Requirement

Who is accountable for defining the capability need or requirement?
Which organizations or authorities can validate, modify, prioritize, or reject it?
What operational evidence or planning process originally caused the requirement to exist?
Which stakeholders can influence the requirement even though they do not formally own it?
What approvals must the requirement receive before it can support acquisition action?
How stable is the requirement, and what events or decisions could cause it to change or disappear?
What evidence do we have that the person advocating for the requirement actually possesses the authority we are attributing to them?

Tracing Where Funding Comes From and Who Controls It

What budget, program, appropriation, innovation fund, operating account, or other source could pay for this capability?
Is the relevant money requested, programmed, approved, allocated, or actually available for obligation?
Who controls the funding decision at each stage?
Are the requirement owner and funding authority located in the same organization or in different parts of the system?
What fiscal-year, appropriation, approval, or expenditure deadlines affect when the customer can act?
Could the customer need the capability strongly while still lacking authority to redirect money toward it?
What would have to happen for the current funding position to become commercially actionable?

Identifying the Acquisition Organization and Contracting Authority

Which organization is responsible for acquiring this type of capability on behalf of the military customer?
Which office or official can legally bind the government to the relevant contract?
How does the acquisition organization interact with the operational customer, requirement owner, technical authorities, and budget holders?
What contract vehicles, frameworks, acquisition pathways, or procurement procedures can this organization use?
Which decisions can program or technical personnel make, and which require formal contracting authority?
Are we relying on commitments or assurances from people who cannot authorize the commercial action we need?
How should our pursuit strategy change once the actual acquisition and contracting authorities are clear?

Mapping Formal Authority and Informal Influence

Who can formally approve, fund, evaluate, contract, accept, or block the proposed capability?
Which stakeholders lack formal authority but are trusted enough to influence those decisions materially?
Where does operational credibility carry more weight than organizational seniority?
Which technical, security, legal, or integration stakeholders possess effective veto power even if they are not the final decision-maker?
Which relationships appear influential mainly because of rank or visibility rather than actual involvement in this decision?
Where could informal support help an opportunity progress without replacing the need for formal authority?
Does our current stakeholder map clearly distinguish who can influence an outcome from who can actually cause it?

Understanding Centralized, Decentralized, Service, and Joint Buying Structures

Is relevant buying authority concentrated centrally or distributed across services, commands, units, agencies, or programs?
Which decisions can be made locally, and which require higher-level approval?
Does a service-specific requirement depend on a joint, ministerial, or central acquisition organization to purchase it?
How does the organizational structure affect where demand must be built and where contracts can actually be placed?
Does decentralization create multiple accessible entry points or merely multiple users operating under the same central procurement constraints?
What interoperability, cross-service, or joint requirements become important when several organizations share the capability?
How should our account and opportunity strategy differ because of the customer's particular buying structure?

Understanding How Different Types of Military Acquisition Are Organized

Is the customer treating this as major equipment, software, a service, research, experimentation, sustainment, infrastructure, or an urgent operational requirement?
Which acquisition pathway or organizational structure is normally used for this type of requirement?
How do evidence, approval, contracting, security, integration, and delivery expectations differ because of the acquisition type?
Does the customer need to buy a complete capability, a commercial product, a prototype, a subscription, or a component inside a larger system?
Which parts of the buying system become more or less important because of the category of acquisition?
What assumptions are we carrying over from other defense sales that do not apply to this acquisition type?
How should our route to market, evidence plan, commercial model, and stakeholder engagement change accordingly?

Reconstructing the Need, Budget, Procurement, and Delivery Timelines

When does the operational need become important enough to require action?
When must the requirement be defined or approved to support that action?
When must funding be requested, approved, allocated, and obligated?
When can the acquisition organization begin market engagement and formal procurement?
When could a contract realistically be awarded?
When must the supplier deliver or field the capability for the customer's operational timeline to be met?
Where do these timelines fail to align, and what does that misalignment mean for the opportunity?

Testing Assumptions About How the Customer's Buying System Works

Which parts of our current understanding come from verified customer information rather than inference or analogy?
Are we assuming that this customer buys the same way another service, country, agency, or program does?
Which stakeholder roles or authorities have we inferred from job titles without confirming them?
Are we treating a procurement forecast, budget line, RFI, or innovation activity as stronger evidence of acquisition intent than it actually is?
Which assumptions about funding, timing, contract vehicles, or approval processes would most damage the pursuit if wrong?
What public records, customer conversations, previous procurements, or specialist advice could test those assumptions?
What should remain explicitly unknown until better evidence becomes available?

Understanding Military Needs, Requirements, and Demand

Understanding the Military Problem Before Positioning a Solution

What mission, task, or operational activity is the customer trying to perform?
How is that activity carried out today, and where does current performance fail or become costly?
Who experiences the problem directly, and who experiences its downstream consequences?
Under what operational conditions does the problem become most significant?
What workarounds, existing systems, or nontechnical responses are currently used?
What consequence makes the problem important enough to deserve institutional attention?
If our product did not exist, how would we describe the problem in a way that still makes sense?

Distinguishing Symptoms, Requested Features, Requirements, Problems, and Outcomes

What observable symptom first caused the customer to seek change?
Which requested features are proposed solutions rather than descriptions of the underlying problem?
What does the formal or informal requirement actually require the capability to achieve?
What operational problem is the requirement attempting to solve?
What military outcome would improve if the problem were solved successfully?
Which stated requirements may reflect inherited assumptions rather than conditions essential to the outcome?
How would our proposed solution change if we optimized for the underlying outcome rather than the customer's first requested feature?

Testing Whether a Need Is Institutionally Important

Is the need recognized by an accountable organization rather than only by individual users?
What operational, readiness, strategic, financial, or safety consequence makes the issue important?
Does the problem appear in formal plans, capability assessments, exercises, lessons, modernization activity, or leadership priorities?
Has the customer allocated people, funding, experimentation, or acquisition effort to addressing it?
How does this need compete against other problems seeking attention and resources?
Would the need remain important if its current champion changed role or left the organization?
What evidence would show that the problem has crossed from user preference into institutional priority?

Assessing How Mature a Military Need Has Become

Is the customer still recognizing the problem, defining the desired outcome, shaping a requirement, or preparing to acquire a solution?
Does an accountable requirement owner or sponsor exist?
Are performance expectations, operating conditions, interfaces, and constraints sufficiently understood?
Has the need been prioritized against competing requirements?
Is there a credible funding path?
Has the customer identified an acquisition route, program, experiment, or other mechanism for acting on the need?
What is the next institutional event that would demonstrate greater maturity?

Tracing How a Requirement Emerged and How It May Change

What strategic guidance, operational experience, threat, exercise, capability assessment, or technology change originally created the requirement?
Which assumptions about the operating environment or threat are embedded in it?
Which stakeholders shaped the requirement and what concerns were they trying to address?
What parts of the requirement have already changed, and why?
What budget, technical, integration, affordability, or operational factors could force further change?
Could experimentation or new technology make the current requirement obsolete or materially different?
Which requirement elements should we treat as stable and which should remain active capture risks?

Interpreting Requirements Shaped by Legacy Solutions or Assumptions

Which requirement elements appear tied to the current system, incumbent architecture, historical interface, or traditional way of operating?
What operational, safety, security, interoperability, or support need does each legacy-looking constraint protect?
Which constraints remain genuinely necessary and which may simply reflect inherited implementation choices?
Could another technical approach achieve the same outcome without reproducing the legacy design?
What evidence would be needed to show that an inherited assumption can safely be changed?
Is the customer still able to reconsider the constraint, or has the formal procurement already made compliance mandatory?
Should we comply, seek clarification, propose an allowed alternative, or decide that the requirement does not fit our solution?

Challenging the Customer's Initial Problem Framing Credibly

What evidence suggests that the customer's initial framing addresses a symptom rather than the underlying problem?
What operational consequence follows if the current framing remains unchanged?
Can we propose a different interpretation without dismissing the customer's experience or authority?
What data, test results, user observations, or comparable cases support the alternative framing?
Can the alternative be tested against the same desired military outcome rather than argued as a matter of opinion?
Is this still an appropriate stage of the acquisition process for challenging the framing?
How can we challenge the assumption in a way that increases customer understanding rather than appearing to reshape the problem around our product?

Identifying Latent or Emerging Needs Before Formal Requirements Appear

What changes in threats, doctrine, operations, force design, technology, infrastructure, or personnel are creating new military problems?
Which exercises, experiments, lessons, modernization plans, or research programs reveal problems that have not yet become formal requirements?
What current workarounds or recurring user frustrations suggest unmet demand?
Which existing capabilities are approaching obsolescence, capacity limits, or changing mission conditions?
What public budget, strategy, organizational, or acquisition signals suggest that institutional attention is beginning to form?
Who is likely to become the problem owner or requirement sponsor if the need matures?
What evidence would justify moving from general market observation to active opportunity development?

Determining Whether a Military Problem Is Commercially Addressable

How much of the problem can realistically be improved through a product or service rather than doctrine, organization, policy, training, personnel, or authority?
Does our offering address a major cause of the problem or only one technical component?
What changes in infrastructure, process, data, training, or organization would be required for the solution to produce value?
Can the relevant military organization actually authorize and adopt those changes?
Can the offering integrate with the systems, networks, platforms, and operating conditions on which the mission depends?
Can we deliver, support, and sustain the solution at the scale and tempo required?
After considering all enabling changes, is there still a commercially viable problem for an external supplier to solve?

Distinguishing Enthusiasm and Experimentation From Genuine Demand

What has the customer actually done beyond expressing positive interest?
Does an identifiable sponsor, requirement owner, funding source, or acquisition organization support the activity?
Is the demonstration, trial, or pilot connected to a defined decision about what happens next?
Has the customer committed resources, users, data, facilities, or funding that indicate institutional intent?
Is the same need recognized beyond the individual stakeholders currently engaging with us?
What procurement or transition mechanism could convert successful experimentation into operational adoption?
If the current champion disappeared tomorrow, what evidence would remain that genuine demand still exists?

Navigating Defense Market Access and Eligibility

Determining Whether the Company Is Eligible to Compete

What legal, nationality, ownership, registration, certification, security, or supplier-status requirements govern participation in this opportunity?
Which eligibility conditions must be satisfied before bidding and which can be completed later?
Does our corporate structure, ownership, location, or business model create any restrictions?
Are there requirements that apply differently to prime contractors, subcontractors, local partners, or foreign suppliers?
Which conditions can we satisfy internally and which require a partner, sponsor, government approval, or specialist process?
What evidence will the customer require to verify eligibility?
Is there any eligibility issue that could make further pursuit investment unjustified until it is resolved?

Assessing Classification and Industrial Security Requirements

What level of classified or otherwise protected information could the pursuit or contract involve?
Which personnel, facility, information-system, or organizational clearances would be required?
At what point in the pursuit would access to classified material become necessary?
Can we perform meaningful work without that access, or would the restriction prevent us from competing effectively?
Which partners or subcontractors would also need appropriate security status?
How much time, cost, organizational change, and government sponsorship would obtaining the required security position involve?
Should the security requirement be treated as a manageable access task, a partnering requirement, or a reason not to pursue?

Assessing Cybersecurity and Protected Information Requirements

What types of government, controlled, sensitive, or classified information would we need to receive, process, store, or transmit?
Which cybersecurity standards, assessments, certifications, or contractual controls apply to that information?
Do those requirements extend into our suppliers, cloud providers, partners, or other parts of the delivery chain?
Where are the material gaps between our current security posture and the required one?
What cost and time would remediation require before bid, award, or performance?
Could the required controls conflict with our current commercial infrastructure, product architecture, or operating model?
At what point should cybersecurity specialists determine whether the opportunity remains feasible?

Evaluating Foreign Ownership, Control, or Investment Constraints

Does our ownership structure create restrictions on access to classified work, controlled information, facilities, or contracts?
Which investors, board rights, parent-company relationships, or foreign affiliations are relevant to the customer's security rules?
Could an upcoming investment, acquisition, or ownership change alter our eligibility during the pursuit?
What mitigation measures might be required to manage foreign ownership or control concerns?
Would those measures affect governance, information access, strategic freedom, or the economics of the opportunity?
How long would regulatory or security review realistically take?
Does the potential value of the market justify the structural changes or restrictions required to participate?

Determining How Export Controls and Sanctions Affect the Pursuit

Which products, software, technical data, services, demonstrations, or support activities may be controlled?
Does engaging this customer, geography, partner, or end user require a license or other authorization?
Are there restrictions on sharing technical information before a contract is signed?
Could reexport, retransfer, subcontracting, or local support create additional control requirements?
Do sanctions affect any customer organization, intermediary, partner, owner, bank, or jurisdiction involved in the pursuit?
What assumptions about licensing timing or approval should be reflected in the opportunity plan rather than treated as guaranteed?
What must be confirmed by export-control or sanctions specialists before further commitments are made?

Assessing Localization, Offset, Sovereignty, and Industrial Participation Requirements

What domestic production, local-content, technology-transfer, offset, sovereign-capability, or industrial-participation requirements apply?
Are these requirements formal evaluation factors, contractual obligations, policy expectations, or merely market conventions?
Which parts of the offering or delivery model could realistically be localized without undermining performance or economics?
What local suppliers, facilities, workforce, partners, or investments might be needed?
How would localization affect intellectual property, export control, quality assurance, supply-chain security, and future competition?
What cost or margin impact would the industrial requirements create?
Do these obligations strengthen the case for entering the market or make it commercially unattractive?

Navigating Supplier Registrations, Frameworks, and Approved Vendor Requirements

Which supplier registrations, portals, frameworks, qualification systems, or approved vendor lists control access to relevant opportunities?
Which of these must be completed before a specific opportunity is released?
How long does onboarding normally take, and what documentation or certifications are required?
Does joining a framework create meaningful future access or only theoretical eligibility?
Are there closed frameworks or supplier lists that make direct entry impossible until a future reopening?
Could a prime contractor, reseller, or other existing participant provide an alternative route while we build direct eligibility?
Which registration or framework investments are justified by likely opportunity volume rather than by the desire to appear market-ready?

Determining Whether Local Presence or a Local Partner Is Required

Is local presence legally required, commercially expected, or simply advantageous?
What specific problem would a local partner solve: eligibility, customer access, support, language, logistics, industrial participation, or contracting?
Could we provide those functions more effectively through our own local entity or another route?
What evidence shows that a proposed partner has real capability rather than only claimed connections?
How would the partner affect margin, customer ownership, intellectual property, compliance, and future freedom to compete?
What due diligence is needed before relying on the partner for market access?
Is the opportunity still attractive once the full cost and strategic consequences of local participation are included?

Evaluating the Cost and Timing of Removing Market Access Barriers

Which current access barriers must be removed before we can compete meaningfully?
What is the realistic time required for each registration, certification, clearance, localization step, or corporate change?
Which barriers must be resolved sequentially and which can be addressed in parallel?
What internal people, specialist support, capital, and management attention will the process require?
Is there a credible opportunity pipeline large enough to justify those investments?
Could the market move or the target opportunity close before we become eligible?
Should we remove the barrier now, use an interim partner route, or wait until stronger demand exists?

Recognizing When Access Constraints Require Specialist Support or Make the Market Inaccessible

Which access issue exceeds the competence or authority of the sales and capture team?
Is the issue primarily legal, export-related, security-related, sanctions-related, ownership-related, tax-related, or contractual?
What decisions must pause until an appropriate specialist has reviewed the situation?
Is there a realistic mitigation or alternative route that preserves the opportunity?
What cost, delay, governance burden, or restriction would the mitigation create?
Are we minimizing the seriousness of the issue because of sunk pursuit effort or customer enthusiasm?
At what point should the access constraint be treated as a reason to stop rather than another obstacle to work around?

Discovering and Developing Military Opportunities

Monitoring Strategic and Operational Signals for Emerging Demand

Which changes in defense strategy, force design, doctrine, operations, threats, or modernization priorities could create new demand relevant to us?
Which military organizations are discussing these changes most consistently?
What capability gaps, readiness issues, or operational lessons appear repeatedly across public sources?
Which signals represent broad strategic interest and which suggest a specific customer may soon act?
What time horizon is implied by the signal, and what would need to happen before procurement could follow?
Which competitors or partners appear to be responding to the same emerging demand?
What developments should trigger deeper opportunity investigation rather than continued market monitoring?

Using Budgets, Acquisition Plans, and Procurement Forecasts to Find Opportunities

Which budget lines, program documents, acquisition plans, and procurement forecasts relate directly to capabilities we can provide?
What do these sources reveal about customer organization, funding scale, timing, and acquisition intent?
Is the funding requested, programmed, approved, or actually available?
Which forecast entries are likely to become open competitions and which may use existing contracts, incumbents, or restricted routes?
How do planned dates align with the customer's budget cycle and operational need?
What changes between successive budget or forecast publications indicate that an opportunity is strengthening, slipping, or disappearing?
Which entries warrant direct customer investigation before we treat them as real opportunities?

Using Historical Awards and Contract Expirations to Anticipate Recompetes

Who currently supplies the relevant capability, and which organization awarded the contract?
What was the original contract value, duration, scope, vehicle, and competition method?
When do current contract periods, options, or extension mechanisms expire?
Does the customer appear satisfied with the incumbent, or are there public signs of performance, cost, or capability concerns?
Has the requirement changed enough that the next competition may differ materially from the previous one?
What barriers would a challenger face because of installed systems, integration, data, security, or customer familiarity?
When would we need to begin positioning if we intend to compete credibly for the anticipated recompete?

Discovering Opportunities Through Experiments, Innovation Programs, and Research Activity

Which military experiments, research programs, innovation challenges, or prototype activities address problems relevant to our capabilities?
Is the customer seeking technical learning, operational experimentation, prototype delivery, or a route toward production?
Who owns the problem behind the activity, and how important is it institutionally?
What funding and acquisition mechanisms support the experimentation?
Does the mechanism provide a credible path to follow-on procurement or only a one-time research engagement?
What evidence or customer relationships could participation create even if immediate production does not follow?
Is this activity strategically valuable enough to justify the effort without assuming that experimentation will automatically become demand?

Finding Opportunities in Prime Contractor and Defense Supply Chains

Which major programs or prime contracts contain subsystems, technologies, services, or support needs relevant to us?
Which primes or integrators control access to those portions of the requirement?
What capability gaps, supply-chain vulnerabilities, or customer commitments are they trying to fill?
What evidence would make us credible as a supplier to the prime rather than directly to government?
How much customer visibility, workshare, margin, intellectual property, and future freedom would the supply-chain route preserve?
Are there supplier days, subcontract portals, industrial plans, or published partner needs that reveal upcoming opportunities?
Would entering through the supply chain improve our position enough to justify giving up direct control of the customer relationship?

Connecting an Emerging Military Need to an Identifiable Customer

Which military organization actually experiences or owns the emerging need?
Who is most likely to become the requirement sponsor or accountable problem owner?
Which users or commands can provide evidence that the problem is operationally significant?
Is there an acquisition or program organization likely to act on the need if it matures?
Which budget authority could eventually resource it?
Are several organizations interested in the issue without anyone clearly owning it?
What evidence would allow us to move from a broad need hypothesis to a customer-specific opportunity?

Identifying a Plausible Funding Source and Acquisition Route

What existing or future funding source could realistically pay for this opportunity?
Who controls that funding, and what decisions are required before it can be used?
Which acquisition mechanism could legally and practically place money with a supplier like us?
Could the opportunity use an existing framework, contract vehicle, innovation pathway, prime contract, or new competition?
What eligibility or timing constraints affect those routes?
Has the customer used a similar mechanism for comparable capabilities before?
What additional evidence is needed before the funding and acquisition route are credible enough to support qualification?

Turning Weak Market Signals Into Testable Opportunity Hypotheses

What exactly do we believe may happen, with which customer, around which need, and within what timeframe?
Which observations support that belief and which parts are still inference?
What would need to be true about need, authority, funding, acquisition path, timing, and supplier fit for the opportunity to become real?
Which assumption is most uncertain and most important to test first?
What customer conversation, public record, partner discussion, or acquisition signal could test the hypothesis efficiently?
What evidence would cause us to abandon the hypothesis rather than continue searching for confirming information?
What is the smallest next investment justified while the opportunity remains uncertain?

Developing an Opportunity Before Formal Procurement Begins

What customer problem, requirement, or acquisition uncertainty can we help clarify legitimately before solicitation?
Which stakeholders need to understand our capability, evidence, limitations, or market perspective?
What technical, operational, or commercial evidence would improve our credibility during this stage?
Which requirement assumptions or acquisition choices could still change before the formal process begins?
What partners, certifications, demonstrations, or internal capabilities need to be secured while there is still time?
What procurement-integrity boundaries govern our engagement at this stage?
What position should we aim to have achieved before formal competition makes customer access and solution flexibility more constrained?

Deciding When an Emerging Opportunity Is Ready for Qualification

Is there now a sufficiently specific customer, problem, and potential commercial action to manage this as an opportunity?
Is the need important enough that institutional action is plausible?
Can we identify a credible owner, funding path, acquisition route, and approximate timetable?
Is there a realistic reason our company could participate and compete?
What critical unknowns remain, and are they manageable within a qualified opportunity rather than basic market discovery?
What evidence has changed since this was only a weak signal or market hypothesis?
Does the opportunity now justify formal ownership, pipeline visibility, and additional pursuit resources?

Qualifying Opportunities and Managing the Pursuit Portfolio

Deciding When an Opportunity Is Real Enough to Qualify

Is there a specific military customer, problem, and potential commercial action rather than only general market interest?
What evidence shows that the customer considers the problem important enough to act on?
Can we identify credible requirement ownership, funding, acquisition, and decision pathways?
Is there a plausible timeframe within which the opportunity could become a contract?
Do we have a realistic route to participate and a credible reason we could win?
Which critical uncertainties remain, and are they appropriate for managed qualification rather than basic discovery?
Does the current evidence justify assigning ownership, pursuit resources, and formal pipeline status?

Distinguishing Leads, Prospects, Qualified Opportunities, and Active Pursuits

What minimum evidence should distinguish a lead from a prospect in our military pipeline?
What additional evidence should be required before a prospect becomes a qualified opportunity?
What must be true before a qualified opportunity deserves active pursuit resources?
Are we using stage labels to describe actual customer progress or merely our own level of activity?
Which opportunities have advanced internally without corresponding evidence that the customer has advanced?
What stage should an opportunity occupy when important evidence is missing or has become weaker?
Would another experienced reviewer place each opportunity in the same stage based on the recorded evidence?

Testing Need, Funding, Authority, Acquisition Path, and Timing

What evidence shows that the military need is sufficiently important to support action?
What funding exists or could plausibly become available, and how mature is that funding?
Who possesses the authority to sponsor, approve, fund, acquire, and contract for the requirement?
What acquisition path could realistically convert the need and funding into a supplier contract?
What events or approvals must occur before the opportunity can move forward?
Does the expected timeline align with the customer's operational need, budget process, and procurement process?
Which of need, funding, authority, acquisition path, or timing is currently the weakest link in the opportunity?

Assessing Whether the Company Can Win and Whether the Opportunity Is Worth Pursuing

What credible reasons exist for this customer to select us over the available alternatives?
Where are we currently stronger or weaker than the incumbent and other likely competitors?
Do we possess or have time to build the evidence, relationships, access, team, and solution needed to compete?
What pursuit cost, management attention, technical work, and opportunity cost would competing require?
If we won, would the likely contract provide acceptable margin, cash flow, strategic value, and future potential?
What delivery, security, contractual, or reputational risks could make winning economically unattractive?
Does the combination of win potential and value justify committing scarce pursuit resources?

Estimating Procurement Probability and Probability of Win Separately

What is the probability that the customer will actually proceed with a procurement or other commercial action?
Which evidence increases or decreases confidence that the opportunity itself will happen?
If the opportunity proceeds, what is our probability of winning against the likely alternatives?
Which evidence concerns opportunity maturity and which concerns our competitive position?
Are we accidentally compensating for a weak opportunity by assigning ourselves a high win probability?
How would the expected value change if procurement probability and conditional win probability were modeled separately?
What new evidence would justify changing either probability independently?

Making Pursue, No-Pursue, Continue, and Stop Decisions

What evidence supports committing resources to this opportunity now?
Which qualification, competitive, commercial, or delivery conditions must be true for us to continue?
What unresolved issue could justify a temporary hold rather than a full stop?
What explicit conditions should trigger a no-pursue or stop decision?
Are we continuing because the evidence supports the pursuit or because we have already invested heavily in it?
What better uses exist for the people, budget, and management attention this pursuit would consume?
If this opportunity appeared for the first time today with the evidence we now possess, would we still choose to pursue it?

Requalifying an Opportunity When Material Evidence Changes

What new evidence has changed our understanding of the customer, requirement, funding, timing, competition, or acquisition path?
Does the change make the opportunity more real, less real, more winnable, or less attractive?
Which previous assumptions are no longer valid?
Does the opportunity still meet the qualification criteria that originally admitted it to the pipeline?
Should its stage, probability, expected value, resource allocation, or ownership change?
What new actions or evidence are now required because of the change?
Does the change justify continuing, pausing, restructuring, or stopping the pursuit?

Detecting and Removing Zombie Opportunities

When did this opportunity last receive meaningful new evidence from the customer or buying system?
Has the customer taken any observable action that moves the opportunity toward funding, procurement, or award?
Are repeated internal activities creating the appearance of progress without customer movement?
Have expected milestones slipped repeatedly without credible explanation or replacement dates?
Is the opportunity being kept alive primarily because of historical effort, personal ownership, forecast pressure, or optimism?
What evidence would be required by a specific date for the opportunity to remain qualified?
Should we close, defer, or return the opportunity to monitoring until evidence of genuine movement reappears?

Balancing Long-Cycle Strategic Pursuits With Nearer-Term Opportunities

Which opportunities could create major future value even though procurement remains several years away?
Which nearer-term opportunities can produce revenue, references, learning, or customer access sooner?
How much resource should we devote to shaping future opportunities compared with capturing active ones?
Are long-cycle pursuits consuming resources that should be supporting credible near-term competitions?
Are short-term revenue pressures causing us to neglect strategically important opportunities before competitors establish stronger positions?
Which activities preserve long-term position without requiring full pursuit intensity today?
Does the portfolio provide a sustainable mix of strategic development, active capture, formal competition, and near-term award potential?

Correcting Pipeline Optimism, Incentive Distortions, and Resource Misallocation

Which opportunities carry probabilities, values, or dates that are not supported by current evidence?
Do compensation, forecasting expectations, management pressure, or personal ownership encourage people to keep weak opportunities alive?
Are pipeline stages being interpreted consistently across teams and opportunities?
Which pursuits receive disproportionate resources because of size, prestige, senior sponsorship, or internal politics rather than evidence?
Where are small but credible opportunities being neglected because they appear less strategically impressive?
What independent review or evidence standard would expose systematic optimism or inconsistent qualification?
How should pipeline governance change so that resources follow evidence and expected value rather than enthusiasm?

Building Customer Access and Stakeholder Support

Mapping the Stakeholders Around a Military Opportunity

Which people and organizations are connected to the problem, requirement, funding, acquisition, evaluation, contracting, delivery, and adoption of the capability?
Who will use the capability and who will experience its operational consequences?
Who owns, sponsors, approves, funds, evaluates, acquires, and contracts for the requirement?
Which technical, security, integration, legal, or support stakeholders can materially enable or block progress?
Which external organizations, primes, partners, advisers, or government bodies influence the opportunity?
Where do we currently have meaningful access and where are important stakeholder relationships missing?
Does our stakeholder map reflect the actual decision system rather than only the people we already know?

Understanding What Each Stakeholder Controls, Influences, Fears, and Needs

What formal decision or resource does this stakeholder control?
What outcomes can this stakeholder influence without possessing formal authority?
What professional, operational, technical, commercial, or institutional objectives matter most to them?
What risks or failure modes are they personally responsible for preventing?
What evidence would reduce the uncertainties that matter most to this stakeholder?
What could cause this stakeholder to support, remain neutral toward, or oppose our solution?
Are we engaging this stakeholder based on their actual role and concerns rather than their title alone?

Planning Different Engagement Approaches for Different Stakeholder Roles

What decision or uncertainty should each stakeholder engagement help advance?
What information matters most to operators, requirement owners, technical authorities, acquisition staff, contracting personnel, and senior leaders respectively?
Which stakeholders need detailed technical evidence and which need operational, financial, delivery, or risk evidence?
What legitimate next step should we seek from each stakeholder rather than asking everyone for the same action?
Which conversations should focus on discovery rather than presenting our solution?
How should the sequence of engagements change as the opportunity matures?
What would indicate that our engagement plan is generating broad institutional understanding rather than isolated personal relationships?

Building Credibility Without an Established Defense Track Record

Which parts of our existing commercial, government, or technical experience are genuinely relevant to this military problem?
What evidence can demonstrate that our capability works under conditions that matter to the customer?
Which military-specific uncertainties are not addressed by our existing track record?
Can credible partners, advisers, integrators, references, or independent testing reduce those gaps?
What delivery, security, support, and organizational readiness must we demonstrate in addition to product performance?
How can we acknowledge limited defense experience without overstating transferability or weakening confidence unnecessarily?
What is the fastest credible path from being an unfamiliar supplier to being considered a manageable customer risk?

Preparing for Military Customer Discovery Conversations

What do we already know about the customer's mission, problem, current approach, and institutional context?
Which assumptions do we most need the customer to confirm, reject, or refine?
Who will be in the conversation and what roles do they play in the buying system?
Which questions will help us understand the problem without steering the customer toward our existing product?
What claims or topics should we avoid until we have stronger evidence or specialist guidance?
What information can we legitimately share that would make the conversation more useful to the customer?
What specific learning or next step would make the conversation successful even if no immediate sales action follows?

Preparing for Industry Days, One-to-One Engagements, Conferences, and Demonstrations

What is the customer's purpose for this engagement and what decisions could it inform?
Which stakeholders are likely to attend, and what can we realistically learn or accomplish with each?
What concise message should we communicate about the problem we address and the evidence we possess?
Which questions should we prioritize given the limited time and competitive environment?
What information is likely to be public, shareable, restricted, or inappropriate to seek?
How should we capture observations, commitments, uncertainties, and follow-up actions after the event?
What would distinguish meaningful progress from simply having participated in a high-visibility engagement?

Asking Questions That Reveal the Real Customer Problem

What mission or activity is the customer trying to perform when the problem occurs?
What happens today, and where does performance break down or become unnecessarily difficult?
Who experiences the problem directly and who bears its consequences?
What conditions make the problem better, worse, or operationally significant?
What workarounds does the customer use and what do those workarounds cost or compromise?
What outcome would improve if the problem were genuinely solved?
What answer would disprove our current belief that our offering is relevant?

Maintaining Useful Engagement During Long Periods Without Procurement Activity

What legitimate value can we provide while the customer is not yet ready to procure?
Which changes in the problem, requirement, budget, organization, or acquisition pathway should we continue monitoring?
How often can we engage without becoming repetitive or burdensome?
What new evidence, technical development, customer learning, or market insight would justify another conversation?
Which stakeholders should remain informed even when the opportunity is temporarily inactive?
What signs would indicate that the opportunity is becoming active again?
How do we preserve institutional memory and relationships when military and civilian personnel rotate?

Staying Within Procurement Integrity, Ethics, and Fair Competition Boundaries

What engagement is permitted at the current stage of this customer's procurement process?
Are we seeking information that is legitimately available to us or information that could create an unfair competitive advantage?
Could gifts, hospitality, intermediaries, commissions, or personal relationships create ethical or anti-corruption concerns?
Are we asking a current or former official to influence a process in a way that could violate applicable rules or expectations?
What customer information should we refuse to receive, use, or circulate?
When should legal, ethics, compliance, or contracting specialists review our intended engagement?
Would we be comfortable if the substance and method of this interaction were scrutinized by the customer, competitors, auditors, or the public?

Recovering From Single-Threaded or Fragile Customer Relationships

How dependent is the opportunity on one individual relationship?
Which important stakeholder groups do we currently lack credible access to?
Does support for our solution exist institutionally or only through our strongest contact?
What would happen to the opportunity if that person rotated, changed priorities, or stopped engaging?
How can we broaden relationships without undermining or bypassing our existing contact?
What evidence, documentation, or organizational support can survive personnel turnover?
What engagement plan would create a resilient network across users, requirement owners, acquisition personnel, technical authorities, and decision-makers?

Positioning Military Value and Building Evidence

Translating Product Features Into Military Outcomes and Capability Contributions

What functional effect does each important product feature actually create?
How does that functional effect change a military task, activity, or operating condition?
What operational outcome improves because of that change?
What mission consequence could follow if the improvement is meaningful at scale?
How does the offering contribute to the broader capability rather than claiming to be the entire capability?
Under what conditions does the feature fail to produce the claimed operational value?
Can we explain the value chain from feature to capability contribution without skipping unsupported steps?

Building a Credible Military Value Proposition

What specific military problem are we proposing to improve?
Which customer outcome would change if our solution performs as claimed?
Compared with the customer's current approach or credible alternatives, what is materially better?
What evidence supports each important claim?
What operational, integration, support, security, or lifecycle costs accompany the proposed benefit?
Under what conditions is the value proposition strongest, weakest, or not applicable?
Can the proposition be stated in a way that is specific, bounded, evidence-backed, and meaningful to this customer?

Adapting Positioning for Different Military and Acquisition Stakeholders

Which outcomes matter most to the operators who will use the capability?
What evidence does the requirement owner need to justify institutional action?
What technical, integration, security, or assurance concerns matter to specialist authorities?
What acquisition, schedule, delivery, and support risks matter to program personnel?
What commercial, competition, and contractual concerns matter to procurement and contracting personnel?
What strategic or organizational outcomes matter to senior decision-makers?
Are we changing emphasis for each stakeholder while keeping the underlying claims consistent and truthful?

Determining What Evidence the Customer Needs Before Progressing

What uncertainty is preventing the customer from taking the next decision?
Is the uncertainty about technical performance, military relevance, integration, security, supportability, scalability, cost, or supplier credibility?
Which stakeholder must be satisfied before the opportunity can progress?
What standard or threshold would constitute sufficient evidence for that stakeholder?
Can existing evidence answer the question, or is new testing or demonstration required?
What evidence would be persuasive because it reflects representative military conditions rather than artificial test conditions?
What becomes possible in the customer's decision process once this evidence exists?

Translating Commercial Evidence Into Credible Military Relevance

What has the product already demonstrated in commercial or civilian use?
Which operating conditions in those deployments are genuinely comparable to the military use case?
Which military conditions differ enough that commercial evidence cannot be transferred directly?
What additional risks arise from military integration, security, environment, scale, support, or mission criticality?
Which commercial metrics correspond meaningfully to the military outcome the customer cares about?
What additional testing or evidence would close the most important transfer gaps?
How can we present commercial success as relevant evidence without implying that military suitability has already been proven?

Choosing Between Demonstrations, Trials, Pilots, Experiments, and Other Evidence Activities

What specific customer uncertainty are we trying to reduce?
Does the customer need to see basic functionality, comparative performance, operational utility, integration, fieldability, or scalability?
Which evidence activity is appropriate to the maturity of the solution and the decision being considered?
How representative must the users, environment, data, interfaces, and operating conditions be?
What cost, time, customer commitment, and risk does each evidence option require?
What follow-on decision or acquisition step could success enable?
Are we choosing an evidence activity because it answers a real decision question or simply because the customer is willing to run one?

Designing a Demonstration That Reduces a Material Customer Uncertainty

What exact uncertainty should the demonstration resolve?
Which customer stakeholders need to observe or trust the result?
What baseline or alternative should the demonstrated performance be compared against?
What success criteria should be agreed before the demonstration begins?
How representative are the environment, users, data, interfaces, and operating conditions?
How will results, failures, limitations, and unexpected findings be captured objectively?
What customer decision should become possible if the demonstration succeeds?

Presenting Important Solution Limitations Without Undermining Credibility

Which limitations materially affect the customer's intended use or decision?
Which limitations are known facts and which remain uncertain?
Under what conditions does each limitation become relevant?
What operational or commercial consequence could the limitation create?
What mitigation, workaround, development plan, or boundary exists?
What evidence supports our confidence in the mitigation?
How can we communicate the limitation early enough to build trust without overstating either the problem or our ability to solve it?

Building Evidence Progressively as the Opportunity Matures

What is the minimum evidence needed at the current stage of the opportunity?
Which uncertainties should be resolved before investing in more expensive testing?
How should evidence progress from basic plausibility toward military relevance, operational usefulness, fieldability, scalability, and sustainability?
Which evidence can be reused across customers and which must be customer-specific?
What evidence will later be needed for formal evaluation, contracting, acceptance, or adoption?
Are we generating evidence in a sequence that supports customer decisions rather than accumulating disconnected tests?
What is the next most valuable evidence investment given the current state of the pursuit?

Testing Claims and Evidence for Overstatement, Gaps, and Weak Transferability

Which important claims rely primarily on internal assertion rather than demonstrated evidence?
Does the cited evidence actually test the condition or outcome described in the claim?
Are results from controlled, commercial, or laboratory settings being generalized beyond what they support?
What operating conditions, limitations, sample sizes, or dependencies are missing from the evidence?
Are we confusing technical performance with military relevance, operational utility, fieldability, or scalability?
Which customer objections would expose the weakest claim-evidence link?
How should the claim be narrowed, qualified, or supported before it is used in customer engagement or a formal proposal?

Developing Capture Strategy and Competitive Position

Building an Opportunity-Specific Capture Strategy Before Solicitation

What do we currently know about the customer problem, requirement, funding, acquisition pathway, timing, and decision structure?
What competitive alternatives is the customer likely to consider?
Where are our strongest and weakest positions relative to those alternatives?
What solution, evidence, team, commercial position, and customer support would be required to win?
Which uncertainties or weaknesses can still be changed before solicitation?
What capture actions should have owners, deadlines, and measurable outcomes?
What would need to be true by solicitation release for us to consider our position genuinely competitive?

Constructing a Competitor Picture From Incomplete Information

Which suppliers, incumbents, internal alternatives, or non-purchase options could realistically compete for this customer decision?
What verified information do we have about each competitor's capability, relationships, contracts, evidence, and market position?
What strengths does the customer likely attribute to each alternative?
What weaknesses or risks might matter to the customer?
Which competitor assumptions are based mainly on reputation or industry rumor?
What legitimate public, customer, partner, or market evidence could improve the picture?
Which competitive unknowns are important enough to affect our strategy even if they cannot be resolved fully?

Separating Competitive Facts, Inferences, Hypotheses, and Unknowns

Which competitive statements are supported by verifiable evidence?
Which conclusions are reasonable inferences from known facts but remain unconfirmed?
Which beliefs are only hypotheses that still need testing?
What important questions remain genuinely unknown?
Are we treating repeated internal assumptions as if repetition had converted them into facts?
What evidence could confirm or disprove the most consequential hypotheses?
How would our capture strategy change if the important unknowns resolved against us?

Distinguishing Qualifiers, Differentiators, and Customer-Valued Discriminators

Which capabilities or conditions must every acceptable bidder possess simply to remain eligible?
Where does our offering differ materially from the likely alternatives?
Which of those differences affect an outcome the customer actually values?
Can the difference be demonstrated with credible evidence?
Is the difference difficult enough for competitors to neutralize before evaluation?
Are we mistakenly presenting ordinary compliance or generic strengths as competitive discrimination?
Which small number of customer-valued discriminators should anchor our competitive position?

Inferring Likely Customer Decision Drivers From Legitimate Evidence

What does the customer's stated requirement and evaluation framework reveal about the factors likely to matter?
What do prior procurements suggest about how this customer balances performance, cost, schedule, risk, support, and other considerations?
Which stakeholder concerns repeatedly appear in legitimate customer interactions?
What budgetary, operational, technical, security, or political constraints shape the decision environment?
Which supposed decision drivers are based on our assumptions rather than customer evidence?
How could we test our interpretation without seeking privileged procurement information?
What changes in the customer's circumstances could alter the relative importance of these drivers before award?

Formulating a Defensible Win Strategy

Why would this customer rationally select us rather than each credible alternative?
Which customer priorities does our strategy depend on?
Which strengths and discriminators support that choice?
What weaknesses or customer concerns could undermine the strategy?
What solution, team, evidence, pricing, and delivery position are required for the strategy to remain credible?
Which capture actions must succeed before the strategy can be expressed convincingly in a proposal?
Can we explain the win strategy as a coherent customer decision logic rather than a list of company strengths?

Stress-Testing the Win Strategy Against Named Competitive Alternatives

Why might the customer prefer the incumbent over us?
Why might the customer prefer another challenger, internal solution, or decision not to buy?
Which of our proposed discriminators could competitors credibly match or neutralize?
What weaknesses would a competitor emphasize if arguing against our selection?
Does our strategy still work if the customer weights cost, schedule, integration, or risk differently than we expect?
Which assumptions must be true for our strategy to defeat each named alternative?
What changes should we make now because the stress test exposed a fragile part of the strategy?

Identifying Capture Actions That Can Still Improve the Company's Position

Which current weakness most reduces our probability of winning?
Can that weakness still be changed before formal competition limits our options?
What customer understanding, evidence, partnership, technical work, commercial analysis, or internal decision would improve our position?
Which action has the highest potential effect relative to its cost and remaining time?
Who owns each action and what evidence will show that it succeeded?
Which actions are merely activity and which materially change the customer's reason to select us?
What important disadvantage must we accept because it can no longer be corrected?

Adapting Capture Strategy When Requirements or Acquisition Conditions Change

What exactly has changed in the requirement, funding, schedule, procurement method, evaluation logic, or customer organization?
Which assumptions in the existing capture strategy are now invalid?
Does the change strengthen or weaken our competitive position?
Does our solution, evidence plan, team, pricing approach, or route to market need to change?
Which competitors benefit most from the new conditions?
Is there enough time and economic justification to reposition before formal competition?
Does the revised opportunity still deserve pursuit under our qualification and bid criteria?

Deciding When the Competitive Position Is Too Weak to Continue

Which essential conditions for winning are currently absent?
Are our weaknesses correctable within the remaining time and available resources?
Does the customer have a compelling reason to move away from stronger alternatives or the incumbent?
Are we relying on a single optimistic assumption to justify continued pursuit?
What probability of win is supported by current evidence rather than internal desire?
What resources could be redirected to stronger opportunities if we stop now?
If we had not already invested in the pursuit, would the present competitive position justify entering it today?

Designing Teaming and Partnership Strategy

Deciding Whether to Prime, Subcontract, Join a Consortium, or Use Another Partnering Model

What role gives us the strongest credible position with the customer?
Do we possess the capability, eligibility, balance sheet, delivery organization, customer access, and contracting readiness required to prime?
What would we gain or give up by participating as a subcontractor or technology partner?
Would a consortium, joint venture, reseller, integrator, or other structure solve a material customer or delivery problem?
How would each structure affect margin, control, customer access, intellectual property, risk, and future opportunities?
Which structure would the customer regard as the most credible way to deliver the required capability?
Does the preferred role remain attractive after considering both the pursuit and the business we would actually win?

Identifying Capability, Access, or Delivery Gaps That Require a Partner

Which customer requirements can we not credibly satisfy alone?
Are the gaps technical, geographic, security-related, industrial, contractual, financial, support-related, or relationship-based?
Which gaps are essential to qualification and which merely strengthen competitiveness?
Can we close any gap internally within the available time and cost?
What specific capability or asset must a partner contribute?
Would partnering introduce new dependencies or risks that outweigh the gap it solves?
Which gaps genuinely require partnership rather than simply reflecting internal reluctance to build capability ourselves?

Evaluating Whether a Prospective Partner Materially Improves the Pursuit

What specific weakness or customer concern does this partner improve?
What evidence shows that the partner can deliver the capability, access, or credibility it claims?
Does the customer value the partner's contribution?
How does the partner change our probability of qualifying, winning, and delivering successfully?
What commercial, governance, compliance, reputation, or execution risks would the partner introduce?
Could another partner or internal investment provide the same benefit with fewer disadvantages?
Is the partnership valuable because of demonstrable contribution or mainly because the partner is well known?

Selecting Local, International, and Market-Specific Partners

What local capability, access, support, industrial participation, or eligibility does this market require?
Which prospective partners possess relevant customer relationships without relying solely on claims of influence?
What delivery infrastructure, workforce, certifications, facilities, or supply-chain capabilities can each partner provide?
What reputation and performance history does each potential partner have with this customer and market?
Are there ownership, sanctions, corruption, security, export-control, or conflict-of-interest concerns requiring specialist review?
How would each partner affect economics, intellectual property, customer ownership, and future strategic freedom?
Which partner best solves the market-specific problem while creating an acceptable long-term relationship?

Designing a Customer-Valued Teaming Proposition

What becomes more credible or valuable to the customer because these companies are working together?
How do the partners' capabilities combine into a coherent solution rather than a collection of logos?
Which partner is accountable for each major customer outcome?
Does the team reduce technical, integration, delivery, support, geographic, or commercial risk?
Can the team demonstrate that its interfaces and responsibilities are workable?
What customer concern would remain unresolved even after the team is formed?
Can we explain the team in terms of customer benefit rather than the internal reasons the partners chose each other?

Negotiating Roles, Responsibilities, and Workshare

What scope will each partner own during capture, proposal, contract performance, and support?
Which party will lead the customer relationship and formal submission?
How should workshare reflect actual capability, risk, investment, and customer value?
Who controls solution architecture, integration, pricing inputs, and key delivery decisions?
What dependencies between partners could create schedule or performance risk?
What happens if the customer's final requirement changes the expected workshare materially?
Are roles and responsibilities sufficiently clear to prevent both gaps and duplicated effort?

Managing Exclusivity, Customer Access, and Future Competitive Freedom

Does the proposed partnership require exclusivity, and what legitimate purpose would that exclusivity serve?
Which customers, opportunities, products, technologies, geographies, and time periods would the restriction cover?
Could exclusivity block us from stronger partners or future opportunities?
Who may engage the customer directly, and how will important customer information be shared within the team?
What happens if one party stops performing, withdraws, or becomes competitively unsuitable?
Which rights should survive if the current opportunity is lost or canceled?
Does the agreement preserve enough future freedom to justify the competitive benefit it provides today?

Protecting Intellectual Property, Data, and Confidential Information Within the Team

What existing intellectual property and technical data will each party bring into the relationship?
What new intellectual property could be created jointly during pursuit or performance?
Who may use, disclose, modify, sublicense, or reuse each category of information?
What customer rights could flow through the prime or contract into partner-owned technology?
What information must be shared for the team to function and what information can remain compartmented?
How will confidential customer and partner information be handled if the relationship ends?
Which IP or data terms require specialist review before we disclose information that cannot realistically be recovered?

Governing Partner Contributions During Capture and Proposal Development

What specific capture and proposal deliverables does each partner own?
What deadlines, quality standards, and review processes apply to those contributions?
Who can approve customer messaging, technical claims, pricing inputs, and contractual assumptions on behalf of each partner?
How will inconsistent partner positions be identified and resolved?
What happens if a partner misses deadlines or provides weak evidence?
How will sensitive competitive, pricing, and proprietary information be shared appropriately?
Does the governance structure allow the team to make timely decisions without hiding unresolved disagreements?

Repairing, Restructuring, or Replacing a Partnership That Is Weakening the Pursuit

What evidence shows that the current partnership is reducing rather than increasing our chance of success?
Is the problem caused by capability, performance, trust, governance, economics, customer perception, or strategic divergence?
Can clearer responsibilities, changed workshare, stronger governance, or executive intervention repair the relationship?
What contractual or competitive restrictions affect our ability to change partners?
How would restructuring or replacement affect the customer, solution, schedule, evidence, and proposal?
Is there a credible alternative partner or internal solution available within the remaining time?
At what point is preserving the existing partnership more damaging than accepting the disruption of changing it?

Navigating Formal Competitions and Bid Requirements

Determining What Type of Formal Opportunity the Customer Has Issued

What decision is the customer actually making through this RFI, RFP, ITT, framework call, innovation challenge, prototype solicitation, or other mechanism?
Is the customer seeking market information, technical learning, supplier qualification, competitive selection, contract award, or a step toward a later decision?
What legal or procedural rules govern this particular competition?
What rights or opportunities follow from success at this stage, and what does success not guarantee?
Which customer organizations and authorities control the process?
How does this mechanism affect permitted engagement, evaluation, negotiation, pricing, and proposal strategy?
What would we misunderstand about the opportunity if we treated this mechanism like a conventional competitive tender?

Revalidating the Bid Decision Against the Actual Competition Documents

Does the released solicitation confirm the customer need, scope, funding, timing, and acquisition assumptions on which our pursuit was based?
Are we definitely eligible to participate under the actual conditions stated by the customer?
Can our proposed solution satisfy every mandatory requirement without unacceptable compromise?
Does the published evaluation approach support the competitive advantages on which our capture strategy depends?
Can we produce the required evidence, team, pricing, delivery plan, and submission within the available time?
Have new commercial, security, legal, delivery, or contractual requirements materially changed the attractiveness of the opportunity?
Knowing the actual competition terms, should we bid, change our approach, seek clarification, or stop?

Decomposing the Solicitation Into Requirements, Instructions, and Evaluation Logic

Which provisions define what the customer needs the supplier to deliver?
Which provisions govern how the response must be structured, formatted, submitted, and certified?
Which requirements are mandatory conditions of participation or compliance?
Which criteria will actually be evaluated or scored?
What evidence must accompany each response for the evaluator to credit it?
Where do contractual terms, pricing requirements, assumptions, and delivery commitments connect to the technical response?
Can every important solicitation provision be traced to a clear response owner and treatment plan?

Separating Mandatory Compliance From Scored Competitive Opportunity

Which requirements must be satisfied simply to remain eligible?
Which criteria allow evaluators to distinguish between acceptable bids?
Are any apparently minor compliance requirements capable of causing rejection regardless of proposal quality?
Which evaluated areas offer meaningful room to demonstrate superior customer value?
Are we investing excessive proposal effort in unscored areas while underinvesting in high-value criteria?
Which discriminators are relevant to the published evaluation rather than merely important to us?
Does our proposal strategy clearly separate "must comply" from "must persuade"?

Resolving Ambiguous, Contradictory, Incomplete, or Unrealistic Requirements

Which solicitation provisions have more than one plausible interpretation?
Where do different parts of the competition documents contradict each other?
What information is missing that materially affects solution design, price, schedule, risk, or compliance?
Which requirements appear technically, commercially, or operationally unrealistic?
Can we resolve the issue internally from the full solicitation, amendments, or referenced documents without asking the customer?
What clarification is required before we can make a responsible commitment?
If ambiguity remains unresolved, how should it be reflected in assumptions, qualifications, pricing, or the bid decision?

Preparing Clarification Questions Without Unnecessarily Revealing Strategy

What uncertainty must the customer resolve for us to prepare a compliant and responsible bid?
Can the question be answered from existing competition documents before we ask it formally?
How can we phrase the question neutrally without revealing our solution architecture, pricing logic, weakness, or discriminator?
Could the question inadvertently alert competitors to an issue or opportunity they may not have recognized?
Is the clarification seeking legitimate understanding rather than attempting to influence the competition improperly?
What answer would materially change our technical, commercial, or bid decision?
Which clarification questions are important enough to submit despite the information they may reveal?

Managing Customer Amendments, Answers, and Changing Bid Instructions

What has changed since the solicitation was first issued?
Which requirements, evaluation criteria, deadlines, contract terms, or submission instructions are affected?
Does the customer response clarify the issue fully or create new ambiguity?
Which proposal sections, solution elements, prices, assumptions, or compliance positions must now change?
Who owns implementation and verification of each amendment?
Does any change materially affect our qualification, competitive position, cost, risk, or decision to bid?
How will we ensure that no team member continues working from superseded instructions?

Governing Proposal Assumptions, Qualifications, and Exceptions

Which parts of our offer depend on facts or conditions the customer has not confirmed?
Which assumptions affect price, scope, schedule, performance, integration, support, or delivery risk?
Which assumptions can remain explanatory and which require formal customer acceptance?
Where are we unable or unwilling to comply fully with a stated requirement or term?
What is the commercial or operational consequence if the customer rejects an assumption, qualification, or exception?
Are assumptions and exceptions being recorded consistently across technical, pricing, contractual, and delivery sections?
Which unresolved position is serious enough to require executive or specialist approval before submission?

Navigating Multi-Stage, Negotiated, and Down-Selection Competitions

What decision will the customer make at the current stage?
What must we prove now, and what can legitimately wait until later stages?
How will the field of competitors change after each down-selection?
What information, solution detail, or pricing commitment should we provide at this stage without unnecessarily limiting future flexibility?
What customer feedback or negotiation opportunity may become available between stages?
Which assumptions in our capture strategy must be revisited after each customer decision?
How should our investment level change as the probability and value of advancing through the competition change?

Controlling Formal Submission Requirements, Deadlines, and Bid Mechanics

What exact submission deadline, time zone, portal, file format, naming convention, and delivery method apply?
What page limits, word limits, templates, forms, signatures, certificates, and attachments are mandatory?
Which parts of the submission require approvals or inputs from external partners or executives?
What portal registration, encryption, file-size, or technical constraints could prevent successful submission?
What internal deadline provides enough time for final validation and recovery from submission problems?
Who has authority to release the final bid and confirm that the submitted package is complete?
What evidence will we retain that the correct version was submitted successfully and on time?

Developing and Reviewing Military Proposals

Translating Capture Strategy Into the Proposal Architecture

What customer decision logic should the proposal make easy for evaluators to follow?
Which customer priorities and evaluated criteria should organize the response?
Where should our most important discriminators and supporting evidence appear?
How should the proposal connect the customer problem, solution, evidence, delivery approach, and commercial offer?
Which themes must remain consistent across technical, programmatic, commercial, and executive sections?
What content is necessary for compliance but should not distract from the core win strategy?
Does the proposal architecture visibly express our capture strategy rather than merely mirror the solicitation table of contents?

Organizing the Proposal Team Around Clear Ownership and Decision Rights

Who owns each proposal volume, section, response, attachment, and supporting artifact?
Who has authority to resolve technical, commercial, contractual, and messaging disagreements?
Which contributors provide inputs without owning the final response?
What dependencies between authors could create schedule or consistency problems?
How will partner contributions be integrated and reviewed?
Who controls configuration, versioning, and final incorporation of approved changes?
Is accountability clear enough that every missing or weak section has one identifiable owner?

Maintaining Traceability From Requirements Through Evidence, Pricing, and Commitments

Can every solicitation requirement be traced to a specific proposal response?
Can every evaluated claim be traced to credible supporting evidence?
Can every promised feature, service, milestone, or performance level be traced to delivery capability?
Do technical commitments align with the assumptions used in pricing?
Do pricing assumptions align with contract terms and delivery responsibilities?
Are qualifications, exceptions, and dependencies visible wherever they affect the offer?
Could we reconstruct how each important contractual commitment originated from the solicitation and proposal?

Developing a Coherent Technical and Operational Solution Narrative

What military problem and intended outcome should the solution narrative address?
How does the proposed solution work in the customer's actual operating context?
What are the major components, interfaces, dependencies, and responsibilities?
How does technical performance translate into operational utility?
What evidence supports the most important technical and operational claims?
What limitations, integration requirements, or enabling conditions must the customer understand?
Does the narrative read as one coherent capability rather than disconnected product descriptions?

Integrating Programmatic, Security, Commercial, Legal, and Delivery Perspectives

Does the technical solution create delivery commitments that the program plan can realistically support?
Are security and cybersecurity obligations reflected in the proposed architecture and schedule?
Do commercial assumptions match the actual solution scope and delivery dependencies?
Have legal and contractual positions been reflected consistently across the proposal?
Are supply-chain, support, training, acceptance, and sustainment responsibilities aligned?
Where do different functional contributors currently make conflicting assumptions?
What cross-functional issue could become an expensive post-award problem if not reconciled before submission?

Writing Persuasive, Evidence-Backed Responses to Evaluation Criteria

What exactly is the evaluator being asked to assess in this criterion?
What clear claim should the response make about our ability to satisfy or exceed that need?
Why does that claim matter to the customer's outcome or risk?
What evidence demonstrates that the claim is credible?
How does the response distinguish us where differentiation is relevant and permitted?
Can an evaluator easily find the answer, evidence, and customer benefit without inferring them?
Does the response avoid unsupported marketing language, generic company claims, and irrelevant detail?

Using Past Performance, References, and Prior Evidence Effectively

Which previous projects are genuinely comparable to the customer's requirement?
What aspect of each reference demonstrates relevant technical, operational, delivery, or support capability?
How similar were the scale, environment, security constraints, interfaces, and mission consequences?
What measurable outcome did we achieve?
Which differences limit how far the reference can legitimately be generalized?
Does the customer require formal past-performance information in a specific format or from particular contract types?
Are we using references to prove a relevant point rather than simply displaying recognizable customers?

Running Early Proposal Reviews Before Major Weaknesses Become Expensive

Does the proposal structure align with the solicitation and capture strategy before extensive writing begins?
Are major compliance gaps visible early enough to correct?
Are key discriminators supported by evidence rather than assumed?
Does the proposed solution remain coherent across technical, programmatic, and commercial sections?
Which high-risk sections require early specialist or executive attention?
Are authors solving the right customer problem rather than writing from internal product perspectives?
What major weakness would become expensive to repair if we allowed drafting to continue unchanged?

Running Evaluator-Focused Red Teams and Final Challenge Reviews

Can an evaluator find a complete response to every scored criterion?
What score would each section plausibly earn based only on what is actually written?
Which claims lack enough evidence to receive full credit?
Where could ambiguity, inconsistency, or excessive complexity reduce evaluator confidence?
What weaknesses would a strong competitor exploit if comparing our offer against theirs?
Which late changes would materially improve evaluation outcome and which would merely create churn?
Is the proposal ready to submit based on evaluator value, compliance, coherence, and risk rather than author familiarity?

Reconciling Cross-Proposal Inconsistencies Before Final Approval

Do technical descriptions remain consistent across all proposal volumes and attachments?
Are quantities, dates, milestones, staffing levels, and performance figures identical wherever repeated?
Do pricing, scope, assumptions, and contract positions describe the same commercial offer?
Are partner roles and workshare represented consistently?
Do security, integration, support, and delivery commitments agree across sections?
Has any late change been incorporated everywhere it has downstream consequences?
Can executives approve the proposal knowing that it represents one internally consistent set of commitments?

Pricing and Structuring the Commercial Offer

Identifying the Pricing Regime and Contract Economics

What pricing rules, cost principles, competition conditions, or government-specific requirements apply to this opportunity?
Is the customer expecting a fixed price, cost-reimbursement structure, time-and-materials approach, subscription, framework rate, or another model?
Which costs are allowable, recoverable, capped, reimbursable, or carried by the supplier?
What volume, duration, option, indexation, or funding assumptions materially affect the economics?
Does the proposed contract type transfer significant cost or performance risk to us?
What price documentation or justification may the customer require?
How should the pricing regime change the way we model risk, margin, cash flow, and negotiation flexibility?

Building a Realistic Cost-to-Deliver Model and Price Floor

What direct labor, material, subcontract, software, infrastructure, travel, support, and other costs are required to perform the scope?
Which indirect costs and overheads must be allocated to the contract?
What contingency is justified by identifiable delivery uncertainty?
Which customer dependencies could increase our costs if they are delayed or incomplete?
What cost assumptions are least certain and most sensitive to change?
What margin or risk premium is necessary for the contract to remain economically acceptable?
Below what price would we be accepting an expected economic loss or an unjustifiable risk profile?

Estimating Customer Affordability and a Defensible Price-to-Win Range

What evidence exists about the customer's available budget or affordability ceiling?
What has the customer paid for comparable capabilities or outcomes?
How might the customer value performance, risk reduction, schedule, support, and lifecycle economics relative to price?
What price range are credible competitors likely to offer based on legitimate available evidence?
Which of our discriminators could justify a premium and which are unlikely to influence willingness to pay?
How much uncertainty remains around customer affordability and competitor pricing?
What price range could be both competitively credible and economically acceptable without pretending that a precise "winning price" is knowable?

Structuring Pricing for Uncertain Volumes, Minimums, and Options

What quantities is the customer committed to buy and what quantities are only possible future demand?
How do unit economics change as volume rises or falls?
What minimum order, production run, or commitment is necessary to protect our economics?
Should pricing use tiers, bands, options, breakpoints, or separate fixed and variable elements?
Which setup, integration, tooling, or nonrecurring costs should be recovered independently of volume?
What happens economically if the customer exercises only some options or buys much less than expected?
Does the structure give the customer useful flexibility without transferring unlimited volume risk to us?

Accounting for Schedule Uncertainty, Inflation, and Economic Escalation

How long will the contract remain exposed to labor, material, energy, currency, or supplier price changes?
Which cost categories are most sensitive to inflation or escalation?
What delivery or approval delays could extend the period of exposure?
Does the contract permit indexation, economic price adjustment, repricing, or another mechanism for managing escalation?
Which indices or formulas would reflect our actual cost drivers most accurately?
What assumptions should be included in the price if no adjustment mechanism is available?
How much margin could disappear under plausible inflation and schedule scenarios?

Pricing Configuration Changes, Technical Uncertainty, and Customer Dependencies

Which parts of the solution are fully defined and which remain subject to customer decisions or technical discovery?
What customer-furnished information, equipment, facilities, approvals, or interfaces does our cost depend on?
Which configuration changes could materially alter engineering, testing, integration, or support costs?
Can uncertain work be separated into options, allowances, provisional items, or later-priced changes?
What assumptions must be stated explicitly to prevent undefined scope from being treated as included?
How should risk be allocated when neither side can reliably estimate the eventual work?
Does the proposed pricing structure protect both competitiveness and economic viability as uncertainty resolves?

Pricing Support, Sustainment, and Lifecycle Obligations

What support, maintenance, training, spares, updates, field service, warranties, or sustainment activities are included?
Over what operating life and usage level must those services be provided?
What failure rates, repair volumes, staffing levels, and logistics assumptions drive cost?
Which lifecycle obligations are fixed and which depend on actual customer usage?
How should technology refresh, software updates, obsolescence, and supply-chain changes be priced?
Does the customer evaluate total lifecycle cost rather than acquisition price alone?
Are we pricing a sustainable support capability or underestimating long-term obligations to make the initial offer attractive?

Structuring Payment, Financing, and Working Capital Requirements

When will we incur the largest costs relative to when the customer pays us?
What advance payments, milestones, progress payments, acceptance events, or invoicing terms are available?
How much working capital must we finance before cash is received?
Could customer acceptance delays materially extend our cash-conversion cycle?
Are significant supplier payments due earlier than customer receipts?
What financing cost or liquidity risk should be reflected in the commercial offer?
Can payment structure be improved without changing headline price in a way that materially strengthens the economics?

Distinguishing Competitive Pricing From Unsustainable Underpricing

Does the proposed price recover realistic expected delivery cost?
What assumptions must hold for the planned margin to be achieved?
Are we relying on optimistic volume, productivity, supplier pricing, or change revenue to make the economics work?
Are we discounting because customer value and competition justify it or because internal pressure demands a lower number?
What delivery behavior would be required after award to compensate for an underpriced bid?
Could an artificially low price create performance, relationship, cash-flow, or reputational problems?
Would we still want to win at this price if no favorable change orders or follow-on work ever appeared?

Testing the Offer's Economic Viability Under Different Delivery Scenarios

What happens to margin if labor effort exceeds plan?
What happens if volumes are lower or higher than forecast?
What happens if delivery, acceptance, licensing, or customer dependencies are delayed?
How sensitive is cash flow to payment timing and milestone slippage?
What happens under plausible inflation, currency, supplier, or material-cost changes?
Which combination of adverse conditions would make the contract economically unacceptable?
Does the proposed price and structure remain viable across a realistic range of delivery outcomes rather than only the base case?

Managing Contract Risk and Negotiation

Identifying Contract Terms That Materially Change Supplier Risk

Which contractual provisions could create financial exposure disproportionate to contract value?
What obligations go beyond what was assumed in the proposal or price?
Which terms transfer schedule, performance, customer-dependency, security, or third-party risk to us?
What termination, warranty, indemnity, liability, audit, or remedy provisions require particular attention?
Which obligations could constrain our technology, intellectual property, future customers, or business model?
What terms differ materially from our standard commercial position?
Which provisions require specialist or executive review before we can accept them?

Distinguishing Priceable, Contractually Allocable, and Unacceptable Risks

Can this risk be estimated sufficiently to include an economic allowance in the price?
Can the risk be reduced through clearer scope, assumptions, limits, exclusions, or shared responsibility?
Which party is actually best able to control the underlying cause of the risk?
Could insurance, contingency, or another financial mechanism make the exposure manageable?
Is the potential downside bounded or effectively unlimited?
Would any realistic price compensate us adequately for accepting the risk?
Should the risk be priced, negotiated into a different allocation, or treated as a condition we cannot accept?

Protecting Intellectual Property, Software, Technical Data, and Reuse Rights

What background intellectual property are we bringing into the contract?
What new intellectual property, software, data, designs, or documentation may be created during performance?
What rights does the customer require to use, modify, disclose, reproduce, maintain, or compete the capability?
Could those rights expose proprietary technology to competitors or future suppliers?
What third-party or partner intellectual property limits the rights we can grant?
Which rights must we retain to support future products, customers, upgrades, and international business?
What contractual language requires specialist IP review before we commit?

Assessing Liability, Warranty, Performance, and Availability Obligations

What events could make us liable for loss, damage, failure, delay, or third-party claims?
Are liability caps, exclusions, and indemnities proportionate to the contract and risks we control?
What exactly are we warranting about performance, reliability, defects, or fitness for use?
What service levels, availability targets, response times, or performance guarantees apply?
What remedies, credits, damages, or re-performance obligations follow if targets are missed?
Which customer actions, operating conditions, or external systems affect our ability to meet the obligation?
Can we operationally and economically support these obligations throughout the contract term?

Assessing Security, Compliance, and Flow-Down Obligations Before Acceptance

Which security, cybersecurity, export, regulatory, or customer-policy obligations become contractual requirements?
Which requirements must be flowed down to subcontractors, suppliers, cloud providers, or partners?
Can every relevant party actually comply with the required terms?
What reporting, audit, incident-response, recordkeeping, or certification obligations apply?
What cost and organizational burden has been assumed in the price?
What breach consequences could follow from noncompliance?
Which obligations require specialist confirmation before we accept contractual responsibility?

Understanding the Customer's Negotiating Position, Alternatives, and Constraints

What outcome does the customer most need from the negotiation?
What alternatives does the customer have if agreement with us is not reached?
What alternatives do we have if we decline the customer's position?
Which customer positions may be constrained by law, procurement rules, policy, budget, or delegated authority?
Who on the customer side has authority to change price, scope, schedule, risk allocation, or contract terms?
What timing pressure or operational urgency affects each side?
Which issues are likely genuine constraints and which may be negotiable positions?

Defining Essential, Negotiable, Tradable, and Unacceptable Commercial Positions

Which terms must we obtain for the deal to remain viable?
Which positions are important but can be modified within defined limits?
What items have value to the customer that we could trade at relatively low cost to ourselves?
Which requested terms create exposure we are not authorized or willing to accept?
What is our target, minimum acceptable position, and walk-away point for each major issue?
Who has internal authority to approve movement beyond the planned range?
Are our negotiation positions prioritized clearly enough to avoid fighting equally hard over issues of very different importance?

Exchanging Concessions Without Giving Away Value Independently

What does the customer want that we might be willing to concede?
What should we receive in return before making that concession?
How valuable is the concession to the customer compared with its cost or risk to us?
Can concessions be made conditional on agreement elsewhere?
Are we reducing price or accepting risk before the customer has made reciprocal movement?
How are concessions being recorded so the team does not repeat or contradict them?
Does each concession move the overall package closer to an acceptable agreement rather than simply narrowing one issue?

Converting Proposal Assumptions and Qualifications Into Contractual Positions

Which proposal assumptions remain relevant to scope, price, schedule, performance, or risk?
Has the customer explicitly accepted, rejected, or superseded each important assumption?
Which assumptions should become contractual dependencies or customer responsibilities?
Which qualifications or exceptions must be reflected directly in the contract language?
Are any proposal protections likely to disappear if they are not carried into the final agreement?
What changes to assumptions require corresponding changes in price, schedule, or scope?
Does the final contract accurately reflect the basis on which we agreed to offer the work?

Completing Specialist and Executive Risk Review Before Contract Signature

Which unresolved issues require legal, finance, tax, export, security, insurance, IP, technical, or other specialist judgment?
Have specialists reviewed the actual final contract language rather than earlier drafts or summaries?
What residual risks remain after negotiation?
Are those risks understood by the executives authorized to accept them?
Does the final economics still justify the contract after all negotiated changes?
Have any late concessions created delivery commitments that operational teams have not approved?
If we win exactly the contract now ready for signature, under the written conditions, do we still want to win it?

Transitioning From Award and Managing the Customer Relationship

Conducting the Commercial Transition Immediately After Award

What must move from the pursuit team into the delivery organization immediately after award?
Which customer commitments, deadlines, conditions, and contractual milestones require immediate action?
What assumptions or unresolved issues from negotiation still need active management?
Which customer and partner relationships require formal introduction to post-award owners?
What governance, reporting, invoicing, change, and escalation processes must be established?
Which early mistakes could damage customer confidence before delivery has properly begun?
How will we confirm that everyone responsible for performance understands the commercial basis of the award?

Transferring Pursuit Promises, Assumptions, and Customer Context Into Delivery

What did we explicitly promise in the proposal, negotiation, demonstrations, and customer discussions?
Which commitments became contractual and which remained informal expectations?
What assumptions underpinned our price, schedule, technical approach, and resource plan?
What customer sensitivities, decision history, stakeholder concerns, and competitive context should delivery leaders understand?
Which risks were accepted consciously during pursuit and now require operational mitigation?
What important knowledge exists only in the memories of capture or sales personnel?
How will we document and confirm the handoff so delivery does not rediscover critical context after problems emerge?

Clarifying Ownership Between Account, Program, Commercial, and Support Teams

Who owns contract delivery and day-to-day program performance?
Who owns formal contract interpretation, changes, claims, and commercial positions?
Who owns continuing customer relationships and future opportunity development?
Who owns service, support, warranty, and user-facing operational issues?
Which decisions require coordination rather than unilateral action by one function?
Who may make commitments to the customer and within what authority?
Are escalation paths clear enough to prevent customer issues from falling between organizational boundaries?

Maintaining Stakeholder Continuity After the Pursuit Team Changes

Which customer stakeholders were important during the pursuit and remain important after award?
Who inside our company now owns each relationship?
What context must be transferred before capture or sales personnel reduce involvement?
Which new delivery, support, technical, or contracting relationships must be established?
How will we maintain continuity when customer personnel rotate?
Are we preserving multiple institutional relationships rather than depending on the original champion?
What regular engagement will keep both sides aligned without duplicating formal program governance?

Managing Customer Expectations During Delivery

What does the contract actually require compared with what individual stakeholders may expect?
Which customer expectations were created during the sales process but were never incorporated formally?
What delivery uncertainties should be communicated before they become surprises?
How should progress, limitations, dependencies, and risks be explained without creating unnecessary alarm?
What customer actions or decisions are required for us to meet schedule or performance commitments?
Where should expectations be corrected through conversation and where is a formal contract change required?
Are we maintaining trust through predictable communication rather than optimistic reassurance?

Responding to Customer Dissatisfaction and Emerging Delivery Risk

What exactly is the customer dissatisfied with, and what evidence supports that understanding?
Is the underlying issue technical, schedule-related, commercial, relational, support-related, or expectation-driven?
What contractual obligation or customer expectation is affected?
What immediate action can contain the problem while the root cause is investigated?
Who should own communication, corrective action, and escalation?
What should be documented formally to preserve a shared understanding of the issue and response?
What lesson should change delivery or account behavior after the immediate problem is resolved?

Detecting New Customer Needs Through Delivery Experience

What new operational problems are becoming visible as customers use the capability?
What recurring requests or workarounds suggest unmet needs beyond the existing contract?
Are changing missions, threats, organizations, technologies, or user populations creating new requirements?
Which requests reflect dissatisfaction with current delivery and which represent genuinely new value?
Who owns the emerging need and how broadly is it recognized?
Is there a plausible funding and acquisition pathway for addressing it?
What evidence is needed before treating the observation as a future opportunity rather than informal customer interest?

Distinguishing Current Obligations, Contract Changes, and New Opportunities

Is the requested work already included in the contract scope?
Does the request clarify an existing obligation or add a genuinely new requirement?
What schedule, cost, technical, security, or resource impact would the additional work create?
Does the customer representative making the request have authority to change the contract?
Should the work proceed only after a formal change is authorized?
Is the request better treated as a separate future procurement rather than modification of the existing contract?
How can we protect the relationship while refusing to provide uncontracted scope informally?

Turning Delivery Performance Into Credible Commercial Evidence

Which delivery outcomes demonstrate capabilities that future customers will care about?
What measurable performance, reliability, schedule, support, or operational results can be documented?
Which results can the current customer legitimately confirm or reference?
What security, confidentiality, classification, or contractual restrictions limit what we can disclose?
What lessons make our future claims more precise and credible?
How can performance evidence strengthen renewals, recompetes, adjacent opportunities, or new markets?
Are we collecting evidence systematically while it is available rather than attempting to reconstruct it later?

Protecting the Customer Relationship Without Overpromising or Giving Away Scope

What legitimate customer need is behind the request or concern?
Can we support the customer within existing contractual obligations?
Would accommodating the request create new cost, risk, schedule, or precedent?
Are we tempted to promise something because maintaining goodwill feels easier than discussing scope?
What can we offer conditionally while the commercial implications are resolved?
When should account personnel involve program, commercial, or contracting specialists before responding?
How can we remain responsive and constructive while preserving appropriate boundaries around obligations and value?

Developing Follow-On Business, Recompeting, and Learning From Outcomes

Identifying Follow-On Production, Contract Options, and Continuation Opportunities

What contractual options, additional quantities, phases, extensions, or follow-on production paths already exist around the current award?
Which customer decisions, funding actions, performance milestones, or operational results must occur before continuation becomes possible?
What evidence from current delivery would strengthen the case for exercising an option or ordering additional capability?
Who owns the decision to continue, expand, or fund the capability beyond the current commitment?
How do the economics, risks, and competitive conditions of follow-on work differ from those of the initial contract?
What actions should we take now to preserve a credible path to continuation without assuming that current success guarantees future business?
When should a potential continuation move from account observation into a separately qualified commercial opportunity?

Expanding Into Adjacent Units, Commands, Services, or Customer Organizations

Which other military units, commands, services, agencies, or organizations experience a similar problem to the current customer?
How transferable are the current solution, evidence, interfaces, and operating assumptions to those adjacent users?
What differences in mission, authority, funding, procurement, security, or infrastructure could make the adjacent opportunity materially different?
Can the existing customer legitimately provide evidence, references, or introductions that improve our credibility with the adjacent organization?
Would the adjacent organization buy independently, through the current customer, through a central acquisition body, or through another route?
What additional adaptation, certification, partnership, or support capability would expansion require?
Does the adjacent opportunity deserve independent qualification rather than being treated as automatic account growth?

Developing Upgrade, Modernization, and Additional Capability Opportunities

What new operational needs, threats, user feedback, technology changes, or obsolescence issues create a credible case for upgrading the current capability?
Which improvements are necessary to maintain existing usefulness and which represent genuinely additional customer value?
Who owns the requirement and funding decision for an upgrade or modernization effort?
Can the proposed enhancement be implemented within the existing architecture, or would it require substantial integration, testing, or redesign?
How should we distinguish product-roadmap improvements we would make anyway from customer-specific work that should be funded commercially?
Could the upgrade create new intellectual property, support obligations, interoperability requirements, or competitive exposure?
When is an upgrade best pursued as a contract change, an option, a separate procurement, or part of a future recompete?

Developing Sustainment, Support, Training, and Lifecycle Business

What recurring maintenance, support, spares, training, updates, logistics, field service, or sustainment needs arise from the deployed capability?
Which lifecycle activities does the customer intend to perform internally and which could reasonably be provided by an external supplier?
What usage rates, fleet size, operating environment, deployment pattern, and service expectations determine the scale of the support need?
What evidence from current delivery shows that we can provide reliable lifecycle support at the required tempo and geography?
How should support be structured so that the customer receives continuity without becoming unnecessarily dependent on us?
What pricing, staffing, inventory, technology-refresh, and obsolescence assumptions determine whether the lifecycle business is economically sustainable?
Should the opportunity be pursued through the current contract, a support agreement, a framework, a separate procurement, or another mechanism?

Using an Initial Military Win to Develop International Opportunities

Which foreign military customers face a sufficiently similar problem for the existing capability and evidence to be relevant?
What parts of the original customer's requirement, operating environment, integration, and evidence transfer credibly to the new market?
Which export controls, security rules, national industrial policies, localization requirements, or government approvals could limit transfer?
Can the original customer be referenced, and what contractual, security, classification, or political restrictions govern that reference?
Does the new country require a different prime, local partner, acquisition route, support model, or sovereign capability arrangement?
How should we separate the credibility created by the initial win from evidence that the new customer has real demand and accessible funding?
Does each international opportunity remain attractive after accounting for adaptation, access costs, regulatory constraints, and delivery complexity?

Requalifying Expansion Opportunities Rather Than Assuming Existing Relationships Will Convert

What specific customer need and commercial action make this expansion opportunity real?
Is there an identifiable requirement owner, funding path, acquisition mechanism, and timetable for the additional business?
Are we assuming that positive relationships or current contract performance will automatically translate into another purchase?
How does the competitive environment differ from the one in which we won the original business?
Does the customer have alternatives, procurement obligations, or incumbent relationships that could limit our advantage?
Would we still qualify this opportunity if it came from a customer with whom we had no existing contract?
What evidence should be required before account interest becomes a forecasted or actively pursued expansion opportunity?

Managing Account Growth Without Becoming Dependent on One Military Customer

What proportion of our revenue, backlog, pipeline, and future growth depends on this customer or customer system?
Which products, teams, facilities, certifications, or investments have become economically dependent on continued business from this account?
How vulnerable would we be to a budget cut, leadership change, program cancellation, procurement shift, or loss at recompete?
Are customer-specific requirements pulling our product, organization, or strategy away from broader market opportunities?
Which capabilities or evidence created through this account can be reused to diversify into other customers and markets?
What level of account concentration is commercially acceptable given the stability, margins, strategic value, and switching risk involved?
What diversification actions should we take while continuing to serve and grow the customer successfully?

Preparing for Renewal or Recompete Before the Current Contract Ends

When is the current contract, option period, framework position, or support arrangement likely to face renewal or recompete?
What decisions and budget actions will the customer make before the formal competition begins?
What evidence from current performance should we build and preserve before the customer evaluates future suppliers?
How might the customer's mission, requirement, technology, budget, or acquisition strategy differ by the time of recompete?
Which competitors are likely to challenge our position, and what advantages could they offer that the customer does not receive today?
What technical, commercial, relationship, support, or partnership weaknesses should we correct while there is still time?
At what point should the recompete become a formally governed capture effort rather than an account-management concern?

Challenging Incumbency Assumptions and Addressing Customer Dissatisfaction Before Recompete

What evidence shows that the customer is genuinely satisfied rather than simply continuing to work with us under the current contract?
Which unresolved delivery, support, cost, usability, integration, or relationship issues could become weaknesses at recompete?
Are we mistaking access to the customer and knowledge of the installed system for a guaranteed competitive advantage?
Where could a challenger offer lower switching risk, better economics, newer technology, stronger evidence, or a more attractive commercial model?
What aspects of our own current solution would we attack if we were trying to displace ourselves?
Which customer concerns can still be corrected before they become formal evaluation issues?
If we approached the recompete as a challenger to our own contract, what would we change in our capture strategy?

Learning From Wins, Losses, Pilots, and Terminated Pursuits

What does the available evidence show about why the customer, opportunity, pilot, or pursuit produced the outcome it did?
Which conclusions come directly from customer feedback or observable facts, and which remain internal interpretation or speculation?
Was the original opportunity qualified correctly in terms of need, funding, authority, acquisition path, timing, competitiveness, and economics?
Which parts of market understanding, customer engagement, evidence building, capture, teaming, proposal development, pricing, or negotiation materially affected the outcome?
What did we believe during the pursuit that later proved wrong, incomplete, or unsupported?
What specific change to our processes, decision criteria, evidence standards, or behavior should follow from the learning?
How will we ensure that the lesson influences future pursuits rather than remaining an isolated retrospective observation?

Archive of Christian Ullrich

Selling to the Military Reflex Area

Table of Contents

Selecting Military Markets and Customers

Comparing Military Markets Before Committing Resources

Assessing Strategic Fit Between the Company and a Military Market

Selecting Mission Areas and Capability Problems to Pursue

Prioritizing Military Customer Organizations

Comparing Geographic Markets for Entry

Estimating Accessible Opportunity Behind Headline Defense Spending

Testing Market-Level Demand, Funding, and Urgency

Assessing Competitive Openness and Incumbent Structure

Deciding Whether to Enter Early, Wait, or Continue Watching

Deferring or Exiting an Unattractive Military Market

Understanding Military Buying Systems and Decision Structures

Reconstructing How an Unfamiliar Military Customer Buys

Distinguishing Users, Sponsors, Funders, Buyers, and Contracting Authorities

Tracing Who Owns and Approves the Requirement

Tracing Where Funding Comes From and Who Controls It

Identifying the Acquisition Organization and Contracting Authority

Mapping Formal Authority and Informal Influence

Understanding Centralized, Decentralized, Service, and Joint Buying Structures

Understanding How Different Types of Military Acquisition Are Organized

Reconstructing the Need, Budget, Procurement, and Delivery Timelines

Testing Assumptions About How the Customer's Buying System Works

Understanding Military Needs, Requirements, and Demand

Understanding the Military Problem Before Positioning a Solution

Distinguishing Symptoms, Requested Features, Requirements, Problems, and Outcomes

Testing Whether a Need Is Institutionally Important

Assessing How Mature a Military Need Has Become

Tracing How a Requirement Emerged and How It May Change

Interpreting Requirements Shaped by Legacy Solutions or Assumptions

Challenging the Customer's Initial Problem Framing Credibly

Identifying Latent or Emerging Needs Before Formal Requirements Appear

Determining Whether a Military Problem Is Commercially Addressable

Distinguishing Enthusiasm and Experimentation From Genuine Demand

Navigating Defense Market Access and Eligibility

Determining Whether the Company Is Eligible to Compete

Assessing Classification and Industrial Security Requirements

Assessing Cybersecurity and Protected Information Requirements

Evaluating Foreign Ownership, Control, or Investment Constraints

Determining How Export Controls and Sanctions Affect the Pursuit

Assessing Localization, Offset, Sovereignty, and Industrial Participation Requirements

Navigating Supplier Registrations, Frameworks, and Approved Vendor Requirements

Determining Whether Local Presence or a Local Partner Is Required

Evaluating the Cost and Timing of Removing Market Access Barriers

Recognizing When Access Constraints Require Specialist Support or Make the Market Inaccessible

Discovering and Developing Military Opportunities

Monitoring Strategic and Operational Signals for Emerging Demand

Using Budgets, Acquisition Plans, and Procurement Forecasts to Find Opportunities

Using Historical Awards and Contract Expirations to Anticipate Recompetes

Discovering Opportunities Through Experiments, Innovation Programs, and Research Activity

Finding Opportunities in Prime Contractor and Defense Supply Chains

Connecting an Emerging Military Need to an Identifiable Customer

Identifying a Plausible Funding Source and Acquisition Route

Turning Weak Market Signals Into Testable Opportunity Hypotheses

Developing an Opportunity Before Formal Procurement Begins

Deciding When an Emerging Opportunity Is Ready for Qualification

Qualifying Opportunities and Managing the Pursuit Portfolio

Deciding When an Opportunity Is Real Enough to Qualify

Distinguishing Leads, Prospects, Qualified Opportunities, and Active Pursuits

Testing Need, Funding, Authority, Acquisition Path, and Timing

Assessing Whether the Company Can Win and Whether the Opportunity Is Worth Pursuing

Estimating Procurement Probability and Probability of Win Separately

Making Pursue, No-Pursue, Continue, and Stop Decisions

Requalifying an Opportunity When Material Evidence Changes

Detecting and Removing Zombie Opportunities

Balancing Long-Cycle Strategic Pursuits With Nearer-Term Opportunities

Correcting Pipeline Optimism, Incentive Distortions, and Resource Misallocation

Building Customer Access and Stakeholder Support

Mapping the Stakeholders Around a Military Opportunity

Understanding What Each Stakeholder Controls, Influences, Fears, and Needs

Planning Different Engagement Approaches for Different Stakeholder Roles

Building Credibility Without an Established Defense Track Record

Preparing for Military Customer Discovery Conversations

Preparing for Industry Days, One-to-One Engagements, Conferences, and Demonstrations

Asking Questions That Reveal the Real Customer Problem

Maintaining Useful Engagement During Long Periods Without Procurement Activity

Staying Within Procurement Integrity, Ethics, and Fair Competition Boundaries

Recovering From Single-Threaded or Fragile Customer Relationships