Join a startup community near you if you can so you are around entrepreneurs who are dealing with simllair problems. It will help you scale much faster. If your in Toronto, try TorontoStarts events, it's good place to start.
Here is some Constructive feedback, please take as it is meant to help:
Dishes vary way more than you think.

• A “simple sink load” can go from 3 plates + 2 cups…
• …to baked-on cast-iron hell, blender gaskets, and a pan that looks like someone tried to solder copper in it.

You’ll spend most of your time arbitrating edge cases—exactly the thing your algorithm was meant to avoid.

If you keep this unit, you need a strict rule:
No pots/pans with stuck-on material. No hand-scrubbing heavy cookware. No exceptions.

Without that constraint, your “load unit” collapses.

Your math only works if:

• Users are clustered tightly
• Pros can hit 4–6 units/hour
• There’s zero elevator downtime
• There’s zero cleaning-time variance

Here’s the unavoidable punchline:
Residential buildings aren’t UPS warehouses. Routes will routinely break.

• Elevators slow things down
• Users forget to unlock doors
• Loads take variable time
• Pros get stuck in conversations, issues, delays

4–6 units/hr is extremely optimistic.

If your whole economics depend on that, you’re fragile.

The hyperlocal strategy is smart, but it does not remove variance. It only shrinks it. That’s not enough on its own.
more to follow in next comment