First proof
10+ years shipping mobile products · a desk, not a brochure
What's on your desk that a customer still can't open?
Go on. The answer is a tap.
Don't write a pitch. Tap the job that matches — then a few easy questions. You leave with time, a cost band, and a brief I can reply to.
The room
Where did shipping actually stop?
One tap. No email. If you have a line the next founder should hear, pin it — it stays on the wall.
Tap the honest one. Then leave a line if you have it.
Public, anonymous, 140 characters. No abuse, no links, no spam.
Today on the desk · daily note
AI
An agent that cannot be replayed is a demo.
One tool, a log, a human fallback. Then we talk about write-access.
A one-minute game
What would you do first?
Read the short story. Put three cards in Do first and three in Leave it. Then see how I would sort the same six.
- 01Read the story
- 02Sort every card
- 03See my pick
Today’s story
Every Friday is a spreadsheet
A US ops lead pastes a CSV into Google Sheets. She wants “an AI product.”
Do firstThis week0/3
People need this before anyone else can try it.
- Empty
Leave itNot yet0/3
Nice later. It can wait.
- Empty
Upload the file and get the same report
A link her boss can open
Keep last week’s report without breaking this week
A chat that “explains the business”
iPhone and Android apps
Company login for 400 people
Quick vote
Where is AI in your project right now?
One tap. Counts stay public. No name, no email.
Already live
If people are already using a rough version?
The real block
What is slowing you down?
A decade in mobile, not a slogan
Tap a chapter. See what those years were actually for.
Store listings, crash reports, Flutter, now AI. Same habit: ship something people can open.
2023–now
Web, AI, and rescue
Same shipping habit, more surfaces: Next.js products, AI in the repo, agents that do a job, and vibe-coded apps that need a senior person before a customer sees them.
Ten years of mobile. The new work is making AI useful without creating a second, worse codebase.
Field school
Before a customer opens it, I check five things.
Tap what’s true on your product. Each tap teaches the lesson those ten years were actually for — then you get a plain read of where to start.
Mark all five. Then I’ll tell you where I’d start.
Pick the job
What are you actually trying to ship?
Three honest paths. Tap one. You get the week-one tasks I would run — then a quote if it still fits.
01 · Mobile
Something people can install this month
An idea, a Figma, or a half-finished Flutter repo — and no clear path to TestFlight / Play.
I pin the first slice, the stack, and the store work. You get a clickable build, not another prototype on a laptop.
Week-one tasks
- 01Name the user and the one job the v1 must do
- 02Freeze screens: auth, home, the money path, settings
- 03Pick Flutter or native for a reason, not a trend
- 04Ship to TestFlight / internal testing in week one if the repo exists
- 05Store listing, crash reporting, and a handover you can keep
Not this
- — An unbounded MVP
- — A redesign of the whole brand
- — Six platforms on day one
Play with the budget
Pick a band. See what you actually walk away with.
Not a price list to game. An honest split of what a number can and cannot buy — then send a quote if it still feels like a fit.
You get
- — One milestone with a finish line
- — Staging you can click in days
- — Auth, data, or a production harden pass
You do not get
- — An unbounded MVP
- — A 40-tool copilot
- — Brand identity and illustration
How it works
A process you can brief in one sitting
01
Scope the real job
A short call or written brief. We pin down users, must-haves, budget band, and what “done” looks like. If it is not a fit, I will say so.
02
Quote a clear path
You get a written plan: milestones, stack, what I will ship, and what it costs in USD. No open-ended “we will see”.
03
Build in the open
Weekly progress you can click. Staging links, not slide decks. You always know what landed and what is next.
04
Ship and hand over
Production deploy, analytics, and a handover. Stay on for a sprint of support, or I step back cleanly.
FAQ
Straight answers
Who do you work with?+
Founders, operators, and small product teams in the United States, United Kingdom, Canada, and Australia. Most clients are remote. I overlap US and UK working hours. I have shipped mobile products for 10+ years — App Store apps you can open today.
What can I hire you for?+
Web and mobile product builds, AI-assisted coding on a real codebase, AI agents inside a product or internal workflow, and vibe-coding help when you are building fast in Cursor and need a senior person to keep it shippable.
How do projects start?+
Send the form or book a 20-minute call. I reply with fit, a suggested path, and a quote in USD. Typical start is a paid sprint or a fixed-scope build — not an open retainer on day one.
Do you replace my developers?+
No. I can be the builder, the technical partner next to your team, or the person who reviews AI-generated work before it hits production.
What does it cost?+
Focused sprints typically start around $2,500. Product builds and agent work are quoted after scope. See the pricing page for ranges — I will not invent a number before I understand the job.
More on pricing, AI agents, vibe coding, and notes. Need a number? Leave a brief at the bottom.
Leave it on the desk
Write the job. I will quote it in USD.
Name, email, and the job. I'll reply by email.