How to Sell AI Builds to Dry Cleaners (The Full Rack Pitch)

The Short Answer

Sell to a dry cleaner by selling a cleared rack and a quieter phone, not marketing. A dry cleaner does the work first and gets paid when the customer comes back. Every finished order hanging in plastic is money the owner has already spent labor on and has not collected yet. At the same time, the person at the counter is answering the same few questions by phone while customers wait in line. In my view those two leaks, the forgotten pickup and the repeat question, are where an AI build pays for itself fastest.

That is the Full Rack Pitch: two questions - how many finished orders are on the rack right now, and how many 'is it ready?' calls does the counter take in a day? - followed by a demo of a text that goes out the moment an order is marked ready, and a follow-up for orders that are still waiting. If you have read the pitch for [cleaning companies](/blog/sell-ai-builds-to-cleaning-companies) or [salons and barbershops](/blog/sell-ai-builds-to-salons-and-barbershops), the shape will feel familiar. The difference with dry cleaning is that the customer's property is in the shop, so anything about damage, loss, or stains has to go straight to a person.

What a Dry Cleaner Actually Pays For

Dry cleaning work comes from walk-in customers dropping off garments, regulars on a weekly routine, pickup and delivery customers, and commercial accounts like restaurants, hotels, and offices that send uniforms or linens. Each one has its own leak. I would pitch the first build on one of these five.

• Ready-for-pickup texts: when the counter marks an order as finished in the point-of-sale system, the customer gets a short text with the ticket number, the total if the owner wants it shown, and the hours. This removes most of the 'is it ready?' calls, because the customer no longer has to ask.
• Rack reminders: orders still waiting after a set number of days get a polite reminder, then a second one later. The timing and the wording come from the owner. If the shop has a written policy about what happens to items left too long, the assistant only repeats that exact wording and never threatens anyone.
• A question assistant: people text or message asking about hours, prices for a shirt or a suit, turnaround times, and whether the shop handles leather, wedding dresses, or alterations. An assistant that answers only from the owner's written price list and policies handles most of that without the counter picking up the phone.
• Pickup and delivery booking: customers who want their clothes collected can pick a time slot, confirm their address, and get a reminder the day before. The owner keeps control of the routes and the slots.
• Commercial account follow-up: restaurants, hotels, and offices send repeat work. A simple program that confirms their drop-offs, sends receipts, and checks in with accounts that have gone quiet keeps that work from drifting to the shop down the street.

Notice what is not on the list: anything that judges a garment. Customers ask 'will this red wine stain come out?', 'you ruined my jacket, what are you going to do about it?', and 'where is my missing shirt?' Those answers belong to the owner, who can look at the item. The assistant should say so plainly and get a person involved.

Work inside the shop's own point-of-sale and messaging tools wherever you can. Orders hold names, phone numbers, and home addresses for delivery, 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 Dry Cleaner

Before you reach out, look at the shop from the customer's side. Read their public reviews. Comments about long lines, a phone nobody answers, or a garment that sat for weeks tell you which part of this pitch will land. If you can, drop off one shirt as a real customer and notice whether anyone tells you it is ready, or whether you have to remember on your own.

Then ask the two Full Rack questions. 'How many finished orders are on the rack right now?' Most owners can glance behind them and give you a rough answer, and many point-of-sale systems can list unpicked orders by age, which makes the point for you. 'How many is-it-ready calls do you take in a day?' Then [demo, do not describe](/blog/the-demo-first-close). Mark a test order ready and show the text arriving on your phone with the ticket number and the hours. Then text 'you ruined my silk blouse, I want my money back' and show the assistant staying calm, collecting the ticket number, declining to discuss fault or money, and alerting the owner. 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 point-of-sale system they use, whether it records a phone number on every ticket, and whether their prices and policies are written down anywhere. A shop whose system already tracks order status and phone numbers is a fast build. A shop running on paper tickets is a different project, and getting their prices and policies into writing is its own scoped job. The best first fit is an owner-run shop with one or two locations and a busy counter.

How to Price the Build

Price against the rack and the counter, not your hours, which is the frame [value-based pricing](/blog/value-based-pricing-stop-charging-hourly) exists for. The owner knows what an average order is worth and roughly how many orders are waiting. Do the math out loud with their numbers: if reminders bring back even a small share of those orders sooner, how much cash is that, and how much counter time comes back when fewer people call to ask? If that covers the build in a few months, a scoped first build priced in the low thousands is easy to justify.

Then attach the monthly plan, because prices, hours, holiday closures, and delivery slots change, and the reminder timing needs tuning once you see which messages bring people in. 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: ready texts sent, orders picked up after a reminder, questions answered without a phone call, and delivery slots booked. If they hesitate, the ready-for-pickup text alone is a fine first step. It is small, it works from orders the shop is already finishing, and the owner will feel the phone get quieter within the first week.