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
Permit Agent
Owns AHJ communication, permit status tracking, revision parsing, and expiry warnings.
Field Agent
Owns crew check-ins, document intake, photo logging, and site blocker surfacing.
Ops Supervisor
Owns weekly digests, portfolio risk flagging, and milestone readiness reporting.
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