How Do I Test a New Service Before Building It?

The biggest risk in launching a new service is the 'over-build'. Leaders often create a service offering, document the processes, build a portal, and hire a team before the first customer has ever signed an order. By the time they realise the market demand is lower than expected, they have already burned through months of cash and months of focus.

True validation is about 'manual delivery'. It is about proving that a customer is willing to exchange money for the outcome you are promising, using your existing resources. If you cannot deliver a simplified version of the service with your current tools and team, you have no business 'scaling' it yet.

The 'Manual-First' Delivery Principle

Think of your new service as a 'consultancy engagement' first. Can you achieve the desired outcome for the customer using spreadsheets, email, and human brainpower?

• If the answer is no, your service isn't defined well enough.
• If the answer is yes, then you have a service, but you don't yet have a 'productised' revenue stream.

Testing the Value Proposition

People don't buy 'services'; they buy 'outcomes'. Before you build the service, draft the sales page. If you can't explain the value to a stranger in two sentences, the service is too complex.

The 3-Customer Test

Identify three potential customers—existing clients are perfect for this. Approach them with the offer: 'We are launching a new service that does X, and we want to offer it to you at a 50% discount in exchange for your feedback.' If even your own existing customers won't bite, the service is not worth building.

Commercial Reasoning

Building a new service alters the fundamental levers of your business:

• Revenue: Does this service complement your core offering, or does it confuse your sales message?
• Margin: If you calculate the 'human time' involved, is the margin attractive?
• Cash: How much 'working capital' is tied up in the time it takes to deliver the outcome before payment?
• Capacity: Will this new service distract your best people, or can you use idle capacity?
• Complexity: Does this require new systems (CRM, project management) that increase your operational overhead?
• Risk: What is the reputational cost if the first three services don't deliver the promised outcome?

When NOT to Test

Avoid testing a new service if:

• It requires a massive capital investment just to 'try it'.
• You do not have the fundamental expertise required to deliver the outcome.
• The problem you are solving is a 'nice-to-have', not a 'need-to-have' for the customer.
• You are doing it just because a competitor did it, without understanding their business model.

The Build Decision

Once you have successfully delivered the service to three customers manually, you will know exactly what the 'process' is. Now, and only now, can you look at automation. Can this be done with a tool? Can this task be delegated to a junior hire? Only after you have de-risked the market appetite and the delivery process should you start 'building'.