A bidding tool
built by an operator.
Tidy started as an internal tool: a faster way to write proposals that don't lowball the work. It turned out other cleaning operators had the same problem. So we shipped it.
Why Tidy exists
Most cleaning companies bid by gut feel. A 20,000 sqft office gets a square-footage guess, a flat hourly, and a margin pulled from the air. The job gets won, the crew shows up, the math doesn't work, and the operator eats the difference for six months.
Tidy replaces the gut feel with the same math a $200/hr agency estimator uses — productivity rates by task, real labor cost, overhead burden, profit floor — but packaged so a one-person shop can run it between two cleanings. Per-user pricing. Not per-company. Your price is your price.
It's the tool we wished existed when the work got serious.
What we believe
The operator knows the work.
Software should help an experienced operator move faster, not pretend it knows the building. Tidy assumes the person using it has done the job.
No bloat.
Every feature has to earn its place in the bidding flow. If it doesn't make a proposal better, faster, or more likely to close, it doesn't ship.
Honest pricing.
No enterprise tier with feature gates. No "contact sales" for the part of the product that actually matters. What you see is what you get.
Where we are
Tidy is in private beta. We're working with a small first cohort of design partners to ship v1. The feedback loop is direct: every design partner has a private channel to the builder, and every shipped feature traces back to something someone on a crew actually asked for.
If you run a cleaning operation and want to join the cohort, the application is on the landing page. We read every submission.