opsforenergy
Use Case

Solar EPC

A 15-project solar EPC spends an estimated 23 hours/week on permit follow-up, document intake, and subcontractor coordination. None of that work requires human judgment. All of it eats PM time.

The Agent System

One agent layer handles the full coordination loop: permit tracking, field updates, document intake, subcontractor follow-up, and weekly reporting. It wakes on scheduled heartbeats, reads incoming emails and SMS, classifies and parses them, queries Supabase for project context, acts based on predefined rules, and notifies the PM channel via Telegram. When confidence is low, it surfaces the item to a human for approval before proceeding.

The Workflow

1
Email arrives
AHJ, subcontractor, or crew sends an update to the agent inbox.
2
Agent wakes
Heartbeat triggers the agent to check its inbox (2hr for permits, 4hr for field).
3
Classifies
The agent parses the email, identifies the type, and extracts key details.
4
Queries Supabase
The agent looks up the project, permit, or milestone to match the update.
5
Acts
Logs the update, changes status, or flags a risk based on predefined rules.
6
Notifies
Sends a concise Telegram message to the PM channel with the action taken.

Proof Point

~23
hours/week saved
100+
emails processed/week
15
active permits tracked

*Numbers are estimated based on a mid-size solar EPC running 12–18 active projects. Actual savings depend on inbox volume and workflow maturity.

Tech Stack

PaperclipAgentMailSupabaseTelegramClaude Sonnet 4
Want to see this in action? Here's the demo →