Marcus runs dispatch for a three-truck HVAC company out of a converted garage. Intake comes in by text, gets logged into a shared spreadsheet his dispatcher Rita updates between calls, and anything odd gets a sticky note on her monitor.

Every few months something slips. A callback sits too long. A job gets booked onto a truck already out on another call. A customer who phoned twice gets a note that says nothing useful.

Marcus thinks about replacing the whole setup, then pictures the weekend it would take, the history that might not transfer, and Rita relearning a job she already knows cold. He puts it off again, the same way he did last quarter.

Marcus isn't failing to switch because the spreadsheet works. He is caught in status quo bias, the tendency to weigh the certain cost of staying against the uncertain cost of changing, even when staying costs more. Samuelson and Zeckhauser documented this back in 1988: people default to what they already have, not because it performs better, but because its losses feel familiar and arrive in small pieces that never add up to one visible number.

The missed callback in March and the double-booking in June never get added into one figure. Each lands as a one-off, forgivable, absorbed into the idea that it happens sometimes. The switch, by contrast, arrives all at once: a weekend of setup, Rita relearning her routine, the fear that two years of job history gets lost in the move. Loss aversion makes that concentrated, visible cost feel heavier than the diffuse one, even though the diffuse one is larger across a year. The spreadsheet isn't winning on merit. It's winning because its damage never presents a bill.

A request comes in by text or call, gets classified by job type and urgency, gets routed to the next open truck and time slot, and gets resolved with a confirmation sent back automatically. None of that requires Marcus or Rita to learn a new screen.

The part that actually breaks status quo bias happens before any of that. The old spreadsheet's job history gets pulled in during setup instead of dumped on Rita to retype. The sticky-note exceptions get captured by asking her how she already handles them, then built into the system quietly. There's no weekend lost, no day where the business runs on something nobody trusts yet.

What changes is the arithmetic Marcus never consciously ran. Automated scheduling targets exactly the labor and overtime waste that quietly erodes margins many small operators run at just 2 to 5 percent, according to TimeForge's 2025 analysis. The missed callback and the double-booking stop piling up as stories Marcus tells himself are manageable, because they stop happening at all.

Webspenser · Reply to this email with the moment you'd like covered next.

Two things from the blog worth your time this fortnight. Plus one extra.

Stop wasting time rewriting generic drafts. Build a repeatable small business AI strategy by matching the right prompt framework to your output risk.

Not every Google review should get an AI reply. Use one simple rule by star rating to decide what auto-posts and what needs your approval first.

TimeForge · Lays out the labor, compliance, and overtime math that manual scheduling quietly loses.

Why people in your business behave the way they do, and what technology can do about it. Bi-weekly, three minutes.