AI for companies that waterproof basements: storm surges and service plans.

A basement waterproofing company does not get its work evenly. A wet week, a cloudburst or a thaw brings a burst of inquiries all at once: water at the floor-wall joint, a pump that stopped, a damp smell, a corner of drywall that has gone dark. Months later the same company is running something quieter, a base of sump service plans whose visits, records and reminders have to happen whether or not it rained. The surge sells the systems; the service base keeps the customers. An AI back office in this trade is judged on whether it helps with both.

On both sides the assistants' part is preparation: triage cards during the surge, proposal drafts after the inspection, a note on where each sump is allowed to discharge, and the reminder list for the service plans. They do not answer the phone, diagnose where the water is coming from, make statements about mold, set a price or tell a homeowner that a discharge line is legal. Those decisions stay with the owner, the inspector and, where a rule needs one, a licensed plumber or the municipality.

A waterproofing owner already feels the difference between the two halves of the business; it helps to write it down before deciding what an assistant should do. The surge is a sorting problem: many inquiries, mixed urgency, and an owner who can only inspect so many basements in a day. The service base is a memory problem: every installed pump, every warranty, every annual visit and every discharge line, held for years and acted on at the right time. The same assistants can serve both, but the work they prepare is different.

Consider, as an illustration, a waterproofing company with an owner who carries out every inspection, two install crews and an office that is one person on weekdays. Three days of late-summer thunderstorms leave the inbox full: web forms, answering-service notes, emails with phone photos of puddles (brought to the triage Bot's folder by a custom integration, tested first). The owner's written rule ranks them; the snowmelt-week article in this series shows a full rule, line by line. If the triage routine runs overnight in a storm and reaches anything that needs the owner's yes, the request lapses after about ten minutes (Cursor's help pages say thirty) and nothing is carried out, so the night ends at a ranked queue, never at a reply.

Three flags sit on top of the ranking, each taken from EPA's guide, A Brief Guide to Mold, Moisture and Your Home (as checked on 15 October 2026). None of them is a diagnosis, and none produces a sentence to the homeowner. Each moves the card to the owner.

The phone stays with people. The assistant starts from what was captured in writing; how calls and missed calls are handled is a separate system, and the HVAC missed-call workflow article covers that mechanism.

• SEWAGE OR CONTAMINATED WATER

  Where water or mold damage was caused by sewage or other contaminated water, EPA's guide says to call in a professional with experience cleaning and fixing buildings damaged by contaminated water. In this design the company does not do contaminated-water clean-up, so the card goes to the owner for a referral, and a sewer backup is a matter for a plumber or drain specialist.

• THE AREA OF MOLD

  EPA's guide says that where the moldy area is less than about ten square feet, roughly three feet by three, homeowners can in most cases handle the job themselves; where there has been a lot of water damage, or growth covers more than ten square feet, it points readers to EPA's guidance on mold remediation in schools and commercial buildings. The card records what the customer described and how big they said it was. The assistant measures nothing and says nothing about it.

• WET MATERIALS AND THE CLOCK

  EPA's guide says water-damaged areas and items should be dried within twenty-four to forty-eight hours to prevent mold growth. A soaked carpet or wet drywall in a finished basement therefore moves up the queue, and the owner decides whether drying belongs to a restoration company before any waterproofing visit.

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.

Grok Bot lets a person create named Bots, each with its own job and conversation, working on a persistent cloud computer with a browser, files and a command line. Bots use connectors where they exist and can operate many browser-based tools that have none, handing logins, two-factor codes, CAPTCHAs and payments back to a person. Routines run a Bot's workflow on a timetable, with no two scheduled runs closer than five minutes. The documentation describes no telephony at all: no answered calls, no voicemail, no texts to customers.

The documentation also recommends the smallest useful roster. For a waterproofing company the first Bot is triage, because every later step starts from a card. A proposal Bot, a discharge Bot and a service-plan Bot follow once the cards are reliable. These roles are Aevrion's design, not features of the product. In this design they pass work through the computer's shared workspace: the triage Bot saves each card to a folder there, and the proposal Bot reads it after the owner has booked an inspection. Whether any of their steps pauses for the owner's approval depends on the tool, its risk and the rules the owner sets, rather than on a blanket setting.

Where the water comes from is the inspector's judgment, made in the basement: the floor-wall joint, a crack, a window well, the slab, condensation, or water arriving at the house because the ground or the gutters send it there. EPA's guide lists two exterior checks among its moisture-control tips: make sure the ground slopes away from the foundation, and keep roof gutters clean and repaired. It also advises keeping indoor relative humidity below sixty percent where possible, ideally between thirty and fifty. Those points belong on the owner's inspection sheet, so a proposal can show what the inspector actually checked. A crack that suggests structural movement is a question for a foundation repair company and, where needed, an engineer; a separate guide in this series covers that trade.

