DEV Community: Revenue Search

What move-out cleaning taught me about definition of done

Revenue Search — Sat, 29 Aug 2026 19:49:04 +0000

I run a cleaning company in the GTA, and the job that taught me the most about shipping quality work wasn't a complicated one. It was move-out cleans.

A move-out clean has the clearest acceptance test in the business. A landlord or property manager walks in with a checklist and either signs off the deposit or they don't. There is no "looks good to me." Either the oven passes or it doesn't. That external, binary sign-off changed how I think about the word "done."

When we started, "done" meant the place looked clean. That is the trap. Looking clean and passing an inspection are two different states, the same way code that runs on your laptop and code that passes CI are two different states. The gap is always in the places nobody looks until someone with a checklist does: inside the oven, the fridge seals, cabinet interiors, window tracks, the tops of the door frames.

So we treated it like a flaky test suite. We wrote the acceptance criteria down, made it identical every time, and stopped relying on judgment. Our move-out cleaning across the GTA now runs off a fixed checklist that mirrors what property managers actually inspect, not what feels thorough in the moment. When a manager flags something we missed, that item gets added to the list for every future job. The checklist is the regression suite.

A few things transferred surprisingly well from software:

A written definition of done beats "use your judgment" every time, especially with a rotating crew.
The expensive failures live at the boundaries: the edges, the seams, the surfaces you can't see from the middle of the room.
When a check fails in the field, you don't just fix that one instance. You add it to the list so it can never silently fail again.
A photo before handoff is just monitoring. You want to catch the problem before the customer does.

None of this is glamorous. But the boring, repeatable version is the one that gets the deposit back every single time, and "every time" is the only quality bar a customer actually cares about.

What short-term rental turnovers taught me about building reliable systems

Revenue Search — Fri, 28 Aug 2026 04:53:27 +0000

I do not write code for a living, I run cleaning operations, but the more short-term rentals we took on, the more the job started to look like a systems reliability problem. Here is what carried over.

The turnover is a job with a hard deadline and no room to retry. A guest checks out at 11, the next checks in at 4, and in that window the unit has to be fully reset. Miss it and there is no rollback. That constraint forces you to think like an engineer: what is the minimum reliable process, and where does it break.

Checklists are your unit tests. Every unit gets the same checklist every time, not because the cleaner is careless, but because human memory is a bad place to store a process. When something gets missed, you fix the checklist, not the person.

Photo verification is your monitoring. We send a photo report before the next guest arrives. It is the equivalent of a health check: cheap to run, and it catches the one turnover in fifty that went wrong before it becomes a one-star review. Without it you are flying blind and only find out when a customer complains.

Idempotency beats raw speed. A turnover that is fast but inconsistent is worse than one that is slightly slower but identical every time, because inconsistency is what destroys a review score. Optimize for the same result every run first, then make it faster.

That mindset is basically the whole service now. If you host in the GTA and want the operational side handled, this is what we built our short-term rental turnover cleaning across the GTA around: same checklist, same team, photo-verified, every single turn.

The takeaway for anyone running operations, technical or not: treat the recurring job as a system, instrument it, and fix the process instead of blaming the person. It scales a lot better than heroics.

Capacity planning, but for food: lessons from catering a 150-person event

Revenue Search — Thu, 20 Aug 2026 15:43:59 +0000

I don't write about food much, but I spent a weekend helping a friend coordinate catering for a 150-person event, and it turned out to be a capacity-planning problem in a chef's jacket. If you've ever sized a worker pool or argued about batch sizes, a lot of this will feel familiar.

Throughput is set by your slowest station, not your headcount

The naive assumption is "more cooks equals more food." But a kitchen has fixed stations: so many burners, so much oven space, one rice cooker of a given size. Past a point, extra people just contend for the same resources. It's Amdahl's law with steam. The real question is what your bottleneck station can push per hour.

Lead time is the real constraint

