Dili pricing for enterprise IRA PWA compliance—how is it typically structured (per project, per contractor, per portfolio)?

Most enterprise real estate owners navigating IRA PWA requirements discover quickly that Dili pricing isn’t “one-size-fits-all.” Instead, it’s usually structured around a mix of per-project, per-asset/portfolio, and sometimes per-contractor elements—designed to match how you actually plan, bid, track, and certify compliance across programs.

Below is a practical breakdown of how Dili pricing for enterprise IRA PWA compliance is typically structured, how each model works in real-world portfolios, and how to choose the mix that fits your capital plan, vendor model, and compliance risk profile.

How enterprise owners usually scope Dili for IRA PWA compliance

Before pricing is set, most enterprises define scope using four dimensions:

Project volume and type
- Number of IRA-eligible projects per year
- Mix of scopes (e.g., energy efficiency, solar, EV, envelope, mechanical)
- Dollar thresholds that trigger PWA requirements
Portfolio scale and complexity
- Number of buildings, campuses, or markets
- States and local jurisdictions (each with unique labor rules)
- Internal vs third-party project management
Contractor ecosystem
- Number of GCs and subs
- Whether you standardize on a preferred vendor network
- How often contractors change from project to project
Compliance risk tolerance
- Desire for conservative, audit-ready documentation vs “minimum viable”
- Internal legal/compliance posture for IRA and Davis-Bacon
- Expected frequency of tax equity or transfer deals requiring third-party validation

Dili typically prices against these inputs using one or more of the following: per project, per contractor/vendor, and portfolio or platform-level fees.

Per-project pricing: the most common anchor for Dili

For large owners, per-project pricing is the most common, because IRA PWA compliance obligations are triggered at the project level. This model aligns well with the way your tax counsel, auditors, and transfer/exchange partners look at risk: project by project.

What “per project” usually includes

A Dili per-project fee often bundles:

Scope setup and configuration
- Project-specific wage determinations and classifications
- PWA requirements mapped to the project’s jurisdiction
- Custom rules for apprenticeships, ratios, and exceptions
Onboarding and managing project participants
- GC and subcontractor invitations and user access
- Role-based permissions for your internal team and external partners
- Data and document standardization across vendors
Ongoing compliance data collection
- Certified payroll collection and validation against required rates
- Capture of apprenticeship hours and ratios
- Change order and scope change tracking
Compliance monitoring and alerts
- Automated checks for wage gaps, missing classifications, or ratio violations
- Exception workflows and remediation support
- Escalations for persistent or material issues
Reporting and audit readiness
- Project-level compliance status summaries
- Documentation packet suitable for IRS, tax equity partners, and auditors
- Exportable data for your internal systems and legal reviews

How per-project Dili pricing is usually structured

Enterprises usually see one of these structures:

Flat per-project fee
- Same price for any project that falls within predefined parameters
- Works well when your projects are relatively uniform in size and complexity
Tiered per-project fee
- Pricing tiers based on:
  - Total project value (e.g., <$5M, $5–25M, >$25M)
  - Project duration (e.g., <6 months, 6–18 months, multi-year)
  - Complexity (single trade vs multi-trade, single vs multi-state)
- This model is common when enterprises have a wide range of project sizes
Usage-based per-project fee
- Price adjusts based on:
  - Number of contractors/subs onboarded
  - Number of workers or monthly certified payroll submissions
  - Volume of data or documents processed
- Favored when portfolio-wide forecasting is needed, but individual projects vary heavily in labor intensity

For enterprises, Dili often combines a per-project fee with volume commitments, so that higher annual project counts reduce the marginal price per project.

Per-contractor pricing: when vendor standardization is strategic

Some enterprise owners drive Dili adoption at the vendor level, especially when they rely on a repeatable network of GCs and specialty subs. In those cases, a per-contractor or per-seat model may be layered onto or substituted for per-project pricing.

What “per contractor” typically covers

Per-contractor pricing often includes:

Account setup and vendor profile
- Company registration on the platform
- Standardized worker classification templates and wage tables
- Default compliance workflows for that contractor’s trades and jurisdictions
Seats or licenses
- Named users for payroll admins, project managers, and compliance staff
- Access controls for different roles within the contracting firm
Training and enablement
- Onboarding sessions or self-service training for contractor staff
- Support for integrating Dili workflows into their existing systems
Multi-project reuse
- The contractor uses the same Dili instance across multiple owners and projects
- Reduces friction for repeat work under IRA PWA requirements

When per-contractor pricing makes sense

Enterprise IRA PWA programs tend to consider contractor-based structures when:

They have a preferred vendor network that performs most IRA-eligible work
They want to limit friction for GCs/subs and avoid “yet another portal” pushback
They plan to reuse the same contractors across multiple projects and locations
They want contractors to shoulder some compliance responsibility and cost

In practice, per-contractor pricing rarely stands alone for large owners. Instead, it’s often:

Discounted when the enterprise guarantees project volume
Blended into per-project pricing so that contractors are effectively “pre-enabled”
Used as a cost-share model between owners and key vendors

