Inquiries

Open To Work

I build the software that runs your operation. Early ideas, first versions, and second versions. Below is how I work and what I'd need from you. If you'd rather just talk, that's the first option.

Full time or contract. I'm looking for a full time role with a San Francisco team, and I'm patient about finding the right one. While I look, I'm contracting. Tell me which one you're here about and we'll start there.

Three ways to start

Pick the lightest one that works for you.

Book 20 minutes. A conversation, not a pitch. You describe what you're working on and I'll tell you what I think, whether or not we end up working together.

Loading calendar…

Email me. If you'd rather write a few sentences and see where it goes.

Send the form. At the bottom of this page, if you want to lay it all out at once.

What I help with

Early stage. You have an idea and no clear shape yet. We work out what the product should be, which technologies are worth committing to, and what the plan looks like. You come out of this with something you can put in front of customers and learn from.

Minimum viable product. Are customers ready to pay you? This is the simplest usable version of the thing someone would hand money over for. Designs help, but we can scope it together if you don't have them.

Product iteration. You have something already and want it to be better, faster, or newer. I'll audit what exists, find the growth areas, and ship changes.

How I work

Days 1 to 10. Find the real problem.
We talk at the start and end of every day. I sit with your team, your product, and your customers, and write down what's actually going on. You get a document you can hand to anyone.

Day 10. The recommendation.
Two or three directions worth taking, what each would take to build, and my pick with the reasoning behind it. You can stop here and take the document anywhere.

Weeks 3 and on. Build.
We choose two or three and I build first versions you can put in front of real people.

What I need from you to get started

Thirty minutes a day, at the start and end. This is the part that makes the rest work.
One person on your side who can answer questions without scheduling a meeting first.
Access to whoever actually makes the call on what gets built.
Whatever already exists: designs, docs, code, customer notes, a messy Notion. Messy is fine. Nothing is also fine, it just changes where we start.
Permission to tell you the problem is different from the one you brought me.

I'm not the only person you get

I come from an entrepreneurial family and friend group: founders, operators, designers, and engineers who have built and sold things. When something falls outside what I do well, I usually know who to ask, and I'd rather point you to the right person than pretend.

Who this is not for

If you need the polished, finished version on a small budget, I'm the wrong person and I'd rather say so now. What I build first is a start. Its job is to get you the conversations that actually matter, and those conversations usually change what the finished version should be.

Technologies

Web and mobile applications. React, React Native, and Expo. The product your customers see, and the admin panels and dashboards your team needs to actually run it.

Backend services. Serverless, Node, Python, Ruby on Rails, and others.

Infrastructure and data. AWS (S3, CloudFront, Lambda), Vercel, Supabase. PostgreSQL, DynamoDB, SQL Server.

Native applications. iOS and macOS, when a product genuinely needs them.