Some dishes are effectively precomputable — batch them ahead and hold them warm. Others degrade fast and have to be finished just-in-time or they're mush by service. Good caterers schedule backward from serving time, staging the make-ahead items and reserving scarce station-minutes for the things that can't wait. When I looked at how one small halal kitchen lays out its catering options across Toronto it read like a dependency graph: prep tasks with different shelf lives, scheduled so the critical path lands exactly at service.

Overprovision the cheap things, not the expensive ones

Rice, bread, and salad are your cheap horizontal scaling. Running out is embarrassing and easily avoided, so you overprovision. The expensive protein is where you forecast carefully, because waste there is real money. Same instinct as caching cheap computed results while staying stingy with costly external calls.

Failure modes are degradation, not crashes

A kitchen rarely goes down. It degrades: service slows, quality drops, the line backs up. The equivalent of graceful degradation is keeping a couple of dishes that hold well as a buffer, so one slow station doesn't stall the whole event. Plan the fallback before you need it.

None of this is groundbreaking if you do systems work. But it was a good reminder that capacity planning, batching, lead time, and failure modes aren't software ideas — they're just how any constrained system under a deadline behaves. Food is only the version you can eat.

Lead time is a feature: a planning lesson from booking catering

Revenue Search — Sat, 15 Aug 2026 23:03:53 +0000

A tangent from my usual posts, but the principle mapped over cleanly.

I've been helping a small family food business figure out their catering ops, and the single biggest predictor of whether an order goes smoothly isn't the food or the price. It's lead time. The customers who book two weeks out get exactly what they want. The ones who call the day before get whatever's possible, at a premium, with the stress baked in.

That's the same lesson as capacity planning. Slack in the schedule isn't waste; it's the buffer that absorbs the things you didn't foresee. A kitchen booked to 100% today has zero room for the surprise 80-person order tomorrow, exactly like a service running at redline has no headroom for a traffic spike.

The practical version they wrote up: how far in advance to book halal catering in Toronto. Short answer: the good vendors and the good dates go early, and "we'll figure it out later" is how you end up paying rush pricing for a worse result.

Applies to deploys, launches, and dinner for 80. Give the system time and it gives you options. Compress the timeline and every problem gets more expensive.

What running a cleaning company taught me about scheduling systems

Revenue Search — Tue, 11 Aug 2026 03:07:23 +0000

I don't write software for a living. I run a cleaning company in Toronto. But the last two years of trying to schedule crews across a city has taught me more about constraint solving than any tutorial ever did, and some of it might be useful if you're building anything with appointments in it.

The naive model breaks immediately

My first system was a spreadsheet: job, address, time, cleaner. It worked for about eleven jobs. The moment you have two crews and a city, you're not scheduling appointments anymore, you're solving a routing problem with soft constraints:

Travel time between jobs is not symmetric (rush hour on the DVP going north is not the same as going south)
Job duration is a guess, and a wrong guess cascades into every job after it
Some jobs are hard-pinned (a move-out clean has to be done before the landlord walkthrough at 4pm)
Some cleaners can't take certain jobs (allergies, no ladder, no car)

The classic mistake is treating duration as fixed. It isn't. A 3-bedroom deep clean is 3 to 5 hours depending on how much grease is on the stove, and you don't know until you're standing in the kitchen.

What actually helped: buffers as a first-class concept

The fix wasn't a smarter algorithm, it was admitting uncertainty in the data model. Every job now carries a duration_min and duration_max, and the scheduler packs against the max. We lose some theoretical throughput. We stopped being late, which is worth vastly more.

If you're modelling anything real-world with time in it, store the range, not the point estimate. Averages lie in exactly the case you care about.

Idempotency matters when humans are the API

Crews text updates. Clients reply to confirmations. Someone reschedules twice. Early on, a double-confirm would create two jobs and two invoices, which is a genuinely embarrassing way to learn about idempotency keys.

