Developing services

Your service pilot went well. Is it ready to expand?

Your first customers like the new service. The team has delivered it, and sales is ready to invite a larger group. Before agreeing, ask one more question: did the pilot demonstrate a repeatable service, or did exceptional personal effort make a promising idea work?

Both outcomes contain value, but they support different decisions. A service pilot should help you identify the conditions under which you can keep the customer promise. Reviewing those conditions deserves its own decision, involving the people who delivered the work as well as those who sold it.

Three colleagues discuss a technical component, cards and a notebook at a workshop table.

Establish what the pilot actually tested

Compare the original offer with the service customers received. Include its scope, price, timing and division of responsibilities. Did customers provide the expected information? Did your team add support that was never included in the offer? Was the owner available throughout when that would not normally be possible?

Avoid treating every difference as waste. Extra explanation might be the reason customers found the service valuable. Equally, an impressive result may depend on preparation that nobody has allowed for in the next round. You need to decide which differences belong in the service and which arose from an unfinished way of working.

Our article on developing a new service covers shaping the first offer. This review starts after that offer has been tried: what do the results justify doing next?

Separate learning effort from delivery effort

Consider a fictional supplier testing a technical preparation review for customers. Eight reviews are completed on time and the feedback is encouraging. However, a senior specialist has checked every submission before the ordinary team sees it, and the owner has personally resolved the difficult cases.

The pilot has demonstrated a useful outcome. It has not yet shown that the proposed team can deliver the same service with its planned support. That distinction should shape the next step, rather than disappear behind a positive satisfaction score.

Group the effort into one-off preparation, recurring delivery and avoidable recovery work. Creating an initial guide may be a one-off activity. Discussing the findings with each customer may remain part of delivery. Chasing missing information may point to a problem with the intake process. Do not assume that all extra effort disappears once the team has more practice.

Ask employees to explain the actions that kept the promise intact. Which decisions could they make themselves? When did they need someone else's knowledge or authority? Recognise the judgement involved before deciding what to standardise. A review that blames people for compensating for missing support is unlikely to reveal the full picture.

Build a small body of evidence

The UK's GOV.UK Service Manual recommends combining performance measures with user research and other evidence rather than relying solely on digital analytics. That is a useful design principle here, not a regulatory reporting obligation for your business.

Choose evidence that answers the particular promise you are testing:

Decision question Evidence to review together
Did the customer obtain the promised result? Completed work, outstanding issues and feedback after using the outcome.
Could the team deliver with normal support? Actual effort, waiting, handovers and specialist intervention.
Is there demand for the continuing offer? Responses to a specific follow-on offer with its price and boundaries.
Can the service handle a difficult request? The sequence of an exception and the decisions it required.

Include unsuccessful and declined requests, with their reasons. A pilot restricted to your easiest customers cannot answer every question about a wider market. Record how participants were selected and which conditions remain untested. Small numbers can guide the next experiment without establishing a reliable forecast for every future customer.

Test the next commercial commitment

Positive feedback tells you something about the experience. It does not establish that a customer will buy the continuing service on the intended terms. Present the actual next offer: what remains included, what support changes, when it can be delivered and what the customer will pay.

A customer may value the outcome but insist on retaining direct access to the owner. That response exposes a design decision. Specialist consultation might belong in a separate service level. A trained colleague might be able to provide it. Or the offer may be best suited to a deliberately limited customer group.

Keep the reasons for declining separate. A lack of need, an unsuitable price, missing customer information and inconvenient timing suggest different responses. An unanswered proposal is an unknown outcome, not proof of rejection. This distinction matters when the team later explains why it chose to change or stop the offer.

Define three real options

Before expanding, agree the conditions that must be met. Safe delivery, an understandable promise and access to the necessary expertise may be essential. Other criteria will depend on the service and the investment being considered. There is no universal satisfaction score or pilot size that makes expansion sensible.

Continuing can mean admitting a limited next group with the required capacity already arranged. Adapting can mean changing one important part of the offer and testing that change. Stopping can mean ending this version while completing existing commitments properly. It need not mean abandoning the customer problem that prompted the idea.

Appoint a person responsible for the decision, with evidence from sales, delivery and administration. Record the choice, the evidence behind it, the uncertainty that remains and the next review point. A pilot should not become a permanent service merely because nobody has made a closing decision.

Expand what you can learn, not just the volume

Choose the next group around the uncertainty you need to resolve. If the question is whether another colleague can deliver the service, keep the offer and customer type reasonably consistent. If you are testing a new customer segment, avoid changing the price, operating method and support at the same time without recognising the effect on the comparison.

Prepare the practical support for that step. A shared record of the offer version, customer commitments, open actions and outcomes may be enough initially. Decide which information and decisions need lasting software support before commissioning a larger platform. A polished portal cannot compensate for an offer whose responsibilities are still unclear.

Through business process analysis, IndustrylinQ can help turn the pilot evidence into a concrete next decision with your team. Bring the offer that was sold, a few complete customer journeys and the actual effort involved. Together, these show what deserves to be retained, what needs changing and which next commitment the business can responsibly make.

Your next step

What do you want to make possible?

You do not need a software specification to start.

Talk about your next step