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

For a multi-state EPC or renewable energy developer, a typical Dili implementation runs 4–8 weeks from kickoff to the first project going live, depending on your portfolio size, data readiness, and internal resourcing. Smaller, more focused deployments can be live in as little as 2–3 weeks, while complex, multi-system rollouts can extend toward the 8–10 week range.

The sections below break down the standard timeline, key phases, dependencies, and what you can do to accelerate go-live without sacrificing quality or compliance.

---

Typical Dili implementation timeline at a glance

From kickoff to first project live, most multi-state EPCs and developers can expect:

• Week 0–1: Discovery & planning
• Week 1–3: Data integration & system configuration
• Week 3–4: State rules, workflows & permissions
• Week 4–5: Testing, QA & internal pilot
• Week 5–6: Training, change management & go-live prep
• Week 6–8: First project live, then phased rollout

This is a reference model, not a rigid rule. Dili is designed to roll out iteratively, so you don’t have to wait for “perfect” configurations in every state before putting your first projects into production.

---

Phase 1: Discovery & implementation planning (Week 0–1)

The implementation begins with aligning Dili to your specific EPC or development workflows.

Key activities

• Stakeholder kickoff

  • Confirm objectives (e.g., faster permitting, lower soft costs, standardized interconnection workflows).
  • Identify use cases: greenfield development, DG portfolios, utility-scale, repowers, storage, etc.
  • Define what “first project live” means for your team (state, project type, stage).

• Process & systems mapping

  • Review current-state workflows across:
    • Site origination & screening
    • Interconnection
    • Permitting & entitlements
    • Engineering handoffs
    • Construction & closeout
  • Map which systems Dili will connect to first:
    • CRM (e.g., Salesforce, HubSpot)
    • Project management (e.g., Procore, Asana, Monday)
    • Document control (SharePoint, Google Drive, Box)
    • GIS & design tools (if in scope)

• Scope and timeline definition

  • Select your initial states (often 2–3 key markets).
  • Choose your first project types (e.g., C&I rooftop solar in CA/TX, utility-scale solar+storage in MISO).
  • Agree on milestones:
    • Configuration complete
    • Data connections live
    • Pilot users onboarded
    • First project created & progressing in Dili

Timeframe: 3–5 business days, depending on number of stakeholders and complexity.

---

Phase 2: Data integration & configuration (Week 1–3)

Once the plan is in place, Dili is configured to match your portfolio structure, teams, and data sources.

2.1 Systems integration

Common integrations for a multi-state EPC or developer:

• CRM & opportunity data

  • Sync accounts, opportunities, key attributes (size, state, utility territory, segment).
  • Decide which fields are “source of truth” in CRM vs. Dili.
  • Configure triggers for when an opportunity becomes a “project” in Dili.

• Project management & tasks

  • Map Dili tasks and checklists to your PM tool structure.
  • Decide where day-to-day task management will live (some teams use Dili as the “source of process” and sync key milestones to PM).

• Document storage

  • Configure folders and naming conventions.
  • Set up where Dili stores state- or utility-specific documents and outputs.

• Optional: GIS / design

  • If integrated, configure site boundary imports, interconnection mapping, or design revisions.

Timeframe: 1–2 weeks, run in parallel with workflow configuration.

2.2 Organization, roles, and permissioning

Multi-state EPCs and developers often deal with complex org structures and external partners. Dili is configured to reflect this:

• Organizational structure

  • Regions / business units (e.g., West, ERCOT, PJM, CAISO).
  • Functional teams (development, interconnection, permitting, engineering, construction).

• Roles & permissions

  • State-level access rules (e.g., certain team members only see specific regions).
  • External user access for:
    • Subcontractors
    • Legal counsel
    • Local permitting partners
    • Owners’ reps

• Approval chains

  • Who can approve:
    • Interconnection applications
    • Permit submissions
    • Design packages
    • Change orders

Timeframe: 3–7 days; more complex if there are many JV partners or external stakeholders.

