DrumFleet
← Blog

When the spreadsheet breaks (and what to do before you buy software)

Your washer/dryer rental spreadsheet is fine under ~5 sets. Here's where it quietly starts costing you money — payments, contracts, payback — and what to do before you buy software.

By DrumFleet · · 4 min read

If you're running a washer and dryer rental fleet on a spreadsheet, you're not behind. You're normal.

Most of us start the same way. A Google Sheet named something like MACHINES v7 FINAL (2). Stripe in another tab. Contracts in email attachments. Saturday morning spent figuring out who actually owes you money. We ran a fleet like that. The spreadsheet wasn't the enemy. Past a certain size it just stopped being honest with you.

This isn't a pitch to rip it out on day one. It's the order the cracks usually show up — and what I'd do at each one before spending a dollar on software.

Under about five sets, keep the sheet

You can hold five renters in your head. Five payments is five minutes in Stripe. Your next dollar belongs on a sixth machine, not a subscription.

That's why the inventory tracker is free. Source, cost, serial, where it lives, what it's earned. Still buying first sets off Facebook Marketplace? Pair that sheet with how to start a washer and dryer rental business and go buy machines.

Software can wait.

Payments go first — usually around set 6 to 8

The spreadsheet doesn't charge cards. You do.

You're reconciling Stripe against rows by hand. A declined card sits invisible until you go looking. One missed decline is often a full month of rent, which for a lot of fleets is more than a month of any tool you'd buy.

Before you shop for software: every renter on card-on-file autopay. No Venmo. No "I'll text you." Same hour you already spend in Stripe, scan for declines. If you can't see a failed payment without hunting, that's the first real crack — and it's a process fix, not a product purchase yet.

Contracts get fuzzy around set 10

Which renters signed the version with the pest clause? Who got the relocation fee language? The sheet doesn't know. Your Sent folder knows, sort of.

Lock one current agreement in one place, dated. Stop editing the Word doc per renter. Steal the annotated rental agreement we run if you need a starting point, then freeze a version. Version drift is how you end up enforcing a clause that was never signed I've watched that argument go badly.

Then Saturdays disappear set 12 to 15

Who's late. What's in repair. Which machine goes where this week. Pulling that picture from the sheet, Stripe, email, and your notes is the quiet hour this business takes from your weekend every week.

One status column you actually trust — out, available, repair, retrieved — updated the day something moves. When updating status feels like a second job, you're past what a sheet wants to be.

We wrote the longer blunt version with the table here: DrumFleet vs. the spreadsheet.

The column that goes stale first

Payback per machine is the number this business actually runs on. What you paid all-in. What that unit has earned. The month it crossed over.

A sheet can do that math. A lot of operators never finish filling it in. When Saturday is spent reconciling payments, payback is the first column that dies — and then you can't tell which sets are working and which ones are hobbies with serial numbers.

If you've got cost and rent history but haven't looked at payback in a month, that isn't an urgent software emergency. It's a signal the admin stack is eating the job the sheet was supposed to do.

Before you buy anything

Still under five sets? Buy another machine.

Past that, fix the boring stuff first: autopay, one contract version, status you update the day it changes, payback you can read without rebuilding formulas.

When Saturdays are gone to reconciliation and declined cards are surprises, then look at software — and look for something built for monthly appliance rentals, not event gear or generic assets with rental bolted on. The questions that matter are dull and specific. Does autopay start on install day, not signup? Do failed cards retry and get flagged, or sit quiet? Is payback tracked per machine without a second spreadsheet?

Soft landing

Under five sets: take the free tracker, keep going, come back later.

Past that, and the sheet is lying to you one column at a time: import what you have and let it retire with honor. DrumFleet's trial is 14 days on the full Growth plan, no card.

The spreadsheet was never the problem. Pretending it still works after it stopped telling you the truth is.

More from the blog

Built on a working fleet

Four things generic rental software gets wrong.

DrumFleet was the internal tooling for a washer and dryer rental business before it was a product. It shows in the details — and every one of these is checkable inside the free trial.

Autopay starts on install day.
Not on signup, not on the 1st. The first invoice carries rent plus deposit plus delivery, then the cycle settles onto the billing day you chose.
The contract knows about relocation.
Minimum term, relocation fee, retrieval clause, ID on file. Renters move, and the paperwork either survives that or it doesn't.
Payback is tracked per machine.
What you paid, what it has earned, and the month it crossed over. This is the number the business actually runs on, and almost nothing else reports it.
A failed card starts a ladder, not a silence.
Retry, flag, then a dunning sequence on day 0, 3 and 7 — inside the grace window you set, before the retrieval clause is in play.

Rent out more machines with less chasing.

Autopay, e-signed contracts and every machine tracked from your phone. Free for 14 days, no card.

No card required. 14 days on the full Growth plan.