Most manufacturers can justify a digital pilot. The harder part is what comes next: choosing what to scale, what to skip, and how to make smart decisions without restarting the business case every time. Without a clear ROI framework, even promising digital programs stall, buried under shifting priorities, long timelines, or low-return initiatives that eat up resources.
In a session at Operations Calling, Rick Ross, Senior Director of Manufacturing Technology at Generac, shared how his team shifted away from large, one-time rollouts toward a continuous model of transformation. They started thinking in small, composable solutions. Each one was scoped to prove value quickly, designed to scale, and evaluated based on how much measurable impact it delivered. Over time, this became their operating model and not just for building tech, but for building confidence.
This blog outlines the key learnings from that shift: how to use ROI to align teams, fund what works, avoid what doesn’t, and build a transformation roadmap that compounds value over time.
Why digital transformation breaks when treated as one big project
There’s a reason so many “transformation programs” never make it past year one. When digital change is treated like a one-time rollout, one massive scope, teams lose the ability to adapt.
Big projects invite big timelines, and long timelines create friction: executive sponsors leave, budgets shrink, new priorities emerge. Even when the technology works, the moment to prove impact may have already passed.
“From ideation to implementation was somewhere between 5 and 10 days. If that was a more traditional system or a more traditional approach, that would have probably been five to 10 months.” - Rick Ross, Senior Director of Manufacturing Technology
That’s the core problem. When scope is fixed and delivery is slow, transformation becomes fragile. The better model is continuous: short loops, fast feedback, and a clear way to decide what’s worth doing next.
What ROI-Driven Transformation Actually Looks Like
Treating ROI as a continuous decision-making tool changes how teams prioritize, align, and scale. It gives manufacturers the flexibility to move fast without losing credibility, and the structure to avoid waste without killing momentum.
Below are six hard-won learnings from teams that are doing this well.
Learning 1: Use ROI as a common language to align teams
Every function has its own priorities. Operators want usability. Quality wants control. Finance wants numbers. Leadership wants confidence.
That’s why ROI works best not as a spreadsheet, but as a shared language. A simple, repeatable way to show progress, without reinventing the message for every audience.
One manufacturing leader explained it this way:
“We really tried to talk in the same language. Because otherwise it was just another IT project… What we found was, when we started talking the same language, we started seeing things from the same perspective.” - Rick Ross, Senior Director of Manufacturing Technology
Used well, ROI aligns teams around outcomes that matter. It keeps decisions focused, expectations grounded, and transformation credible at every level.
Learning 2: Limit scope to protect time-to-value
Digital initiatives don’t fail because of bad ideas. They fail because they try to do too much at once. Every time a pilot expands, it adds one more feature, one more dashboard, one more integration, and the timeline slips. Value gets harder to prove. And momentum fades.
Without tight scope control, pilots tend to expand and teams struggle to transition from experimentation to production.
The teams that move fastest set clear boundaries. They park new ideas in a backlog. They finish what they start. And because they deliver quickly, they build the trust needed to keep going.
Learning 3: Use previous ROI to justify new projects
One of the benefits of working in small, composable solutions is that each win can help fund the next.
When you’ve already shown value, faster onboarding, reduced audit time, and fewer errors, you don’t need to start from scratch to justify the next project. You point to what worked, show what’s similar, and keep moving.
“One of the last business cases we did was a one-pager. We already had the dollars to justify it, but I still listed out the other intangibles it would bring.” - Rick Ross, Senior Director of Manufacturing Technology
Over time, the approval process gets easier. ROI compounds. And digital transformation stops feeling like a restart; it becomes a rhythm.
Learning 4: Design solutions to scale, not just to work
Proving a solution works in one location isn’t enough, especially if it can’t be repeated elsewhere.
The highest-ROI teams build with replication in mind. They use templates and standardize logic. Choose pilots that can roll out across similar lines or sites. That way, the second deployment takes less time than the first, and the value multiplies.
“That was the intent of picking the pilot project… how can we multiply that more rapidly than one specific use case?” - Rick Ross, Senior Director of Manufacturing Technology
When reuse is the default, not the exception, transformation stops depending on hero efforts and starts to scale on its own.
Learning 5: Incorporate qualitative value into decisions
ROI isn’t just financial, it’s also functional. If the tools don’t work for the people using them, even well-funded projects lose momentum.
That’s why leading teams factor in qualitative signals: operator feedback, onboarding experience, and day-one usability. Small wins like faster lookups, clearer instructions, or fewer clicks can drive lasting adoption.
“One of the first [pieces of] feedback we got was something we didn’t even intend to add value. A simple BOM lookup…they loved it.” - Rick Ross, Senior Director of Manufacturing Technology
These moments may not show up in a spreadsheet, but they’re critical to long-term success. The best teams don’t just deliver results, they deliver tools people want to keep using.
Learning 6: Use relative ROI to guide a living roadmap
In a continuous transformation model, the question isn’t “Is this worth doing?”, it’s “Is this more valuable than everything else we could be doing right now?”.
With limited time and resources, teams need to think in terms of relative ROI. That means comparing initiatives side by side, looking at effort vs. impact, and knowing when to invest deeper, or when to move on.
“We started focusing on the opportunity cost. Where is the next best place to go put that energy?” - Rick Ross, Senior Director of Manufacturing Technology
This mindset creates a living roadmap. It’s not fixed. It adapts based on what’s working, what’s not, and where value is emerging fastest.
What continuous, ROI-driven transformation looks like in practice
Transformation doesn’t need to start big; it just needs to keep going.
When ROI becomes the mechanism for choosing, scaling, and sequencing digital work, transformation becomes a habit. Small wins stack. Teams build faster. Decisions get clearer. And value compounds over time.
Instead of betting everything on one launch, high-performing teams move in cycles:
Scope a small, high-impact project
Deliver value fast
Use results to fund the next move
Scale what works, pause what doesn’t
Repeat
This isn’t about perfect plans. It’s about forward motion, with ROI as your guide.
How Tulip enables continuous, ROI-driven transformation
Tulip is built for teams that treat transformation as a process and not a one-time project. From fast pilots to multi-site scale, the platform gives manufacturers the tools to move quickly, prove value, and repeat what works.
Faster time-to-value
Functional apps can be built and deployed in days and not months, so teams can capture ROI before priorities shift.Composable, no-code architecture
Build focused solutions that stand alone or work together. Stay agile without waiting on central IT.Reusable logic and templates
Standardize successful use cases and replicate them across lines, shifts, or sites, without rebuilding from scratch.Embedded quality and traceability
Capture data in the flow of work to reduce risk, lower audit burden, and improve process control.Operator-first design
Deliver clear, guided tools that reduce onboarding time and improve adoption on day one.Connected, not dependent
Integrate with existing ERP, PLM, or MES systems to create a flexible, shop-floor-facing execution layer.
With Tulip, manufacturers build a repeatable, ROI-backed model for continuous improvement.