AI for Plumbers — Diagnostic Memory That Sticks

Updated January 2026 | 7 min read

You get a callback from an address you serviced eight months ago. Same complaint, but you can't remember if you replaced the flapper valve or just adjusted the chain. Your truck stock shows three Bradford White parts that might fit, but you're not sure which one goes with their model year.

Standard AI can't help. It doesn't know you already snaked that drain twice, that the house has galvanized supply lines, or that the customer refuses PEX because they read something online.

Claude Code with Obsidian gives your AI a permanent file of job histories, system configurations, and customer preferences. Every diagnosis, every part installed, every quirk of every property—written once, available forever. No monthly fee. No cloud dependency. Just a markdown file that remembers what you did and why.

What Plumbers Need AI to Remember

Job history matters when troubleshooting. The water heater you installed three years ago is still under warranty. The pressure regulator failed once already. The mainline has a belly that catches debris. Without records, you're diagnosing from scratch every time.

System details determine parts and labor. Cast iron stack or PVC? City water or well? Tankless or traditional? Separate shut-offs or one main valve? You photograph jobsites but don't always file them where you'll find them six months later.

Customer preferences affect every estimate. Some want builder-grade fixtures because they're renting the place out. Others want spec sheets for every component. A few demand same-brand replacements even when better options exist. Forgetting this wastes everyone's time.

Parts catalogs live in your head until they don't. You know which supply house stocks Moen cartridges and which one has better pricing on ABS fittings. You know the Delta rep gives bulk discounts. AI can hold this, but only if it persists between conversations.

The Diagnostic Protocol Problem

Low water pressure has twelve possible causes. You run through them systematically, but if you've already ruled out six at this address last year, you're repeating work. A memory system lets you skip to the remaining possibilities.

Intermittent issues require pattern recognition. The toilet that runs at night but not during the day. The drain that backs up only when the washing machine runs. The leak that appears after heavy rain. You need notes from previous visits to spot the pattern.

Code compliance varies by jurisdiction and year built. A 1980 house has different requirements than new construction. The city inspector cares about venting configurations; the county doesn't. Your memory file holds the local rules so you don't have to look them up mid-job.

How the Memory System Works for Plumbers

You create a markdown file in Obsidian. Inside: customer addresses with job histories, common issues by fixture brand, supplier contacts with pricing notes, diagnostic checklists, and truck inventory logs. Plain text, readable by you and by Claude.

Claude Code reads this file every time you start a conversation. You mention an address, and Claude already knows the water heater model, the last service date, and that the customer wants text updates, not phone calls.

When you finish a job, you update the file—parts installed, time spent, issues found, follow-up needed. Next time that customer calls, the history's already loaded. No digging through invoices or trying to remember if you wrote it down.

The structure scales from solo operation to multi-truck outfit. One plumber? Single file tracks everything. Five techs? Separate files for jobs, inventory, suppliers, and equipment maintenance. Claude reads all of it because it's just organized folders.

Job History Template

Each address gets a section with system type, fixture brands, pipe materials, and access notes (crawlspace entry, attic hatch location, shut-off valve behind the dryer). Include a log of every visit: date, work performed, parts used, labor hours, issues noted.

Track warranty dates and model numbers. The Bradford White has a six-year tank warranty. The Kohler faucet is model K-560-CP. The Zoeller sump pump was installed October 2023. When something fails, you know immediately if it's covered.

Note recurring problems. The kitchen drain clogs annually because of inadequate slope. The pressure tank loses precharge every two years. The shower valve cartridge failed twice—next time, upgrade to a better model instead of replacing like-for-like.

Parts Catalog and Supplier Notes

Your file holds cross-references for common parts. Fluidmaster 400A fits most Kohler and American Standard toilets. The 1.5-inch P-trap adapter works with both ABS and PVC. The 3/4-inch SharkBite coupling is in truck stock, bin 3.

Supplier pricing matters when margins are tight. Ferguson gives contractor discount on orders over $500. The local guy matches internet prices if you ask. Home Depot is open late but doesn't stock pro-grade backflow preventers. Claude cross-checks your notes before suggesting where to source a part.

Specialty parts need lead time. The European faucet cartridge takes two weeks. The commercial backflow assembly requires certification to install. The grinder pump impeller is special order only. Your file tracks this so you don't promise same-day service on something you can't get.

Diagnostic Checklists by Symptom

Running toilet? Check flapper seal, chain length, fill valve, flush valve seat, tank-to-bowl gasket. Your file holds the sequence and the common fix ratios. Flapper fails 60% of the time, fill valve 25%, everything else splits the remainder. You start with the likely culprit.

No hot water? Verify power, check breaker, test heating elements, inspect T&P valve, confirm thermostat settings, examine anode rod. Electric vs. gas vs. tankless each have different trees. The file walks you through model-specific steps based on what you've logged before.

Slow drain? Try plunger, snake from fixture, pull trap, camera inspection, hydro jet, check vent stack. Severity determines method. Your notes say which drains responded to augering and which needed jetting. Pattern recognition cuts diagnostic time.

Customer Communication Preferences

Some customers want photos of every issue before you fix it. Others say just handle it and send the invoice. One needs three-item estimates for insurance. Another pre-approves anything under $300. Your file holds these rules so you don't have to ask twice.

Scheduling quirks matter. The rental property manager wants all work coordinated through the tenant. The commercial account requires after-hours service. The elderly homeowner needs extra notice and someone to walk her through what was done. Claude surfaces these notes when you're booking the appointment.

What This Costs vs. What It Saves

Setup is $997 one-time. You get Claude Code installed, Obsidian configured, and a starter file template for plumbing operations. No subscription. No per-tech fees. Your job history and supplier notes stay on your device, accessible offline.

Compare that to one wasted trip because you forgot the property needs a specialty part. Or one callback because you repeated the same fix that didn't work last time. Or one lost estimate because you couldn't remember the customer's fixture brand.

The system pays for itself when you stop re-diagnosing the same issues every visit. It pays again when parts orders pull from actual supplier pricing instead of memory. It keeps paying every time a customer calls and you already know their system inside out.