In short
- After a successful pilot, companies fall into one of two traps: stopping (the proof existed, the momentum dispersed) or launching a grand transformation programme — exactly what large implementations drown in.
- Healthy growth runs between them: further implementations in a steady rhythm, one after another, each building on what already worked.
- Rhythm ≠ sprint. Working month by month sustains momentum without loading the department with work outside its daily job.
- The most common brake is fear of a long contract — which is why the decision to continue should be made monthly, based on what actually got built.
- A pilot usually leaves its own list of next ideas. Writing it down is the cheapest way to stop the momentum from fading.
Two traps after a pilot
After a successful pilot, companies fall into one of two traps. The first is stopping. One application works, so the topic is considered closed, and the team goes back to its daily routine. Six months later the tool is still running, but nothing new has been built, because no one had the time or the rhythm for it. The proof was there — the momentum dissipated.
The second trap is the opposite one. Excited by the first success, a company tries to do everything at once and ends up in a large transformation program — exactly where big implementations sink. Healthy growth runs between these two extremes: further implementations are built at a steady rhythm, one after another, each still grounded in what has already worked.
What healthy growth looks like
Scaling implementations after a pilot takes several forms, depending on what's on the company's list. Sometimes it means clearing a backlog — during the pilot, a department wrote down a dozen or so further ideas and now works through them one by one, without a gap in between. Other times it means moving into a second department — production saw the result, so sales or service follows. And sometimes it's about maintaining what already works alongside building something new, because tools in production need to keep pace with changes in the process.
What ties them together is rhythm. Instead of bursts and standstills, the work runs month after month, at a pace the company sets itself and can adjust as circumstances change. That's what sustains the momentum a single implementation lacks, without loading the department's team with tasks outside its daily work.
No multi-year commitment
The most common brake after a pilot is fear of a long contract. A company doesn't want to sign up for a year of cooperation before seeing that the pace and quality hold up. That's why scaling implementations with me starts with a short minimum period and then runs month by month — it can be paused with a month's notice, no penalties. The decision to continue is made every month, based on what has actually been built, not once at the start, in the dark.
For manufacturing SMEs, there's one more thing. Scaling implementations falls within the scope of Dig.IT grant funding, so expanding the portfolio can be spread out with a subsidy covering part of the cost. How to combine the two, I explain separately.
What we don't know yet
Before acting on this article, it is worth checking whether the answers to these questions are known on your side:
- whether the list of next ideas was written down before the team returned to daily duties;
- who keeps the rhythm once the deadline pressure of the pilot is gone;
- how much time the department can give each month without it costing them their core work;
- whether the next tools share a data source, or each lives on its own;
- what you will treat as the moment to pause development.
Frequently asked questions
What should we do after a successful pilot?
Write down what else in that department or the one next door calls for support — a pilot usually leaves such a list — and work through it in a steady rhythm, one implementation after another. The biggest risk at this stage is not a wrong choice but a loss of momentum.
Do we have to sign a long contract after the pilot?
You should not have to. A sensible model starts with a short minimum period and then runs month by month, with the option to pause on a month's notice. The decision to continue then rests on what got built, rather than being made once at the start, blind.
How do we avoid drifting into a grand transformation programme?
By keeping the scope narrow after the pilot too. Success tempts you to do the same thing everywhere at once — and that is the moment a project stops being a series of measurable steps and becomes a programme that sinks halfway.
Can further work be financed from a grant?
For manufacturing SMEs, expanding the portfolio falls within the scope of Dig.IT funding, so part of the cost can be offset by the grant. Terms and application windows are published by the Industrial Development Agency.
What's next
If the pilot worked in your company, the worst thing you can do is let the momentum dissipate. Start by writing down what else in that department, or the one next to it, is calling out for support — a pilot usually leaves that kind of list behind. The pace and shape of further work is matched to that list and to the company's capacity. What scaling implementations looks like as a package, in which pace variants and under what terms, I describe on its page.
→ See how Implementation Partnership works
→ Book a 30-minute consultation
