Gutter cleaning busy season with one crew: an illustrative October week.

A one-crew gutter company in October has more work than days. Cleanings are modest per visit and come due in their hundreds; installs are few and worth far more; both need the same truck, ladders and people. Supervised AI assistants can keep the week's paperwork moving around that conflict: reminder drafts, quote drafts, the photo record and a single board of what is due. The split of crew days, the order of work after a storm and every question about a roof edge stay with the owner.

What follows is one illustrative week. Treat it as a sketch of how the work could be arranged: no real company and no measured result stands behind it.

In this illustration the owner measures, quotes and climbs; two crew members clean and help on installs; the company tows one seamless machine on a trailer. Going into the week, about two hundred cleaning recalls are due, three install quotes are waiting to be measured or written, and the forecast shows wind and rain arriving on Thursday.

The One-Man Army idea, which the pillar article explains, is that the owner holds every decision while each recurring desk job goes to its own named AI assistant. In this company that means four Bots the owner set up: Recalls, Quotes, Job Record, and a Coordinator that posts the week's board.

Grok Bot's documentation describes Bots that share one persistent cloud computer, send each other asynchronous requests, and work together in a group chat where a coordinating Bot can hand out work. Cursor's help pages say no switch turns off messaging between Bots; a Bot follows instructions about it. A coordinator that supervises the others is not a product feature: it is Aevrion's pattern, assembled from the group chat and those Bot-to-Bot messages.

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 Monday-morning routine on the Coordinator reads the recall list and the quote drafts the other Bots keep in the shared /workspace, and the forecast note the owner pasted in on Sunday, then posts the week's board to the group. The board is a proposal. It says what is due, not what should happen.

Before anything on the board below moves, the owner makes the week's real decision: how to spend five crew days. Every day given to an install is a full day of cleanings that slides into next week; every week an install waits is a week the homeowner might ask another company. No rule a Bot remembers can weigh that, because it turns on cash, on which customers have been loyal, and on how the owner reads the sky. In this illustration the owner gives Monday to the first cluster, Tuesday morning to measuring and the afternoon to a short route, Wednesday and Friday to the largest clusters, and keeps Thursday open.

Monday's board, as the owner reads it before the crew arrives (illustrative):

• CLEANINGS DUE

  About two hundred recalls, grouped into the neighborhoods the owner approved in September, largest groups first.

• QUOTE A: AFTER A NEW ROOF

  A roofer finished a re-roof last week and passed the homeowner on for new seamless gutters. The house has had none since the tear-off. Not yet measured.

• QUOTE B: GUARDS

  A cleaning customer asked for a gutter guard quote after a second blocked downspout. Measured last month; the draft is waiting for prices.

• QUOTE C: A FAILED RUN

  A home-inspection report flagged a back run pulling away from the fascia. The owner has not seen it yet.

• THURSDAY

  Wind and rain forecast. No ladder work is planned; the owner decides on Wednesday evening.

• DRAFTS WAITING

  Reminder drafts for the first neighborhood group, waiting for the owner in the Recalls Bot's thread.

On Tuesday the owner measures Quote A and Quote C before lunch, dictating notes and photographing every elevation. The notes go to the Quotes Bot as text; the photos go to it from the owner directly, because handoffs posted to a group are currently text-only. By evening the Quotes Bot has drafted both in the company's layout: run lengths, corners, outlets, downspouts, hangers, guards as an option and removal of the old system, each line priced from the owner's current sheet rather than from anything it remembers. The owner sends Quote A that night, because that household is living under a new roof with no gutters.

Quote C is where the week's first boundary shows. The photos suggest the run pulled away because the fascia board behind it has gone soft. The Quotes Bot leaves the fascia line empty and puts a question at the top of the draft: repair the board as part of the install, price it as a change order, or ask a roofer to see it first. That is the owner's choice. A rotted board at the roof edge can be a roof problem, and this company's written rule sends anything that might be the roofer's to the owner, with a referral note prepared and not sent.

Quote B, the guard quote, needs only prices. The draft lists the guard the owner chose, the linear feet from last month's measure and a note that the customer's cleaning recall should be reviewed once guards are fitted. Whether guards suit that roofline is a judgment the owner makes on site, not one the draft offers.

Wednesday is a route day through the largest neighborhood group. Each visit produces before and after photos and, now and then, a defect: a leaking seam, a missing hanger, an end cap letting go. The crew show the owner their photos at the truck, and the owner forwards them to the Job Record Bot in its own conversation, because the Bots belong to the owner's account and a crew member's phone has no line to them.

