case study
Removing operational friction so independent property owners can spend more time hosting guests.
Building products has always been more than designing beautiful interfaces for me. Throughout my career I've worked on enterprise products, fintech platforms, and large-scale design systems used by thousands of people. While those experiences taught me how to build products at scale, I always wanted to experience something different.
I wanted to build a product where every design decision had a direct impact on a real business.
That product became Hostvize.
A few years ago, I started hosting my own property in Auroville.
Like most independent property owners, I listed it on Airbnb and later explored other booking platforms. While OTAs (Online Travel Agencies) are excellent for getting bookings, managing a property behind the scenes quickly became frustrating.
The daily workflow looked something like this:
Most software available in the market solves these problems—but they're designed for hotels, chains, or large hospitality businesses.
For someone running one property with five rooms, the software often felt heavier than the problem itself.
During my research I looked into products such as:
These are powerful systems.
But they usually come with:
Most independent hosts don't need revenue management engines, advanced channel distribution, or enterprise reporting.
They simply want to know:
Who is arriving today?
Which rooms are available?
How much money have I collected?
What still needs attention?
That's when I realised there was room for something much simpler.
Hostvize isn't trying to become another enterprise Property Management System.
Instead, it's designed around a simple idea:
Remove operational friction so hosts can spend more time hosting guests instead of managing software.
Everything is designed around speed, clarity, and simplicity.
A host should be able to open the dashboard and immediately understand the health of their property in under a minute.
Hostvize follows a few principles that influenced every feature.
Every feature has to justify why it exists.
Instead of adding dozens of modules, Hostvize focuses on solving the most common daily tasks exceptionally well.
Many independent hosts don't sit in front of a desktop computer.
They are at reception.
Cleaning rooms.
Talking to guests.
Managing staff.
The product is designed so important workflows can be completed from a phone within seconds.
Automation shouldn't make software more complicated.
It should remove repetitive work.
Examples include:
Every workflow inside Hostvize comes from actual hosting experiences.
Small pain points matter.
Things like:
These are daily operational problems—not edge cases.
Designed around the daily work of independent hosts.
Manage one or multiple properties from a single dashboard.
Each property has:
The experience stays simple regardless of property size.
Hostvize provides a clean reservation workflow that tracks the entire guest lifecycle.
Dates, rooms, and availability. Every stay starts with a question.
Guest details, dates, and a room come together in one reservation.
Welcome the guest and turn a reservation into an active stay.
Keep guest information and payments close, with more time for the person in front of you.
Review the balance and invoice as the guest checks out.
Previous stays and payment history stay connected for their next visit.
Everything remains connected in one place.
Instead of complicated calendar views, Hostvize focuses on clarity.
Hosts can quickly see:
without navigating through multiple screens.
One of the biggest problems with OTAs is commission.
Hostvize allows property owners to have their own booking page where guests can book directly.
Benefits include:
Instead of sending guests to third-party platforms, hosts own the booking experience.
Many small hosts already use Airbnb or Booking.com.
Instead of replacing them immediately, Hostvize works alongside them.
Using iCal synchronization, calendars stay updated across platforms while reducing double bookings.
This allows hosts to transition gradually without disrupting their existing business.
Hotels perform a night audit every day.
Small properties rarely do because it's tedious.
Hostvize automates this process.
At the end of the day hosts can instantly see:
This creates operational clarity without spreadsheets.
Every stay builds customer knowledge.
Hostvize stores guest information so returning visitors feel recognised.
Hosts can quickly see:
Building relationships becomes easier over time.
The biggest challenge wasn't technology.
It was deciding what not to build.
It's easy to keep adding features.
Large PMS products have hundreds.
Hostvize intentionally avoids feature bloat.
Every new feature is evaluated against one question:
Will this save time for a small property owner today?
If the answer is no, it doesn't belong.
Building Hostvize changed how I think about design.
Instead of asking:
"How do we make this screen better?"
I now ask:
"How do we remove this screen entirely?"
I became much more conscious of:
Design no longer ends in Figma.
It continues through development, deployment, customer feedback, and business decisions.
Hostvize isn't a concept project.
It's a real product built around real operational problems.
It combines everything I've learned over the past twelve years:
Building Hostvize has given me something client work rarely can—the opportunity to experience the complete lifecycle of creating a software product.
From identifying a problem, validating it with real users, designing the experience, building the product, shipping features, fixing bugs, pricing the business, and continuously improving it based on feedback.
That journey has fundamentally changed how I design products.
Because great products aren't created by adding more features.
They're created by deeply understanding the people who use them and removing everything they don't need.