The one-person handyman company: twelve small jobs a week, one desk.

Two days on one repair and a dozen one-hour fixes can fill the same week. They do not cost the same at the desk. Every small job needs its own scope, its own screen against the owner's license rules, its own slot, its own materials and its own invoice, and a landlord with six units sends six of each with six different tenants to work around. For a one-person handyman company that desk time comes out of evenings, or out of the next morning's first job.

This article follows one illustrative week in California for a handyman who works alone. It shows which pieces of that admin a small set of AI assistants can prepare, and which stay with the owner. Nothing in it describes a real company, and no outcome is claimed for it.

Every visit in this sketch is done by the owner, and nobody else touches the desk. The week's work arrives from four directions, each with its own kind of paperwork.

The obvious way to take on more small jobs is to bring someone along. In California, that step changes the legal footing of the business. The Contractors State License Board's bulletin on Assembly Bill 2622 (as checked on 15 October 2026) is explicit that the minor-work exemption from licensing does not survive hiring help: an unlicensed person who employs even one worker on a project needs a license, however small the project. So the owner in this illustration either stays alone or takes the license decision first, with the board or a lawyer. The license-limit screening article in this series covers the rest of the rule.

Staying alone means the desk has to shrink instead. Aevrion's One-Man Army model gives every recurring kind of desk work its own named assistant and leaves the decisions with the owner; the pillar article sets it out. Here it is built on Grok Bot: the Bots below are ones the owner creates under Aevrion's design, each with a defined job, all working on one persistent cloud computer that the owner's account provides.

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.

The documentation suggests the smallest roster that works, adding a Bot only when a role is stable. Four is the most this week justifies, and the owner would start with the first one alone.

• LISTS BOT

  Turns every list, punch list and work order into one card per task with its photo, and runs the owner's license and paint screen over each card.

• ACCESS BOT

  Lays the week's visits out against the tenants' windows, the agent's deadline and the homeowners' preferences, and drafts confirmations for the owner to send.

• MATERIALS BOT

  Drafts a materials list per visit from the cards, grouped into one shop run where it can be, with customer-supplied parts marked.

• INVOICE BOT

  Matches completion photos to lines and drafts each invoice in the form the customer needs, including the landlord's order numbers.

The landlord emails six orders on Monday: a dripping kitchen tap in one unit, a closet door off its track in another, a cracked switch plate, a loose stair handrail, a bathroom door that binds, and blinds to replace. The landlord also passes on when each tenant has agreed to be in or to allow entry. Arranging entry sits between the landlord and the tenant, and the Access Bot treats each window as a fixed fact, not something to negotiate.

The Lists Bot builds one card per order and screens it. The tap is plumbing and the switch plate sits on an electrical fitting, so both are flagged against the owner's rules and wait for the owner, who decides whether to refer them to licensed trades or handle them in a way the owner has confirmed is within the rules. The Access Bot then proposes a route through the building that respects every window and drafts one confirmation per tenant window for the landlord. None of them leaves until the owner reads it and presses Send.

The landlord's building dates from the 1960s. EPA's page on the Renovation, Repair and Painting rule (as checked on 15 October 2026) says anyone paid to do work that disturbs painted surfaces in a home built before 1978 must hold the firm certification EPA requires and use workers trained in lead-safe practices, and that the rule applies to a home that is rented out. The same page notes that a tenant's landlord or property manager must comply when work disturbs paint. California is not on the page's list of states that run their own program, so EPA administers it there.

So the screen carries a second flag. Planing the binding bathroom door, easing the sticking closet track if it means scraping the frame, or any patch-and-paint on the walls is marked for the owner with the building's year beside it. The owner decides whether the business holds the credential and runs the job under the rule, or refers it. The records and timing that go with that decision belong to the painting article on RRP records, which this site keeps for the purpose; the handyman's screen only raises the flag.

The agent's list has fourteen lines, from touch-up paint to a dead outdoor light. It has a fixed end: the day the listing photos are taken. The Lists Bot cards it, the screen flags the outdoor light as electrical and the touch-up lines with the house's year, and the Access Bot works back from the photo date to propose visits the owner can actually fit.