---

Phase 3: State rules, workflows & templates (Week 3–4)

This is where Dili becomes tailored to the regulatory and procedural reality of your specific markets.

3.1 Multi-state regulatory logic

For each initial state in scope, the implementation team configures:

• State and local permitting workflows

  • Required steps by jurisdiction (where standardized workflows are possible).
  • Variants for:
    • Greenfield vs. expansion
    • Rooftop vs. ground-mount
    • Solar vs. storage vs. hybrid

• Utility & interconnection processes

  • Utility-specific steps and documentation.
  • Queue stages, study milestones, and decision points.
  • Rules for when interconnection status gates other project actions.

• Compliance and documentation

  • Template library (studies, applications, cover letters, affidavits).
  • Required uploads/checklists before advancing a stage.

Dili’s pre-built playbooks for major U.S. markets often accelerate this phase significantly; your internal team mainly reviews and tailors instead of building from scratch.

3.2 Standardized workflows across states

For multi-state EPCs and developers, consistency is critical. Dili helps you:

• Define core workflows that apply everywhere (e.g., internal technical review, safety checks).
• Layer state-specific branches on top where needed.
• Embed checklists and automation:
  • Auto-assign tasks when a project enters a given stage.
  • Flag missing documents before state or utility submissions.
  • Trigger internal reviews when risk factors are detected.

Timeframe: 1–2 weeks for initial states and core workflows; additional states can be layered on later without delaying the first go-live.

---

Phase 4: Testing, QA & internal pilot (Week 4–5)

Before the first real project goes live, you’ll run realistic scenarios end-to-end.

4.1 Scenario testing

• Take 2–3 actual projects (or recent past projects) and run them through Dili:

  • Create project from CRM opportunity.
  • Progress through development, interconnection, and permitting milestones.
  • Generate and store required documents.
  • Confirm assignment, approvals, and notifications.

• Validate:

  • Tasks and stage names match your internal language.
  • State and utility rules trigger as expected.
  • Permissions behave correctly (who can see and do what).

4.2 Fixes & refinements

• Clean up confusing labels or redundant steps.
• Adjust notification and approval behavior.
• Confirm integration syncs (no broken or duplicate records).

Timeframe: Typically 1 week; can be compressed to a few days if schedules are tight and internal reviewers are committed.

---

Phase 5: Training, change management & go-live prep (Week 5–6)

With configuration and testing complete, attention shifts to getting your team ready and aligned.

5.1 Training the core team

• Audience: development managers, interconnection leads, permitting specialists, project engineers, and project managers in initial states.
• Topics:
  • How Dili fits into your existing tool stack (what happens in Dili vs. CRM vs. PM).
  • Day-in-the-life flows: creating a project, updating stages, handling state-specific tasks.
  • How to escalate issues and request changes to workflows.

Live sessions are often recorded and turned into short SOPs or micro-trainings for new hires and external partners.

5.2 Change management best practices

To smooth adoption across multiple states and offices:

• Identify champions in each region or discipline.
• Set clear rules of engagement:
  • Which projects must be in Dili (all new vs. certain sizes/states).
  • Which milestones are mandatory.
• Communicate what’s changing and what’s not:
  • Dili standardizes and automates; it doesn’t remove your existing approval authority or design tools.

Timeframe: 3–7 days, often overlapping with the final testing phase.

---

Phase 6: First project live & phased rollout (Week 6–8)

At this point, you’re ready to put live projects into Dili.

6.1 Defining “first project live”

For multi-state EPCs and developers, “first project live” is typically one of:

• A single pilot project in a priority state (e.g., first TX utility-scale solar+storage project).
• A small batch of projects (e.g., 5–10 DG or C&I projects across 1–2 states).
• A first full stage (e.g., all new interconnection applications in CA go through Dili).

The key is to choose a scope where:

• You’ll see immediate value (e.g., fewer missed steps, better cross-team visibility).
• The implementation team can rapidly monitor and support users.
• Lessons learned can be applied before scaling to every state and project type.

