DARLING PROJECTSSTRATEGIC BUSINESS DEVELOPMENT • GROWTH ARCHITECTURE • CRM SYSTEMS

WIN MORE

Focus where conditions that increase the probability of business development success already exist.

TYPE
Strategic Business Development Dossier

CLASSIFICATION
Commercial Framework

VERSION
Working Publication Draft

Orientation

Business development depends on the quality of focus before the quality of pursuit.

Every account, market, contact, referral, and conversation carries a different probability profile. The work begins by recognizing where favorable conditions already exist, where they are emerging, and where additional evidence is required before resources are committed.

This dossier is written as an operating reference for practical business development. It avoids sales theater, motivational language, and generic persuasion doctrine. The emphasis is opportunity intelligence, value alignment, strategic fit, stakeholder structure, question architecture, and shared future-state success.

Opportunity quality improves when visible conditions, organizational movement, stakeholder access, and provider strengths converge.

Selection

Which accounts, markets, and stakeholders deserve attention based on observable conditions?

Alignment

Where do customer objectives, provider strengths, economics, and timing fit together?

Advancement

What evidence supports movement to the next stage of investment?

Opportunity Architecture

An opportunity is a temporary alignment between independent systems.

A customer operates within objectives, constraints, risk tolerance, budgets, politics, priorities, and timing. A provider operates within capabilities, capacity, economics, delivery model, experience, and strategic direction. The environment adds competitive pressure, market change, regulatory movement, technology shifts, and trigger events.

Business development becomes more effective when these systems are read together rather than separately.

CUSTOMER SYSTEM

PROVIDER SYSTEM

ENVIRONMENTAL SYSTEM

HIGH-PROBABILITY OPPORTUNITY

Operating Implication

Account selection should consider the visible condition of the customer, the strategic fit of the provider, and the movement occurring in the environment. A problem alone is insufficient. Capability alone is insufficient. The useful signal is alignment among systems.

Value Alignment

Customer value and provider value must be evaluated together.

A customer may value a deliverable that a provider can produce. That does not automatically make the opportunity attractive. The stronger condition occurs when the desired customer outcome aligns with provider strengths, economics, differentiation, and strategic direction.

Commodity-Fit Scenario

Customer requirement: raw survey data, tables, basic output.

Provider capability: available.

Assessment: the request can be fulfilled, but may underuse strengths in interpretation, executive communication, and strategic reporting.

Value-Alignment Scenario

Customer requirement: findings, implications, recommendations, executive-ready reporting.

Provider strength: analysis, interpretation, communication, strategic insight.

Assessment: customer value, provider strength, differentiation, and economics align.

Harris Interactive Example

In a market research environment, a client may request respondent data. The data has value. The organization can deliver it. The stronger business development opportunity appears when the client needs understanding: what the results mean, what actions they imply, what leadership should consider, and how findings support decisions.

That distinction matters. Raw data satisfies a request. Insight supports a decision. Executive reporting, findings, implications, and recommendations move the engagement away from commodity output and toward strategic contribution.

Definition: Value alignment exists when the outcome valued by the customer corresponds with the strengths, economics, and strategic interests of the provider.

Signals & Metadata

Status describes what exists. Movement reveals what may be changing.

Business development intelligence often comes from accumulated observations that appear minor in isolation. Leadership movement, hiring patterns, technology investments, acquisitions, expansion, and strategic announcements become more useful when interpreted together.

Signal Type	Observable Examples	Potential BD Relevance
Leadership Movement	New CEO, CIO, CFO, VP Sales, operating leader	New priorities, renewed initiatives, sponsor access, strategic reset
Investment Activity	Funding, facility expansion, technology modernization, hiring	Budget availability, operational change, growth objectives
Operational Pressure	Backlog, service complaints, performance gaps, regulatory deadlines	Urgency, risk reduction, process improvement need
Market Movement	Competitor change, customer expectations, new regulation, industry disruption	Repositioning, differentiation, blue ocean openings

OBSERVE

→

CAPTURE

→

INTERPRET

→

TRIANGULATE

→

ACT

Metadata should support timing, account selection, stakeholder mapping, and question design. The goal is to stay close enough to organizational movement that outreach can be relevant before the opportunity becomes obvious to everyone else.

Question Architecture

Questions are sensors.

