RENTTER
A property workflow platform designed to reduce rental friction through better coordination, visibility, and trust.
These projects reflect how I think as a product manager across systems, AI, and experience design. Some begin with operational friction. Others begin with behavior, curiosity, or a strong product instinct. What connects them is my approach: understand the problem deeply, frame the opportunity clearly, and build with intention.
Challenge
Rental management often runs on scattered communication, manual follow-up, and incomplete visibility across people, responsibilities, and timelines. What looks like a simple admin issue is usually a deeper workflow problem.
When information lives across chats, memory, spreadsheets, and informal coordination, delays become common, accountability weakens, and trust depends too heavily on human effort instead of system design.
Opportunity
Rentter began with the opportunity to treat rental coordination as a product problem rather than a task management problem. The goal was to design a system that could simplify day-to-day operations while creating more clarity for everyone involved.
Instead of patching one pain point at a time, the product direction focused on building a structure that could support visibility, reduce confusion, and make coordination feel more dependable.
My Role
I shaped the product direction from the ground up by identifying workflow gaps, defining the user problem, and translating those needs into product structure.
My work included product framing, feature thinking, user story development, acceptance criteria, and making sure the product logic stayed tied to real-world behaviors rather than abstract assumptions.
How I Thought About It
What drew me to Rentter was the kind of complexity it contained. This was not a flashy consumer problem. It was a deeply practical coordination challenge hiding inside everyday operations.
I enjoy products like this because the value comes from designing better systems. The question was not just what features to build, but how the product itself could take pressure off the user by reducing memory burden, surfacing the right information, and making actions easier to follow through.
What It Became
Rentter became a strong expression of my systems-oriented product thinking. It turned an operationally messy space into a structured product concept grounded in workflow clarity and real user need.
It also reflects the kind of product work I am most energized by: practical, behavior-aware, and designed to make everyday coordination simpler and more reliable.
Across all three projects, the common thread is clear: I like working in ambiguity, finding the real shape of the problem, and building product direction where others might only see scattered ideas. That is the kind of product work I want to keep doing — thoughtful, high-ownership, AI-aware, and grounded in real human value.