A professional-services company presents a strategy for moving towards a recurring software offer. The presentation explains why customers want a service they can use without commissioning a separate project, and why a standard product could support a different relationship with them.
Staff can see the attraction. At the next planning meeting, however, the product team has little protected time, client projects still require the same specialists, and nobody has agreed which customer requests the standard offer will exclude. The story explains an opportunity while leaving important choices open.
That distinction matters without making the story worthless. A strategic narrative can connect evidence, explain a proposed position, and help people understand why their work may need to change. It becomes insufficient when the organisation treats agreement with that explanation as approval of a specific course of action.
The company needs to establish what has been decided, what is being investigated, and what commitment the next stage requires. A useful account of the strategy can carry all three, with enough clarity to prevent aspiration, hypothesis, and funded work from appearing interchangeable.
Understanding What the Narrative Contributes
The recurring-software proposal needs a reason that people can examine. Customers may want a capability more frequently than a project model provides, while repeated delivery work may reveal a function that can be standardised. Those observations can explain why a product opportunity deserves attention.
The narrative should connect that evidence to the proposed approach. It might explain which customer problem the product addresses, what existing alternatives fail to provide, and why the company appears capable of building a worthwhile offer.
This reasoning helps distributed decisions. A designer can assess whether a request serves the intended customer need. A salesperson can understand why the company is not trying to reproduce every element of its consulting service in software. Without that context, a task list can be specific while still leaving teams unable to judge a new situation.
The explanation also needs limits. Early interviews may establish interest without proving sustained demand. Repeated project work may suggest commonality without showing that the exceptions are economical to support. The narrative should distinguish those findings rather than turn an appealing connection into a confident forecast.
Different audiences need different detail. A board may consider investment and risk, staff may need implications for their work, and customers need an accurate account of what is available. Those versions should remain consistent without requiring every communication to include the complete operating plan.
The problem is therefore an unclear relationship between explanation and commitment, rather than narrative as a form of communication. A clear story can improve strategic judgment when readers can identify which claims have support and which choices remain to be made.
Identifying the Decisions the Explanation Has Not Settled
The product opportunity leaves several substantive choices. The company needs to define the initial customer group, the capability it will standardise, and what service it will provide for cases outside that scope. It also needs to decide how much capacity it will devote before stronger evidence is available.
Those choices affect the kind of business being built. A broadly configurable product may require different support and pricing from a narrow application. Accepting extensive customer-specific work could preserve consulting revenue while preventing the product team from developing a repeatable offer.
The organisation should compare plausible alternatives, including continuing the current model with targeted improvements. A compelling case for change does not establish that one particular product plan is the best response. The comparison needs expected benefits, costs, uncertainties, and the consequences of displaced work.
The Green Book’s appraisal guidance provides a structured example of assessing different ways to pursue an objective. A commercial company needs its own financial and market analysis, but the practice of examining alternatives helps prevent the narrative from carrying the decision by itself.
Strategic intent and decisions should remain distinguishable in the record. Leadership may support exploring a recurring offer without having approved a full replacement of the services business. That distinction gives teams a clearer account of what they are authorised to promise and spend.
An advisory engagement can help investigate those choices without making them for the company. Data and strategy services illustrate why the agreed scope matters: recommendations, an approved investment, and an operating result are different deliverables. A useful assessment makes the next decision possible rather than imply that implementation has already been secured.
The record should state who will resolve an open choice and what information is needed. An explicit investigation can be a sound stage of strategy. A question left invisible in an apparently complete plan is harder to manage.
Making the First Commitment Specific Without Fixing Every Task
The company might approve a bounded trial around one recurring customer task. That commitment should identify the intended result, available capacity, operating conditions, and evidence needed for a further investment.
The development team needs a realistic place in the resource plan. If its specialists continue to carry full project commitments, leadership should explain how the trial fits or revise the allocation. A small investment may be appropriate for early learning, provided it can answer the question being asked.
The trade-off should include effects on current customers and staff. Some projects may move, temporary cover may be needed, or the trial may be narrower than the original ambition. Those consequences should reach the people affected rather than remain a private assumption in the budget.
Clear authority should cover scope changes, customer promises, and exceptions. The team can make implementation choices within an agreed remit, while a material change to the offer or investment goes to the authorised owner.
Specificity should support useful decisions, not prescribe every action. A headcount number does not establish what capability the team has, and a long roadmap does not prove that dependencies are ready. The plan needs enough context for specialists to investigate and improve the route.
The trial also needs an operating account. Who reviews customer data, supports users, and responds if the service behaves incorrectly? Manual steps can be appropriate during investigation, but their effort and limitations belong in the result rather than disappear from the business case.
The strategy document can connect these commitments to the explanation. It should show what approval means now and what later decisions remain conditional, instead of presenting every future stage as equally settled.
Testing Whether the Proposed Business Works
The first trial should examine the mechanism behind the opportunity. Can suitable customers complete the recurring task? Do they return, require extensive help, or ask for a different capability? Is the value sufficient to support a plausible price and operating model?
These questions need evidence beyond launch activity. Accounts created and demonstrations delivered can show interest or progress without establishing a repeatable business. Usage needs interpretation, and reported willingness to pay should not be treated as equivalent to a sustained commercial relationship.
The Magenta Book’s evaluation guidance distinguishes implementation from impact questions. The company can apply that distinction by examining whether the intended experience was actually provided and whether the observed result supports the business hypothesis.
Comparison matters where the company wants to make a causal claim. A change in customer spending may reflect a wider relationship, a promotion, or ordinary variation. The report should state what the available design can establish and where a contribution claim is more defensible than a precise attribution.
The company should also assess the cost of producing the result. Revenue from the pilot may depend on specialist assistance that cannot be sustained at the proposed price. A useful product may emerge with a narrower scope, a different service tier, or another customer group than the first narrative anticipated.
Those findings should be able to revise the plan. A persuasive story is not evidence against an inconvenient result. Equally, one poor observation should not automatically end an investment that needs a longer period or a corrected implementation before the relevant question can be assessed.
The review should explain why the next action follows from the evidence. Expansion, a focused further trial, a changed approach, and closure are all possible decisions. Their quality depends on the reasoning and consequences rather than whether they preserve the initial presentation.
Keeping the Story Consistent With the Current Commitment
As the company learns, it should update its explanation and the related operating records. If the product is now intended for a narrower group, Sales, delivery teams, and customer communications need the relevant change. An internal decision is incomplete if people continue acting on an earlier promise.
Handoffs should preserve the reasons behind the current scope and the questions still open. Staff should not need to infer the strategy from several presentations with different dates or depend on a colleague’s memory of the original discussion.
A review should also examine what earlier commitments remain. Services customers may still need support, contracts may limit what can stop, and shared staff may require a transition period. Moving towards a product business does not remove those responsibilities simply because the story describes a new destination.
Leadership can rebuild confidence through a dependable connection between explanation, decisions, and action. That may include acknowledging that an earlier assumption was wrong or that an expected investment is no longer justified. Consistent reasoning and honest updates can matter more than keeping every sentence unchanged.
The narrative remains useful when it helps people understand why the company is making its current choices. The operating commitments show what those choices require, and evidence from delivery tests whether they remain worthwhile. For this company, a credible strategy holds those elements together without asking a compelling story to stand in for the decisions it has not yet made.
