Find the difficulty that is limiting growth

To decide where to act, follow the journey from an incoming enquiry to completion of the service. Observe how many opportunities progress, why others stop and where the team loses time. The difficulty may concern demand, the proposal, sales follow-up or the company's actual capacity to deliver the work it sells.

A full diary does not, by itself, explain business health. It may reflect well-priced work or projects consuming too many hours for the amount charged. Similarly, a small number of enquiries may be appropriate when they are relevant and support a sustainable operation. You need to understand the relationship between volume and quality.

Choose a period that fits your sales cycle and collect examples of enquiries, proposals and completed projects. Avoid comparing weeks with very different conditions without recording the context. The first objective is to locate an observable difficulty, so that the next decision has a clear reason and a way to monitor its effects.

Make the offer understandable and its scope deliverable

A service offer should explain whom it is for, which problem it addresses, what it includes and what depends on the customer. That clarity supports sales and delivery. Define responsibilities and approval points as well, so that the proposal corresponds to work the team can realistically undertake with the resources available.

When everything is presented as customisable, comparing projects and forecasting effort can become difficult. That does not require selling identical packages to everyone. You can retain adaptation to each customer while defining common stages, necessary information, deliverables and a way to handle changes to the original request as the project develops.

Imagine a website development service. Gathering content, approving the structure and validating pages are different tasks. If nobody knows who approves work or when content will arrive, the team can become blocked despite having technical capacity. A good proposal anticipates these dependencies and turns vague expectations into commitments that everyone can understand.

Connect price, effort and margins

The price of a service needs to be assessed alongside the work required to deliver it. Consider team time, tools, partners, revisions and ongoing communication. The margin available from a project helps compare offers, but it must be considered together with the company's other costs and the way its capacity is used.

Record the actual effort required by several projects and compare it with the estimate. If the difference repeatedly appears at the same stage, you have a concrete question: is information missing, is scope open-ended, was the estimate too short, or does a task need another process? The answer may change the proposal, price or execution.

It also matters to distinguish revenue from profitability. My own businesses have generated €6 million in revenue across my career, but an aggregate figure does not explain the economics of each offer. When analysing a service, I want to understand what it costs to sell, deliver and maintain the relationship with that type of customer.

Build a sales journey that supports learning

The sales process should connect each opportunity with an origin, a need and a next step. This lets you understand where people progress or stop responding. The information helps improve qualification, proposals and follow-up, rather than reducing the analysis to the total number of contacts received over a particular period.

A company may receive enquiries through recommendations, search, content or campaigns. The pace and expectations can differ. Record the context and recurring questions without automatically assuming that the channel producing the most contacts is the most useful. The suitability of the projects and the effort required to win them both matter.

The guide to sales automation with AI develops enquiry organisation and follow-up. Before automating messages, define who responds, what information they need and when an enquiry should stop or be passed to someone else. A consistent process helps the team direct its attention towards the situations that require a conversation.

Increase capacity while maintaining control of delivery

Capacity grows when the team can repeat work using clear criteria and handle exceptions without always depending on the founder. Document objectives, stages, examples and responsibilities, then observe where the process still fails. Hiring or automation may make sense, but the decision depends on the work that actually needs to be absorbed.

A useful document shows how to recognise a completed task and what to do when something is missing. It can include examples of good delivery, questions that clarify the request and points requiring approval. A new team member needs to understand the objective as well as reproduce a particular sequence of clicks.

If an experienced person handles everything from memory, start by observing recurring decisions. What information do they seek? Which errors do they identify? When do they ask for help? Those answers form a practical knowledge base. Business process automation explores the move from clear rules to monitored execution, including failures and maintenance.

Use AI where quality can be checked

AI can support a service business by preparing information, organising enquiries and producing initial versions of work. Choose a task with examples and quality criteria. Define who checks the result and what use is permitted, particularly when customer data is involved or when decisions have consequences for the business and its customers.

A briefing summary can help the team locate requirements, provided people can consult the original information. A proposal prepared from a template can reduce work, but its scope and terms still need review. The time required for checking should be included when assessing the benefit of the solution and its suitability for routine use.

The AI guide for business owners explains how to compare effort, risk and actual use. The starting point can be small: one task, one responsible person and a set of examples. If frequent corrections are necessary, investigate why before extending the system to other customers or business processes.

Choose a priority and monitor its effect

A useful growth plan starts with a priority that addresses the difficulty you identified. Define what will change, who will execute it and which signals you will monitor. Review the result in the context of the period, including changes in demand or staffing. Learning should guide the next decision and allocation of effort.

If enquiry suitability is the problem, track customer profiles and reasons for declining work. If delivery is the issue, observe revisions, blockages and hours per project. If continuity is the concern, investigate why customers renew or leave. Each question needs indicators that describe the corresponding work and support a decision about it.

Individual business mentoring offers a way to explore these decisions from your situation. For the entrepreneurial context behind this approach, see my businesses and results. Bring your current offer, a few examples and the main difficulty: that preparation makes it possible to start with something you can improve in the actual work.