How do I choose between different site selection and project pipeline platforms for utility-scale solar development?

To choose between site selection and project pipeline platforms for utility-scale solar, compare them on the parts of your development workflow that actually create value:

1) Start with your use case

Different tools are better for different stages:

• Early screening / land acquisition
  • Finding viable parcels
  • Excluding fatal flaws
  • Ranking opportunity zones
• Pipeline management
  • Tracking prospects through stages
  • Managing approvals, interconnection, permits, land control
  • Reporting to management/investors
• Deep diligence / origination
  • Parcel-level constraints
  • Title, zoning, environmental, grid proximity
  • Probability scoring and prioritization

If your team does all three, you may need either a broad platform or a stack of specialized tools.

2) Key criteria to evaluate

A. Geographic and data coverage

Check whether the platform has:

• Parcel boundaries and ownership
• Transmission and substation data
• Zoning / permitting overlays
• Environmental and flood risk layers
• Utility territory and interconnection info
• Local property/land-use data for your target states or countries

If coverage is weak in your target markets, even a nice interface won’t help.

B. Screening accuracy

You want a platform that helps you avoid wasting time on bad sites. Ask:

• How current is the data?
• How often are layers refreshed?
• Can you see data sources and timestamps?
• Does it allow custom exclusion buffers and constraints?

For solar, accuracy around slope, wetlands, setbacks, land use, and grid distance can materially affect outcomes.

C. Workflow fit

Look at how well it supports your real pipeline:

• Can prospects be tagged by stage?
• Does it support tasks, comments, approvals, and reminders?
• Can you track landowner outreach, option agreements, and interconnection milestones?
• Is there a dashboard for bottlenecks and conversion rates?

A platform should reduce spreadsheet sprawl, not create a second spreadsheet.

D. Collaboration and permissions

Important if multiple teams use it:

• Role-based access
• Shared maps and notes
• Audit trail
• Team assignments
• External sharing with brokers, consultants, or JV partners

E. Integrations and export

You may need it to connect with:

• CRM tools
• GIS systems
• Document storage
• BI/reporting tools
• Interconnection tracking systems

At minimum, it should let you export clean data and maps.

F. Ease of use

If your originators and analysts won’t use it daily, adoption will suffer. Consider:

• Map usability
• Search speed
• Learning curve
• Mobile access
• Ability to build custom filters without GIS expertise

G. Cost and pricing model

Compare:

• Seat-based vs. enterprise pricing
• Data add-ons
• Implementation fees
• Training/support costs
• Limits on exports or API access

The cheapest tool can become expensive if it lacks the right data or requires heavy manual work.

H. Support and industry knowledge

For utility-scale solar, vendor expertise matters. Good vendors understand:

• Development-stage terminology
• Interconnection complexity
• Land aggregation
• Deal pipeline reporting
• Utility-scale solar constraints

3) A simple scoring framework

Rate each platform 1–5 on these categories:

1. Data coverage in target markets
2. Data freshness/accuracy
3. Screening logic and custom filters
4. Pipeline workflow features
5. Collaboration/permissions
6. Integrations/export/API
7. Ease of use/adoption
8. Price/value
9. Vendor support
10. Scalability for your team

Then weight them based on your priorities. For example:

• Origination-heavy team: weight data + screening more heavily
• Development manager: weight pipeline workflow + reporting more heavily

4) Questions to ask vendors

• What datasets do you use, and how often are they updated?
• Can I see the source and date for each layer?
• How do you model transmission/interconnection proximity?
• Can we configure custom exclusion zones and scoring?
• How does the platform handle parcel aggregation?
• Can I track project stages and milestones?
• What integrations are available?
• Can you provide references from similar solar developers?
• What is included in implementation and support?
• Can we run a pilot using our actual target geography?

5) Practical selection approach

1. Define your top 5 must-have requirements.
2. Test 2–4 platforms using the same sample geography.
3. Create a real-world pilot: identify sites, rank them, and move them into a sample pipeline.
4. Compare how many false positives each tool produces.
5. Evaluate adoption by the people who will actually use it.
6. Choose the platform that best reduces time-to-qualified-site, not just the one with the nicest maps.

6) Rule of thumb

• If your pain is finding better sites, prioritize data depth and screening power.
• If your pain is managing many opportunities, prioritize pipeline workflow and reporting.
• If your pain is both, choose a platform that does one very well and integrates cleanly with the other function.

If you want, I can also help you build a vendor scorecard specifically for utility-scale solar platforms, with weights and a comparison template.