Let the Agent Chase the Paperwork
The move in short
Agent — a scheduled agent that checks permit portals, subcontractor inboxes, and the grid operator's status page each morning, then posts a plain summary of every job's blockers to the delivery channel before anyone arrives at the office
The Company
Aurinko Asennus Oy installs solar panels and small battery systems for commercial buildings — warehouses, light industrial units, a few large farms — across Pirkanmaa and the surrounding region. They've got about 25 people: a handful of engineers, installation crews, a couple of project managers, and a small back office. Jobs range from a 20-panel roof on a logistics shed to a 200-panel system on a food processing plant. Every single one has a different permit route, a different grid operator contact, and a different subcontractor doing the electrical work.
The Pain
Marika is the head of delivery. She manages eight to twelve active installations at any point, and a big chunk of her afternoons disappear into checking things that haven't moved. She's logging into the regional permit portal to see if an approval came through. She's scanning her inbox for a reply from the grid operator in Valkeakoski. She's messaging a subcontractor to ask if their part of the job is booked in. None of it is hard, but all of it is slow, and it's happening every single day across every active job. If she misses something, the crew shows up and there's nothing to do. That's a wasted day and an annoyed customer.
The Move
Aurinko Asennus could set up a scheduled agent — something like Lindy or a Make scenario with an AI step in the middle — that runs automatically each morning at 7am. It logs into the permit portal, reads the status on each open application, checks for new emails from the grid operator addresses they've added to a watched list, and pings the subcontractor booking system they already use. Then it pulls all of that together and posts one plain message to their Slack delivery channel: job by job, what's confirmed, what's still waiting, and what's been sitting without movement for more than three days.
Marika walks in, reads it in five minutes, and knows exactly where to spend her energy. She's not digging through tabs. She's calling the one contact who's actually holding things up.
The blind spot
Everyone assumes this kind of setup needs a developer to build it. It doesn't, not anymore. The permit portal login, the email scanning, the Slack message — these are all things you can wire together in Make or a similar tool with an AI agent step in the middle. It takes an afternoon to set up, not a sprint.
The pattern
The same move fits wherever one person is manually checking the same scattered sources every day:
- A construction site manager checking three subcontractor WhatsApp threads and a weather service before deciding whether to send crews out
- A procurement lead checking supplier lead-time pages and an ERP for stock levels every Monday morning
- A service manager tracking open support tickets across email, a portal, and a shared spreadsheet before the weekly call