Talk through your project.

Fifteen-plus years building native iOS apps, with 150+ clients on everything from small MVPs to products used by tens of millions. Before that, a decade-plus in VP-level IT and business leadership at Activision Blizzard, Vertafore, and Adaptive Biotechnologies. The combination matters — I think about apps as products and businesses, not just code.

Most senior iOS developers came up through engineering. I came up through enterprise IT and spent more than a decade in VP-level leadership at companies like Activision Blizzard, Vertafore, and Adaptive Biotechnologies before returning to hands-on development full-time. So the consultation isn't just code judgment — it's product strategy, monetization, App Store experience, and an honest read on whether an app is even the right move for your situation. Most apps don't fail for technical reasons.

Yes — it's one of the most common reasons people book. Whether you're stalled mid-build, working with a developer you're not sure you trust, or trying to evaluate AI-generated code before you ship it, the consultation is built for that. Bring code, screenshots, contracts, anything you want to talk through. We'll work with what you have.

Yes — and this is the ideal time to talk. Most of the costly mistakes in app development happen in the first few weeks, before any code gets written: the wrong platform, the wrong contract, the wrong developer, an unrealistic timeline. An hour at this stage saves money, time, and frustration later. You don't need to know what you don't know going in. That's the point.