RESEARCH & INSIGHTS · STRATEGY FIRM CASE : BEHAVIORAL PROJECTIONS
« How do you integrate 24-month behavioral projections into a strategy consulting firm's deliverables? »
A strategic recommendation describes what should be done. The next question, the one executive leadership asks when making the trade-off, is different : what happens when the populations concerned start reacting?
A European strategy firm — 340 consultants, presence in 8 countries, positioned at the premium end of executive advisory — wanted to answer that question without diluting the methodology that defines its signature.
- FIRM
- 340 consultants, 8 European countries
- PROJECTION HORIZON
- 24 months of behavioral trajectories
- FIRST YEAR
- 18 client engagements with projections
- ADDITIONAL FEES AT 18 MONTHS
- 6,8 M€
THE CONTEXT
Competitive
concurrentielle
that plays out
in the field
methodological.
The firm was facing growing competitive pressure from large US consulting firms. Those firms were investing heavily in advanced quantitative analysis and positioning their offers as natively incorporating predictive modeling, while the European firm remained based on a traditional strategy-consulting methodology.
Executive teams at large European companies increasingly expected quantified projections of the impacts of proposed decisions over 12- to 36-month horizons. Large US consulting firms offered these projections through traditional econometric models.
The partnership leadership explored a partnership with a precise objective : integrate 24-month behavioral projections into client deliverables without diluting the firm's brand or signature methodology.
WHAT THE DECISION HAD TO SOLVE
- COMPETITIVE PRESSURElarge US consulting firms were investing heavily in advanced quantitative analysis and positioning their offering as natively integrating predictive modeling
- A SHIFT IN CLIENT EXPECTATIONSexecutive teams increasingly expected quantified projections of the impacts of proposed decisions over 12- to 36-month horizons
- A METHODOLOGY NOT TO DILUTEcompetitive analysis, qualitative interviews, sector benchmarks, expert recommendations: the firm's signature and brand asset
- DIFFERENTIATION SOUGHTa projection grounded in behavioral modeling rather than purely economic modeling, better aligned with executives' execution concerns
A MECHANISM : DO NOT REPLACE, AUGMENT
The methodology
remains central.
What is added
is the execution
logic.
The partnership was structured around a clear principle : it does not alter the firm's signature methodology; it adds a 24-month behavioral-projection layer. Qualitative interviews, competitive analysis and sector benchmarks remain at the heart of the method.
The projections complement operational recommendations by quantifying expected impacts of proposed decisions : customer adoption, internal resistance, displacement effects and market trajectories. This architecture preserves the firm's methodological identity.
A DISTINCTION : INDICATORS VS BEHAVIORS
One projects
a trajectory.
The other describes
how it
unfolds.
The two approaches are not opposed point for point. Behavioral modeling, grounded in stakeholder typologies and adoption or resistance dynamics, is perceived by executives as more aligned with their concrete execution concerns than purely econometric models.
- WHAT A RECOMMENDATION SAYSwhat should be done, supported by competitive analysis, interviews and the firm's sector expertise
- WHAT IT DOES NOT SAYwhat happens when the populations concerned begin reacting to the decision, month by month
- WHAT AN ECONOMETRIC MODEL PROJECTSa trajectory of indicators: what could happen to the aggregates over the horizon considered
- WHAT A BEHAVIORAL PROJECTION ADDSthe execution logic: through which adoptions, resistances and displacement effects the trajectory forms
An econometric model asks about indicators. A behavioral model asks about the actors who produce — or prevent — the trajectory of those indicators.
That second question is the one executive teams ask when making the trade-off, and it was the one the firm's methodology could not yet address quantitatively.
WHAT IS BUILT
Two service families
of services,
a single
signature.
The system exposes a dedicated API to the firm, hosted on French infrastructure and calibrated for strategy-consulting use. Consultants define the scenarios to test; the system produces the projections.
- 01FRAMINGthe firm's consultants define the stakeholder typologies and strategic scenarios to test on the engagement
- 02GENERATIONthe API produces coherent synthetic populations based on those typologies: customers, employees, partners, regulators, public opinion
- 03PROJECTION24-month behavioral trajectories for these stakeholders under each scenario considered
- 04SIGNATUREthe deliverable remains the firm's: strategic recommendation and execution projection, under its brand and methodology
The first service family generates coherent synthetic populations based on stakeholder typologies defined by consultants for each engagement : customers, employees, partners, regulators and public opinion depending on the configuration.
The second produces 24-month behavioral projections of these stakeholders' trajectories under the strategic scenarios considered by the firm.
THE POPULATION
These are not
of indicators.
They are
of the
stakeholders.
The typologies are not supplied by the system : they are defined engagement by engagement by the firm's consultants, based on their sector knowledge and interviews. The system instantiates them as coherent populations.
CLIENTS
typologies defined by consultants for each engagement, instantiated as coherent synthetic populations
EMPLOYEES
the internal resistance triggered by a transformation decision, projected over 24 months
PARTNERS AND REGULATORS
stakeholders who condition execution without being the decision's customers
PUBLIC OPINION
mobilized according to engagement configuration when the decision carries public exposure
The typologies used vary by engagement configuration. No personally identifiable data enters the system ; the infrastructure is hosted in France.
CALIBRATION
Integrating a capability
is not
plugging in an API.
- 01
TEN WEEKS OF CALIBRATION
The partnership was preceded by a 10-week calibration phase before any real client engagement.
- 02
SIXTY-EIGHT PARTNERS AND DIRECTORS TRAINED
The firm's 68 partners and directors were trained to use the API during this phase.
- 03
TWO RETROSPECTIVE PILOT ENGAGEMENTS
Two pilot engagements were conducted on anonymized cases from the firm's history to compare projections with outcomes observed later.
- 04
COMPARABLE ACCURACY, GREATER RICHNESS
The retrospective projections aligned with the observed outcomes with accuracy comparable to retrospective econometric models, while providing richer analysis of behavioral dynamics.
Ten weeks of calibration, 68 partners and directors trained, two retrospective pilot engagements : the capability exists only once it has been calibrated, validated and taught. That sequence, not the technical availability of the API, determines the activation date.
FIRST REVELATION
The technology
was not meant to
erase the brand.
The firm remains the author of the strategy. The projection layer is methodological : it appears neither as a third-party tool in the deliverable nor as an actor in the client relationship. Integrations designed as an additional layer on the existing methodology are better accepted internally and valued more commercially than those designed as replacement or redesign.
Technology creates more value when it strengthens existing expertise than when it tries to take its place.
SECOND REVELATION
Projection
became
an argument
as a competitive advantage.
Of the 18 engagements conducted in the first year of the partnership, the firm identified 6 engagements won explicitly because of the newly integrated behavioral-projection capability. Those 6 engagements would not have been won without the partnership, under the competitive conditions against large US firms bidding for the same mandates.
WITHOUT THE PROJECTION CAPABILITY
A respected methodology — but a client expectation met by the competitor
WITH THE PROJECTION CAPABILITY
6 engagements won — 8,2 M€ in billed fees
Methodological differentiation is not an intangible extra : here it is a determinant of winning engagements against competitors with stronger commercial positions.
DEPLOYMENT
Four months
after signature,
eighteen engagements
in twelve months.
AAUGMENTED STRATEGY ENGAGEMENTS
12 engagementsTraditional strategy consulting augmented with a projection layerAdditional feesBTRANSFORMATION PLANS
4 engagementsDesign of 24- to 36-month transformation plansAdditional feesCGOVERNANCE DECISIONS
2 engagementsPreparation of major governance decisionsAdditional feesEvery engagement was billed with an additional fee justified by the added projection capability.
RESULTS AT 18 MONTHS
The chain,
from consultant framing
to the recommendation
signed by the firm.
- CLIENT EXECUTIVE TEAM
- FRAMING BY CONSULTANTS
- STAKEHOLDER TYPOLOGIES
- SYNTHETIC POPULATIONS
- STRATEGIC SCENARIOS
- 24-MONTH PROJECTIONS
- RECOMMENDATION SIGNED BY THE FIRM
Additional fees generated by the projection capability total €6.8 million over 18 months. The 6 engagements won because of the capability represent an additional €8.2 million. Conversion on bids against large US consulting firms is up 22 % over the period. The firm industrialized the methodology across its full strategy offering and is preparing to deploy the partnership in its Asian subsidiaries.
A BUSINESS MECHANISM
AI did not
reduce fees.
It increased
billable value.
Internal efficiency does not mechanically imply lower prices. Here, the technology did not shorten the engagement : it added a capability to the deliverable that clients were willing to pay for on every engagement concerned.
- ENGAGEMENTS WITH 12-MONTH PROJECTIONS
- 18 engagements
- ADDITIONAL FEES AT 18 MONTHS
- 6,8 M€
- ENGAGEMENTS WON BECAUSE OF THE CAPABILITY
- 6 engagements — 8,2 M€
- CONVERSION AGAINST LARGE US CONSULTING FIRMS
- +22 %
WHAT THIS CASE ADDS
An infrastructure
partner,
not a vendor
not a tool.
- INFRASTRUCTURE
- A methodological partner, not a tool vendor
- INCREASE
- Add a layer rather than replace a method
- DIFFERENTIATION
- Projection becomes a competitive argument
- CLIENT RELATIONSHIP
- Framing and client relationship remain with the firm
- VALUE
- A capability converted into fees and win rate
TAKEAWAY
The firm did not need
need to become
a technology
company.
It needed something that
than the technology
made its methodology
harder to beat.
Integration as an additional layer preserves a signature methodology better than replacement. The firm's methodology remains at the heart of the offer ; the additional layer enriches it without distorting it. This principle requires a partnership architecture that respects established methodological identities rather than subverting them.
Methodological differentiation against dominant competitors is a structural commercial instrument, not a positioning claim : here it is measured in engagements won, fees billed and conversion rate.
POSSIBLE FUTURES
Three ways
to meet the same expectation.
A
INTEGRATE NOTHING
Keep the methodology alone against competitors equipped with predictive capabilities
- signature methodology preserved
- client demand for quantified projections left unmet
- competitions lost to large US consulting firms
B
BECOME A TECHNOLOGY COMPANY
Redesign the methodology around a modeling tool
- visible predictive capability
- diluted methodological identity
- fragile internal acceptance, weakened brand
C
AUGMENT THE EXISTING METHODOLOGY
An additional layer of 24-month behavioral projections under the firm's brand
- 18 client engagements in the first year
- 6 engagements explicitly won because of the capability, 8,2 M€ in fees
- 6,8 M€ in additional fees at 18 months
- +22 % conversion against large US consulting firms
A real case.
An unnamed firm.
This case is based on an API integration partnership for a European strategy firm. The client is not named, no personally identifiable data entered the system, and the detailed results remain the client's property.
Only information documented in the source case — firm scope, API architecture, calibration, engagement volumes, fees and conversion rate — is reproduced here.
