Skip to content
James McKinney

Open to product & solutions rolesRemote or relocation

I spent ten years three feet from the customer.Now I build for them.

Ripple showing how a news story affects the reader's life
Ripple · Personalized news

I learned how to lead, prioritize, and solve customer problems 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 for a customer-facing role where product judgment and hands-on problem solving meet.

10+
products shipped
20+
people led
11
sources in one AI pipeline

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 holding nearly every management role: floor, bar, scheduling, kitchen, and assistant general manager. The work included hiring, training, schedules, inventory, budgets, vendor orders, performance reviews, and customer complaints.

Demand exceeded capacity

Open tables did not mean we could serve them

An incorrect forecast left a weekday shift short-staffed when the restaurant suddenly filled. I started a wait with tables still open, let the kitchen and servers recover, then reopened the patio one or two tables per server.

Result: the team stabilized, servers made good money, and guests who stayed thanked us.

The metric could not be trusted

Fix the inventory data before judging food cost

I found products recorded in the wrong quantities. A ten-pound case might be counted as seven. I corrected the inputs, tracked waste, ordered against sales, and worked to retain the experienced staff who kept waste down.

Result: first or second in food cost across six locations.

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.

Teams of 20+1st or 2nd in Food Cost, 6-Store FranchiseOpen Tables, Controlled Wait

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.

3 Years on One Bet80–90 Hour WeeksCalled It

04 · 2024–

How I build

AI helps me build software. Product judgment is still the work.

Most ideas start with something I notice: a complaint, an awkward workflow, or an existing product that feels one feature short. I search the App Store for alternatives, then ask Claude or ChatGPT to challenge the idea. I want the reasons it could fail, not automatic encouragement.

  1. 01

    Notice

    Start with a complaint, awkward workflow, or missing feature.

  2. 02

    Challenge

    Research alternatives and ask AI to make the case against the idea.

  3. 03

    Scope

    Define the user, the central feature, the screens, and the business model.

  4. 04

    Build and test

    Run it on real devices, inspect failures, revise, and decide whether to ship.

When something fails, I read the build error or inspect the Xcode, n8n, or Supabase logs. I give that evidence back to the AI, ask it to explain the cause, test the proposed fix, and keep going until the real behavior changes. I do not understand every error on sight, but I know how to investigate one.

AI helps with research, planning, code, debugging, and creative work. I own the product decisions, quality bar, testing, release, marketing, and the outcome when an idea does not work.

10+ Shipped / 12 Months50+ Folders, Most Dead at 80%2 Months Built, Then CutThe Water Found a Home · Top of This Page

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.

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.

06 · More work

More shipped products

The rest of the index, with the decisions and numbers inside each case study.

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 customer-facing role between people and the product. That could be product management, product operations, solutions, implementation, or an early-stage role where the boundaries are less rigid. I want to hear what customers are struggling with, help define the answer, and work with a team to make it real.

My route into technology was not traditional. It gave me more than a decade of customer-facing judgment and operating responsibility before I opened Xcode. I have led teams, filled whatever role the shift needed, and learned when to make the call and when someone else has the better idea.

I do my best work around other people. I can build alone, but ideas get better when they are challenged by someone equally invested in the outcome. Collaboration is the part of work I miss most.

Remote works. So does relocating for the right team.

The rest of me is on the shelf.

James McKinney