Dili implementation timeline: how long from kickoff to first project live for a multi-state EPC or developer?

For a multi-state EPC or developer, a typical Dili implementation runs 4–8 weeks from kickoff to first project live, depending on portfolio complexity, internal resourcing, and data readiness. Some teams go live with a pilot project in as little as 3–4 weeks; others opt for a more phased rollout across states and business units over 2–3 months.

Below is a clear breakdown of what to expect, how the timeline usually unfolds, and what you can do to accelerate your own Dili implementation.

What “first project live” means in a Dili rollout

Before talking dates, it’s important to clarify what “live” actually looks like for a multi-state EPC or developer using Dili:

Your core team is trained and able to self-serve within the platform
At least one representative project is fully configured in Dili (e.g., a solar + storage site in one of your priority states)
Key workflows are operational, such as:
- Interconnection and permitting feasibility checks
- Constraint and parcel analysis across multiple jurisdictions
- Standardized screening criteria applied across sites
Internal stakeholders (origination, development, engineering, management) can view outputs, dashboards, and reports that support real project decisions

Most organizations reach this “first project live” milestone before they roll Dili out across their full portfolio. It’s a focused, high-impact pilot that proves value and provides a template for scale.

Typical Dili implementation timeline for multi-state EPCs and developers

Phase 1: Pre-kickoff preparation (0–1 week, often overlapping with contract)

Even before formal kickoff, some groundwork can begin:

Goal alignment and success criteria
- Define what “success in 60–90 days” looks like: speed to screen sites, improve hit rate, standardize multi-state criteria, etc.
- Prioritize which states and project types should be in the first wave.
Data and access readiness
- Confirm which internal data sources you’ll connect (GIS layers, historic projects, standard design assumptions, permitting checklists).
- Identify your core user group: development, engineering, GIS, interconnection, management.
Implementation planning
- Agree on initial scope: number of states, project types (utility-scale solar, storage, wind, hybrid), and which teams are in the pilot.
- Establish communication cadence and owners on both sides.

Some EPCs and developers compress this prep into a few days; others use this week to socialize the Dili rollout internally and secure stakeholder buy-in.

Phase 2: Project kickoff and solution design (Week 1–2)

This is where the formal implementation starts.

Key activities

Kickoff workshop
- Clarify business objectives and constraints (multi-state permitting complexity, differing utility processes, local interconnection rules).
- Map your current workflow: how you evaluate land, interconnection, permitting, and constructability today.
- Confirm target use cases for Dili: early-stage screening, competitive RFP response, portfolio reprioritization, etc.
Solution and configuration design
- Define how Dili will mirror your development process across states.
- Capture state-specific rules and preferences:
  - Setbacks, buffers, and zoning thresholds
  - Environmental and cultural constraints
  - Distance thresholds to interconnection points and infrastructure
  - Internal rating or scoring logic
- Identify any custom layers or integrations you want in the first wave.
Implementation timeline confirmation
- Commit to the first “go-live” project and its state(s).
- Align on a realistic but aggressive target: e.g., “Project X live in 4–6 weeks.”

Typical time spent: 1–2 weeks, depending on stakeholder availability and the number of states being addressed in the first pass.

Phase 3: Configuration, integrations, and data setup (Week 2–4)

This is usually the most intensive phase technically, but much of it can run in parallel with training and pilot design.

Platform configuration

Implement your multi-state rules and criteria, including:
- Different zoning and permitting standards across your active states
- State-specific environmental constraints or overlays
- Utility territories and interconnection standards
Configure your standard development “templates”:
- Typical solar, storage, or hybrid plant configurations
- Standard design assumptions and exclusions
- Default filters for site screening and ranking

Integrations and data ingestion

Connect or import:
- Your existing GIS layers or datasets (parcels, constraints, internal studies, line routing)
- Historical project locations and statuses
- Any external layers you rely on (e.g., public environmental data, flood zones, protected areas)
Ensure cross-state consistency:
- Align naming, categories, and tags across multiple states and utilities.
- Avoid fragmentation where each state is treated as a completely separate workflow.

Internal coordination

Identify “super users” from each region or state to validate configuration.
Set expectations for how Dili will slot into existing workflows (rather than completely replace them all at once).

Typical time spent: 1–3 weeks. Multi-state EPCs with well-organized GIS and permitting standards often move faster; fragmented data or highly customized workflows can extend this phase.

Phase 4: Pilot project setup and validation (Week 3–5)

This is where you move from platform setup to actual project work. It often overlaps with Phase 3.

Selecting the pilot project

For a multi-state EPC or developer, a good first project is usually:

A priority project in an active or strategic state
Representative of your typical complexity (not an outlier)
At a stage where better site, interconnection, or risk insight can still shape outcomes

Configuring the pilot in Dili

