Overview

Klenzaa needed a working MVP before it could become a business.

Klenzaa is a two sided platform connecting STR (Short-term Rentals) hosts with cleaning professionals who handle turnovers between guests. There was no existing product when I started. The client had a validated business idea, target personas, and a business level competitor analysis already in place. My job was to design the MVP that would carry all of it. They pointed me toward tools like Turno and asked me to study what worked, so Klenzaa could improve on it.

Problem it solves

Managing cleaning schedules and payments for vacation rentals across multiple booking platforms is inefficient and time-consuming for hosts. Coordinating with cleaners, tracking availability, and processing payments manually leads to errors, delays, and increased administrative overhead.

Competitive Research

The client's research told us who Klenzaa was competing with. It didn't tell us what we can improve on.

So I ran my own teardown, not at the business or positioning level, but at the interaction level: was the dashboard clear with minimal steps, did the tool offer real automation for checklists and scheduling, or did navigation quietly turn admin heavy. I compared Turno, Breezeway, TIDY, Properly, ResortCleaning, Cleanster, and HostHive against those three questions.

UX teardown comparing Turno, Breezeway, TIDY, Properly and others
My own pattern level teardown of seven competitor tools
Pain Points

Three problems came out of that teardown.

01

Unclear task delegation

Hosts had no clean way to hand off a cleaning task to the right person with the right instructions.

02

No real time visibility

Hosts couldn't see what stage a cleaning was at without checking manually.

03

No standard for quality

Without a shared checklist system, cleaning quality varied from property to property.

Solutions

How I solved those three core problems.

01

Structured task handoff

Designed property-centric task assignment, which means a host assigns a cleaner and a checklist straight from a property panel or while setting it up, the host does not have to wander or get confused for assigning or handing off proper instructions.

02

Live progress tracking

Built a single-source dashboard so hosts see real-time status updates without manual check-ins.

03

Standardized checklist modules

Created modular, priority-tagged checklists to maintain consistent cleaning quality across properties.

Sign Up Page Walkthrough

Dashboard Walkthrough

Checklists & Modules Walkthrough

Properties & Property Details Panel Walkthrough

Scope & Priorities

The MVP was shaped around fast property setup, understandable scheduling, property centric checklist assignment, structured checklist management, and a dashboard that acts as a single source of truth.

Let's start with how the dashboard came to be...

Three versions, each one built to fix a specific problem in the version before it.

Version 1

A calendar grid, color coded by property

Each property got its own color, plotted across a shared calendar view. It looked complete and communicated everything at a glance, in theory.

What broke: past a handful of properties, hosts couldn't remember which color belonged to which property.

Version 1 calendar grid color coded by property
Version 2

Each property becomes its own row

Every property got a row, with its schedule laid out across the timeline. Reading the dashboard stopped requiring memorization.

What was still unresolved: Color for task type too? What about same day conflicts? How can I help users see updates and proof directly from the dashboard and not wander around?

Version 2 of the dashboard, annotated with open questions
Version 3

How the final version was improvised answering all design decisions

  • Color for task type too? Yes. Properties are unbounded, which is why their colors failed. Task types are a small, fixed set, so a fixed palette keeps working.
  • Same day conflicts? Not a layout problem. The product simply doesn't allow two tasks on one property at the same time, so the conflict is prevented at the data level. Even if there is a time overlap, I have designed an overlap pattern directly into the calendar layout.
  • Live progress tracking: Designed the dashboard directly so hosts can view ongoing cleaning work in real time and verify image proof, solving the challenge of live progress tracking.
Klenzaa product card design
Checklists

The checklists have to work in a way that users can create separate checklists, edit them easily, and understand their modules so that when automated, the checklists are easily assigned to the properties.

One checklist with a toggle, or two separate checklists?

Two separate checklists. The host checklist covers personal management tasks, while the cleaner checklist (tagged For Cleaners) covers job-specific cleaning items. They are built and owned independently rather than filtered from a single shared list.

Why organize checklist items into modules?

Different properties require unique task combinations. Modular room blocks like Kitchen, Bedroom, and Bathroom, plus a General module, allow hosts to compose exact checklists per property rather than repeatedly editing one long master list.

Why give individual items a priority tag?

So the items that matter most don't get lost inside a longer module. A task like Broom hall can be marked High Priority inside the General module, so a cleaner moving quickly through the list still sees what can't be skipped.

A cleaner's checklist, built from modules, with priority tags and recommended modules to add

The harder problem underneath it

If a host edits a checklist on a single scheduled clean, how do we ensure future jobs across all properties aren't accidentally changed?

Instead of relying on warning labels, the interface prevents mistakes by default. Standard items are locked on scheduled cleans so hosts can only append one-off additions, keeping global automation intact.

Adding a one off additional item to a scheduled clean checklist
Properties

Properties & Property Details Panel

Visual guide and components

The component library was kept small on purpose.

Buttons, cards, status chips, side panels, nothing more. Building a bigger system ahead of real feedback is a bet on assumptions that haven't been tested yet. Klenzaa's component set stayed deliberately lean so it could evolve once real hosts and cleaners had used it, instead of locking in decisions before there was proof they were the right ones.

Klenzaa Design System visual guide
Klenzaa Design System component library
What's Next

Property setup is manual today because automation needed a foundation first.

The client's real long term goal is automated setup, pulling property data directly from Airbnb or Vrbo listings. Manual setup isn't a placeholder for that, it's the foundation it will sit on top of. Integration hooks for that pull already exist from this engagement, even though the automation itself sat outside the three month scope. If two more weeks opened up, this is where they would go, since it's the part furthest from where the product is actually headed.

Scope

What I designed, and what stayed out of scope.

Designed end to end
  • Property setup
  • Scheduling
  • Role based checklists
  • Dashboard
  • Marketplace handoff
Out of scope
  • Cleaner facing app
  • Payment flows
  • Formal user testing rounds
Outcome

Klenzaa's current product runs on this design.

The live product uses this UI and these branding guidelines today. It's still evolving, and I don't have visibility into how real hosts or cleaners have responded since handoff. That's the honest state of it, not a guess dressed up as a metric.

Reflection

What changed in how I design

Before this project, most of my decisions were instinctive first, justified after. Klenzaa is where that flipped. Every element on a screen now needs a reason it exists, down to why a card is a certain size or why a color shows up here and not there.