AI for gutter companies: cleaning routes and install quotes, one office.

A gutter company that both cleans and installs sells two different things under one name. Cleaning is recurring, seasonal and modest per visit, so it pays only when the visits are grouped tightly. Installation is occasional and valuable: seamless runs measured in linear feet, a choice of profile and metal, and a quote that has to be right before coil goes through the machine on the driveway. The two share customers. A cleaning visit finds the sagging run that becomes next spring's install, and every new install ought to become a cleaning customer.

On both sides of that line the paperwork can be prepared by supervised AI assistants: the seasonal recall list, the install quote draft built from the owner's measurements, and the photo record of each visit. They do not choose between a ladder and roof access, decide which customers go first after a storm, price a job, tell a homeowner their fascia is sound, or decide whether a job needs a license.

Set the two side by side before deciding what an assistant should prepare. The descriptions below are common trade practice rather than regulation, and every company prices and schedules its own way.

The failure this trade is prone to is a quiet one. A cleaning crew notices a seam that drips or a run pulling off its hangers, the photo sits in somebody's camera roll, and the replacement is never quoted. Or a new install goes in and the homeowner is never added to the autumn recall. Both happen because cleanings and installs are tracked in different places, or in one place nobody reads across.

The remedy is a customer record that carries both histories: cleaning visits with their dates and defects, and any install with its run lengths, profile, guards and warranty. That record belongs in the company's own software or spreadsheet. Grok Bot's documentation is explicit that a Bot's recollection cannot replace the system of record, so an assistant reopens the list each time rather than recalling last month's version. Reading records held in field-service software is a custom integration, or supervised browser use where the vendor permits it, subject to testing; the simplest start is an export the owner attaches as a spreadsheet.

Grok Bot lets one user run several named Bots, each holding a single job in its own thread, on a persistent cloud computer, and they hand back drafts and files a person can review. Every Bot the owner runs uses that same computer, files and browser sign-ins included, so a customer export saved there is readable by every one of them; separate Bots are not a security boundary. Grok Bot has no phone line, so booking calls stay with whoever answers them now, and routine schedules must sit at least five minutes apart. The gutter roles below are Aevrion's design, not features the product ships with.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

A gutter company needs three desks covered before it needs more Bots. That follows the documentation's advice to begin with the fewest Bots that cover the work and to add a specialist only once a job has settled into a separate, steady role. The three are Bots the owner creates and names, each holding one desk; the roster is an Aevrion pattern, not a product feature.

• RECALLS AND SCHEDULING

  Builds the seasonal recall list from the customer export, proposes neighborhood groupings for the owner to approve, and drafts reminders the owner sends. The cleaning-scheduling guide in this series covers how that list is built.

• QUOTE PREP

  Turns the owner's measurements and notes into an install quote draft in the company's own layout, priced from the owner's current sheet.

• JOB RECORD

  Files before and after photos against the customer, lists the defects the crew pointed out, and keeps install close-out items such as the water test and warranty registration open until a person checks them off.

• ONE ROUTING RULE

  Bots belong to the owner's account, so the crew's photos reach the Job Record Bot through the owner, or through a shared cloud folder the owner connects as a custom integration. If the Bots later work in a group chat, handoffs posted there are currently text-only, and an image another Bot must inspect is sent to that Bot on its own.

In this illustration a homeowner whose old gutters are failing asks for a seamless system. The owner visits, measures and makes notes: run lengths on each elevation, inside and outside corners, the state of the fascia boards, whether there is drip edge, and where each downspout drops. The homeowner wants to compare a five-inch and a six-inch K-style system, with and without guards. One note is a question rather than a measurement: the back downspout would empty beside the neighbor's fence.

From those notes the Quote Prep Bot drafts the quote in the company's own layout. Every price is read from the owner's current sheet each time, and anything the sheet does not price, such as a copper half-round section, is named and left empty. The draft prices the back run but leaves the drop location open, with the choices the owner listed: extend the downspout, add an underground drain if the company offers one, or move the outlet to another corner. Choosing is the owner's call with the homeowner, because where the water lands can matter to the neighbor as much as to the house.

A soft fascia board is the owner's call too, as is any roofer referral; the October guide shows one. Storm repairs and roof-edge work belong to roofing, and Aevrion's roofing guide covers that side.

The quote reaches the homeowner only when the owner sends it. Chasing unsigned quotes is a separate workflow, and this page does not set one out.

Cleaning work arrives in waves, around leaf drop and again in spring in many areas, and a visit pays best when its neighbors are booked the same day. That makes the recall list a map problem as much as a calendar one. The Recalls Bot can draft neighborhood groupings from the export, but a grouping is a proposal, and the owner's local knowledge overrides it.

