MVP BUILD
Screenbnb Platform
Screenbnb is an AI platform that helps rental managers spot the best properties to turn into Airbnbs by analyzing profit potential, regulations, and market trends.
I led the 0 → 1 design of its MVP, simplifying complex data into clear insights and delivering developer-ready designs that kept the build simple and trustworthy.
PRODUCT
Screenbnb
ROLE
Product Designer
DURATION
October 2024 - February 2025
TEAM
Jason Henkel (CEO & developer)
The constraints at play
Building Screenbnb's MVP meant diving into an industry I knew nothing about. To move fast, I had to learn on the fly while designing within three key constraints:
Unfamiliar field
I had no background in real estate or short-term rentals, so I had to quickly learn about the industry's metrics, workflows, and compliance.
Developer constraints
The MVP was built by a first time developer, so every decision had to stay technically feasible.
Evolving scope
There were no fixed flows with priorities constantly changing weekly under tight deadlines.
Challenge
Design a clean and intuitive web experience that helps short term rental (STR) managers find high potential listings, while keeping it simple enough for a first time developer to build.
Existing tools showed data, but not decisions
I audited competitors with the founder, and his feedback worked like a mini stakeholder interview, revealing what worked, what didn't, and the pain points STR managers face daily.
…help STR managers go from discovery to decision without feeling overwhelmed by data or lost in complex navigation?
Mapping the product backbone
Prioritizing for MVP
I mapped the founder's wishlist into clear flows, making it easy to spot what was critical for the MVP versus what could wait.
Learning through mapping
These flows helped me quickly learn the space of how managers would move through the product, what data mattered, and where the focus was needed.
Image
Flow diagram of product structure and MVP screens
Core flows that shaped the MVP
Core user flows
Discovery
Seeing what Screenbnb is, understanding the value, and starting a plan
Exploration
Browsing listings, previewing financials, and short listing potential properties
Comparison
Zooming into markets and evaluating high potential areas to make confident decisions
Image
A shared reference point with the founder that streamlined feedback and requirements
Final design
Dashboard
An overview of the essentials. Key metrics and statistics are presented cleanly, with tags and color cues to keep insights scannable and the layout development friendly.
Image
Central hub showing key metrics, market summaries, and listing insights at a glance
Listings
Side by side map and property list make it easy to scan options, while complex rental data is simplified into clear, digestible chunks.
When diving into a single property, the most important details surface first, with noise stripped away so managers can evaluate the clarity and confidence.
Image
Listings - side by side map and list view
Image
Single listing - key property details upfront
Competitive overview
Markets compared with ease. A clear summary sits at the top for instant context, while scroll and click interactions let managers explore nearby properties without ever losing their place on the map.
Image
Quick market summary and interactive map for exploring comp properties
Developer handoff
I documented specs, interactions, and components to keep handoff smooth and organized. Since the developer was new, I kept everything clear and labeled, ensuring the build was feasible and set up for success.
Image
Design specs prepared for development handoff
Lessons from Screenbnb…
🧠 Designing in an unfamiliar space made me a fast learner
I had to quickly grasp industry terms, user goals, and technical constraints, translating that into clear, intuitive interfaces.
🧩 Simplicity was a constraint, not a style choice
Knowing the product would be built by a first time developer, every decision I made had to balance visual clarity with technical feasibility.
📐 Structure brings clarity to complexity
Conducting audits, using task driven flows, and mapping out the information architecture helped turn dense requirements into something clear and actionable.