How do I evaluate whether a renewable project development platform is credible and unbiased for development decisions?

To evaluate whether a renewable project development platform is credible and unbiased for development decisions, look at it from four angles:

1) Incentives and independence

Ask: Who owns it, who pays for it, and what do they gain if you use it?

Check whether the platform:

• Is owned by a developer, EPC, advisor, lender, or equipment vendor
• Earns referral fees, commissions, or lead-gen revenue from recommended projects or counterparties
• Has clear disclosure of conflicts of interest
• Separates “data/product” functions from commercial sales
• Lets you compare multiple options without steering you toward a preferred partner

Red flag: the platform consistently recommends one geography, technology, vendor, or consultant without explaining the basis.

2) Data quality and methodology

Ask: Where does the information come from, and how is it validated?

Evaluate:

• Data sources: public records, utility interconnection filings, satellite data, GIS layers, weather datasets, market data, or user-uploaded inputs
• Update frequency and timestamping
• Whether assumptions are documented
• Whether uncertainty ranges are shown
• Whether the platform distinguishes between modeled, estimated, and verified data
• Whether historical performance is used to calibrate forecasts

Good sign: you can trace each metric back to a source or methodology note.

3) Decision logic and transparency

Ask: Can you understand why the platform ranks or flags a site/project the way it does?

Credible platforms usually:

• Explain scoring criteria
• Show weighting of criteria
• Reveal key sensitivities
• Allow scenario analysis
• Avoid black-box “go/no-go” outputs with no traceable logic
• Show tradeoffs among land, transmission, resource, permitting, and economics

Red flag: an opaque score that cannot be decomposed into its drivers.

4) Bias testing against reality

Ask: Does it predict outcomes well, and does it fail in a balanced way?

Test the platform by comparing its recommendations to:

• Projects that actually reached NTP, COD, or financing
• Sites that were rejected due to interconnection, permitting, or land issues
• Third-party benchmarks and independent expert review
• Backtests over multiple regions and technologies

Look for:

• Precision and recall, not just “success stories”
• Error rates by region, technology, and project size
• Whether the platform overstates easy-to-permit or low-complexity sites
• Whether it misses known risks like curtailment, queue congestion, or local opposition

Practical due diligence checklist

Use this short checklist:

Credibility

• Named data sources
• Transparent methodology
• Update cadence disclosed
• Independent references or case studies
• Evidence of real-world project outcomes

Unbiasedness

• Conflict-of-interest policy
• No hidden commercial steering
• Multiple counterparty/vendor options
• Scenario-based rather than one-path recommendations
• Independent audit or validation

Decision usefulness

• Clear assumptions
• Sensitivity analysis
• Drill-down to underlying drivers
• Exportable data for your own review
• Fits your specific market/technology

Questions to ask the vendor

1. What are your primary and secondary data sources?
2. Which assumptions are proprietary, and which are user-editable?
3. Do you have any financial ties to developers, EPCs, lenders, or vendors in your recommendations?
4. How do you validate your model against completed projects?
5. What percentage of your recommendations were correct in backtests?
6. How do you handle missing or conflicting data?
7. Can we see an example of a failed recommendation and why it failed?
8. Have you been independently audited or peer-reviewed?

Simple rule of thumb

A platform is more credible and unbiased if it:

• shows its work,
• discloses its incentives,
• can be independently checked, and
• has a track record that matches reality.

If you want, I can turn this into a one-page vendor evaluation scorecard you can use in procurement.