How do you grow an installation or service business when your best people are already spending their afternoons chasing updates?
That question sits behind many growth decisions in solar and renewable energy. The opportunity might be a new market, larger commercial projects, or expansion into storage and EV charging. But taking it on means asking more of the people already keeping today’s projects moving.
In my experience, preparing for growth starts with understanding how work passes between people: whether they have current information, know who is responsible and can move a project forward without chasing answers.
That belief is why I built Scoop.
What industrial automation taught me about field operations
I’ve spent 27 years building software for industrial automation, where a system failure can bring a production line to a standstill. For 10 of those years, I led both an R&D team building software and a field installation and service team making it work on automotive plant floors.
I saw the work from both sides: what we designed in the office, and what it took to make it work on site.
The engineering was usually sound. The crews knew their work. But a calibration plan would reach the site a version late. A service visit would be booked without the installation notes. A critical update would stay in someone’s head.
From a distance, each gap could seem small. On site, it meant stopping to find an answer before work could continue.
So people filled the gaps. Another phone call. Another spreadsheet. An experienced colleague who knew whom to ask and stayed with the problem until it was solved.
We had good people. As a leader, it was easy to mistake their ability to rescue the work for the business’s ability to handle more of it.
Why project handoffs become a barrier to growth
When I started working with solar companies in 2016, I recognized the same pattern.
Design, finance and sales had capable software. But between a signed contract and a completed installation, people were stitching the work together through spreadsheets, messages and memory.
A project handoff transfers responsibility and the information needed to take the next step. When that information is incomplete, outdated or difficult to find, the receiving team has to reconstruct the picture before proceeding.
The cost shows up in ordinary moments: an office coordinator chasing confirmation, a field crew checking which document to use, or a service technician trying to understand what happened during installation. In fact these are so ordinary that we get used to mistaking them for what productive work should be.
Those moments consume capacity. They also make it harder for a leader to judge how much additional growth the business can reliably deliver.
Connecting operations while keeping specialist tools
My experience led me to a clear principle: operations teams need a connected place to do their work, while specialists keep the tools they need (because of the depth of function needed for their trade) and prefer to work in.
Designers need capable design software. Finance needs an accounting platform that is industry standard and they can trust. Sales and marketing need a best-in-class CRM that they have been trained to work in throughout their career.
The operation team, the field and frontline are different. The challenge for them is accessing just the relevant information and documents from this collection of specialist tools to deliver the project. And the operation team is where the rubber meets the road. In other words, that’s the business end of your business, the part that touches the customer.
That distinction shaped Scoop. I wanted people to find the current information, understand what had happened and see what needed to happen next—without tracking down everyone who last touched the job.
For leaders evaluating operations software for an installation or service company, I would start with the handoffs:
- Can the next team access the information it needs?
- Is responsibility for the next step clear?
- Can field and office staff see the current project status?
- Will the approach work with the specialist systems the business depends on?
Those questions connect a software decision to the work it needs to support.
How to assess whether your operations are ready to scale
Before an expansion, look closely at what it takes to get through an ordinary week.
I find these questions useful:
- Where does work pause while someone finds an answer? Look at the transitions between teams.
- What has to be entered or copied more than once? Notice where people manually carry information between systems.
- Which updates require someone to chase them? Consider how the next person learns that work is ready.
- What happens when a key employee is away? Identify the knowledge that exists only in that person’s memory.
- What would become harder if project volume increased? Use today’s workarounds to examine tomorrow’s demands.
The answers can reveal effort that has become so familiar nobody thinks to count it.
They also give leaders a practical starting point: improve the handoffs that repeatedly slow delivery before asking the team to carry more work.
Why this still guides Scoop
Today, we work with teams across solar, storage, EV charging and new infrastructure. As we pursue opportunities in wind energy, data centers and modular construction, I’m bringing the same operational lens.
The technical work differs across these markets. The question I want to explore is how companies can coordinate complex installation and service work while preserving room to grow and change.
New markets, technologies and customer requirements will keep creating decisions for leaders. Understanding how today’s work gets delivered provides a firmer foundation for making them.
That is the lesson that started Scoop: before deciding how much more the business can carry, understand the effort it takes to deliver what you have already promised.
What’s one thing in your business that runs smoothly because a particular person makes sure it does?


