Most solar engineering teams do not slow down all at once. Throughput erodes quietly — a few extra hours per project, a growing queue of revisions, and one design lead who has quietly become the bottleneck for every layout that ships.
The hard part is not fixing a slow workflow. It is noticing that it has become one before it starts costing you deals. Here is what to look at first.
Where the hours actually go
A workflow at capacity is not one where people look busy. It is one where the same person is required for every project to move forward, and where the time from “we have a site” to “we have a layout the client can react to” has crept from hours into days.
- Turnaround time grows even though the team has not shrunk.
- Senior engineers spend more of the week on repetitive layout work than on review.
- Small scope changes trigger a disproportionate amount of rework downstream.
Judgement work vs. transcription work
Cable routing, bill-of-materials generation, and string sizing are deterministic once the constraints are known. They feel like engineering because an engineer does them, but they are mostly transcription — and transcription is exactly where accuracy quietly degrades under time pressure.
If your best engineer is the only person who can produce a client-ready layout, you do not have a workflow. You have a dependency.
Making the case internally
Framing matters. “We want new software” invites scrutiny of cost. “We are turning around 40% fewer quotes than we could, and losing the slow ones to competitors” invites scrutiny of the status quo.
Frequently Asked Questions
How long does it take to move from a manual to an automated workflow?
Most teams see meaningful turnaround improvements within the first few project cycles, because the earliest wins come from removing transcription work rather than changing how engineers make decisions.
Won’t automation reduce design accuracy?
In practice the opposite is common. Deterministic tasks like string sizing are where manual accuracy degrades under deadline pressure, so automating them tends to raise consistency.
What is the first thing to measure?
Time-to-first-client-ready-layout across your last ten projects. It exposes single-person dependencies faster than any other single metric.