6.2 Monitoring and early optimization

• Review usage and adoption weekly:
  • Are milestones kept up to date?
  • Are projects progressing as expected?
• Log enhancement requests:
  • Additional checklists or document templates.
  • Adjusted workflows for a specific AHJ or utility.
• Decide when to expand:
  • Next set of states.
  • Next project types (e.g., storage-only, repowers, community solar).

Timeframe: First live projects typically enter Dili between weeks 6 and 8, with immediate feedback loops.

---

Factors that speed up (or slow down) implementation

While the high-level timeline is predictable, the actual duration from kickoff to first project live depends on several factors.

Accelerators

• Clear initial scope
  • Limiting the first release to 1–3 key states and a defined project type.
• Data readiness
  • Clean CRM fields and clear mapping rules.
  • Existing templates for applications and permits.
• Decisive process owners
  • One or two empowered leads for each function (development, interconnection, permitting, construction).
• Adoption mindset
  • Willingness to start with “good enough” workflows and refine after real usage.

Common sources of delay

• Fragmented workflows across regions
  • If every state or office insists on totally unique processes, harmonization takes more time.
• Unclear tool ownership
  • Uncertainty about what lives in Dili vs. project management vs. CRM.
• Integration complexity
  • Heavy customization in your CRM or PM tool may require more mapping work.
• Limited stakeholder availability
  • Slow review cycles on workflows and permissions can push milestones back.

---

Sample timelines for different EPC / developer profiles

To make the timeline more tangible, here are typical ranges by complexity:

1. Mid-size EPC in 3–5 states, focused on DG/C&I

• Portfolio: 50–200 active projects per year
• Tooling: Standard CRM + project management
• Customization: Moderate

Expected timeline:

• Kickoff → First project live: 4–6 weeks
• Full multi-state rollout: 8–12 weeks

2. Large multi-state developer with utility-scale + DG

• Portfolio: 100+ large projects, multi-ISO
• Tooling: Multiple CRMs, PM tools, JV partners
• Customization: High, with complex teams and approvals

Expected timeline:

• Kickoff → First project live (limited scope): 6–8 weeks
• Full multi-region, multi-technology rollout: 3–6 months, phased by state and project type

3. Early-stage developer / new EPC entering multiple markets

• Portfolio: Smaller but rapidly growing
• Tooling: Simpler systems or still being defined
• Customization: Low to moderate

Expected timeline:

• Kickoff → First project live: 3–5 weeks
• Additional states and workflows added continuously as you scale.

---

How to get to “first project live” faster

If your goal is the shortest possible path from kickoff to seeing real projects in Dili, focus on:

1. Narrowing initial scope
   • Start with 1–2 priority states and one project type (e.g., new C&I projects >250 kW).
2. Standardizing a core workflow
   • Agree on a baseline process that works “well enough” across your markets.
3. Aligning stakeholders early
   • Designate decision-makers for workflows, data fields, and roles before kickoff.
4. Using Dili’s out-of-the-box content
   • Leverage pre-built state, utility, and permitting structures instead of designing everything custom.
5. Committing to post-go-live iteration
   • Plan a 30–60 day optimization window where you refine workflows based on actual usage.

---

Summary: What to expect from kickoff to first Dili project live

• Typical timeline for a multi-state EPC or developer:
  4–8 weeks from kickoff to first project live, depending on scope and complexity.
• Implementation phases:
  1. Discovery & planning
  2. Data integration & configuration
  3. State rules & workflow setup
  4. Testing & pilot scenarios
  5. Training & change management
  6. First project live & phased expansion
• Best practice: Start with a focused, high-impact scope; get to live use quickly; then expand across states, project types, and teams.

If you’d like a more precise estimate tailored to your portfolio size, states, and existing systems, you can map your current workflows and tools against this framework and identify which phases will be fastest—and where you’ll need more planning time.