A strong question does more than collect information. It reveals structure: priorities, constraints, authority, urgency, assumptions, stakeholder relationships, decision criteria, and commitment level.

Stage	Question Function	Example Question	Signal Revealed
Account Selection	Identify visible movement	What changed inside this account that warrants attention?	Timing, trigger events, strategic relevance
Initial Contact	Establish relevance	Is this initiative tied to a current operating priority?	Need strength, urgency
Discovery	Clarify outcomes	What would a successful future state look like six months after implementation?	Value alignment, stakeholder expectations
Qualification	Test commitment	What information would need to be confirmed before assigning resources?	Decision process, seriousness, next action
Advancement	Confirm movement	Who else needs to validate this before the next step?	Stakeholders, authority, access

Question Design Rules

Match the question to the stage.
Ask for evidence, not reassurance.
Listen for what changed, who cares, and what happens next.
Capture answers in a way that improves future account intelligence.

Blue Ocean as One Strategy

Blue Ocean thinking is useful when competition itself is a poor organizing principle.

Some opportunities improve when the provider competes better. Other opportunities improve when the provider changes the basis of comparison. Blue Ocean strategy belongs in the second category.

Red Ocean Condition

Multiple providers are evaluated against similar criteria: price, feature list, availability, and familiarity.

Direct comparison increases pricing pressure and reduces differentiation.

Blue Ocean Response

Reframe value around a different business issue, stakeholder outcome, operating model, or future-state advantage.

The goal is improved fit, not novelty for its own sake.

Method	Application	Effect
Redefine Value	Shift from deliverable to outcome	Less commodity comparison
Address Overlooked Stakeholders	Include users, operations, finance, compliance, or leadership	Broader support
Combine Capabilities	Package research, reporting, strategy, and execution	Stronger differentiation
Create New Criteria	Introduce speed, trust, continuity, risk reduction, or future-state fit	Improved positioning

Stakeholder Architecture

Organizations decide through people with different definitions of value.

Stakeholder alignment requires more than identifying the economic buyer. It requires understanding who benefits, who approves, who influences, who implements, who absorbs risk, and who may be affected by change.

Stakeholder	Typical Focus	Relevant BD Question
Executive Sponsor	Strategic result, risk, timing, business impact	Which outcome matters enough to justify action now?
Financial Authority	Cost, return, budget fit, tradeoffs	How will this be evaluated against other priorities?
Operational Owner	Implementation, continuity, workload, adoption	What must remain stable during execution?
Technical Evaluator	Feasibility, integration, security, reliability	Which constraints define the safe path forward?
User Group	Usability, workflow, practical impact	What changes in daily work if this succeeds?

Stakeholder alignment is strongest when the future state makes sense from more than one seat at the table.

Opportunity Assessment Matrix

Winning and worth winning are separate evaluations.

An opportunity can be winnable and still be strategically weak. A strong assessment considers customer need, provider fit, economic fit, stakeholder access, and timing together.

LOW STRATEGIC FIT

HIGH STRATEGIC FIT

HIGH CUSTOMER NEED

Serviceable Opportunity
Can be pursued when capacity allows. Watch margin pressure and differentiation limits.

Priority Opportunity
Customer need and provider strengths align. Strong candidate for focused pursuit.

LOW CUSTOMER NEED

Low Priority
Limited reason to invest unless strategic account value exists elsewhere.

Development Opportunity
May become attractive if need, timing, or stakeholder urgency changes.

Assessment Standard

Each advancement should improve visibility. If the next action does not clarify need, value alignment, strategic fit, stakeholder access, timing, trust, or commitment, the action may be activity without meaningful diagnostic value.

Operating Creed

Focus where favorable conditions exist. Account selection is a strategic business development function.
Read movement before status. Change events often create more useful signals than static account descriptions.
Use questions as sensors. Each question should improve visibility into structure, commitment, risk, timing, or alignment.
Separate capability from fit. The ability to perform work does not automatically make the work strategically attractive.
Distinguish customer value from value alignment. A customer may value a deliverable that underuses provider strengths.
Look for shared future-state success. Strong opportunities improve conditions for the stakeholders required to advance them.
Advance with evidence. Movement should be supported by observable behavior, documented priorities, access, information, or commitment.

Final Position: Business development success improves when time, attention, and resources are concentrated on opportunities where customer need, provider strengths, stakeholder alignment, timing, economics, and desired future state already intersect.