Make the service conditions shape the strategy

A pipeline counts opportunities; it does not by itself describe capacity. Sixteen forty-hour jobs and eight four-hundred-hour jobs total 3,840 chamber-hours, although treating every job as forty hours produces only 960. Both calculations use the same twenty-four entries. I now require the relevant technical owner to explain the resource assumptions before strategy interprets demand as an investable service route. Setup, staffing, maintenance and other allowances must remain separate where the model excludes them. Prospective jobs also remain distinct from contracted orders. The useful output is a decision account that shows what can fit, what requires another route and what remains unknown. It should not pretend that a corrected hour total alone establishes technical suitability or financial attractiveness. Those questions require their own evidence and authorised decisions before the organisation makes a commitment.

A testing business sells work performed competently, not a favourable conclusion purchased by the customer. In a reviewed twelve-contract proposal, three used fees contingent on a favourable outcome while nine used fixed work-based fees. The commercial attraction of the first three was clear, but the incentive conflicted with the service position we wanted to maintain. I recommended removing that route before approval. Qualified laboratory and legal owners assessed the actual arrangements; strategy did not pronounce on compliance through a slogan. A fixed fee alone also does not establish impartiality, because other relationships and pressures remain relevant. The strategic question is whether the revenue model supports the reason a customer can rely on the work, and whether the company is prepared to decline an apparently attractive offer when that condition is undermined.

Technical quality and recipient acceptance are related questions, but they are not identical. Our market-entry review considered fourteen prospective overseas customers. Nine indicated that the proposed reporting route could be considered under their stated requirements; five required a different accepted laboratory route. Those indications were not orders or universal acceptance across a country. I asked the team to preserve that distinction before sizing an owned-facility expansion. The five did not become reachable simply because our report format improved or the company opened an office nearer them. We explored a defined referral arrangement while keeping contracts, competence and result ownership with the appropriate parties. Strategy should identify which part of the customer’s process the company can credibly serve, rather than assume that technical ambition removes every external acceptance condition.

A strategy paper connects opportunity, capability and alternatives, but it must not silently acquire the authority of all the professionals whose work it summarises. My team’s annual expense supports analysis, while the proposal portfolio requires separate capital decisions. Laboratory owners retain methods and result release; qualified reviewers retain competence and acceptance assessments. I make those boundaries visible in the recommendation so that an encouraging market account cannot be read as approval to begin an unsupported service. The discipline also changes how we report progress. A revised proposal, a funded study, an authorised investment and a completed service are different events. Directors should be able to see which has occurred and what must follow. That clarity allows a commercial decision to remain ambitious without pretending that its dependencies have already been resolved by the act of recommending it.