---
title: "Comment by Steven Mock on \"Designing Different UX Flows for Independent Owners vs Agencies in a SaaS\" | Hashnode"
description: "This rings true from the property side too. An independent owner with a handful of units and an agency managing hundreds are doing the same basic jobs — collect"
url: "https://hashnode.com/posts/designing-different-ux-flows-for-independent-owners-vs-agencies-in-a-saas/69f4e75aec32cba9e54c8f98/comment/6aeec0e7a4f3775d71d9277a"
---

[Discussion](https://hashnode.com/posts/designing-different-ux-flows-for-independent-owners-vs-agencies-in-a-saas/69f4e75aec32cba9e54c8f98)

Comment [Designing Different UX Flows for Independent Owners vs Agencies in a SaaS](https://hashnode.com/posts/designing-different-ux-flows-for-independent-owners-vs-agencies-in-a-saas/69f4e75aec32cba9e54c8f98)

[Steven Mock](https://hashnode.com/@stevenmock)

[6d ago](https://hashnode.com/posts/designing-different-ux-flows-for-independent-owners-vs-agencies-in-a-saas/69f4e75aec32cba9e54c8f98/comment/6aeec0e7a4f3775d71d9277a)

This rings true from the property side too. An independent owner with a handful of units and an agency managing hundreds are doing the same basic jobs — collect rent, handle maintenance, keep records straight — but they need very different views of it. Hiding the advanced features instead of removing them is the right approach: the owner gets a simple screen that doesn't overwhelm them, and the agency can still get to the detail when they need it. The point about data isolation is just as important — an owner should only ever see their own properties, full stop.