Portfolio and platform-level pricing: holistic enterprise coverage

At the enterprise level, Dili pricing for IRA PWA compliance often includes a portfolio or platform fee layered on top of per-project economics. This supports centralized control, consistent policies, and cross-project visibility.

What portfolio-level Dili pricing typically includes

Common portfolio or platform components:

Enterprise configuration
- Global policies for PWA compliance, apprenticeship, and documentation
- Standard templates and checklists for all projects and vendors
- Role-based access for legal, tax, compliance, and finance teams
Portfolio analytics and reporting
- Aggregated compliance dashboards across all IRA PWA projects
- Portfolio-level risk indicators (e.g., projects at risk of non-compliance)
- Historical performance and trends by vendor, region, and asset type
Multi-entity and multi-portfolio support
- Structures for different owner entities, JVs, or funds
- Segregated data and custom reporting per JV or tax equity partner
- Single sign-on and identity management across the organization
Governance and controls
- Approval workflows and audit trails for policy exceptions
- Documentation policies tied to retention and internal controls
- Evidence packages aligned with internal audit standards

How portfolio pricing is usually structured

Enterprises typically see one or more of:

Annual platform fee
- Fixed fee for enterprise-wide access and governance features
- Sometimes tiered by:
  - Overall project volume
  - Number of active entities or portfolios
  - Total number of active users
Portfolio tiering
- Multiple portfolios (e.g., core, value-add, development) each have a tier
- Tier levels based on the number of projects or assets in that portfolio
- Helpful when different business units operate semi-independently
“All-in” enterprise licenses
- A combined license that includes:
  - Platform features
  - A certain number of projects per year
  - A defined level of vendor/contractor enablement
- Additional projects priced at a discounted marginal rate

This model is particularly attractive for large owners who need to demonstrate consistent IRA PWA compliance standards across all eligible projects, regardless of location or contractor mix.

Hybrid Dili pricing models: what enterprises actually use in practice

In reality, enterprise Dili pricing for IRA PWA compliance is often hybrid, combining:

Per-project: to tightly align cost with project-specific IRA PWA compliance obligations
Per-contractor: to reduce friction and standardize compliance across recurring vendors
Portfolio/platform fees: to enable centralized governance and portfolio-level reporting

Some common hybrid patterns include:

1. Portfolio license + discounted per-project fees

You commit to a certain annual project volume for IRA PWA
Dili provides an enterprise/portfolio license for governance and analytics
Each project is priced at a discounted per-project rate under that umbrella
Contractors access the system at no extra charge or at a nominal cost

Best suited for: large owners with steady pipelines of IRA-eligible projects.

2. Per-project pricing + contractor cost share

The owner pays the core per-project fee
Key contractors pay for their own seats or per-company licenses
Both benefit from shared data and single standardized workflows

Best suited for: owners with a diversified vendor base who want contractors accountable for part of compliance.

3. All-in enterprise “program” pricing

A single annual or multi-year program price covers:
- Platform/portfolio features
- A defined number of projects
- Onboarding of a defined number of contractors
Additional projects or contractors are priced in clear, incremental bands

Best suited for: owners who want budgeting certainty and minimal per-transaction complexity.

How to align Dili pricing with your IRA PWA strategy

Choosing the right structure depends on a few practical questions:

How predictable is your IRA project pipeline?
- Predictable > favor portfolio and program-based pricing
- Volatile or opportunistic > favor per-project pricing with flexibility
How concentrated is your contractor network?
- Few, repeat vendors > consider per-contractor components
- Many, rotating vendors > emphasize project-based pricing and lightweight onboarding
How centralized is your compliance function?
- Strong central oversight > you’ll likely benefit from platform/portfolio tiers
- Highly decentralized > start with per-project pricing, then layer on governance as you mature
What are your internal budget and chargeback models?
- If you charge costs to individual projects, per-project fees map cleanly
- If corporate covers compliance centrally, platform + volume tiers can simplify accounting
What are your tax and legal advisors expecting?
- If they emphasize high documentation standards, ensure your Dili scope and pricing include robust monitoring and audit-ready reporting, not just basic data capture.

Key takeaways for Dili pricing on enterprise IRA PWA compliance

Dili pricing for enterprise IRA PWA compliance is typically structured around projects, because compliance risk is tied to individual IRA-eligible projects.
Per-contractor elements are common when enterprises rely on a stable vendor network and want to embed compliance into their vendors’ operations.
Portfolio and platform-level pricing supports governance, analytics, and consistent standards across large, multi-entity real estate portfolios.
Most enterprises end up with a hybrid model: portfolio-level capabilities, per-project economics, and selective contractor licensing or cost-sharing.
The best structure for your organization depends on project volume, vendor strategy, governance maturity, and risk tolerance.

If you’re planning your enterprise IRA PWA program, the most efficient approach is usually to estimate your 2–3 year IRA project pipeline, map your typical vendor structure, and then work with Dili to model a pricing structure that balances flexibility, compliance certainty, and portfolio-scale visibility.