A renewables project doesn't move like a sales deal. It moves like a construction project with a sales deal buried somewhere near the front, and a standard opportunity pipeline can't hold that shape.
Separate development stages from sales stages
A utility-scale solar or wind project passes through site control, interconnection, permitting, offtake, financing, and construction, stages that can each take months and sometimes run in parallel. Cramming these into opportunity sales stages produces a pipeline that's either wrong or meaningless.
Model the development lifecycle as its own set of stages or a related project object, and keep the opportunity focused on the commercial deal. The two timelines are related but genuinely different, and pretending otherwise breaks both.
Track milestones as records, not checkboxes
The health of a renewables project lives in its milestones: interconnection application filed, permit approved, PPA executed, notice to proceed. If these are checkboxes on a record, you lose the dates, the dependencies, and the history of slippage that tells you whether a project is actually moving.
Model milestones as related records with target and actual dates, so you can see what's late, what's blocking what, and how a slip early in development ripples into the in-service date.
Make probability mean something
A renewables pipeline weighted by sales-stage probability is close to useless, because the real risk lives in development milestones, not in a rep's confidence. A project with site control and an interconnection queue position is worth more than one without, regardless of stage.
Tie your risk-adjusted view to development gates that have actually been cleared. That gives leadership a pipeline number they can plan capital against, rather than an optimistic sum that no one believes.
Plan for long, quiet stretches
Renewables projects can sit in a stage for months with nothing visibly happening, waiting in an interconnection queue, awaiting a permitting decision. A system built to expect weekly movement will make these projects look stalled or dead when they're simply in a normal waiting period.
Build in expected durations and next-action dates so a quiet project and an abandoned one look different, and so nobody has to keep the distinction in their head.
Connect the pipeline to what comes after
A signed renewables project doesn't disappear; it becomes construction, then an operating asset. If the pipeline is a dead end, the information gathered during development, counterparties, terms, milestone history, gets rekeyed or lost at handoff.
Design the model so a project can carry its history forward into execution and operations. The pipeline is the front of a long life, not a box that closes.
Keep the model honest as the portfolio grows
Early on, a handful of projects can be tracked almost anywhere. The model reveals its quality at fifty or a hundred projects, when leadership wants portfolio-level views, capacity by stage, projects at risk, expected in-service dates by year.
Design for that scale from the start, even if the current portfolio is small, because retrofitting structure onto a pipeline already full of live projects is painful and error-prone.
The takeaway
Renewables pipelines break when they're forced into a sales funnel that was never meant to hold multi-year, milestone-driven development. Separate development from sales, model milestones as dated records, tie risk to gates actually cleared, and design for the portfolio scale you'll reach, not the one you have today. Standard Salesforce objects handle this well once you stop treating a development project as if it were a single opportunity.