Now every state change is keyed on (job_id, transition), and replaying it is a no-op. Same principle as any webhook handler, just with more human chaos on the input side.

Publish the constraints to your users

The last thing, and it's more product than engineering: we put our actual prices and time windows on the site instead of hiding them behind a quote form. It cut the back-and-forth enormously because people self-select. Our flat-rate cleaning services in Toronto page is basically the constraint set made public, and it does more scheduling work than any feature I've built.

If your booking flow requires a phone call to discover the price, your scheduler isn't the bottleneck. Your information architecture is.

Not everything worth optimizing is code: a tradeoffs story from food logistics

Revenue Search — Tue, 04 Aug 2026 22:58:59 +0000

Not everything worth optimizing is code.

I've been helping a small family food business in Scarborough think through their catering operations, and the delivery-versus-pickup decision turned out to be a cleaner tradeoff problem than half the feature flags I've shipped.

Pickup minimizes variables. No delivery window to miss, no driver, no traffic. The cost is pushed onto the customer, and you lose the people who won't drive.

Delivery removes friction for the customer but adds a stack of failure modes: timing, temperature, a driver, an address, someone on site to receive it. Every one is a thing that can go wrong on the day.

The interesting part is that the right answer isn't a blanket policy — it depends on order size and occasion. Small weekday orders lean pickup; big catered events lean delivery. They wrote up the full decision framework here if you want the non-engineer version: halal catering delivery vs pickup in Toronto.

The takeaway that stuck with me: "reduce the number of things that can fail on the day" is just as true for a food order as it is for a deploy.

Cleaning a condo is not the same as cleaning a house — what actually changes

Revenue Search — Mon, 27 Jul 2026 23:40:54 +0000

I moved from a house to a downtown condo a couple of years ago and assumed cleaning would get easier because the place was smaller. It didn't. It just got different, and it took me a while to figure out why the same routine that worked in the house left the condo feeling dusty within days.

A few things about condos change the job in ways that aren't obvious:

The dust is relentless because of forced-air HVAC. Condos push conditioned air through vents constantly, and that moves fine dust onto every horizontal surface far faster than in a house. Wiping once a week isn't enough on the surfaces near a vent.

You can't get behind or under much. Built-in cabinetry, wall-mounted units, and tight kitchens mean the grime collects in seams and corners you have to deliberately go after, not sweep past.

Floor-to-ceiling windows and tracks. Condos love glass. The tracks and sills collect a surprising amount of grit, and the interior glass shows every mark against the city light.

Shared-building realities. Elevator dust, hallway carpet fibers tracked in, and balcony soot from traffic below all end up inside. It's not you being messy; it's the environment.

Storage is tight, so clutter reads louder. In a house, clutter spreads out. In a condo, the same amount of stuff makes the whole unit feel dirty even when the surfaces are clean.

What changed my results was treating the condo as its own cleaning profile rather than a mini-house: prioritize the vents and the surfaces downwind of them, do the window tracks on a schedule, and accept that "small" doesn't mean "quick." When I stopped wanting to do it myself, I looked at how a service scopes condo cleaning in Toronto specifically, and the itemized list matched exactly the things my house routine had been missing.

The takeaway: square footage is a bad proxy for how much cleaning a place needs. The building's systems and layout matter more, and a condo quietly demands attention in places a house never did.

The difference between a "clean" apartment and a deep clean, itemized

Revenue Search — Sun, 26 Jul 2026 19:31:17 +0000

I always thought my apartment was clean. Then I paid for an actual deep clean once, watched what they did, and realized my normal cleaning was skipping about half the surfaces in the place. Sharing the itemized difference because most people, me included, conflate "tidy" with "clean."

A normal clean, the kind most of us do weekly, is really: visible surfaces wiped, floors vacuumed and mopped, bathroom sink and toilet, kitchen counters, take out the trash. Maybe 60 to 90 minutes. It makes the place look presentable.

