Paces

1. If an organization requires transparent, self-serve pricing and immediate procurement. The vendor’s public materials indicate a sales-led engagement model rather than published pricing tiers.

2. If independently validated ROI guarantees are required. Public-facing speed and ROI claims lack detailed methodology; organizations should plan to run a pilot and validate outcomes internally.

3. If the primary risk is hazardous materials or ASTM Phase I ESA compliance. In such cases, specialized ESA providers and tooling are more appropriate.

4. If an organization already maintains a mature GIS and data engineering capability and prefers to build an internal stack. An internally assembled stack (ArcGIS plus curated datasets and consultants) can provide more direct control and auditability, albeit with internal resource investment.

5. If public, documented security certifications are a strict procurement gate. The vendor does not appear to publish a trust center with explicit certifications in the sources reviewed.

• Development activity concentrated in a single locality where deep local permitting knowledge and relationships already exist
• Security requirements that mandate publicly documented security certifications (e.g., SOC 2/ISO) that the vendor does not publicly publish
• Workflows that rely primarily on Phase I Environmental Site Assessment (ESA) processes for hazardous materials and contamination compliance; this vendor appears oriented to permitting, interconnection, and environmental constraint screening rather than full ESA substitution

The vendor’s homepage includes customer quotes emphasizing early mistake prevention and improved site identification. These are vendor-published testimonials and should be treated as promotional material unless validated:

• A quote attributed to the CEO of a development firm highlights the cost impact of early-stage mistakes and states that the vendor provides data that reduces such mistakes.
• A product testimonial from a project development manager reports identification of parcels that internal GIS had missed and subsequent movement of those parcels into development.

The vendor’s funding announcement and marketing materials list larger customers in aggregate; such listings are vendor claims unless independently verified.

Because public negative reviews are scarce, churn reasons are inferred from typical failure modes in this product category:

• Coverage gaps or local inaccuracies in permitting and zoning datasets
• Lack of integration with existing GIS, procurement, and CRM tools
• Pricing that does not match the perceived option value for early-stage screening compared with bespoke GIS layers and consultants
• Organizational resistance or stakeholder preference for traditional consultant reports and manual sign-offs

The vendor publishes case studies describing outcomes such as reduced cycle times and increased pipeline viability for specific customers. These are vendor-authored materials.

Example: a case study describes a smaller solar development team scaling results using the vendor’s product; detailed metrics are available in the vendor’s case study materials and may require direct vendor access.

Vendor headlines include claims of materially increased success rates for specific customers; the underlying methodologies and baselines are not visible in the public excerpts reviewed.

• Attribution bias: vendor-authored case studies typically emphasize positive outcomes and may omit failures or contextual limitations.
• Missing methodology: claims of substantially faster or significantly shorter timelines lack public definitions (phase measured, selection criteria, geographic scope, sample size) and therefore require verification.
• What to request from the vendor before accepting ROI claims: prior/after cycle-time metrics, project cohort selection criteria, counterfactual analysis (what would have occurred without the product), and examples where platform outputs were validated against later outcomes.

Paces is a B2B software and services platform designed to support early-stage energy infrastructure development. The product aims to help teams:

• identify viable sites (site origination)
• identify and quantify key development risks earlier (permitting, interconnection/grid constraints, environmental constraints)
• shorten due diligence workflows that are typically manual, sequential, and spread across multiple tools and vendors

The vendor positions the product as a way to reduce development risk and shorten the path from origination to construction-ready projects by consolidating disparate datasets and applying analytics, machine learning models, and services provided by subject-matter experts. The homepage messaging emphasizes earlier risk identification, reduced time-to-construction, and enabling smaller development teams to evaluate larger project funnels.

Key vendor claims to treat cautiously (require independent validation):

• Vendor statements claiming substantially faster time-to-power and significantly reduced timelines are presented without publicly documented methodology, cohort definition, baseline assumptions, or independent audit in the publicly accessible pages reviewed.

Sources referenced in the research include official vendor product pages, product marketing materials, and publicly available funding information.

Paces primarily targets:

• Renewable energy developers (solar, storage, and potentially wind)
• Data center developers and other large-load developers seeking earlier visibility into power availability
• Utilities and broader energy infrastructure teams involved in siting and early-stage risk screening

The company markets itself as a GIS and data platform for pre-construction decision-making and due diligence with an emphasis on permitting and interconnection constraints as key bottlenecks.