In a small trial, the team can often keep a close eye on what's happening. If somebody gets stuck, there's someone available to help. If information hasn't arrived, somebody can chase it. That might be perfectly sensible while you're learning, but we need to recognise the work people are doing around the software.

As the service grows, those arrangements need another look. Can a new member of staff understand what to do? Can somebody get help without contacting the founder? If a connection between two systems fails, will the team know, and who will deal with it?

Keeping improvements manageable

In my work with a small software business and a large corporate customer, part of the challenge was finding a way to improve the service regularly while giving the customer confidence in the changes. Testing mattered, but so did understanding how their people already worked and how much disruption a release might cause.

I've talked about this as "the best change is no change". What I mean is that, where a process already works well, we can try to fit the new service into it and make it easier or faster. If people can recognise what they're supposed to do, there's less to explain each time we improve something.

That takes discussion with the customer and their leadership team. We need to understand their constraints, agree how changes will be checked and give them a reason to trust the way we're working.

It doesn't mean building a large, complicated platform before you've had a customer use it. I've also had to take products in the opposite direction, simplifying what was being built so that people could start using the service and giving feedback.

I'd start with what the pilot has taught us, then look at what's needed for the next stage: support, testing, integrations, data handling and clear responsibilities. Which of those needs attention now will depend on the service and how it's going to grow.

If you're working out what needs to change before the service grows, a technology, product and delivery review can help establish the next steps.