Back to Blog & Insights

Business Growth

Turn the Sales Promise Into a One-Page Service-Start Sheet

Before delivery begins, translate proposal language into a one-page record of outcomes, deliverables, inputs, approvals, ownership and change boundaries.

Service owner and client reviewing deliverables, approvals and responsibilities on a one-page start sheet

A brand consultant wins a launch project with a proposal promising to support the launch as needed. The client imagines campaign copy, retailer materials and daily availability. The consultant expects to provide a messaging guide and two review calls. Neither interpretation is unreasonable, but the phrase is too elastic to direct the work.

Before the kickoff, the consultant replaces it with a service-start sheet. It names the assets: a messaging guide, three email drafts and copy for five social posts. It sets two review points, identifies the marketing director as the decision owner and defines approval as written confirmation in the shared project workspace. Requests for additional assets trigger a scope discussion rather than quietly entering the workload.

Translate the sale without rewriting it

The service-start sheet is a one-page bridge between an accepted proposal and delivery. It is not a new contract, a detailed standard operating procedure or a client progress report. Its job is to make the working interpretation visible before time is spent.

Business Wales notes that written agreements can clarify expectations, support trust and make disagreements easier to address. That principle can be applied in a proportionate way: capture only the information the client and delivery team need to start the same assignment. The UK Competition and Markets Authority also emphasizes clear, readable and unambiguous terms, with significant information made prominent rather than buried in vague wording.

Begin with the outcome. Ask: What should be different when this service is complete? Avoid substituting activity for an outcome. “Run three workshops” is a deliverable; “give the leadership team an agreed positioning direction” is an outcome. Keep it specific enough to guide choices without promising a result the provider cannot control.

Define what each side must do

List the deliverables in recognizable units, including relevant formats and review points. Then identify the client inputs required to produce them: brand files, data, access, feedback or subject-matter interviews. Add who supplies each input and when it is needed. If an input arrives late or incomplete, the sheet should prompt a delivery conversation rather than leave the team to improvise.

Next, state the acceptance evidence. This might be an approved document, confirmation that agreed edits are complete or signoff after a scheduled review. Name one decision owner on the client side, even when several people contribute feedback. The UK Government Commercial Function recommends defined roles and responsibilities, proportionate performance measures, documented management plans and tracking delivery against agreed obligations. A compact start sheet applies that discipline without importing a large management process into a small engagement.

Finish with the change boundary: the point at which a request becomes different or additional work. Use plain operational language. For example: One consolidated revision round is included. New audiences, extra asset types or a change to the approved direction require a revised plan. The boundary does not need pricing or legal clauses to be useful; it needs to tell both parties when to stop and discuss the request.

Use a five-minute readback

At kickoff, ask the delivery lead to read the sheet aloud in about five minutes while the client listens for mismatches. Then ask: What are you expecting that is not written here? Which input or approval could stall the work? Who can make the final call? What would count as a request outside this assignment?

If an answer reveals a small ambiguity, revise the sheet and confirm it. If the client accepts the interpretation, record that acceptance in the normal project channel. If the requested work changes the outcome, effort or responsibility materially, decline to start that portion until the proposal or plan is revised. The aim is not to anticipate every possibility. It is to ensure the promise being delivered is the promise everyone recognizes.


Sources