Leat, the full simulation.
An early-stage company developing community solar gardens and storage batteries, whose interconnection filings lag behind construction schedules. The case followed on this page, the grid connection study for a Rice County solar garden, received on a Thursday with fifteen days to respond.
An early-stage company developing community solar gardens and storage batteries, whose interconnection filings lag behind construction schedules.
Every interconnection filing complete ahead of deadline.
- Leat was founded by two former grid operator engineers. The Minneapolis-based company develops community solar gardens, which local residents subscribe to in order to lower electricity bills, alongside grid-connected batteries. It employs eighteen people with around twenty projects under development across Minnesota.
- Every project requires an interconnection application with the grid operator, involving engineering studies and strict milestones. In the United States, the median time between application and commercial operation was over five years for plants completed in 2025.
- Following a 2023 statute, new Minnesota community solar gardens fall under a state Department of Commerce programme reserving at least 30% of each garden for low- to moderate-income households. The two founders spend their evenings tracking deadlines across spreadsheets.
- An agent tracks each interconnection application from initial filing to agreement, managing deadlines and utility inquiries. It reviews technical studies as they arrive and summarises required network upgrades for the engineering team.
- Ahead of each milestone, it compiles required submittal documents and flags missing items. The lead engineer reviews every document and signs off on every submission.
What remains with the engineers
Engineers sign every formal application and response to the utility, and the founders decide whether to advance or drop a project following each study. The agent submits nothing on its own.
- Deadlines met
- Applications complete on first submission
- Response time to utility inquiries
- Engineer time spent on administrative filings
Community solar subscriber management
Low-income households that subscribe provide proof of income. The agent checks that each file is complete and answers subscriber enquiries.
The subscriber team approves each registration.
Land leases
Each solar garden is installed on land leased from a farmer or a municipality. The agent tracks lease deadlines and prepares correspondence.
The founders negotiate each lease.
Local zoning and permits
The agent gathers permit documentation for each county and tracks the accompanying public meetings.
The lead engineer submits each permit application.
Battery asset performance
Once the batteries are in service, the agent monitors their alarms and state of charge, then prepares reports for the grid operator.
The operator decides on each intervention.
the grid connection study for a Rice County solar garden, received on a Thursday with fifteen days to respond
A grid connection study received on a Thursday, before and after.
- The study
- The study arrives by email, and nobody has time to read it before the weekend.
- The agent summarises the study within the hour, including the required grid works.
- First workstream
- The deadline
- The deadline is logged in a spreadsheet, among dozens of others.
- The agent reminds the lead engineer of the deadline, along with what is missing.
- First workstream
- The missing document
- The landowner certificate is missing the day before submission.
- The agent flags the missing document two weeks prior, and the engineer follows up with the owner.
- First workstream
- The submission
- The file is submitted incomplete, and the grid operator returns it.
- The engineer signs off a complete file, prepared by the agent.
- First workstream
- The subscriber
- A subscriber family submits an incomplete income certificate, and enrolment stalls.
- The agent spots the missing document and replies to the family.
- Workstream 2
- The lease
- A land lease expires without anyone noticing in advance.
- The agent alerts the founders six months before expiry.
- Workstream 3
- Receive
- It receives every letter and study from the grid operator.
- Summarise
- It summarises each study, including the requested works and their timescales.
- The engineer reviews each summary.
- Track deadlines
- It maintains the schedule for each file, from application to approval.
- Remind
- It reminds the lead engineer of each deadline, along with what is missing.
- Prepare the submission
- It prepares the documents to be submitted and checks that they are complete.
- The lead engineer signs off each submission.
- Answer questions
- It drafts responses to questions from the grid operator.
- The engineer reviews and sends each response.
- Archive
- It files each document into the project folder.
- Report
- It prepares a weekly update on upcoming deadlines and blocked files.
- Grid connection inbox
- Letters and studies from the grid operator.
- Read-only
- Grid operator portal
- The status of each connection request.
- Read-only
- Project folders
- Land plans and leases.
- Read and document preparation
- Deadline calendar
- Deadlines for each file.
- Write
- Team messaging
- Reminders sent to engineers.
- Sending reminders
- Founders
- Set the agent rules with us and decide whether to proceed with or abandon each project.
- Lead connection engineer
- Signs off each submission and each response to the grid operator.
- Subscriber team
- Recruits and enrols subscribers for the solar gardens.
- Land officer
- Negotiates leases with farmers and local councils.
- FDE
- Leads the engagement and writes the agent rules with the team. Accountable for each agent.
- Deadline agent
- Maintains the schedule for each file and sends deadline reminders.
- Reading agent
- Summarises studies and correspondence from the grid operator.
- Submission agent
- Prepares documents for each submission and flags anything missing.
- Quality check agent
- Checks a sample of summaries each week and reports any recurring errors to the FDE.
- A deadline is missed.
- Each deadline is reminded twice, and the lead engineer has full visibility of the schedule.
- A study summary misses a required piece of work.
- Each summary links back to the pages of the study, and the engineer reviews the full study before signing off.
- The agent submits a file autonomously.
- It has no write access to the grid operator portal. Only the engineer submits.
- Subscriber data is leaked.
- Income certificates remain in a restricted area for the subscriber team, and every access is logged.
- A subscriber feels pressured to sign.
- The agent answers questions without ever applying pressure, and only the subscriber team enrols each family.
- We measure the baseline over one month, including deadlines met, returned files, query turnaround times and time spent by engineers. The lead engineer drafts the tracking rules with us.
- The agent tracks files in parallel with the team for two weeks, and we compare its schedule with the spreadsheet.
- Engineers rely on the agent reminders and summaries for all files.
- We compare against the baseline and select the next workstream with the founders.
- Deadlines met
- Share of deadlines met, compared with the baseline month.
- Files complete on first submission
- Share of submissions accepted without requests for additional information.
- Turnaround time for grid operator queries
- Time elapsed between receiving a query and sending the response.
- Engineer time spent on files
- Hours logged each week, compared with the baseline month.