LOUIS SINGER
Back to work

Project / 01

Hive

Product Design / Technology

A real-estate marketplace connecting property investors with vetted contractors.

2025–2026·Atlanta, Georgia

Image needed · Replace cover

Hero — current product

Best polished product screenshot or marketplace moment. Replace the gradient cover.

Status
Real Startup / Launched Product
Role
Co-Founder · CTO
Focus
Product Strategy, UX/UI, Web Development, Marketplace Design
Type
Real business

Hive began with a problem hidden inside nearly every renovation: finding the right contractor is messy. As Co-Founder and CTO, I worked across product strategy, interface design, development, and the broader business model—turning an early idea into a product used on real projects.

Image needed

Placeholder

Product UI — key screens

3–4 screens showing project post → bids → compare → messages. Browser frames preferred.

01

The problem / context

What I was solving

Property investors regularly manage bids, referrals, licenses, messages, photographs, timelines, and contractor relationships across disconnected systems. Even after finding someone, the workflow stays fragmented. The challenge was not simply creating another contractor directory. The challenge was designing trust.

02

My role

How I worked

My responsibilities included helping define product strategy, developing major user workflows, designing investor and contractor experiences, building the front end, contributing to full-stack development, structuring project posting and bidding, refining responsive interfaces, and incorporating feedback from investors and contractors. I was thinking simultaneously as founder, designer, and engineer.

Title

  • Co-Founder
  • CTO
03

Process flow

How it moves

  1. 01Property investor
  2. 02Post project
  3. 03Contractors discover opportunity
  4. 04Submit bids
  5. 05Investor compares options
  6. 06Communication
  7. 07Select contractor
  8. 08Manage project
  9. 09Complete project
04

The system

What it includes

Investor experience

  • Create project
  • Upload project information
  • Compare contractor bids
  • Browse contractor profiles
  • Communicate
  • Monitor renovation progress

Contractor experience

  • Discover projects
  • Submit bids
  • Manage profile
  • Display credentials
  • Communicate with investors
  • Manage project activity

Trust & project tools

  • License and insurance information
  • Profiles, ratings, and project history
  • Verification concepts
  • Messages, photographs, and progress tracking

Image needed

Placeholder

Investor experience

Project creation + bid comparison screens.

Image needed

Placeholder

Contractor experience

Opportunity discovery + profile with credentials.

05

The process

Thinking, versions, evidence

  1. 01EARLY SKETCH

    Early idea

    Notebook sketches, feature lists, product brainstorms, and early platform diagrams. The first question was not what the product should look like—it was what information creates confidence between strangers.

  2. 02STRUCTURE

    Information architecture

    Investor side: Projects, Bids, Contractors, Messages. Contractor side: Opportunities, Bids, Profile, Projects, Messages. Splitting the product by role kept each workflow clear.

  3. 03WHAT CHANGED

    V1 → current

    Early screens were too dense. Iteration focused on reducing friction in posting, bidding, and comparison—keeping only what helped both sides decide.

  4. 04CURRENT PRODUCT

    UI system

    Buttons, property cards, contractor cards, badges, statuses, bid comparison, navigation, and messaging—designed as one system rather than isolated screens.

Image needed

Placeholder

Early sketch

Notebook sketches, feature lists, or early platform diagrams. Keep them messy.

Image needed

Placeholder

V1 — too complicated

Unpolished early screenshots. Do not clean them up.

Image needed

Placeholder

UI system

Buttons, property cards, contractor cards, badges, statuses, bids.

  • V1 — Too complicated. Tried to show everything at once.
  • Trust first — licensing and credentials had to be visible before polish.
  • Feedback loops — investors and contractors changed the roadmap more than my assumptions.

Real-world evidence

What actually happened

$120K+

Early project GMV

150

Early users

2nd / 140

Georgia Tech Startup Exchange Summit

5+

Media features

Image needed

Placeholder

Actual event — Georgia Tech

Stage photo, award, pitch slides, or team imagery from the summit.

06

REAL-WORLD TEST

Georgia Tech Startup Exchange Summit

Hive competed against approximately 140 teams and placed second. Hive was the only high-school team in the competition and received a Microsoft-sponsored monetary prize.

  • Pitch and presentation materials
  • Competition photographs and stage moments
  • Award recognition
07

Press

Coverage

  • Atlanta Business Chronicle
  • Hypepotamus
  • Rough Draft Atlanta
  • Atlanta Jewish Times
  • Atlanta Business Radio

Image needed

Placeholder

Press — article screenshots

Real headlines only: Atlanta Business Chronicle, Hypepotamus, Rough Draft, AJT, Business Radio.

08

Outcome

Where it landed

Hive became a launched product used on real renovation projects, with early marketplace activity, users, competition recognition, and press coverage. The work continues to evolve through real-world feedback.

Image needed

Placeholder

Current product

One strong final product shot — the polished result.

09

Reflection

Building Hive changed the way I think about design. A beautiful interface means very little if the system behind it does not solve the right problem. The most important decisions were often not visual—they were deciding what information mattered, what created trust, and what could be removed.

Next Project

02 Coldwell Banker — Perry Community

Spatial Design / Visualization