I build AI products.
I help founders
build theirs.
Senior AI product strategy for growth-stage companies. Advisory relationships with a small number of founders at a time.
The problem is almost never the model.
It is the layer underneath: context architecture, behaviour design, and the trust logic that makes outputs usable in the real world. Most founders discover this after shipping. That is when they call me.
AI product strategy
I work with founders on the decisions that shape whether AI becomes load-bearing in their organisation or runs quietly in the background. Architecture, behaviour, character, trust logic. The whole structural layer.
Ongoing advisory
For founders who want a thinking partner across product and AI decisions, not a sprint and a handover. I take a small number of retainer relationships at a time.
Context Architecture Sprint
Fixed scope, fixed price. A structured diagnostic for founders who want to understand exactly what is wrong before committing to something larger.
Right fit if
- You have shipped an AI product and it is not changing how anyone operates
- Your team knows the model is not the problem but cannot name what is
- You want someone who has built production AI products, not someone who advises on them from the outside
- You are looking for a thinking partner, not an implementation team
I build multi-stack agentic AI products and advise founders on how to build theirs. I have been building with AI since before the current wave, and I think about it at the intersection of product design, organisational behaviour, and what makes people trust a system. I work with a small number of founders at a time. Direct access, not a delegated team.
GAICD · BCom/Econ, Melbourne University · PG Diploma Music, AFTRS · Based in Sydney
Full bio →I treat context as infrastructure. Most teams stop at prompts. I build the structured context, role logic, source hierarchy, and judgement design that make an AI system usable beyond a demo.
Most engagements run four to eight weeks.
I will show you how I think before you commit.
Not sure where to start?
The Context Architecture Sprint is a fixed-scope, fixed-price engagement. Four to twelve weeks. A full diagnosis of what is wrong with your AI product, a concrete architecture map, and a clear path forward. A good place to start before committing to an ongoing engagement.
View the Sprint →I also build self-serve products: The Conductor and Cielo.
Who do you work with?
Founders and leadership teams at growth-stage companies, typically past the proof of concept stage and dealing with AI that works technically but is not changing how the organisation operates. I work with a small number at a time.
What does an engagement deliver?
Concrete deliverables: a context architecture map, behaviour and character design documentation, trust boundary specifications, and handover artefacts your team can build from. You leave with a system, not a report.
What does it cost?
Advisory retainers and the Context Architecture Sprint are both available. The sprint is fixed scope and fixed price, the right place to start if you want to understand the problem first. Retainer arrangements are scoped individually. Get in touch and I will tell you which fits what you are describing.
How is this different from hiring a prompt engineer?
A prompt engineer optimises what the model says. Context architecture designs what the model knows, when it knows it, and how that shapes what users trust it to do. The problem is almost never the prompts. It is the structural layer that the prompts are trying to compensate for.