PERSONAL

CASE STUDY · 2026

SAL HOME

A PWA my wife and I use to manage three properties — our farmhouse, a shore house, and a rental. Built in a single evening, no Figma, and mostly from my phone.

A fully functional PWA we use daily to manage projects, track spending, and stay on top of maintenance across three properties. Built with Next.js 16, Tailwind v4, shadcn/ui, and Supabase. Recently expanded to support multiple homes, each with its own projects, budgets, and maintenance schedules.

Mobile

PWA

Responsive

◈ Experimental

Personal Project

Next.js

2026YEAR

ROLEDesigner, Developer, User

EMPLOYERPersonal

TIMELINE< 12 hours

TEAMJesse Szygiel · Claude

#Context & Constraints01

Three properties, no shared system, and projects that kept piling up.

My wife and I manage a 150-year-old farmhouse, a shore house, and a rental property. Between the three, something always needs attention — seasonal upkeep, contractor bids, aging infrastructure, tenant issues. The problem wasn't the work itself, it was the organization. Projects, estimates, contractor contacts, and maintenance schedules were scattered across emails, saved contacts, and mental notes that never made it anywhere permanent. We'd tried spreadsheets but they were too much friction to keep updated, especially from a phone. I wanted one place to manage everything across all three.

CONSTRAINT

NO FIGMA · NO DESK

No Shared System

We each had half the picture. Projects I was tracking lived in my head or my inbox. Things she was managing were invisible to me. Nothing was in one place and keeping each other in the loop meant remembering to have a conversation.

Contractor Amnesia

Quotes, contact info, and bid details were scattered across emails and saved contacts with no connection to the actual project. Every time we revisited something, we'd spend 20 minutes finding the context we'd already gathered.

Maintenance Blindspots

Our 150-year-old house has systems that need regular attention — HVAC filter, well water filter, UV filter, septic. Without any tracking, we only remembered something was due when it failed.

#Design System03

Mid-Century Farmhouse

Design System

Inspired by the natural beauty that surrounds us — earthy greens, warm creams, and tones pulled directly from the property. No Figma. Every decision made through conversation.

// Primitive palette

Sage

Primary · Interactive

Brass

Chart · Highlight

Terra

Chart · Warning

Cream

Surface · Light

Clay

Muted · Warm

Taupe

Secondary Text

// Semantic tokens · dark mode

Background

Page background

Card

Card / panel

Primary

Interactive · CTA

Muted

Inactive surface

// Typography

Geist Sans

UI, labels, body copy

Regular

Home. Managed.

Medium

Home. Managed.

SemiBold

Home. Managed.

Alice

Display headings

Regular

Your home, organized.

Geist Mono

Numbers, data, code

Regular

$24,800 committed

Medium

$24,800 committed

// Inspired by the natural beauty that surrounds us — earthy greens, warm creams, and tones pulled directly from the property. No Figma. Every decision made through conversation.

#Impact04

Built in a night, on my phone, and it's one of my most important apps.

Within 12 hours, a concept became a working application two people now rely on daily. What started as a way to track farmhouse projects has grown into how we manage all three properties. The shore house and rental each have their own maintenance cycles, seasonal prep, and schedules to stay on top of. Having everything scoped by property means we always know what's due, what's been spent, and what's next — without mixing contexts. It opened up the ability to ship my own products without needing an engineer or years of learning to do it. I can build and deploy tools now that extend my role and what I'm capable of.

Figma Files Opened

Properties Managed

Concept to Live PWA

Days in Active Daily Use

“

I'm realizing I'm working less in Figma and working directly with Claude through everything — from the color palette, to the user journey, to tweaking the UI. All of this was done through Claude and mostly my mobile device.

— Jesse Szygiel

2026

#What I Learned05

“With the right structure and file organization, removing Figma from the workflow didn't remove the design thinking, it just made the tedious work a lot faster through simple conversation.”

Working with AI to build the experience, design system, and deployment through conversation is a shift in my approach that's genuinely exciting. It lets me focus more on the solution and less time positioning containers and exploring colors manually. It also pushed me into parts of the stack I hadn't touched before. Things that felt out of reach a year ago have a much lower barrier now.

Back to Work

PERSONAL2026DESIGNER, DEVELOPER, USER< 12 HOURS