The Materials Bot then drafts one list for the clear lines, grouped by shop and by whether the seller has paint left over. Buying is the owner's step: the documentation recommends an approval boundary for purchases, and a payment screen is something the owner completes by taking over the Bot's computer. Cursor's help pages add that a card saved in the Bot's Vault can be used at checkout without asking each time, so this design saves no card there. Lines the owner refers out are drafted as a short note to the agent saying which trade they need, which the owner reviews and sends.

One homeowner sent photos; the other sent a paragraph. The first list goes straight to cards. For the second, the Lists Bot drafts one message asking for a photo per task and the few facts each card is missing, and the owner sends it. Neither list is planned or priced until its cards are complete, which is the rule that stops a one-hour visit becoming three.

The three single calls go through the same route in miniature. On their own they are barely worth the desk time; folded into visits already booked nearby, the Access Bot can propose them as stops on the way, for the owner to confirm with each customer.

A group chat holds all four Bots (the documentation permits two to six), and the Lists Bot posts each finished card set there so the Access and Materials Bots can pick it up. The documentation describes a coordinator in a group being able to assign work; in this week the owner plays that part, because four Bots do not need a supervisor. A supervising Bot over the others would be Aevrion's own pattern, not a documented feature.

The week also runs inside what the documentation says about groups. Email drafts and approval requests do not appear in a group, so every tenant confirmation and invoice is reviewed in the owning Bot's own conversation. Handoffs posted to a group are text only, so completion photos go from the owner to the Invoice Bot, or from Bot to Bot, rather than through the group. And the Bots can write to each other directly; Cursor's help pages say no switch turns that off.

The photo-to-line matching is the same rule the handyman money page describes. What this landlord adds is the shape of the paperwork. In the illustration the landlord wants one invoice per order, so each unit's costs land against the right unit, and the Invoice Bot drafts six: the closet track, the handrail and the blinds as done with their photos; the kitchen tap and the switch plate as referred, naming the trade the owner chose; the binding bathroom door held back until the owner has settled the paint question. Prices come from the owner's rate sheet, read every time; the documentation says changing facts belong in the source system, not in what a Bot recalls.

Each invoice waits in the Invoice Bot's conversation as an editable draft until the owner sends it. The homeowner, agent and single-call invoices follow the same route with simpler formats. If the owner asks for them late in the evening, they simply sit in that conversation as drafts until the morning; nothing goes to the landlord until the owner presses Send.

A week like this leaves useful evidence behind. Actual times per task type go into the owner's job log, which is where the next visit's estimate comes from. Any tenant window that failed goes back to the landlord as a note. Any line the screen should have flagged and did not becomes a new line in the owner's rule file. Each of those is the owner's change, written into a file the Bots read, rather than something a Bot is expected to remember.

If the landlord's orders are the heaviest part of the week, that is the workflow to score in Aevrion's workflow automation readiness assessment: one workflow, from a work order arriving to an invoice the landlord can match. The assessment is free and ungated, rates it on twelve fixed dimensions and returns a score, one of four results, the blockers and a next step. Ownership clarity may come out low if access confirmations are split between the landlord and the owner, and a low score there caps the result. Once that is clear, Aevrion Ops can scope the four Bots and any link to the landlord's system, which would be custom integration or supervised browser use where the vendor permits it, subject to testing.

1. For a handyman working alone, desk time grows with the number of jobs, and a landlord's units each count as a job.
2. In California, as checked on 15 October 2026, hiring even one worker on a project ends the unlicensed minor-work exemption, so a helper is a license decision first.
3. Four Bots at most: lists and screening, access, materials and invoices, with the owner deciding every flag, price, purchase and send.
4. Pre-1978 buildings add a paint flag to tasks that disturb painted surfaces; the owner decides how the RRP rule is met or refers the work.
5. Group chats carry the plan, while drafts, approvals and photos move through each Bot's own conversation or from Bot to Bot.
6. Invoices for a landlord are built around the order numbers and a completion photo per line, and wait as drafts until the owner sends them.