Skip to content
flylabs.ai
HomeWorkServicesProductsStack
IT (italiano)/EN (English)
Let's talk
← All work
Solar installer

Grid-connection paperwork that fills itself in

Claude CodePlaywrightZoho CRMGitHub ActionsPython
5 min
per request, down from 45 min on average

The problem

Grid-connection applications filled in by hand on the operator's portal, one at a time.

The solution

An AI system fills them in on its own: the operator types the client's name and the system does the rest.

Architecture diagram: the operator types the client's name, AI runs a preflight on the data, a deterministic bot fills the portal and signs the forms, an automated check validates and the request is submitted to the operator with writeback to the CRM(opens in a new tab)
The architecture: from the client's name to a submitted request, automaticallyTap to enlarge

How it went

Every solar system sold opens a grid-connection request on the operator's portal: personal, technical and document data to be re-entered by hand from the CRM, with delicate checks on identifiers, meter data and system capacities. Expert, repetitive work with a real risk of error.

We built a system that handles the request on its own, with no servers or webhooks: the operator types the client's name and the rest happens automatically.

Before touching the portal, the system runs a preflight on the data: it re-reads the CRM fields and the attached documents with a language model, validates the critical data with consistency checks, and stops if anything is missing or unreadable: better to stop than to guess. Then a deterministic bot fills the portal step by step, uploads the attachments and signs the forms with the company stamp. An automated check validates the result and, only after the client had verified the first signed requests, submission to the operator happens without a per-request human sign-off. Finally the system writes the status and the signed document back to the CRM.

There's also a part that makes the system sturdier over time: every hiccup becomes a tracked incident and every fix a dated, preserved note, so the same errors don't happen twice.

Got a similar process?

Tell us about it in a couple of lines: in the first call, which is free, we'll tell you whether and how it can be done. If it can't, we'll say so.

Let's talk →Next case · Always-fresh ad creatives, without autopilot →
flylabs.ai

Practical AI, built around your work. Then you run it.

HomeWorkServicesProductsStackPrivacyCookie policyinfo@flylabs.ai
© 2026 flylabs.ai
Cesare Bedin (LinkedIn) · VAT no. 05755090288Federico De Cillia (LinkedIn) · VAT no. IT13990330964