The board should see the business behind the number

I want directors to understand the business that sits behind a software company's recurring-revenue figure. The figure is useful, but it does not describe every implementation obligation, product exception or service dependency needed to retain the customer. If a board sees only the subscription record, it may approve a growth plan without seeing the work already committed to deliver it. My responsibility as an executive director is to connect those records before asking directors to make the next allocation.

I organise material recommendations around the promise being made and the capability required to keep it. For a large enterprise agreement, that means the relevant product work, implementation assumptions and continuing support. For an acquisition, it includes the operating knowledge we need to preserve before changing the acquired team or process. For an automated feature, it includes the customer's review burden and the boundaries of our evidence. These are different subjects, but each can create an obligation that is easier to sell or approve than to maintain.

The branch-consolidation programme required that discipline. Engineering could explain the value of a smaller product estate, while commercial colleagues could explain the relationships placed at risk. I brought the board the proposed transitions and their revenue consequences together. We eventually moved twenty-eight deployments, lost four customers at agreed renewal points and retained nine branches. The remaining exceptions had owners and reasons. Directors could then judge the chosen position rather than compare reality with an implausible picture in which every customer would migrate willingly and all complexity would disappear.

I also distinguish a management estimate from observed evidence. The US$3.2 million of deferred bookings attached to the narrower assistant release was a planning consequence, not revenue already earned and then lost. The 34% handling-time improvement applied to two approved document classes with review included. The board needed those definitions to assess the decision. A number stripped of its scope can make an operating choice look easier than it was and encourage a later discussion based on an expectation management never had evidence to support.

Committee papers should retain disagreement where it matters. If product and sales leaders interpret a customer's need differently, I want directors to understand the difference and management's chosen response. I do not require a paper to imply unanimity before it can be considered. I do require a recommendation, a clear owner and an account of what remains uncertain. The board should be able to distinguish a question management needs help judging from work management has simply not completed.

Acquisitions make this especially important because the timetable can create pressure to report integration progress through tasks finished. I ask for evidence that the receiving team can perform the relevant work. Retiring a tool is not progress if the knowledge it carried has become inaccessible. Keeping a tool is not automatically prudent if nobody has defined how its useful content will move. Directors need to see the intended capability, the interim cost and the conditions for the next decision.

In an external board role, I would bring this way of examining obligations without taking over executive delivery. My experience may help management identify a dependency, but responsibility for the solution remains theirs. I would agree any deeper involvement with the chair and keep it within a clear remit. I would also be careful about confidential knowledge: shared customers, suppliers or investors can create conflicts even where the two companies do not compete directly. A director's usefulness depends on being able to participate responsibly, not simply on having relevant experience.

The governance record I value is one that makes the original choice recoverable. When circumstances change, we should be able to see what management believed, what directors accepted and which condition would have led to a different answer. That record supports accountability without pretending that every later outcome was predictable. It also gives the executive team a reason to bring new evidence promptly, because a revised view can be assessed against the decision actually made rather than a simplified story constructed after the result.