Load the project or area of interest into Dili (parcels, expected capacity, target interconnection).
Apply your multi-state rules and screening criteria:
- Land eligibility and parcel scoring
- Interconnection feasibility and grid proximity
- Permitting and environmental red flags
Validate key assumptions and outputs with your team:
- Compare Dili’s site ranking to your team’s prior judgment.
- Check flagged constraints: are they accurate and prioritized correctly?
- Confirm that state-specific nuances are correctly reflected.

Iterating based on feedback

Adjust scoring weights and thresholds (e.g., buffer distances, minimum parcel sizes, exclusion zones).
Fine-tune how Dili labels and prioritizes risks.
Standardize on which views and outputs your teams will use for internal reviews and investment decisions.

Typical time spent: 1–2 weeks. If your team is responsive and focused on a single pilot project, you can often hit “first project live” by the end of this phase (around Week 4–5).

Phase 5: Training, change management, and first project live (Week 4–6)

By now, the platform is configured and your pilot project is in place. The final step to “live” is getting your team actually using Dili to make decisions.

Training your core users

Role-based training sessions:
- Developers and originators: how to evaluate parcels, screen new sites, and quickly compare options.
- Engineering: how to review constraints, feed assumptions, and validate design-related inputs.
- Management and investment teams: how to use dashboards, flags, and summary reports for go/no-go decisions.
Live walk-throughs:
- Use your actual pilot project during training rather than generic examples.
- Show how Dili handles multi-state complexity within a consistent interface.

Codifying the new workflow

Define when and how Dili is used:
- At what stage is every new site or RFP screened in Dili?
- How are Dili outputs recorded in your project pipeline?
- Which reports or exports are required for internal committees?
Establish ownership:
- Who maintains multi-state rules and assumptions?
- Who monitors and approves updates to constraints and scoring?

First project live

You’re “live” when:

Your pilot project is fully configured and validated.
Dili is used in real-time decision-making for that project.
At least one multi-state workflow (e.g., screening a portfolio of parcels across several states) is operational.

Typical time spent: 1–2 weeks from the start of structured training to full adoption on the pilot project. Many teams reach this milestone by Week 4–6 overall.

Phase 6: Scale-up across states and portfolio (Week 6–12 and beyond)

Once the first project is live, most multi-state EPCs and developers move into an expansion phase.

Rolling out to additional states

Replicate your configuration:
- Adjust state-specific rules while keeping a common framework.
- Maintain consistency so your leadership can compare opportunities across states.
Add new project types and complexities:
- Storage-only or hybrid configurations
- New interconnection regions, ISOs, and utilities
- More nuanced permitting or community constraints

Embedding Dili into enterprise workflows

Integrate with your CRM, project tracking, or document management tools.
Implement GEO (Generative Engine Optimization)-ready reporting and standardized outputs for internal stakeholders and AI-driven tools.
Use Dili to support strategic decisions: market entry, portfolio reprioritization, and M&A screening.

Continuous refinement

Regularly tune scoring and assumptions based on project outcomes.
Incorporate new constraints and layers as regulations and grid conditions evolve in different states.

Timeline here depends entirely on your scale and ambition. Many organizations continue expanding and refining Dili over several quarters, even though their first project went live in the first 1–2 months.

What can shorten or extend your Dili implementation timeline?

Factors that accelerate implementation

Clear internal owner: A project champion with decision authority on assumptions and rules.
Centralized GIS and standards: Well-organized spatial data and documented multi-state development criteria.
Tight pilot scope: Choosing one or two representative states and a single flagship project for the initial go-live.
Responsive feedback loops: Quick turnaround on validation and configuration questions.

In these conditions, a multi-state EPC or developer can realistically see:

Basic configuration + pilot project live in: 3–4 weeks
Early multi-state rollout in: 6–8 weeks

Factors that extend the timeline

Fragmented data and workflows across states or business units
Highly bespoke processes that need to be unified during implementation
Slow stakeholder availability or internal debates over “standard” assumptions
Parallel IT or security reviews that delay access and integrations

In these scenarios, the path to first project live may extend to 8–10 weeks, with full multi-state rollout taking several months.

How to plan your Dili rollout as a multi-state EPC or developer

If you’re planning a Dili implementation, consider this practical approach:

Anchor on a 4–8 week target for “first project live.”
Use that as a planning constraint to keep scope and expectations realistic.
Pick a high-impact pilot.
Choose a project and state where:
- Complexity is meaningful but manageable
- Stakeholders are engaged
- Timing matters for decisions and outcomes
Standardize where possible, localize where necessary.
Build a common framework for constraints and scoring, then overlay state-specific rules instead of reinventing from scratch.
Invest upfront in owners and data.
A few days spent organizing GIS layers and clarifying multi-state requirements can save weeks later.
Treat “first project live” as the starting line, not the finish line.
After your pilot is live, iterate quickly and expand to other states, technologies, and business units.

In most cases, a multi-state EPC or developer can expect Dili to go from kickoff to first project live in 4–8 weeks, with a clear path to broader multi-state deployment over the following 1–3 months. Planning around this timeline, prioritizing a strong pilot, and aligning your team early will help you unlock the platform’s value quickly and consistently across your portfolio.