SaaS vs Custom

Dry cleaner (Brisbane, single shop, 500–800 items in queue per day, 150–200 pickups/day, 50 active member subscribers, 10–15 corporate orders/week, $35k–50k monthly revenue). Service delivery: customer walks in with 5 dress shirts, pants (10 items, mixed). Customer requests: "I need them Tuesday morning, can you do it?" Dry cleaner assesses: standard dry clean (shirts + pants 7–10 business days typical turnaround, rush available 3–5 days at 20% premium). Dry cleaner quotes: 10 items × $6/item = $60 standard, or $72 rush (Tuesday = 2 days, rush fee). Customer chooses: standard $60, pickup Thursday. Dry cleaner intakes: 10 items, writes ticket number by hand on paper tag (ticket #4521 in sequence, next customer gets #4522 — no system, just incrementing counter). Dry cleaner attaches: paper tag to first shirt (stapled to collar, or sewn if customer will complain). Dry cleaner logs: customer name, phone, ticket number on index card (handwritten, filed in cash drawer). Dry cleaner processes: items sent to pressing room. Items cleaned. Items pressed/steamed. Items folded, stored on rack by ticket number (4521 hanging next to 4520, 4522). Customer called manually: "your items ready Thursday morning." Customer comes Thursday. Dry cleaner searches: "ticket 4521" through hanging racks (50–100 tickets hanging, visual search, staff memory, slow, error-prone). Staff finds: items (mostly), hands to customer. Customer leaves. BUT: customer says "where's my blue shirt?" Staff searches: can't find blue shirt. Customer says "I brought 5 shirts, you lost one." Dry cleaner says "we have 4 here, the 5th must be here somewhere." Dispute over shirt. Staff remembers "did someone pick up 4521 early without paying? Did I move items between ticket numbers?" No audit trail. Dry cleaner can't prove: which items were in the ticket, or if shirt was never received, or if staff lost it. Customer angry, threatens to pay "only for 4 items, not 5." Relationship damaged, dispute unresolved. Member subscriber scenario: Mary is subscriber (weekly 5 shirts for $50/week). Every Monday: Mary drops off 5 clean shirts to be dry cleaned (from previous week, customer's subscription "I send 5 dirty shirts, you send back 5 clean ones"). Dry cleaner manually logs: "Mary, 5 shirts, due Friday." Friday: 5 shirts ready. Dry cleaner manually calls Mary "your shirts ready." Mary doesn't pick up Friday. Dry cleaner manually calls again Saturday morning. Mary says "I'll get them Tuesday." Tuesday: Mary picks up 5 shirts, pays $50 (cash, or Mary on account, dry cleaner tracks "Mary owes $0, paid in full"). Next Monday: Mary brings 5 more dirty shirts. Rinse and repeat. But: dry cleaner never sends SMS, can't auto-bill (no payment processing), can't track if Mary has prepaid vs on-credit, can't generate invoice. Mary disputes "you said $50/week, but you charged me $52 last month." Dry cleaner checks old receipts: finds $50 entries, but also $2 "restocking fee" manually added by staff. Dispute, Mary cancels subscription. Dry cleaner loses $200/month recurring revenue. Corporate order scenario: "ABC Corp" corporate cleaning (30 shirts/week, pickup every Friday, invoice to corporate account, net-30 payment). Dry cleaner receives: call from ABC Corp "we need 30 shirts done by Friday." Dry cleaner manually logs: "ABC Corp, 30 shirts, Friday." Friday: 30 shirts cleaned and pressed. Dry cleaner manually creates invoice (Excel template, fills in "ABC Corp, 30 shirts × $6 = $180, due June 30"). ABC Corp picks up. Dry cleaner never auto-sends invoice (no email, no system). ABC Corp accounting calls month later: "we didn't receive invoice, how much do we owe?" Dry cleaner re-sends invoice. ABC Corp pays 45 days late (net-30 terms violated, cash flow hit). Dry cleaner loses visibility on recurring revenue. Damage/dispute scenario: customer drops off suit jacket (wedding suit, pristine condition, "be careful, I have a wedding next Saturday"). Dry cleaner cleans, presses, but pressing machine gets too hot, shrinks jacket 2 sizes. Suit now unwearable. Customer collects, tries on: "this is ruined!" Dry cleaner says "we didn't shrink it, maybe it was already treated." Dispute. Customer demands: $300 replacement cost (suit was $400 originally). Dry cleaner refuses, says "we don't cover shrinkage claims." Customer threatens lawsuit. Dry cleaner has: no intake photos (damage before/after undocumented), no condition notes (staff remembers "it looked fine"), no shrinkage log (pressing machine temperature not logged, no maintenance records). Dry cleaner loses dispute or settles for $150 (hits profit margin). No litigation defense. Chemical compliance scenario: Australian dry cleaning industry historically used perchloroethylene (perc), a solvent with lead contamination risk (older formulations, rare but documented). Regulations: Australian Environmental Protection and Biodiversity Conservation Act (EPBC Act) + State Hazardous Waste regulations require: (1) inventory of chemical solvents used (type, quantity), (2) safety data sheets (SDS) on file, (3) waste disposal compliance (proper hazmat disposal, not dumping down drain), (4) staff training (chemical safety, spill response, first aid). Dry cleaner uses: "standard solvent" supplier, never verified SDS, never logged inventory, never trained staff on spill response. One day: solvent tank leaks in processing room, 20 litres spilled, staff exposure (inhalation, skin contact). Staff member goes to hospital, respiratory irritation diagnosed. Workplace injury report filed. Regulator investigates: asks "do you have SDS on file? Do you have staff training records? Do you have waste disposal receipts?" Dry cleaner has: none of these. Fine issued ($5k–15k depending on state), business reputation damaged, staff morale hit, potential prosecution. Operational chaos compounds: 3 staff (manager + 2 cleaners), all manual processes. No centralized system. All knowledge in manager's head. Manager takes sick leave 1 week. Substitute manager doesn't know: which tickets are overdue, which customers are subscribers, which corporates are on auto-bill. Items pile up on racks. Customers call: "where are my clothes?" Substitute manager can't find tickets (no system), guesses at inventory ("I think we have your items"). Customer frustrated. Manager returns to work: finds 20 pickups overdue, 10 customers angry, 2 subscribers cancelled, 1 corporate contract suspended. Revenue collapsed week 1 of absence. Hiring + training new staff: new cleaner joins, gets trained on: "tickets are handwritten numbers, we keep them on index cards, fold items this way, press on high heat." New cleaner makes mistakes (high heat shrinks item, staff forgets to attach tag to 5 items, items get mixed up with other ticket numbers). Quality drops. Customer complaints increase. Manager spends time fixing staff errors instead of growing business. Growth blocked by operational friction.

Six Features Custom Dry Cleaner Software Delivers

1. Tag Intake + Photo Capture, Condition Assessment, Damage Liability Documentation, Pickup Ready SMS Notification

Customer walks in with 5 dress shirts, 2 pants (7 items). System displays: intake form (customer name, phone, email, preferred pickup date). Staff selects: item type (dress shirt, count 5; trousers, count 2). System prompts: condition assessment (excellent/good/fair/poor, visible stains, tears, worn areas). Staff notes: "5 shirts pristine, no visible stains, button slightly loose on shirt #3. Pants: good condition, small wine stain on cuff." System captures: photo of each item (or bundle photo — 5 shirts folded together, then pants). System generates: unique ticket number (automatically, e.g., "000001") and RFID tag ID linked to ticket. System prints: label with ticket number + barcode. Staff attaches: label to first item (stapled or heat-sealed). System logs: intake record (7 items, condition notes, photo library, customer contact, promised pickup Thursday 9am). System sends: intake confirmation SMS to customer "your 7 items received, condition noted, ready Thursday 9am, reply CONFIRM or change date." Customer replies: "CONFIRM." System triggers: notification to pressing room (7 items, standard processing, due Thursday 9am). Processing room receives: job list (7 items, ticket 000001, priority standard, due Thursday 9am). Items cleaned, pressed, folded. System logs (optional, pressing room manager updates): "ticket 000001 pressing started Wed 2pm, completed Wed 6pm, items ready storage." System auto-triggers: pickup SMS (Thursday 7am) "your items ready! Pick up by 5pm today or we charge $1/day storage. Confirm pickup time: REPLY with time or call 07 1234 5678." Customer replies: "coming at 9:15am." System confirms: reservation (ticket 000001, pickup time Thursday 9:15am). Thursday 9:15am: customer arrives. Staff scans: barcode on ticket 000001. System displays: (1) customer name, phone, email, (2) intake list (5 shirts, 2 pants), (3) condition notes ("pristine, no visible stains, button slightly loose on shirt #3, small wine stain on cuff"), (4) intake photos (customer can view, verify items match original condition — if any damage happened during processing, visible here). Staff retrieves: items from storage (items tagged 000001, quick lookup, no manual search). Staff does: final visual check (condition vs photos — if wine stain is now larger, staff notes it before handoff). Staff hands: items to customer. System logs: pickup (ticket 000001, verified by customer, marked closed). System sends: thank-you SMS "thanks for coming! Rate your experience: GOOD/BAD or call to discuss." **Value: liability protection (intake photos + condition notes create before/after evidence, if customer disputes "you damaged my shirt," system shows proof of intake condition). Plus: customer confidence (SMS updates keep customer informed, "your items ready" SMS == faster pickup, less overcrowding in shop). Plus: zero lost items (barcode tag system means items never get mixed up between ticket numbers, staff scans to retrieve, no manual search, items always found). Plus: process efficiency (staff scans barcode, system displays everything needed, vs staff manually searching index card and racks).**

2. Pickup Window Booking Calendar, SMS Scheduling, Multi-Day Holds, Overstay Charges Automation

Customer at intake: promised pickup "Thursday morning." System displays: pickup calendar (Thursday available 9am–5pm, Friday available 9am–1pm, Saturday closed). Customer selects: "Thursday 10am–11am" (1-hour pickup window). System reserves: slot for ticket 000001 (customer name, 7 items, Thursday 10–11am). If 10+ customers book same window: system flags "Thursday 10–11am is overbooked (12 customers, only 2 staff at counter), recommend moving 2 customers to 11am–12pm window." Manager reviews, asks 2 customers to shift. System updates: calendar reflects new slots. If customer doesn't show Thursday by 11am: system auto-extends hold (items stay in storage). System auto-triggers: overstay SMS Friday morning "your items still in storage! Pick up by Saturday 1pm or hold expires (donation to charity). Confirm pickup: REPLY or call." Customer doesn't reply. Saturday 1pm: hold expires. System marks: ticket 000001 "unclaimed, ready for donation rotation." Manager donates items to charity (tax-deductible), logs donation. System logs: unpaid storage ($1/day × 2 days = $2 storage charge, waived as unclaimed). **Value: calendar visibility (staff knows exactly when customers are coming, can staff counter appropriately, reduces customer wait time). Plus: no-show automation (system handles overstays, charges storage automatically, no manual nagging, reduces deadweight inventory sitting in storage). Plus: peak management (system shows overbooking, staff can stagger customers, smooth pickup flow).**

3. Member Subscription Management, Auto-Billing, Recurring Order Tracking, Subscription Churn Prevention

Mary is subscriber: "5 shirts/week for $50." System displays: subscription settings (Mary, 5-shirt weekly subscription, $50/week, auto-billed every Monday). Every Monday: Mary brings 5 dirty shirts. System auto-creates: order (Mary's subscription order, 5 shirts, due Friday). System auto-bills: $50 payment processed (linked to Mary's saved credit card or account balance). System sends: invoice SMS "weekly subscription: 5 shirts for $50, charged to your card ending in 5678, due Friday 5pm." Friday: 5 shirts ready. System sends: pickup SMS "your 5 shirts are ready, pickup by Saturday 1pm or $1/day storage applies." Mary picks up. Saturday: Mary brings 5 new dirty shirts. System tracks: "Mary on-time, consistent pickup, healthy subscriber." If Mary misses pickup (shirts sit Sat/Sun): system escalates (Friday pickup missed SMS + Monday morning "weekend hold fee $2 for Sat/Sun storage, added to next week's charge"). If Mary cancels subscription (calls manager "stop my subscription"): system marks: subscription status "cancelled effective immediately." System logs: churn (Mary was 8 weeks subscriber, revenue lost $400, reason recorded if manager notes "too expensive"). System flags: churn analytics (if 3+ subscribers cancel in one month, manager alerted "subscriber churn spike, review pricing or quality"). For new subscriber onboarding: system displays: subscription plans (5 shirts/week $50, 10 shirts/week $95, 20 shirts/week $175). Customer selects: "5 shirts/week." System collects: payment info (credit card, or account auto-bill). System sets: auto-bill schedule (every Monday). System sends: welcome SMS "welcome to weekly shirts! You'll be charged $50 every Monday for 5 shirts, pickup Friday. Cancel anytime by calling. Your first 5 shirts due Friday." **Value: recurring revenue automation (system handles billing, no manual invoicing, no payment disputes, $50/week × 50 subscribers = $10k/month recurring predictable revenue). Plus: churn visibility (system tracks which subscribers cancel, why they churn, allows manager to identify "is it price, quality, or competition?"). Plus: subscriber retention (SMS reminders + pickup window confirmation = engaged customers, less likely to churn). Plus: scaling ease (200-subscriber network across 4 shops = $40k/month recurring, system handles all billing and tracking, not possible at manual scale).**

4. Corporate Recurring Orders, Auto-Invoice, Payment Scheduling, Net-30/Net-60 Tracking, Corporate Dashboard

ABC Corp corporate cleaning: "30 shirts/week, every Friday pickup, invoice on pickup, net-30 payment terms." System displays: corporate order settings (ABC Corp, 30 shirts/week, Friday pickup, net-30 invoice). Manager creates: recurring order template (ABC Corp, 30 shirts, standard cleaning, Friday due date, repeat weekly). Every Monday–Friday: ABC Corp can log in (corporate dashboard) and view: (1) this week's order (30 shirts collected, cleaning in progress, expected Friday 5pm), (2) previous invoices (May 1–May 7: invoice $180, due June 6, status "paid May 20", May 8–May 14: invoice $180, due June 13, status "awaiting payment"). Friday: 30 shirts ready. System auto-generates: invoice (ABC Corp, 30 shirts × $6 = $180, invoice date Friday, due date 30 days out = next Friday + 30 = [calculated]). System auto-sends: invoice to ABC Corp email + corporate dashboard (digital invoice + PDF). System logs: invoice sent (timestamp, email confirmation). ABC Corp accounting receives: email with invoice PDF. ABC Corp pays: check or bank transfer by due date (or sometimes late). System tracks: payment received (when cheque clears, system marks invoice "paid"). If invoice overdue 10 days: system auto-escalates SMS to ABC Corp manager "your $180 invoice is 10 days overdue, due [date], please arrange payment." If overdue 30 days: system escalates (phone call to manager: "invoice is 30 days overdue, we need immediate payment or will suspend service"). System generates: corporate dashboard analytics (ABC Corp manager logs in, sees: YTD spending $2,340, average invoice $180/week, on-time payment rate 85% (paid 34 invoices on time, 6 invoices overdue), next order Friday). **Value: recurring revenue automation (ABC Corp generates $180/week × 52 weeks = $9,360/year guaranteed, system tracks it all). Plus: cash flow clarity (manager knows exactly when invoices due, can chase payment proactively). Plus: corporate trust (ABC Corp appreciates digital invoicing, dashboard visibility, professionalism). Plus: scaling ease (if manager wants to add 5 more corporates, system handles all billing and tracking across all 5, not possible manually).**

5. Damage Logging + Liability Liability Tracking, Shrinkage Prevention, Insurance Claims Documentation, Dispute Resolution

Suit jacket intake: customer says "this is a $400 wedding suit, be very careful, no shrinking." System logs: high-value item, customer verbal warning recorded, pressure on staff (manager notes "customer high expectation, wedding event, review pressing carefully"). System displays: pressing instructions (normal heat, check shrinkage risk — wool suit, review care label before processing). Jacket processed: cleaned, pressed on medium heat. Jacket pressed: looks normal (staff visually inspects, no obvious shrinkage). Staff hands to customer. Customer tries on: "it's shrunk 2 sizes!" Customer returns: demands refund $400. Manager checks: has pressing staff made shrinkage claims before? (system checks historical shrinkage incidents). System shows: "last 6 months, 2 shrinkage disputes (both wool suits), both resolved customer refund $100 + $50 store credit." Manager realizes: pressing team may have temperature issue. Manager investigates: presses machine temperature sensor (manually checked, thermometer reads 78°C, safe for wool, but actual pressing temperature may vary if sensor is miscalibrated). Manager escalates: "equipment may be faulty, investigate before processing next batch." For dispute with current customer: system has (1) intake photo (suit looks pristine, no visible shrinkage), (2) condition notes ("wedding suit, wool, customer warning: be careful no shrinking"), (3) no processing log (system doesn't log pressing temperature if manager doesn't manually log it). Manager lacks documentation: can't prove suit shrunk during processing vs customer error (dry cleaning at home). Dispute unresolved. Customer angry, leaves negative review ("they shrunk my suit and refused refund"). But if system had automatic logging: (1) pressing team scans suit ticket before processing, (2) system logs temperature, time, cycle type (3) if temperature exceeded wool safe range, system flags alert: "suit processing exceeded 70°C, shrinkage risk — review before handoff." Staff rechecks suit, notes shrinkage, calls customer proactively "we noticed potential shrinkage, investigating, offering $200 credit or exchange." Dispute prevented, customer satisfied, relationship maintained. Damage log scenario: customer returns to pickup, notices small tear in shirt cuff. Customer says "this wasn't here when I dropped off." System displays: intake photo (customer can zoom, verify if tear visible in original). If tear NOT in intake photo: system shows "this damage occurred during processing, manager will investigate and offer compensation." Manager investigates: pressing team reviews: "we didn't notice tear during pressing, but possible we caused it during folding or from hanger." Manager offers: $20 credit ("next 2 dry clean orders 10% off") to resolve. Dispute contained. If tear WAS visible in intake photo: system shows customer "your intake photo shows this tear already present, we cleaned it but can't be liable for pre-existing damage." Dispute resolved with photo evidence. System maintains: damage log (every dispute logged: item, damage type, date, resolution, $ amount refunded/credited). Manager reviews quarterly: "3 shrinkage claims, 2 tear disputes, 1 stain re-appearance claim, total refunds $320/quarter = 0.2% of $160k quarterly revenue, acceptable loss rate." If damage claims spike (e.g., 10 claims one month): manager investigates (is equipment failing? Is new pressing staff untrained? Are customers being careless?). **Value: liability protection (intake photos create indisputable before/after evidence, zero gray area on whether damage was pre-existing). Plus: dispute prevention (proactive communication when damage detected, resolve before customer discovers issue). Plus: process improvement (damage log highlights if specific equipment or staff are causing issues, manager can address root cause). Plus: insurance claims (if customer sues, system documentation (photos + logs + damage notes) proves liability vs negligence, reduces payout amount or proves shop not at fault).**

6. Chemical Inventory + SDS Logging, Staff Training Records, Waste Disposal Compliance, Lead Safety Auditing

Dry cleaning solvent inventory: manager receives: "10-litre container of dry cleaning solvent, supplier ABC Chemicals." System displays: chemical intake form (product name, quantity, date received, supplier name, SDS attached). Manager uploads: SDS (PDF from supplier, contains: hazard summary, PPE requirements, first aid, waste disposal method). System logs: chemical record (solvent XYZ, 10 litres received June 1, SDS on file, hazard "flammable, CNS depressant, requires ventilation"). System generates: staff alert (all staff at shop receive: "new chemical received: solvent XYZ, hazard info: flammable, requires gloves + mask + ventilation, SDS available on system or request printed copy from manager"). Manager conducts: staff training (30 min session, covers: SDS highlights, PPE requirements, spill response, first aid for inhalation). System logs: training attendance (5 staff attended training June 1, names recorded, completion timestamp). System archives: SDS library (searchable by chemical name, all staff can pull up: "where is SDS for solvent XYZ?" System displays PDF + key hazards). Inventory management: system tracks: 10 litres received June 1, used daily (system estimates ~0.5 litres/day based on shop volume), current inventory 8 litres as of June 6. System alerts: "solvent XYZ at 80% capacity remaining, reorder by June 15 to avoid stockout." Manager reorders: 10 more litres. Waste disposal: system tracks: used solvent (contaminated with dry cleaning residue, must be disposed as hazmat, not dumped down drain). Manager contracts: approved waste disposal contractor (ABC Hazmat Disposal, licensed, EPA-compliant). System logs: waste pickup (June 15, 5 litres of used solvent collected, disposed via ABC Hazmat, receipt #AWD-12345 on file, cost $200). System archives: disposal receipts (all pickups documented, regulators can inspect "where did you dispose of waste?" System shows: dated receipt, contractor license, destination facility). Compliance audit: state regulator (EPA equivalent) inspects shop. Inspector asks: (1) "do you have SDS on file for all chemicals?" System displays: SDS library (solvent XYZ + 3 other chemicals, all SDS present). Inspector satisfied. (2) "do you have staff training records?" System displays: training log (all 5 staff, training date, completion timestamp, names). Inspector satisfied. (3) "where do you dispose of waste?" System displays: disposal receipts (5 pickups logged, contractor licensed, destination facility documented). Inspector satisfied. (4) "have you had any spills or incidents?" System displays: incident log (zero spills reported in last 12 months). Inspector satisfied. Inspection passed, zero violations. **Value: compliance audit-ready (SDS + training + disposal all documented, regulator can inspect with zero findings). Plus: staff safety (training mandatory, staff know how to use chemicals safely, spill response practiced, first aid knowledge sharp). Plus: waste compliance (all waste properly disposed, zero environmental violations, zero fines). Plus: insurance advantage (if employee sues for exposure (respiratory issue linked to chemical), system shows "staff properly trained, SDS on file, ventilation required and maintained," reduces liability, helps defend against claim).**

3-Store Dry Cleaner Network — Real ROI Projection

Dry cleaner chain: 3 shops (Brisbane CBD, Southside, Northside), 500–800 items/shop/day = 1,500–2,400 items/day across network, 150 active member subscribers, 20 corporate orders/week, $120k–160k monthly revenue across 3 shops. Current stack: manual ticket numbering (paper tags, handwritten numbers), index card customer log (filing cabinet), no SMS notifications (manual phone calls), member subscriptions tracked on spreadsheet (no auto-billing), corporate invoicing via Excel (manual creation, email, no tracking), damage disputes (intake photos none, disputes = "he-said-she-said"), chemical logs scattered (SDS in filing cabinet, staff training informal, waste disposal receipts lost). Operational cost estimate: staff overhead (manual intake + tag attachment + ticket logging + phone calls for pickups + corporate invoicing + damage dispute resolution = 2–3 FTE per shop, $50k–70k/shop/year salary, 3 shops = $150k–210k/year), lost/disputed items (missing items, shrinkage claims, damage disputes = 10–20 per shop per month, average loss $100 per incident, 3 shops × 15 incidents/month × $100 = $54k/year), corporate revenue loss (invoicing errors, payment tracking failures, customers switching to competitors due to poor service = 2–3 corporate accounts lost per year, $2k–5k per account = $4k–15k/year), subscriber churn (no SMS updates, poor pickup experience, customers cancel = 20–30% churn rate annually on 150 subscribers, 30 × $50/month × 12 months = $18k/year churn loss), chemical compliance risk (no SDS logging, no training records, regulator fine if spill occurs = low probability but $5k–20k fine if happens), staff turnover (high churn due to repetitive manual work, turnover cost = $10k per new hire × 2 turnovers/year per shop = $60k/year training cost). Total annual operational friction: $150k–210k (staff) + $54k (lost items) + $4k–15k (corporate loss) + $18k (subscriber churn) + $10k (compliance risk average) + $60k (turnover) = **$296k–367k annual operational friction**. Custom dry cleaner platform build: $60k (one-time, tag tracking + photo intake, SMS notifications, subscriber billing, corporate invoicing, damage logging, chemical compliance dashboard). $4k/year ops (cloud hosting, SMS gateway, payment processing fees built-in). Year 1 investment: $64k. Year 1 value captured: (1) eliminate lost/disputed items ($54k prevented), (2) eliminate staff overhead on manual tasks (2–3 FTE per shop → 1.5 FTE per shop for exception handling, saves 1.5 FTE × $60k = $90k), (3) recover corporate revenue (reduce churn, improve invoicing, better payment tracking = retain 1–2 corporate accounts, $3k–10k revenue saved), (4) reduce subscriber churn (SMS + smooth pickup experience = reduce churn from 30% to 10%, keep 20 subscribers × $50/month × 12 = $12k saved), (5) eliminate turnover cost (smooth process = staff happier, reduce turnover 2 per shop to 1 per shop per year, saves 1.5 FTE × $40k = $60k). Year 1 conservative value: $54k + $90k + $6.5k + $12k + $60k = **$222.5k**. Year 1 net: $222.5k - $64k = **$158.5k positive (payback month 4)**. Year 2: value repeats (no build), ops $4k, net = $222.5k - $4k = **$218.5k pure profit**. Year 3: same **$218.5k**. 3-year projection: Year 1 +$158.5k, Year 2 +$218.5k, Year 3 +$218.5k, cumulative **$595.5k net**. ROI is strong because: (a) lost item prevention ($54k) = 85% of build cost, (b) staff efficiency (1.5 FTE eliminated = $90k) = 140% of build cost, (c) subscriber retention (reduce 30% to 10% churn = $12k) = 19% of build cost, (d) turnover reduction (1.5 FTE saved = $60k) = 94% of build cost, (e) corporate revenue recovery ($6.5k) = 10% of build cost. Stacked value exceeds build cost in month 4. Want your exact ROI? Check platform pricing, or book a call — we'll model: current items/day per shop (affects staff overhead reduction), current lost-item rate (affects dispute resolution value), current subscriber count + churn rate (affects churn recovery value), current corporate orders + invoicing errors (affects corporate recovery value), current damage claim frequency (affects liability protection value), multi-shop scaling plans (expansion to 4+ shops multiplies value), plus compliance audit-readiness (chemical handling confidence, zero regulatory fines, staff safety liability reduced) — we'll show payback timeline + year 2+ annual profit potential.

Australian Regulations: Lead in Dry Cleaning Chemicals, Chemical Handling + Waste Disposal, Award Compliance, Environmental Protection Act

**Lead in Dry Cleaning Solvents** — Australian dry cleaning historically used perchloroethylene (perc) as primary solvent. Perc itself is not lead, but some older perc formulations contained lead contamination (rare, but documented in 1980s–1990s imports). Australia banned lead-based dry cleaning solvents in 2010 (part of National Chemicals Framework). Current perc formulations (post-2010) are lead-free, tested, and compliant. However, if dry cleaner uses older stock (perc purchased pre-2010, stored long-term): regulatory risk. Velocity X supports: chemical inventory tracking (all solvents logged with purchase date, supplier, SDS). If purchase date pre-2010: system flags "old solvent stock detected, recommend replacing with post-2010 compliant solvent." Dry cleaner can then replace, document replacement, show compliance. **Chemical Handling + Waste Disposal** — Australian Environmental Protection and Biodiversity Conservation Act (EPBC Act) + state-based Hazardous Waste regulations (e.g., NSW Protection of the Environment Operations Act 1997) require: (1) SDS on file for all chemicals used, (2) staff training on chemical safety, (3) proper waste disposal (hazmat contractor, licensed facility, documented receipts), (4) spill response plan (staff know what to do if chemical spills — ventilation, cleanup procedure, first aid). Velocity X enforces: SDS library (all chemicals documented, searchable), training logs (attendance recorded, mandatory for all staff), waste disposal tracking (contractor pickups logged, receipts archived), incident reporting (spill report form auto-generated if incident logged). Regulators inspect shops every 3–5 years — system makes inspection easy. **Australian Award Compliance — Dry Cleaner Classification** — "Dry Cleaners" award (Fair Work Commission) governs: minimum wages, penalty rates, leave entitlements, hours of work. Specifically: staff role classification determines wage. A "dry cleaning operator" (presses clothes, cleans garments) vs "supervisor" (manages operations, trains staff) have different minimum wages. If manager uses this software to optimize throughput: system may inadvertently increase work pace such that staff pressure increases (burnout, fatigue). Velocity X note: implement software to REDUCE manual overhead (tag tracking, SMS = less phone calls for staff to make), not increase work pace. Ensure manager maintains Award-compliant hours (staff don't exceed 38 hrs/week standard without overtime), penalty rates honored (weekend work at 150%+ rate), leave entitlements tracked. Velocity X can assist with: hours-of-work logging (staff clock in/out, system tracks hours, manager reviews to ensure compliance), penalty rate calculation (if staff works Saturday, system auto-calculates 150% penalty rate for that day's wage). **Dry Cleaner Licensing — National** — Australia doesn't require federal license for dry cleaning operations (unlike pawnbrokers), but: (1) business registration (ASIC, ABN), (2) public liability insurance recommended, (3) occupational health and safety (WorkSafe / SafeWork NSW) compliance (ventilation, staff safety, training records), (4) GST registration if revenue >$75k/year (most shops). Velocity X supports: invoice/receipt generation (GST-compliant), safety logging (incident reports, training), insurance audit trail (system documents all staff training, maintenance records, chemical handling — helps insurer assess risk if claim filed).

Six FAQs

How does barcode tag tracking prevent lost items and customer disputes?

Customer brings 7 items, system generates barcode ticket. Items stored in racks by barcode. At pickup: staff scans barcode, system displays item list ("5 shirts, 2 pants, taken in condition excellent/good/fair, intake photos attached"). Staff retrieves items using barcode location, zero manual search. Chance of lost item or mixed-up ticket: near zero (barcode ensures exact match). **Value: zero lost items (system tracks every item, prevents mix-ups). Plus: liability protection (intake photos prove item condition, customer can't dispute "you lost my shirt" without evidence).**

How does SMS pickup scheduling prevent pickup delays and overstay costs?

Customer books pickup "Thursday 10am." System sends: reminder SMS Thursday 7am "your clothes ready, pickup booked 10–11am." Customer confirms. If customer doesn't show: system auto-extends hold, sends SMS Friday "still in storage, pick up by Saturday 1pm or hold expires ($1/day storage applies)." No-show handled automatically, no manager nagging. **Value: automation (system handles no-shows, zero manual staff follow-up). Plus: cash flow (storage fees collected automatically if customer overstays, $1–2/day adds up across 50 customers, ~$100/month extra revenue).**

How does auto-billing prevent subscriber churn and ensure recurring revenue?

Mary subscriber: "5 shirts/week $50." Every Monday: system auto-bills $50 (from saved card). System sends: SMS confirmation "weekly subscription charged $50, due Friday." If payment fails (card expired): system retries next day, alerts Mary "payment failed, update card or subscription pauses." If Mary cancels: system logs churn (Mary cancelled, revenue lost $400/month). Manager can then follow up: "Mary, we'd love to keep you, can we offer a discount?" With 50 subscribers × $50/week = $10k/month recurring, auto-billing captures 99% of revenue (vs manual billing = 70% collection rate). **Value: recurring revenue predictability (system handles all billing, no manual invoicing). Plus: subscriber retention analytics (manager sees why subscribers churn, can address root cause).**

How does damage logging prevent shrinkage disputes and liability claims?

Suit intake: customer says "be careful no shrinking." System logs: verbal warning, condition notes ("wedding suit, wool, pristine, $400 value"). Suit processed, handed to customer. Customer claims: "you shrunk it!" System displays: intake photo (zoomed, shows fit), condition notes ("wool, at risk of shrinkage if over-pressed"). System has documentation: if shrinkage occurred during processing, system shows evidence (pressing temperature logs if available, or at least intake photo proving original fit). Dispute resolved via evidence. **Value: liability protection (photos + condition notes = indisputable before/after evidence). Plus: process improvement (if shrinkage common, manager investigates equipment temperature, prevents future claims).**

How does corporate invoicing automation ensure on-time payment and recurring revenue?

ABC Corp: "30 shirts/week, net-30 invoice." Every Friday: system auto-generates invoice ($180), emails to ABC Corp accounting + posts to corporate dashboard. ABC Corp receives: digital invoice + printed PDF. System tracks: payment due date (30 days out), auto-escalates if overdue (SMS at 10 days late, phone call at 30 days late). Manager has visibility: corporate dashboard shows YTD spending, on-time payment rate, next order date. **Value: cash flow predictability ($180/week × 52 = $9,360/year guaranteed from ABC Corp, system tracks it). Plus: payment chasing automation (system escalates overdue invoices, reduces manual follow-up). Plus: scaling ease (5 corporates × $9k/year = $45k/year recurring, not possible to track manually).**

How does chemical inventory + SDS logging ensure regulatory compliance and staff safety?

Dry cleaning solvent received: manager uploads SDS, system logs chemical record + hazard info. System sends: staff alert (flammable, requires gloves + mask + ventilation). Manager conducts: training (30 min, SDS highlights + spill response). System logs: attendance + completion. Regulator inspects: asks "do you have SDS? Have you trained staff?" System displays: SDS library + training log (all staff trained, names, dates, completion). Inspection passed, zero violations. **Value: compliance audit-ready (SDS + training + disposal all documented). Plus: staff safety (mandatory training, knowledge sharp, spill response practiced). Plus: insurance advantage (documented training proves duty-of-care, helps defend against worker compensation claim if exposure occurs).**