OURHIVE

AI-Powered Home Management Platform

Header ImageHeader Image

The Problem

A founder with a proven analog property management system needed it translated into a scalable digital product, for two distinct audiences, across mobile and desktop, with minimal budget, no existing design infrastructure, and a feature scope that kept expanding.

Context

  • Founding and sole designer at an early-stage startup
  • No PM, no design precedent, full ownership of strategy and execution
  • Greenfield product across mobile and desktop simultaneously

Constraints

  • No budget for broad user testing
  • Large and shifting feature scope with limited ability to validate product-market fit
  • Mobile and desktop had to be designed concurrently with no PM

Results

  • Shipped production-ready mobile and desktop experiences across two distinct user audiences
  • Delivered 11 core features end-to-end
  • Reduced design review cycles from 3 days to 1 day
  • Built two design systems from scratch, accelerating dev cycles by 35%

PART 1

Background

The founder had developed an analog property management system focused on maintaining and protecting a home and its occupants. It included tools for budgeting, upkeep, task management, contractor coordination, and property insights.

My role was to translate this into a scalable digital product, defining the UX, system architecture, and design foundation for two distinct audiences: homeowners and professional property managers.

Business Requirement
  • Convert analog IP into a useable mobile and web product
  • Build for two distinct audiences:  home owners and professional property managers
  • Deliver complete, testable mobile and desktop experiences
  • Establish a brand that stands out in a crowded category
User Needs
  • Identify & prevent insurance risks
  • Catalog and manage home, appliances and possessions
  • Discover & complete projects to extend the lifespan of their home
  • Track family members, vendors, contractors, team members
Internal Goals
  • Design to launch today, while supporting long-term evolution
  • Build internal product design processes & systems
  • Create patterns that scale without requiring redesign
  • Reduce rework across design and engineering

Roles & Responsibilities

⦿

Drive & Execute Design Strategy. Led discovery and design strategy using interviews, market research, and systems thinking to align product vision with user needs.

⦿

Design Ops. Built lightweight but scalable processes for collaboration, delivery, and iteration under tight time and resource constraints.

⦿

Cross-functional Alignment. Collaborated daily with the CEO, CTO, and Head of Product to ensure feasibility, scope clarity, and brand consistency.

PART 2

Research, Identify and Differentiate

With limited access to users and the field, I developed a lean research approach. It leveraged targeted interviews, competitive analysis, and AI-assisted synthesis to rapidly form and validate hypotheses.

Learn the competition

I conducted thorough research and analysis of direct and tangential competition.

This enabled us to fine tune our product market fit and identify opportunities to differentiate ourselves.

Identify the users

I didn't have access to a broad set of users. I compensated by repeatedly interviewing a half-dozen champions and by tapping into AI tools.

Two distinct audiences emerged with different needs and different stakes.

  • Homeowners varied widely in house size, number of properties, age, and experience level, but shared a common goal: more visibility, less headache. The tool needed to meet them where they were, regardless of how hands-on they wanted to be.
  • Property managers had a different relationship entirely. This was their job. The tool needed to help them deliver more value to their clients: deeper data, faster decisions, less manual coordination.

That split drove every major platform decision that followed.

Design to Differentiate

Balancing the desires of the owner, the market and the users, I developed a foundational brand and design system.

PART 3

Journey, Structure, Flow

After defining key personas and mapping core user journeys, I developed the information architecture, user flows, key design system moments.

Primary User Journey

The principal function of the app was to deliver a personalized maintenance plan to our users. This plan was developed in four steps: build your team, add your house, build your inventory, customize your plan through use.  

The structure allows users to reach value quickly while supporting deeper engagement over time.

Information Architecture
  • Defined a structure that supports large volumes of data and multiple workflows
  • Organized key entities such as home, inventory, tasks and projects
  • Used early concepts to validate direction with users and stakeholders
  • Provided roadmap and structure for PM
User Flow
  • Created end-to-end user journeys for core experiences
  • Partnered with engineering to align flows to what was feasible and adaptable
  • Used flows to identify gaps, edge cases, and opportunities for simplification

PART 4

Mobile Design

I prioritized mobile for onboarding and data capture, where users could quickly build their home inventory.

Setup your home

I designed the onboarding screen to be light, quick and intuitive. We debated the structure and depth of the onboarding set-up. I convinced the team to make this is minimal as possible so the users could experience the value of the app as soon as possible.

Build a digital twin of everything you own

Most users don't know the make, model, or purchase source of what they own. Manual entry would have produced incomplete data and an unreliable maintenance plan.

  • The Solution: point your camera at anything in your home and let AI identify and categorize it. From there, the maintenance plan stops being generic. "Replace refrigerator filter" becomes "Replace Amana refrigerator filter with Part AB-7359."
  • The design decision: camera capture as the default, manual entry as the fallback. Higher data accuracy meant a more useful plan for every downstream feature.
  • The tradeoff: we were scraping multiple databases, so retrieval wasn't always clean. When confidence was low, users could review and confirm. Brand imagery was the other constraint: official product photos weren't always retrievable, so user-captured images filled the gap. Not ideal visually, but it kept the data honest.

Discover & use your maintenance plan

After identifying a home’s inventory, I create a tailored maintenance plan that adapts to the user’s needs. They can then delegate tasks, customize routines, and uncover helpful resources for proactive home care.

PART 5

Desktop Design

Desktop was built for property managers.The larger canvas allowed for richer data display, open navigation, and a dashboard experience that gave power users everything at a glance.

Onboarding

Setup runs as a guided four-step flow so a property manager can stand up a full home profile in one sitting, not piecemeal.

Dashboard

The desktop home surfaces multi-property status, team, and budget in a single view. That's oversight a PM needs at a desk, not a phone.

Maintenance Plan

Recurring work is organized by month and made fully customizable, so managers schedule against real seasons and client needs, not a fixed template.

Projects

A single job opens into scope, assigned team, budget, and progress in one frame. Managing the work, not just listing tasks.

Inventory

Every owned asset lives in one room-by-room view, feeding the same digital-twin system the mobile capture builds.

Part 6

Results & Learnings

Results

  • Shipped a production-ready mobile and desktop experience on schedule and on budget across two distinct user audiences. The company folded after launch.
  • Delivered 11 core features end-to-end, from onboarding through a fully personalized maintenance plan
  • Built two design systems from scratch, accelerating dev cycles by 35%

Learnings

  • Designing for scale requires balancing long-term vision with immediate execution. Over-indexing on either creates risk.
  • With limited user access, a narrow feature focus kept us from building what we couldn't validate.
  • Without a PM, I learned how quickly design stalls without a clear, shared prioritization system.