How to explain a complex service before the proposal

Describe what the client will receive

Start with the form of the work and the person who will use it. That might be a document for an operations team, materials for a campaign, or guidance through a particular process. Connect the deliverable to its purpose while keeping any wider business result in context.

Planning example: a professional service firm in Indonesia helps a client map an internal workflow. Its initial deliverables might be a process map and a list of issues to discuss. Implementing every recommended change is a separate question unless that work is explicitly part of the offer.

• What will the client receive?
• Who will use the work?
• Which decision or activity will it support?

Separate the core, variable, and additional work

Group the scope into three parts. Core work can be explained from the start. Variable work depends on information such as the number of teams or locations involved. Additional work needs a separate discussion. This helps a client understand flexibility without assuming every requirement fits the initial offer.

Put each boundary beside the deliverable it affects. A fixed package can be easier to compare, but it needs a stable definition. A service with more variation may be better explained through an initial framework and a clear process for agreeing the rest once the need is understood.

Show what you need from the client

Professional work often depends on documents, access, feedback, and approval. List the inputs and explain why they matter. Distinguish what must be ready before work starts from information that can be developed later. These dependencies should be visible in the service process so the client can prepare realistically.

The person who first contacts you may not own every input or decision. Ask who holds the information and how approvals happen. When materials are missing, discuss the preparation step before giving a more detailed account of the work or schedule. That keeps the explanation grounded in the actual situation.

• Which inputs are essential at the start?
• Who owns the information and approvals?
• What preparation is needed if something is missing?

Turn the explanation into a short starting brief

A useful first brief covers the need, intended use of the work, current situation, available materials, and open questions. It helps both sides discuss scope without expecting the client to know the solution already. Use language they recognise rather than requiring the terminology your delivery team uses internally.

Keep track of the questions that return. If clients repeatedly assume an additional task is included, improve that explanation. If preparing documents causes confusion, make the inputs clearer. Keep approved wording available to the team so the website and sales conversations describe the same offer.