Go-to-market for AI products, with a technical partner to harden the product itself.
An AI product that works in a demo is a long way from one that can be sold. The gap is usually some combination of an unproven revenue model, an unclear picture of who the user actually is, policy and regulatory questions nobody has worked through, and product decisions that only become visible when you try to take it to market.
I work on applications from that point forward, and I have run the same process on products I have helped build myself.
Assessing the market and the user, building and testing the revenue model, working through the policy and regulatory questions, and identifying the product blocks standing between where the application is now and a launch anyone will notice. Then the plan for getting it picked up and attracting the users it needs.
Part of the work is deciding whether a product should proceed at all. One consumer application I assessed had a workable product and a regulatory path expensive enough that the honest answer was not to build it. Reaching that conclusion early is worth more than a launch plan for something that should not launch.
Where a product needs work before it can go to market, I bring in a technical partner to harden the build while I take the go-to-market, the revenue model, and whatever else is missing. It means a prototype can reach launch without the founder assembling a team for it, and it is how I extend into product work without pretending to be an engineer.
Every engagement runs with AI in the workflow, primarily for sequencing and structuring outputs — carrying a single narrative consistently across a deck, a whitepaper, a website and the posts that follow, and rebuilding documents that have drifted out of shape.
What it does not do is supply the substance. The thinking, the positioning, and the judgement come from our work together, and the work only speeds up once those exist. Used the other way round, it produces a great deal of material that says nothing.
An application currently in development, where the work is identifying the product blocks and building the route to users.
A short call is usually enough to know whether this is a fit. If it isn't, I'll say so and point you somewhere better.
Tell me what you’re building