Weather adds another list: visits a storm postpones and the requests it brings in wait apart from the recall order, in an order the owner sets, and storm damage repair stays with a roofer. The scheduling guide in this series sets out how the recall list, the owner's corrections and the rebook queue are built, and the October guide follows one crew through the busiest week of the year.

Almost every gutter visit happens on a ladder or at the roof edge. For employers doing construction work, the US federal ladder standard, 29 CFR 1926.1053, sets duties that bear directly on this trade (as checked on 15 October 2026). Whether a given visit counts as construction work, and so which OSHA standard governs it, is for the owner to confirm. Some states run their own OSHA-approved state plan: California's, Cal/OSHA, covers most private-sector workers in that state, so a California company looks to Cal/OSHA's rules.

The assistant's part is small and useful. The Job Record Bot can keep a register of each ladder with its last inspection date and any tag-out a person recorded, and put an overdue one at the top of the morning list. It never decides that a ladder is fit to use, that a roof can be walked or that the wind is too strong. Those calls are made at the house, by the people climbing.

The federal duties that matter most on a gutter visit are these.

• REACHING A ROOF

  A portable ladder used to reach an upper landing extends at least three feet above it or, where it is too short, is secured at the top to a rigid support with a grasping device such as a grabrail.

• ANGLE

  A non-self-supporting ladder is set so that its foot is about a quarter of its working length out from the top support.

• FOOTING

  Ladders are used on stable, level surfaces unless secured against displacement, and not on slippery surfaces unless secured or fitted with slip-resistant feet.

• INSPECTION

  A competent person inspects ladders for visible defects periodically and after anything that could affect their safe use.

• DEFECTS

  A portable ladder with structural defects is marked as defective or tagged Do Not Use, and withdrawn from service until repaired.

Licensing for gutter installation varies by state, and this page describes only California. As checked on 15 October 2026, the Contractors State License Board's C-43 Sheet Metal Contractor classification describes a contractor who selects, cuts, shapes, fabricates and installs sheet metal, and names gutters and leaders among its examples.

California also has a minor-work exemption. A CSLB industry bulletin dated 31 December 2024 says that from 1 January 2025, Assembly Bill 2622 raised the limit for unlicensed minor work from five hundred dollars to one thousand dollars, on two conditions: the work must not need a permit of any kind, and the unlicensed person must not employ anyone on the project. If either condition fails, a license is required even below one thousand dollars. The bulletin adds that unlicensed individuals may advertise work up to that amount only if the advertisement says they are not licensed.

For a company that sends a crew, the second condition is the one that bites. None of this is legal advice: the owner confirms which license the company's work needs with the CSLB or a lawyer, and an assistant never decides it. What the Quote Prep Bot can do is add a line to every California install draft showing the classification the owner has recorded for that kind of work and whether the owner has marked the job as needing a permit, so no quote leaves without someone having looked.

Each row below pairs what an assistant can have ready with the person who decides. A recall routine that runs before the crew leaves the yard finishes as drafts on the owner's list; the cleaning-scheduling guide explains why a routine nobody is watching should ask for nothing.

Take the photos from last autumn's cleaning visits that show a defect, and check each one against the quotes sent since. Every defect without a quote is an install the company has already found and not sold, and the reason the Job Record Bot comes first.

Recalls or install quotes: either one is a single workflow the readiness assessment can score, free and ungated, against its twelve dimensions, returning a result, the blockers it found and a next step at once; rule clarity will score low if the storm order lives only in the owner's head. A scoping conversation with Aevrion Ops then covers the access, storm-order and referral rules the Bots must respect, the three-Bot roster and where each stops for approval, and any custom integration to the scheduling or field-service software already in use, within what each vendor's API or terms allow and only after testing.

1. A gutter company is two businesses, seasonal cleanings and linear-foot installs, and its back office has to run both from a single customer list.
2. Three Bots are enough to begin: recalls and scheduling, install quote preparation, and the job record.
3. Install quote drafts come from the owner's measurements and current price sheet; where a downspout should drain and any fascia problem are flagged, and the owner decides them, including any roofer referral.
4. OSHA's construction ladder standard sets employer duties on extension, angle, footing, inspection and defective ladders; the assistant tracks inspection dates and never judges access.
5. In California the CSLB's C-43 Sheet Metal classification names gutters and leaders, and the one-thousand-dollar minor-work exemption does not cover permitted work or anyone who employs a helper.
6. Access, visit order, prices, referrals, licenses and every customer message stay with the owner; the assistants prepare registers, queues and drafts.