The Job Record Bot files each set against the customer and lists the defects for the owner. A defect is not a quote. Some become a note to the customer, some a spring install conversation, and some nothing; the owner decides which. Any note to a customer is a draft that lands in the owner's one-to-one thread with that Bot, and only the owner reviews and sends it. A crew member may be asked what they saw. They never send the draft.

Ladder discipline belongs to the people on site, not to software. OSHA's ladder standard for construction, 29 CFR 1926.1053 (as checked on 15 October 2026), places duties on employers, among them that a competent person inspect ladders at regular intervals and after any incident that might affect safe use, and that a defective portable ladder be marked or tagged and kept out of service until repaired. Whether a cleaning visit is construction work is for the owner to confirm, and in a state that runs an OSHA-approved state plan, that plan's rules apply. On Wednesday evening the Job Record Bot's list shows the extension ladder a crew member tagged out after its foot slid on a wet patio. The Bot records the tag; the ladder stays out of service until it is repaired, and the owner, not a Bot, returns it to use.

On Wednesday evening the owner reads the forecast again and makes the call: no ladders on Thursday. That is a safety decision, and no assistant makes it or leans on it. The Recalls Bot drafts new-date notices for Thursday's customers, and the owner sends them before bed.

The storm threatens the install side too. Quote A came back signed that afternoon, and the household with the new roof asks whether the gutters can go up before the next rain. Friday is the first dry day, and it cannot carry everything. Given to the install, it pushes Thursday's postponed cleanings and Friday's own cluster into next week; given to cleanings, it leaves the new roof shedding water off bare eaves for another week. The Coordinator puts both versions of Friday on the board, with the visits each one moves. The owner chooses: the install takes Friday morning, Thursday's postponed visits take the afternoon, and Friday's planned cluster waits.

Thursday's visits and the requests the storm brings in go into the rebook queue the scheduling guide describes, and the owner orders it. This company does no storm repair or roof work, so the owner reads those requests personally and decides whether to point the homeowner to a roofer. The Job Record Bot only gathers what the homeowner sent.

On Friday morning the crew runs Quote A's gutters off the machine in the driveway and hangs them; the afternoon goes to Thursday's postponed visits, because the owner said so. Back at the yard the owner reviews the other two quote drafts, sends Quote B with the guards priced, and sends Quote C without the fascia line, because the owner has decided a roofer should look at the board first; with the homeowner's agreement, the owner sends the referral note the Job Record Bot prepared to a roofer the company trusts.

The board the Coordinator posts on Friday afternoon is the most useful of the week, because it shows the slip plainly: which neighborhood groups are now split across two weeks, how long the rebook queue still is, and which quotes are waiting on a homeowner. From that board the owner sets next week's split, and the cycle starts again on Monday.

The group chat is where the board and the handoffs are visible; it is not where decisions are made. Neither approval cards nor email drafts are shown in a group chat; they stay in each Bot's direct thread with the owner, and the board only points to them. Handoffs between Bots are visible too. When the Job Record Bot finds a defect on a cleaning customer's record, it passes a note to the Quotes Bot as a possible spring install, and the Quotes Bot owns it from there. The documentation advises a single owner at each stage, because too many parallel handoffs can create duplicate work.

By the end of the month the slipped clusters are the first November routes, the rebook queue is empty, and the fascia job waits on the roofer. Quote A's household now has gutters and joins the spring recall list, so the install has already become a cleaning customer. The guard customer from Monday's board has asked to wait for spring, and the Quotes Bot already holds the note.

For a gutter company heading into its own October, the readiness assessment is free and needs no sign-up. Score one workflow in it, the recall-and-rebook week, against its twelve dimensions; the verdict comes back immediately as one of four bands, alongside the blockers and a suggested next step, and exception frequency is the score to watch if storms reorder the season every year. Aevrion Ops can then map which crew-day decisions stay with you, which drafts the Bots should prepare, and which custom integrations to your scheduling software are possible, subject to what the vendor's API or terms permit and to testing.

1. In the gutter cleaning busy season the decision that matters is how crew days split between many modest cleanings and a few valuable installs, and it belongs to the owner.
2. A Coordinator can post a weekly board of recalls, quotes and the forecast; the board proposes and the owner decides.
3. Photos reach the Job Record Bot from the owner, sent directly rather than through the group, because group handoffs are currently text-only.
4. A storm threatens installs as well as cleanings: the owner decides which gets the first dry day, with the board showing what each choice moves.
5. Fascia rot and storm-damaged runs go to the owner, who decides whether a roofer should see them first.
6. Every customer draft waits in the owner's private thread with the Bot that wrote it, and the owner alone sends it.