Opening a second state: one AHJ and interconnection workflow across territories

Opening a second state is the expansion move that looks like a sales decision and is actually an operations decision. Of the 105 US install businesses we reviewed in October 2026, 29 were visibly expanding into a new state, office or territory. The solar install businesses that make it work are the ones that treat it as a process migration, not a marketing launch. The ones that struggle rarely struggle because there wasn't demand. They struggle because the second state quietly became a second company: its own licensing, its own permitting queues, its own utility interconnection processes, and eventually its own spreadsheet.

The goal of this guide is narrower than "how to expand": it's how to open a second state without splitting your workflow in two. One process, tagged by state, instead of two processes that the office has to reconcile by memory.

The three gates that don't travel with you

Three things that worked in your home state do not transfer, and each needs its own setup:

Licensing sits with each state. There is no national electrical contractor license that travels across state lines. Most states license contractors themselves, with their own requirements, exams, bonds and insurance rules; some, like New York, leave it to the city or county. Before you quote a single job across the line, you need to know exactly which license the new state requires, how long it takes, and what it costs. This is the longest lead-time item in the whole expansion, so it goes first.

Permitting sits with each AHJ. City, county or utility, whichever authority covers the job site. The variance between them is enormous: NREL's SolarAPP+ performance review measured a 7-business-day median for traditional manual permit review, with 13% of permits taking more than 30 business days, against instant approval in jurisdictions running automated review. At the end of 2023, 97 jurisdictions had fully adopted SolarAPP+ and another 70 were piloting it, out of the thousands of local authorities in the country. Your second state can have a completely different mix of fast and slow AHJs, and so can your first. We've covered what that permitting variance costs separately, because it's its own operational problem.

Interconnection sits with each utility. Permission to operate comes from the utility whose grid the system connects to, and every utility runs its own application process, portal, forms and queue. If your first state is dominated by one or two utilities, your second state's utilities will have different rules on system size thresholds and what counts as a modified versus new application. Your ops team has to track a different PTO clock for each, with the compliance trail on the job record rather than in the portal alone.

None of these are reasons not to expand. They're the reason the expansion is an operations project with a sales plan attached, not the other way around.

The failure mode: two states, two systems

What usually happens is organic and starts small. The first few jobs in the new state get run through the same process as everything else. Then someone notices the new AHJ's forms don't fit, so they get their own folder. Then the new utility's portal logins live in the ops manager's browser instead of a shared password manager, and the portal links never make it onto the job. Six months in, nobody in the office can answer "where is this job" without first asking "which state is it in", because that determines which spreadsheet to open.

At that point the business is running two workflows, and every coordination cost it was absorbing in one state is now being paid twice. This is the same pattern that pushes growing install businesses off generic CRMs: the tool can hold a contact but not the actual shape of the job, so the real process runs somewhere else, one state at a time.

The alternative is one workflow with state as an attribute of the job, not the organizing principle of the business.

One workflow, tagged by state

Set up the second state as new values on existing structure, not as new structure:

• Jobs carry a state and an AHJ. Every job in either state lives in one operations queue, tagged by state and AHJ, so you can filter by tag. The office answers "where is this job" the same way for both territories.
• Permitting rules live on the job, not in heads. When a job's AHJ requires an engineer's stamp above a certain system size, or a particular form, that's recorded against the jobs it affects. If your target states run automated permitting, submissions go through the same record either way.
• Interconnection tracking is a stage, not a side channel. Application submitted, approved, PTO granted, each with a date on the job record. The PTO clock is visible next to the permit clock and the install date, not in the utility's portal alone.
• One set of document templates, producing permit packages and contracts per state from the same job data. Different requirements, same system.
• Automations keyed to status changes, not to states. A permit approved in either state notifies the crew and opens scheduling. A job sitting at the same stage too long flags itself, whichever side of the line it's on.
• The field sees the same job record through the mobile app, whichever state the roof is in. Crews don't care about the line, they care that the job details, documents and schedule changes are in one place on the day.

The test for whether this is working: an ops person should be able to work the Monday queue without knowing which state each job is in until the state matters for that specific step. If state determines how they find the job, the system is wrong.

Before you open: the checklist

In order, because the lead times force it:

1. State license. Requirements, exam, bond, insurance. Longest lead time, starts first.
2. Map the AHJs you'll actually hit. Not every authority in the state, the ones covering the metro area or region you're targeting. For each: portal, forms, whether it runs automated review, and any size thresholds that trigger extra requirements.
3. Map the utilities. Interconnection application process, portal links and references on the jobs (logins in a shared password manager), and the rules that affect quoting (net metering treatment, size caps, what a battery addition means for an existing agreement).
4. Set up the job structure. State and AHJ fields, interconnection stages, document templates per state, in whatever runs your operations today. If your current setup can't hold two states in one workflow, that gap is the expansion's real cost. It's worth comparing the CRM options install businesses actually use before committing the second state to it.
5. Quote the second state honestly. Sales promises should be built on the new state's permitting and interconnection timelines, not extrapolated from the first. A two-week promise carried across a state line is how new-market reviews start mentioning communication gaps.

Don't expand the process into a copy

The temptation in month three is to hire a coordinator for the new state and let them build the process they're used to. Resist it. You want one process owner and one workflow, with state as data. Two coordinators running two workflows means every cross-state question (and there will be more than you expect, because crews and inventory don't respect the line) becomes a meeting.

If the expansion is on your roadmap for next year, where US demand is heading is worth a read alongside this. The states adding installs fastest are also the ones where your second-state workflow will be stress-tested hardest.

One workflow, two states, state as a field. That's the whole discipline. If you want to see what that looks like in practice for a business your size, request a demo and we'll walk through it against your states and utilities.