How to Sell AI Builds to Chimney Sweeps (The Fall Rush Pitch)
- A chimney sweep's year is lopsided. When the weather turns cold, every homeowner who wants a fire calls in the same few weeks, and the crew is on roofs all day. The rest of the year, the phone is quiet, even though every past customer is due for a yearly inspection.
- The strongest first builds: an intake assistant that answers the company's own questions, collects the address and the type of fireplace or stove, and books the visit; a yearly inspection reminder program built from the company's own service records and sent before the rush; and a review request after the job. The AI never tells a homeowner a chimney is safe to use, never diagnoses a problem from a photo, and never quotes a repair.
- Use the Profit Room's Fall Rush Pitch: ask the owner how many past customers have not booked this year's inspection, and how many calls went to voicemail last fall. Price the first build against the jobs those two numbers turn into, then attach a monthly plan.
The Short Answer
Sell to a chimney sweep by selling booked inspections and a smoother fall, not more leads. Most chimney companies are small, and the person who would answer the phone is often on a ladder. When the first cold week arrives, homeowners call down the list until someone picks up, and the company that answers gets the job. Meanwhile, the customers they served last year are due again, and nobody reminds them until they are already in the rush with everyone else.
That is the Fall Rush Pitch: two questions - how many past customers have not booked this year's inspection, and how many calls went to voicemail last fall? - followed by a demo of an assistant that books visits in the company's own words and a reminder program that fills the calendar before the cold weather does. If you have read the pitch for [septic service companies](/blog/sell-ai-builds-to-septic-service-companies) or [HVAC companies](/blog/sell-ai-builds-to-hvac-companies), the shape is familiar. The difference with chimney work is that the reminder can move jobs out of the rush and into the quiet months, which is worth as much to the owner as the extra jobs themselves.
What a Chimney Sweep Actually Pays For
The routine side of the business runs on a yearly clock. The national fire code standard for chimneys says chimneys, fireplaces, and vents should be inspected at least once a year for soundness, freedom from deposits, and correct clearances, with cleaning, maintenance, and repairs done if necessary. That yearly schedule is the whole opportunity: every customer the company has ever served is due again, and the company can see exactly when from its own records. In my view, the first build worth pitching sits on one of four leaks.
- Fall rush intake: an assistant on the website, in messages, and behind a missed-call text that answers the company's own questions about services and service area, collects the address, the type of fireplace, stove, or insert, and when it was last swept, and books the visit or hands the conversation to a person.
- Yearly inspection reminders: a reminder program built from the company's own service records that messages each past customer before the rush, offers open times in the quieter months, and lets them book in a couple of taps.
- Follow-up on recommended work: when a technician has written up recommended repairs, a polite reminder in the owner's wording that the customer has not booked them yet, with a link to call or schedule. The assistant repeats what the technician wrote. It does not add to it.
- Review and referral requests: a short thank-you after the job that asks for a review, since homeowners pick the chimney company their neighbors trust.
Notice what is not on the list: any judgment about the chimney itself. Homeowners ask 'is it safe to light a fire tonight?', 'is this crack a problem?', and 'how much will a new liner cost?' Those are questions for a technician who has seen the chimney. The assistant should say so, in the owner's words, and get a visit on the calendar.
Work inside the company's own scheduling and billing tools wherever you can, and keep payment details out of chat. Service records hold customer addresses and notes about their homes, so treat them as private. [Is it safe to use Claude Code with client data](/blog/is-it-safe-to-use-claude-code-with-client-data) covers how to handle that side of the build. You can build and test all of this in the Claude Code desktop app; the terminal is optional.
How to Pitch the Chimney Sweep Owner
Before you reach out, call the company on a weekday morning, when the crew is usually on a job, and note what happens. Does a person answer? Does it ring out to voicemail? Does anyone text back? Then send a request through their website and time the reply. Read their public reviews too. Comments about being booked out for weeks, or about nobody calling back, tell you how hard the intake half of this pitch will land.
Then ask the two Fall Rush questions. 'How many past customers have not booked this year's inspection?' Most owners do not know, and that is the point. 'How many calls went to voicemail last fall?' Then [demo, do not describe](/blog/the-demo-first-close). On your phone, send 'you swept our chimney last year, can we get on the schedule?' and show the assistant offering open times and booking the visit. Then send 'there is smoke coming into the living room, what do I do?' and show it telling the homeowner to call emergency services right away and alerting a person at the company. That second message is what wins the owner's trust. It shows the build knows where it stops.
[Qualify before you build](/blog/qualify-a-lead-before-the-call). Ask what they use for scheduling and billing, whether past jobs are recorded with a date and an address, and whether their prices and service area are written down. A company with a few years of clean service records is a fast build, because the reminder program has something to work from on day one. A company whose history lives on paper tickets is a different project, and digitizing those records is its own scoped job. The best first fit is a small owner-led company with years of past customers and no reminder system.
How to Price the Build
Price against booked jobs, not your hours - the frame [value-based pricing](/blog/value-based-pricing-stop-charging-hourly) exists for. The owner knows what a typical inspection and sweep is worth and how many calls they lose when the phones are slammed. Do the math out loud with their numbers: take the count of past customers who have not booked this year, assume only a small share book after a reminder, and add the fall calls that used to ring out. If those jobs cover the build within a season, a scoped first build priced in the low thousands is easy to justify.
Then attach the monthly plan, because the customer list grows every season, prices change, and reminder timing needs tuning as you see who books. Structure it the way [packaging a maintenance plan for AI builds](/blog/package-a-maintenance-plan-for-ai-builds) lays out, and report what the owner cares about: reminders sent, visits booked from reminders, calls answered during the rush, and reviews collected. If they hesitate, a small paid reminder-only build on their existing records is a fine first step. It is close to a [win-back campaign for past customers](/blog/reactivation-email-win-back-past-clients), and it shows results without touching the phones.
| Build | Leak it plugs | Where the AI must stop |
|---|---|---|
| Yearly inspection reminders | Past customers who never book their next inspection | Telling anyone their chimney is fine without a visit |
| Fall rush intake | Calls that ring out while the crew is on a roof | Any safety advice, especially about smoke, fire, or alarms |
| Recommended work follow-up | Repairs the technician wrote up that never get booked | Adding to or changing what the technician wrote |
| Review and referral requests | Happy customers who never tell the neighbors | Messaging anyone who did not opt in |
Chimney sweep builds, ranked by how fast they pay back
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
What is the best first AI build to sell a chimney sweep?
Usually a yearly inspection reminder program built from the company's own service records, sent before the fall rush. Every past customer is due again, and moving some of those visits into the quieter months helps the owner as much as the extra jobs. An intake assistant for the rush is the natural second build.
How often should a chimney be inspected?
The fire code standard for chimneys calls for chimneys, fireplaces, and vents to be inspected at least once a year, with cleaning and repairs done if needed. That yearly schedule is what makes a reminder program work, though the owner should set the exact timing and wording.
Can an AI assistant tell a homeowner if their chimney is safe to use?
No. It can collect details and book a visit, but any judgment about safety belongs to a technician who has seen the chimney. Messages about smoke in the house, a chimney fire, a burning smell, or a carbon monoxide alarm should get one answer: call emergency services now, and a person is alerted.
Should the assistant quote chimney sweeping prices?
Only prices the owner has written down and approved, such as a standard sweep and inspection. Repairs, liners, and rebuilds should never be quoted by the assistant, because they depend on what the technician finds.
How much should I charge a chimney sweep for an AI build?
Price against the inspections the reminders bring back and the rush calls the intake assistant catches, using the owner's own numbers, not your hours. A scoped first build priced in the low thousands is usually easy to justify, followed by a monthly plan to keep records, prices, and reminder timing current.
Last reviewed November 1, 2026.
Co-founder of the Claude Code Profit Room. Went from shipping software to closing paying clients, and now teaches builders the selling half of the equation.
More from David Iya →