A comparison between acquisition and internal development can become persuasive before it becomes precise. One column contains a substantial purchase price; the other contains a smaller training or recruitment budget. The difference appears to support an obvious conclusion. Yet the two routes may provide different organisations, relationships and readiness at different times. A workshop is more than a collection of individual skills, and a development programme is more than a cheaper version of an operating enterprise. Strategy needs to explain those differences before asking the expenditure figures to decide the matter.
In our fictional case, a ₹26 crore workshop acquisition was compared with a two-year capability-development route. Eighteen potential trainees were considered, twelve met the entry conditions and six needed further preparation. The selected programme carried ₹3.4 crore authorisation. That decision did not establish that the company had obtained the proposed workshop's capability for ₹22.6 crore less. It had selected a narrower route with a different timetable and unresolved learning. Treating the amounts as equivalent prices would have concealed the very consequences the strategic decision needed to examine.
The acquisition sponsor's concern was practical. Customers might need the work before the internal route could supply it. Participants might leave, progress more slowly than expected or require additional experience. An existing workshop could bring supervisors, methods, relationships and an operating context that the company could not reproduce simply by paying for training. I considered those points part of the comparison rather than objections to dismiss. Choosing development meant accepting that some work would remain outside current capability and that the enterprise would need arrangements for those needs while learning continued.
The acquisition alternative also needed an honest account. Buying a business does not remove the work of understanding it or make its expertise instantly available throughout the purchaser's organisation. Integration can alter how judgement is exercised, as my earlier quotation-process error demonstrated. A workshop may bring capability within a defined context without supporting every assignment the purchaser wants to undertake. Qualified technical owners must establish the actual scope. Strategy should therefore avoid treating acquisition as immediate universal competence just as carefully as it avoids treating attendance at training as completed capability.
## Compare the work each route can actually support
I would start the comparison with the work the enterprise needs to support. Which assignments are in scope, when are they needed and what conditions must be established before they can be entrusted to the proposed organisation? The answer requires qualified people, not a strategist constructing a competence claim from a list of certificates. The strategy team's role is to make the business choice intelligible once those conditions are understood. A useful account connects scope, timing and responsibility, so that directors can see what the selected route will provide and what will remain unavailable.
## Keep learning stages attached to the capability claim
The review point in our programme was deliberately bounded. Eight of the twelve participants had completed the first stage; four were continuing it. Expenditure was ₹2.2 crore, leaving ₹1.2 crore unspent authorisation. A completed first stage did not mean independent qualification for every repair. The account retained both the progress and the limits, without calling the programme a failure because it was unfinished or a complete success because some participants had progressed. The next decision needed to examine the actual stage reached, not a general impression that capability was now inside the company.
This distinction can be uncomfortable in public leadership writing. A headline that says capability was built appears stronger than one that says a defined first stage was completed. The broader claim may be unsupported. A useful case study can instead show why the slower route was chosen, what it required and how progress affected the next decision. That account reveals judgement without attributing an operating result that the evidence does not establish. It also gives proper recognition to the technical colleagues responsible for training and assessment, whose work should not disappear into a strategist's claim of transformation.
There is a legitimate concern that too many qualifications make decisions harder to communicate. Directors cannot examine every detail of every training stage or acquisition workstream. The answer is to retain the distinctions that change the commitment. If a proposal depends on people being able to undertake particular work by a particular point, the status of that capability belongs in the main account. Details that do not alter the decision can sit elsewhere. Clarity is not achieved by promoting every intermediate milestone into a final capability; it is achieved by explaining which stage matters and why.
The cost comparison also needs a consistent boundary. A training authorisation may omit continued external support, management attention or opportunities the company chooses not to pursue while developing capability. An acquisition price may omit integration effort or future investment. The fictional figures do not provide a complete lifecycle comparison of every route, so I do not manufacture one. I can state the authorisation and expenditure actually described, explain what each alternative concerns and identify the further assessment required. A smaller initial commitment can be appropriate without being proof of superior total economics.
## Let the slower choice retain the opportunity it gives up
Timing should likewise remain a strategic choice rather than an inconvenience hidden after approval. If the company chooses a two-year route, it must understand what that means for the market it is prepared to serve now. It may deliberately forgo some opportunities, maintain qualified external arrangements or limit the initial offer. Those consequences should be discussed before the programme is presented as a complete answer to growth. A realistic timetable can still support ambition. It prevents the institution from promising the market an organisation that its own development plan says does not yet exist.
For a board, I would frame oversight around the capability assumption supporting the business plan. Directors should understand who establishes competence, what work is authorised, which stages remain unfinished and what happens if the expected progress changes. That does not make them training assessors or technical supervisors. It lets them examine whether the commercial proposition is consistent with the organisation available to deliver it. They should also hear why management preferred development or acquisition and what evidence would justify revisiting the choice, rather than treating approval as a reason to defend the original route indefinitely.
My conclusion is that a capability decision should retain its organisation and its clock. The company selected a bounded development route in this example and accepted its unfinished state. Another business might reasonably need the acquisition route or a different partnership. The useful strategic work lies in making those alternatives comparable in meaning, not merely in currency. A leadership account becomes more credible when it can say what the enterprise can do, what it is still learning and what it has chosen to give up while that learning proceeds, without disguising a partial stage as the business it decided not to buy.