The proposal Bot turns the inspection notes and photos into a draft in the company's own format: the system the owner chose, such as interior drain tile with a sump, a wall vapor barrier, crack injection, window-well drains, downspout extensions or a dehumidifier, with the owner's description of each. Each price is looked up in the owner's catalog on every draft, since the documentation warns that a Bot's memory is no substitute for the record, and the warranty wording is pasted in from the owner's own document rather than summarized. Reading a catalog held in field-service or estimating software is a custom integration or supervised browser use where the vendor permits it, subject to testing.

Where the owner offers financing, the draft mentions it in the owner's words and a person handles the application. The lender's portal is a login like any other: once saved on the computer the four Bots share, the triage, discharge and service-plan Bots could reach it as easily as the proposal Bot, since the documentation does not treat Bots as walls between one another. Keeping finance apart therefore takes a second user account, not a second Bot.

A sump system moves water out of the basement, and a municipality may regulate where it goes. The discharge Bot's work is research, not judgment: it finds the town's published rule through supervised browser use and gives the owner and the installer the link, the date it was read and what is still to confirm, or says plainly that no rule turned up.

Nothing it drafts tells a homeowner that a discharge is legal or compliant. One city's ordinance shows why that matters: Delano, Minnesota, bars sump pump and footing-tile water from its sanitary sewer and sets out an inspection route and a monthly surcharge. The sump service plan article walks through that ordinance and the service records it shapes.

A homeowner may ask a waterproofing company about radon while it is in the basement, and the company is not the place to answer. EPA's page on finding a radon measurement or mitigation professional, checked on 15 October 2026, sends homeowners to their state's radon program for help finding qualified professionals. It says states receiving EPA's indoor radon grants list only providers credentialed through a state process or through one of two national radon proficiency programs: the National Radon Proficiency Program (NRPP) and the National Radon Safety Board (NRSB). EPA's page on radon-resistant construction names the same two programs and the state radon coordinator.

So the assistant's reply, drafted for the owner to send, names those routes and stops. It gives no view on testing, no reading, no level and no product. Any question it cannot place goes to the owner.

Each system sold in a surge becomes a pump, a check valve, a float and a discharge line that the company has a commercial interest in keeping in service. A service-plan Bot keeps a register of those plans in the shared workspace and runs a routine that drafts each period's reminder list for the owner to approve. The visit itself, testing the pump and checking the valve, the float and the discharge line, is the technician's, and none of it is decided by an assistant.

The companion article on annual sump pump service plans sets out the register, the visit record and the reminder routine in detail, with Delano's ordinance as its worked example. A second companion follows one owner who inspects, sells and services alone through a week of spring thaw, with five Bots sharing a group chat.

Each of these is made by the inspector on site, by the owner at the kitchen table, or by the municipality or a licensed plumber.

• THE WATER'S SOURCE

  Diagnosed by the inspector in the basement, never inferred from a photo.

• THE SYSTEM

  Drain tile, sump, membrane or grading work is the owner's design.

• PRICE AND FINANCING

  Set by the owner from the catalog; financing paperwork is handled by a person.

• MOLD AND HEALTH

  No assistant makes a statement about mold or health; the owner refers out.

• DISCHARGE ROUTING

  Where a line runs, and whether it meets the local rule, is confirmed by the owner, the municipality or a licensed plumber.

• PERMITS

  Whether a job needs one, and every application, belong to the owner.

• WARRANTY

  Claims and their outcomes are the owner's; the assistant quotes the warranty text and nothing more.

• EVERY OUTGOING MESSAGE

  Customer, referral and reminder messages are drafts the owner sends.

In this trade the first deliverable is the owner's written ranking of flooded, damp, contaminated and mold-worry inquiries. Run it by hand over the messages from the most recent storm: if it would have put the right basements first, and flagged the plan customers whose pumps stopped, the triage Bot has a rule worth applying, and the service register can follow in a dry month.

A scoping exercise with Aevrion Ops would cover the written triage rule, the three EPA flags as the owner wants them applied, the proposal format, the discharge note, the service register and the custom integrations to the inquiry inbox and field-service software, subject to each vendor's API or terms and to testing. Begin with the workflow automation readiness assessment, scoring surge triage as its one workflow; if the surge is already on its way, a scoping conversation is the shorter route.

1. A waterproofing company runs a rain-driven surge and a recurring sump service base; its back office has to serve both.
2. Surge triage follows the owner's written rule, with three flags taken from EPA's mold guide: contaminated water, the area of mold and the drying window.
3. Assistants start from written inquiries; Grok Bot's documentation describes no telephony, and an overnight triage run stops at a ranked queue.
4. Proposals are drafted in the owner's own format from the inspection notes, with the warranty quoted rather than summarized.
5. Each sump job carries a researched note on the local discharge rule that a person confirms; no assistant tells a homeowner a discharge is legal.
6. Radon questions get a referral to the state's radon program or the NRPP and NRSB proficiency programs, and nothing else.