u/Worth-Stuff7351

Looking for some advice regarding a lease agreement my sister received for a room rental in a house in Ontario.

Section 9 of the Ontario Standard Lease lists a $250.00 total refundable key deposit, with the following breakdown:

• $25.00 for a single room key
• $225.00 for "digital lock entry" for the main entrance

https://preview.redd.it/5m04uxxkdzfh1.png?width=986&format=png&auto=webp&s=45c4382c438a127df68a94cd2dfc66aaee325e9b

A few details about the setup:

• She is renting a single room in a house, landlord doesn't live in the house but there are other tenants in other rooms.
• The main entrance lock is a digital keypad / electronic entry.

Charging $225 for a digital lock entry seems extremely high especially if it's just a code/keypad where no physical fob or keycard is being handed over.

Is this fee reasonable or am I thinking too much?

My app has 62 paying users from 680 sign ups.

Is 9% conversion rate good in the SaaS business?

Also is there a standard name for this metric?

My app has 62 paying users from 680 sign ups. Is 9% conversion rate good in the SaaS business?

Also is there a standard name for this metric?

Wanted to share a quick story from last week about how a seemingly minor security constraint collided with a live event, and how handling the fallout became a massive learning experience for my SaaS journey.

The Situation:
I run a web-based photo-sharing platform. Last week, a photographer was using it live at an event and suddenly couldn’t upload any photos. He panicked and reached out to me immediately. The software hadn’t crashed, but on his end, it just looked completely broken.

The Root Cause (The Hidden Edge Case):
When I built the platform, I capped filename character limits as a standard security best practice. What I didn’t account for was this specific photographer using an incredibly unusual, long naming convention for his files. Because he exceeded the limit, the system blocked the upload. To make matters worse, my error handling failed to tell him why it was failing; it just didn't process.

How I Handled It:
Because it was a live event, I dropped everything and managed to deploy a fix to the validation logic within an hour. Even though it was fixed quickly, the user had to go through a high-stress situation in front of clients. I proactively refunded his software fee for the hassle.

Takeaway:

• Your UI needs to speak human. If security constraints or validation limits are triggered, the system must explicitly tell the user how to fix it (e.g., "Filename too long, please reduce characters").
• Live events are the ultimate stress test. No matter how safe or thoroughly tested your architecture is, real-world users will always find an edge case you didn't think of.
• Mistakes mature the product. It’s painful when it happens, but these real-world friction points are exactly how software matures over time.