I work with software company CEOs whose product-market fit isn’t coming together - whether they built something that worked and the ground shifted, or they’re trying to get to fit for the first time. I’ve navigated five technology shifts across 30 years. GenAI is the sixth, not the first.
Engineering, product, executive - three genuinely different disciplines, each in its full depth. Chief architect. VP Product. CPO. CPTO: both at once. CEO. Four exits. Multiple turnarounds. Across companies from scrappy early-stage to acquisition-ready.
Most advisors see one slice - technical, product, or business. Three disciplines in full depth makes it possible to hold all of them simultaneously, without losing resolution when the conversation moves between them.
Sometimes that’s as a thinking partner - privately, on your side of the table, no stake in the answer. Sometimes the situation calls for stepping inside and leading product or engineering directly. The common thread is product-market fit: finding it, losing it, re-finding it.
Draft of a Pattern for when founder-led product stops scaling
What happens when companies expand their product offerings and their product operating system doesn’t keep up? One intervention is to establish explicit decision ownership, avoiding governance bottlenecks and ensuring clear accountability for outcomes.
v2 of simple d3 with Meteor - now rendering individual records
A second simple example of integrating D3 with Meteor, demonstrating reactive data syncing to visualize changes in a collection using circles.
Simplest d3 + meteor example I could make
A simple example demonstrating the integration of Meteor and D3, leveraging reactive data between client and server