What problem is actually being presented?
Start by understanding what happens today and why the person decided to seek help. A request for ads, automation or a new website may simply be the solution they imagined. You need to understand the underlying need before defining the work you are going to estimate and include in your proposal.
If a potential customer says they want more enquiries, ask how current enquiries arrive, what the team does with them and where they struggle. Demand may be insufficient, but there may also be proposals without follow-up or insufficient capacity to respond. Quoting for acquisition before clarifying this could leave the main need unresolved.
You do not need to turn the initial conversation into a complete audit. You need enough information to understand whether you can help and what further diagnosis is required. When that investigative work is a service in its own right, explain its scope and price instead of promising unlimited analysis before any commitment.
This care is part of turning leads into customers in a service business. An opportunity progresses when need, delivery capacity and working conditions fit together. A meeting can clarify that the fit does not yet exist without that being a sales failure.
To prepare your next step, explore Service pricing and profitability.
How do you make the desired outcome concrete enough?
Ask what the customer would like to see change and how they would recognise improvement. Connect that expectation to an observable starting point, an assessment period and clear responsibilities. Distinguish what you will deliver from business outcomes that also depend on the team, the market and decisions outside your own control.
“I want to grow” does not define a deliverable on its own. It could mean selling more to existing customers, increasing quote requests or reducing manual work to improve service capacity. These priorities may require different services, even when all of them sit under the word growth.
Imagine a hypothetical example of organising sales operations. The service might deliver CRM stages, defined responsibilities and a follow-up routine. That work could help the business handle opportunities better, but it cannot guarantee a number of sales. The proposal should make the difference between the implemented process and the desired outcome clear.
Confirm what would be excluded too. If the customer expects the provider to make calls, but the service only includes organising the process, that disagreement needs to surface before the final price. A clear list of exclusions prevents two people from agreeing on the same amount while imagining different work.
How do you assess the impact of carrying on unchanged?
Explore consequences the customer can describe and, where possible, measure: time consumed, rework, delays or unused capacity. Use estimates with explicit assumptions when data is missing. Do not turn a possible opportunity into a certain loss or present the problem's total impact as a guaranteed benefit of hiring you to solve it.
In a hypothetical example, a task takes eight hours each week and a change could reduce part of that effort. Assessing the improvement requires knowing how much time would remain necessary, who would check execution and what additional costs would arise. The initial eight hours are not automatically eight recoverable hours.
The same care applies to sales. An opportunity that did not progress does not equal the full value of a sale that was certainly lost. Possible revenue does not equal profit either. When comparing alternatives, consider delivery resources, uncertainty and what the company would have to stop doing.
Opportunity cost helps discuss choices between alternatives. It is not an invoice already issued or a debt created by the customer not hiring you. If the information cannot support a serious estimate, keep the analysis qualitative and propose how to gather data. A limited conclusion can be more useful than an impressive calculation without a basis.
Which resources and conditions could change the proposal?
Confirm who will support the project, what information is available, who can decide and how much capacity exists to implement changes. Add time and budget constraints. These conditions affect scope and execution, so they should shape the proposal before you commit to work that depends on resources which have not yet been secured.
A customer may need the service and recognise its value but have nobody available to approve materials. Another may have a team and budget but depend on a supplier for data access. Commercial interest alone does not resolve these dependencies or make them disappear from the delivery plan.
Ask about budget directly and with context. The answer helps establish whether there is a fit or whether the scope needs to shrink. A lower budget does not justify promising the same work with insufficient resources, and a higher budget does not remove the need to explain what is included.
What you need to know about a customer before accepting a project includes precisely their goals, expectations and capacity to participate. If an essential condition is missing, you can propose a limited first phase, wait for that condition or conclude that another kind of support is more appropriate.
What if the customer asks the price straight away?
Answer with information you can already substantiate. If the service has a fixed price, present it with its scope; if it depends on diagnosis, explain that dependency and offer a range when you have a basis. The person should understand the approximate scale without sitting through a long conversation to discover an obvious mismatch.
A range needs explanation: what distinguishes the lower end from the upper end and which factors might change the estimate. Do not use an entry price that rarely corresponds to the service being discussed. That creates an expectation that later makes the real proposal harder to assess fairly.
When you cannot yet estimate, say which information is missing and agree how to obtain it. A transparent answer allows the customer to choose whether to continue the conversation. Repeatedly postponing the price question can make it seem that you want a commitment before explaining the conditions.
It also matters how you defend a service price when execution becomes faster. Time is one delivery resource, but a proposal may include diagnosis, responsibility and review. Explain those concrete components without inventing abstract value to justify any amount you choose.
How should you present the price after diagnosis?
Relate the price to the agreed scope, deliverables, responsibilities and working conditions. Explain what depends on the customer and what will be reviewed throughout the project. Leave room for questions and agree a next step, allowing the decision to be made with sufficient information about the proposal and its practical implications.
Restate the need using the wording confirmed during the conversation. Then show how the proposed work addresses that need, in what sequence and within which limits. You do not need to hide the amount at the end of a lengthy document; the context needs to be clear and accessible.
If an objection arises, understand what is being questioned. It may concern ability to pay, the project's priority, confidence in delivery or a difference between the expected and proposed scope. Each answer can lead to a different decision, including the decision not to proceed with the work.
Diagnosis is sound when you can recommend honestly, even if the recommendation is to wait or seek another solution. Presenting a coherent price requires that willingness. The aim is an executable agreement understood by both sides, without turning the customer's need into a promise of results you cannot control.