
Open to product rolesRemote or relocation
I spent ten years three feet from the customer.Now I build for them.
I learned product judgment by working every position in a restaurant, then managing teams of 20+. Since 2024, I’ve shipped iOS apps, a SaaS, and a Shopify app. Now I’m looking to bring that customer instinct and hands-on product work to a team.

Selected work
Three products, three different decisions
The full case studies include the tradeoffs, the numbers, and what I would change.

Ripple
Turned an 11-source news pipeline into briefings that explain what a story means for one reader.
7 months · iOS · AI pipeline

FILL
Built with a working electrician, then simplified around gloves, glare, and the calculations he repeats on the job.
31 active devices · field collaboration

Grove
Used cancellations and onboarding behavior to reshape a two-day build instead of defending the first version.
#92 → #19 for “fiber counter”
02 · 2010–2020
Over a decade on my feet
Restaurant work taught me to notice the customer, the team, and the problem that will matter five minutes from now.
I worked every position in a restaurant before I managed one: kitchen, bar, floor, and everything in between. A shift only works when people understand how their decisions land on everyone else.
On one Sunday opening, a grill had been left on high all night with no hood running. A coworker and I spent three and a half hours clearing smoke and wiping soot from every surface. Then I ran the floor until the evening manager arrived. What bothered me most was what a customer might walk into.
Managing meant P&L, scheduling, training, and getting more than twenty people through a Friday rush. It also meant jumping into someone else’s station, taking direction when they knew it better, and making a call when the room needed one.
The best shifts were never one person carrying the room. They were a group noticing what the others needed. I know how to lead that kind of team, and I know how to be part of it.
COVID ended that career in the spring of 2020, and I’ll be honest: I was ready for a change. The part I still miss is the crew.
03 · 2021–2024
The in-between
Two businesses taught me to separate effort from evidence.
What came next wasn’t software. I ran a t-shirt brand for a few years. It made sales when I fed it ad money and 80- or 90-hour weeks. The underlying math never improved, so I ended it.
I also spent a stretch of those years developing a protein bar with my brother. Hundreds of store-bought bars taste-tested, dozens of recipes. It never launched. I liked the customer and product work far more than the idea of running the operation.
I learned to ask a plain question: if I were seeing this work for the first time today, would the evidence justify another month? Sometimes the honest answer is no.
04 · 2024–
How I build
AI helps me build software. Product judgment is still the work.
I grew up around computers and wanted to work in tech for a long time. AI finally gave me a practical way to learn by building products people could actually use.
My first setup was ChatGPT in one window and Xcode in the other: ask, test, read the error, try again. The tools have improved since then, and so has my understanding of the systems underneath them.
AI helps me write the code. I still have to understand the customer, define the product, choose the tradeoffs, test the edge cases, price it, ship it, and support it afterward.
AI helps me move faster.The product decisions are still mine.
Ten-plus products shipped in about a year. What that number doesn’t show is the folder on my Mac holding fifty-some projects, most of them dead at 80 percent built. They died because I did the customer math and it didn’t work out, and finishing is the expensive part.
The shipped products are easy to count. The more useful work was often deciding what not to finish.
The best example cost me two months. I wanted Ripple’s button to send a literal water ripple across the screen. I built it.
I paused the whole app at one point because I couldn’t get it right. When it finally worked, I realized it was still wrong for a news app someone might open ten times a day. I cut it.
05 · Convictions
How I make product decisions
Four questions that show up across the work.
They are not a framework so much as a way to stay honest about what the product needs.
What can I remove?
takt has no accounts, streaks, or gamification. Grove tracks one nutrient instead of forty. More features would make both products less useful.
Does the technology help the task?
Ripple does not ask users to care which model is behind it. It asks about their life, then uses that context to explain why a story matters to them.
What changed after people used it?
TelemetryDeck showed people leaving Grove’s onboarding, so I rebuilt it. The first version is a hypothesis, even when I like it.
Has this earned more time?
Echoes stayed a private test bed. Wandering Bacon proved its concept and was wound down. Continuing is a decision, not the default.
I move quickly, but I still want to be able to explain every decision to the person using the product.
06 · The work
The evidence
Ten-plus shipped products. Real numbers, including the unflattering ones.
The shipped case studies carry the real numbers: the flattering ones and the other kind. New work appears here before launch too.
Ripple News
Most news apps organize the world by publisher. Ripple organizes it around you.
Tell it who you are (your work, your town, who’s in your house) and when a story breaks, the Ripple button shows how it reaches your life.
Not a summary. The consequences, for you. I don’t know of another news product that does this.
Under the hood it’s SwiftUI, an 11-source pipeline running through n8n, Supabase, and OpenAI doing the reasoning, with the paywall on RevenueCat. Seven months from idea to App Store, counting the two I spent building an animation I later cut.
“This app is so legit. I want to consume all my content in this form. ‘See the Ripple’ is so fresh, and an amazing use of my info and location.”
The index

Grove
fiber tracker. Idea to App Store in two days; one subtitle change moved it from #92 to #19 for “fiber counter.”
#92 → #19 in search
iOS · ASO · Subscriptions

takt
a pomodoro timer that refuses to do too much. The first app I shipped, and where I learned how much taste matters.
The first one
iOS · Design

FILL
NEC conduit-fill calculator, built with a working IBEW electrician. Designed for a gloved hand in the sun.
Built with an IBEW electrician
iOS · Freemium

Tip Out
tip splitting for restaurant crews, from my old life. $4.99 once, no subscription, because it costs me nothing to run.
2 days to ship
iOS · One-time pricing

Mixtape
send a friend songs like it’s 1995. The 24-hour wait was on purpose. So was retiring it.
Retired on purpose
iOS · Product Hunt

Yapper
an AI phone receptionist for the trades. My distribution experiment, running in public.
Running in public
SaaS · Voice AI

RentalFlow
rental management inside Shopify, built for my brother’s store first.
Live on Shopify
Shopify · B2B

Echoes
voice notes that transcribe themselves. Never shipped, on purpose; it was the test bed.
The test bed
iOS · Never shipped
07 · The Ask
Now
A year of building, a year of distribution, and the ask: a team.
This past year I mostly stopped starting new things. I picked three products and worked on distribution: ASO, search ads, cold emails, and even postcards to plumbers. Shipping was only the beginning.
I can build a product alone. I do not want to build my career alone.
I’m looking for a product role on a team that starts with the user, ideally where AI is useful to people who do not care about AI for its own sake. My route here was not traditional. It gave me a decade of customer-facing judgment and operating responsibility before I ever opened Xcode.
I have led teams, worked for other people, and filled whatever role the shift needed. I know when to make the call and when someone else has the better idea. Collaboration is the part of work I miss most.
Remote works. So does relocating for the right team.

