BUILT BY REFUSING TO SETTLE

THE PROBLEM

I oversee IT & Logistics at a Design Build general contractor. I help shape our processes and workflows, keeping us AI-driven and efficient. My team uses JobTread every day to run jobs, track budgets, and keep projects on schedule. It's a great platform — but there were things that drove me crazy.

Formatting text in budget descriptions? Copy-paste from somewhere else. Checking off tasks from the schedule view? Open the task, scroll down, click complete, navigate back. Every. Single. Time. A dark theme to ease eye strain during long sessions? Not an option.

THE SOLUTION

So I built the fixes myself. A Chrome extension that adds the features my team needed — drag and drop for the schedule, a text formatter, task checkboxes right on the calendar. Small things, but they saved us real time every day.

Then I realized: every team using JobTread has these same pain points. What started as internal tools for my team turned into something bigger. I added dark mode, a job switcher, budget hierarchy shading, quick notes — features that any construction team could use.

THE REALITY

I have a full-time job. I have three kids, all six and under. This isn't a venture-backed startup with a team of engineers. It's one person building in the margins — early mornings, late nights, nap times.

I build JT Power Tools with Claude Code as my development partner. AI handles the heavy lifting on code architecture while I focus on knowing exactly what construction teams need — the same AI-driven approach I bring to my day job. It's a workflow that lets a solo developer ship features at a pace that shouldn't be possible.

Five months in, we're at 20 features, 40+ releases, and 400+ users. Every feature exists because someone on a job site said "I wish I could do this." That's still how it works.