A deep clean is a different scope entirely. The itemized list, roughly in order:

Inside the oven, inside the fridge, inside the microwave
Range hood filter (degreased, not wiped)
Inside cabinets and drawers, not just the fronts
Baseboards, door frames, and the tops of doors
Light fixtures and ceiling fans (where the dust actually lives)
Switch plates and door handles (the germ surfaces nobody touches)
Window interiors, sills, and tracks
Grout and tile, scrubbed not sprayed
Behind and under movable appliances
Vents and returns

That is 4 to 7 hours for a one or two bedroom, which is why it is priced as its own service and not a longer version of a regular clean.

The practical takeaway: a deep clean is worth budgeting a couple of times a year (spring, and before or after anything big like a move or guests), while a regular clean handles the in-between. If you want to see how the two are priced separately, a company I have used lays out what a deep clean includes in Toronto with the scope and a flat rate, which made it easy to decide when it is actually worth it versus doing the weekly version myself.

The meta-point: naming the scope precisely changes the decision. Once "deep clean" stops being a vague upsell and becomes a concrete 20-item list, you can actually reason about when your time is better spent doing it versus paying for it.

Why I stopped doing my own move-in cleaning (a time-value breakdown)

Revenue Search — Sun, 26 Jul 2026 19:26:02 +0000

I moved into a new place in Toronto last month and, being a "I'll just do it myself" person, spent my first weekend deep-cleaning an apartment someone else had lived in. I want to lay out why I would not do that again, as a straight time-value calc.

The thing about a move-in clean is that it is not a normal tidy. You are cleaning a space where you have no idea what the previous tenant did or did not do. That means inside every cabinet and drawer, inside the oven and the fridge, behind the toilet, the inside of the dishwasher, the range hood filter, light switches, and the baseboards, before a single box of yours comes in. Done to an actual standard, that is 6 to 9 hours for a one or two bedroom. I know because I did it.

Here is the calc I should have run first. Take the flat price of a move-in clean and divide it by the hours it would take you to do it to the same standard. If that number is below what an hour of your time is worth, outsource. Mine came out to roughly a third of what I would charge for my own time, which is not a close call.

The input people get wrong is the price, because most cleaners will not give you a number until they are in the unit, which makes the whole thing impossible to plan. So I only get quotes from companies that publish flat rates. For the move I used one that lists move-in cleaning in Toronto at a flat rate sized to the unit, which let me plug a real number into the calc instead of guessing.

The broader point, since this is not a cleaning audience: "just do it yourself" is a decision most people never actually price. Your weekend has a value even when no one is paying you for it. Once you put a number on the hours, a surprising amount of one-time grunt work turns out to be a bad trade, and moving is the clearest example, because you are already out of time and energy exactly when the work is biggest.

Running the numbers on Airbnb turnover cleaning (as a host, not a cleaner)

Revenue Search — Sat, 25 Jul 2026 17:38:13 +0000

I run a small short-term rental in Toronto and for the first year I cleaned every turnover myself to "save money." I want to walk through why I stopped, because the math was not what I assumed.

The trap is that turnover cleaning feels free when you do it yourself. It is not. Each turnover was roughly 2 to 3 hours of my time: strip and remake beds with hotel-standard corners, reset the kitchen, scrub the bathroom to review-proof standard, restock consumables, stage it, and photograph any damage. Multiply by the number of stays and I was quietly working a part-time job at an hourly rate I would never accept from an actual employer.

Then there is the failure mode. Miss one hair in the shower or one smudge on a glass and you eat it in the reviews, and in short-term rentals your review score is your pricing power. A single "not clean" review measurably drops what you can charge for months. So the "free" DIY clean is actually a high-variance bet against your own revenue.

