I've navigated five technology system transitions across 30 years. Now I work with revenue-stage SaaS CEOs on the AI transition - privately, as a thinking partner, with no agenda but theirs.
Engineering, product, executive - three disciplines, full depth. Chief architect. VP Product. CPO. CPTO. CEO. Four exits across every stage.
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.
The CEOs I work with have read everything worth reading. The gap isn't information — it's that none of it maps onto their specific situation, and they've run out of people who can help make that translation without an agenda.
A lens drawn from Carlota Perez
A lens drawn from economic historian Carlota Perez’s work on how technology changes in waves — not all at once. The current information age has already produced five technology systems (personal computers, web, mobile, SaaS/cloud, tech-enabled services); GenAI is the sixth. Each time a new system ascends, companies fit for the prior one find themselves post-PMF in the old system and pre-PMF in the new one simultaneously — which is a recognizable condition, not an unprecedented one.
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.