Selling It Upstairs: Co-Writing the Sponsor's Internal Case

Most UK clients do not approve work on their own. A sponsor may champion a project, but the money often sits with a finance business partner, a procurement team, an executive committee or a board sub-group. When approval stalls, the delivery timetable begins to slip before anyone has booked a kick-off meeting. The most useful thing a client-facing professional can do at that point is not to write a glossier proposal. It is to help the sponsor build the internal case they need to defend.

That work is commercially valuable, but it is not a sales document. It is a one-page decision aid, co-authored with the sponsor, written in the client's language and designed to survive scrutiny from people who have no reason to share the sponsor's enthusiasm.

The page belongs to the sponsor

The first discipline is ownership. A supplier-written business case often reads like a proposal with a different title. It leans on the supplier's differentiators, describes the solution in detail and treats the client's internal approval process as a formality. Finance teams recognise this pattern quickly, and it weakens the sponsor's position.

The page should sound like the sponsor, use the sponsor's operational vocabulary and reflect the sponsor's risk appetite. If the sponsor cannot explain it in two minutes without referring to supplier marketing, it is too long or too promotional. The supplier's role is to ask good questions, provide evidence where appropriate and help structure the argument. The sponsor's role is to own the claim.

Start with the decision, not the solution

A one-page case is not a summary of everything known about the project. It answers a narrower question: what decision is being requested now? That might be approval to fund a discovery phase, release of a capital budget, endorsement of a shortlist or permission to enter a competitive procurement. State the ask at the top. If the reader has to reach the bottom to discover what they are being asked to approve, the page has failed.

This matters because approval bodies often meet infrequently and review many papers. A clear ask allows them to focus on the evidence that matters. It also prevents the common problem of a project being approved in principle but not funded in practice.

The six boxes that survive scrutiny

A useful structure is six short sections. The first is the problem, described in operational terms rather than technical ones. What is happening now, who is affected and what evidence supports that? Internal data is more persuasive than market commentary.

The second is the cost of inaction. This is often the weakest part of an internal case, yet it is the part finance will press hardest. Quantify where possible: staff time, lost revenue, compliance exposure, maintenance costs or risk of service failure. Where quantification is not credible, describe the exposure plainly and say what is uncertain.

The third is options considered. Include doing nothing and at least one lower-cost alternative. Explain why the preferred option is preferred, not why the alternatives are foolish. This demonstrates that the sponsor has tested the proposal rather than fallen in love with it.

The fourth is risks and mitigations. Be honest about delivery risk, supplier dependency, adoption risk and any assumptions that could invalidate the numbers. A page that admits uncertainty is more credible than one that promises certainty.

The fifth is the measurable outcome. State the baseline, the target, how it will be measured, when it will be measured and who owns the benefit. If benefits are expected beyond the project, say how they will be tracked after closure.

The sixth is the decision and next gate. Specify the amount, the timescale and any conditions attached to approval. This helps the approval body say yes to a defined step rather than an open-ended commitment.

Keep the sales smell out

Adjectives are a warning sign. Transformational, world-class, cutting-edge and seamless may feel persuasive to the supplier, but they invite scepticism from finance and procurement. Replace them with nouns and numbers. Use the client's evidence, not the supplier's case studies, unless the case study directly mirrors the client's situation and can be referenced without breaching confidentiality.

Separate facts from assumptions. If a benefit depends on a adoption rate, state that. If a cost depends on an exchange rate or a supplier quote, say so. A cautious page with a range of outcomes will usually travel further than an optimistic page with a single number.

A working session, not a drafting service

Co-authoring is best done in a single working session with the sponsor and, where possible, a finance business partner. Ninety minutes is usually enough to draft the skeleton. Ask questions, capture the answers in the sponsor's words and agree what evidence still needs to be found. The sponsor should have final edit. The supplier should not circulate a finished page without that sign-off.

A simple test is useful: can the sponsor defend each line to a sceptical colleague? If not, the line is either unsupported or unnecessary. Remove it or strengthen it before the paper goes forward.

The commercial point

Helping a client build internal credibility is itself a form of client-facing expertise. It reduces approval delays before they become project delays. It surfaces misalignment early, when it is still cheap to resolve. It also positions the supplier as an ally in the client's internal process rather than another vendor asking for money.

The one page is not paperwork. It is the sponsor's shield and the shared map for the work ahead. Writing it well is quiet, useful work, and it is often the difference between a project that starts on time and one that spends a quarter waiting for a meeting.