When I finally priced it out, a professional turnover ran a flat fee per clean, and I could pass most or all of it through as a cleaning fee anyway, which guests expect. The service I use lists Airbnb turnover cleaning in Toronto at a flat per-turnover rate, so I can predict the cost per booking exactly and build it into my nightly math instead of guessing.

The reframe for anyone running a rental: your turnover is not a chore, it is a production step with a defect cost. Once you price the defect cost (lost reviews, lost pricing power, your own hours), outsourcing to someone who does it to a consistent standard usually wins, and it scales, which your own two hands do not.

A checklist I wish I had before my post-renovation cleanup

Revenue Search — Sat, 25 Jul 2026 17:32:17 +0000

We finished a kitchen and bathroom reno in Toronto last month, and I genuinely underestimated the cleanup. Not the debris the contractor hauls out, the fine dust that gets into everything afterward.

If you have never lived through it: drywall and sanding dust is microscopic and it settles for days. It coats the tops of cabinets, the inside of light fixtures, window tracks, baseboards, the coils behind the fridge, and a fine film over every surface you own. Vacuuming just launches it back into the air if you do not have the right filter.

Here is the checklist I put together the hard way, in order:

Ceilings and walls first, top down, with a microfiber flat mop. Dust falls, so never start low.
Light fixtures and vents. Take covers off and wash them. This is where the dust hides and then re-coats everything when the furnace kicks on.
HVAC filter, replace it. Reno dust destroys the old one and keeps recirculating.
Every horizontal surface with a damp microfiber, not dry. Dry cloths smear fine dust, damp ones trap it.
Inside cabinets and drawers, they are never actually sealed during a reno.
Floors last, damp mop, then a second pass.

I did the first attempt myself over a weekend, did a mediocre job, then re-did half of it. The second reno I just booked it out. The company I used prices post-renovation cleaning in Toronto as a flat rate based on the space instead of by the hour, which mattered because reno cleans take longer than people expect and an hourly meter would have been brutal.

The meta-lesson, since this is not really a cleaning crowd: reno "done" and reno "livable" are two different milestones, and the gap between them is a full deep clean most people forget to budget for, in time or money. Plan for it up front.

I built a simple decision rule for when to hire a cleaner vs do it yourself

Revenue Search — Thu, 23 Jul 2026 18:02:52 +0000

I spend a lot of my week optimizing systems, so it bugged me that "should I clean this myself or pay someone" was a decision I kept making on vibes. So I turned it into a rule, the same way I'd write a threshold for any other build-vs-buy call.

The variable that matters is not money, it's the value of your time against the real hourly cost of the job.

Here's the rule I landed on. Take the all-in price of the clean and divide it by the hours it would take you to do it yourself to the same standard. If that number is lower than what an hour of your time is worth, you outsource. If it's higher, you do it yourself. That's the whole thing.

The trick is being honest about the two inputs.

Your hours: a proper deep clean of a one or two bedroom is not the 90 minutes you imagine. It's more like 5 to 7 hours once you count baseboards, inside the oven, inside the fridge, grout, and the stuff you normally skip. Multiply by two if you'd split it over two resentful evenings.

Their price: this is where most people get stuck, because most cleaning companies won't tell you a number until someone is standing in your kitchen. That breaks the calculation. You can't run a build-vs-buy analysis when one side hides the price. So I only get quotes from places that publish flat rates up front. For a recent condo clean I used one that lists their flat-rate deep clean pricing for Scarborough openly, which meant I could actually plug a real number into the rule instead of guessing.

I ran my own case: roughly 6 hours of my Saturday versus a flat rate that worked out to well under what an afternoon of my time is worth. Outsource, clearly. I got the Saturday back and the place was cleaner than I'd have managed anyway.

The meta-point isn't about cleaning. It's that "just do it yourself" is a decision most people never actually price out. Once you make the hidden inputs explicit, a lot of chores turn out to be a bad use of your one non-renewable resource. Write the rule once, stop re-litigating it every week.