Consulting
Sometimes you don't need me to build it.
You need someone who has shipped it before to tell you what's worth building, what to cut, and what it will actually take. Or you need the operations side: how your team runs, documented, standardized, and improved.
The problem
Most advice comes from people who don't operate anything. Agencies advise you to buy what they sell. Frameworks arrive in a slide deck and leave with the consultant.
Meanwhile the real questions stay open: is this worth building, why is quality inconsistent, where should AI actually fit, and what should be written down so the business runs without heroics.
How I consult
I run my own companies: a healthcare services business, this studio, apps in both app stores, and a portfolio of content brands. The systems I recommend are the ones I operate on.
You get specific, written recommendations your team can execute, whether or not you ever hire me to build anything.
Two kinds of engagements
Build advisory
For founders and teams deciding what to build and how.
- Scoping a new product and cutting it to a real first version
- Choosing a stack and the build-versus-buy calls
- Planning an app store launch
- A second opinion before you spend real money
Operations consulting
For owners and teams whose delivery depends on process that lives in people's heads.
- Process assessment: how work actually flows, and where it breaks
- SOP libraries with owners and review cadences, in one home
- QA frameworks and quality standards your team can hold
- AI tools placed where they genuinely help, with usage guidelines
- Reporting that gives owners a bird's-eye view without more meetings
How it runs
A conversation
We get on a call and get specific about what's actually going on. I'm honest about whether I'm the right person for it.
Assessment
I read the current state for real: the plan, the code, the process docs, the tools, how work moves through your team. Findings come back written, ranked, and specific.
Recommendations
What to do, in what order, and why. Written so your team can execute it without me in the room.
Execution, if you want it
Hand the plan to your team, or have me build and document the pieces that make sense. Either way you own the deliverables.
Common questions
What does an engagement look like?
It scales to the question. Some engagements are a single call and an honest answer. Most are a short assessment followed by written recommendations, and larger ones run in milestones with deliverables like SOP libraries and QA frameworks. Scope and price are set before I start.
Do you only consult on software builds?
No. About half of this work is operational: how your team runs, where process lives, what gets documented, and where AI tools genuinely help. I advise on the same systems I use to run my own companies.
Will you tell me if my idea isn't worth building?
Yes. That conversation is cheaper now than after you've paid for a build. If the honest answer is a smaller version, an off-the-shelf tool, or waiting, that's the answer you'll get.
Do you work remotely?
Yes. I'm based in St. Louis and work with clients nationwide over video, with written deliverables you keep.
What happens after the recommendations?
The recommendations are written so your team can execute them without me. If you'd rather I build or document some of it, that becomes its own scoped project, and there's no obligation either way.
Bring me the question you're sitting on.
A scoping question, a quality problem, a process that only works when one person is in the building. The first conversation costs you nothing.