Open Blog CMS
A Payload 3 and Next.js CMS built for non-technical marketing teams, with SEO capabilities built into the publishing workflow.
View on GitHub ↗I build products, and the systems that make them grow. I bring product strategy, growth, and go-to-market together. I define who we are building for and what problem is worth solving, then shape the product, positioning, pricing, activation, and retention around it. My best work happens where market insight, product decisions, and user behaviour meet.

I turn ambiguous customer, market, and technical problems into products, from consumer experiences and AI systems to APIs, cloud infrastructure, and identity platforms.
I design activation, retention, pricing, lifecycle, and experimentation systems that move users from first value to repeat usage and revenue.
I define ICPs and buyer segments, shape positioning and category narratives, and carry them through launches, content, sales enablement, and the feedback loops that influence what gets built next.
I translate complex products across AI, APIs, identity, and infrastructure into positioning, developer-facing messaging, technical content, comparisons, category education, and launches without flattening the technical detail.
I shape enterprise GTM around ICPs, buying groups, security and integration requirements, packaging, proof points, competitive positioning, and the narratives needed to move technical products through longer, multi-stakeholder buying cycles.
I turn product, market, customer, and competitive insight into pitch narratives, battlecards, objection handling, use-case briefs, ROI stories, competitive one-pagers, and account-specific messaging that help sales explain where the product wins and why.
I am a product leader who has always owned more than the roadmap. I started in product marketing, learning how to identify the right customer, understand what they value, and shape how they adopt and pay for products. That foundation has stayed with me as I moved deeper into product, defining ICPs and buyer segments, shaping positioning, building 0→1 products, designing activation and monetisation systems, and carrying launches through adoption and retention.
My edge is holding both ends at once: the market and the product, the architecture and the experience, the API contract and the user motivation, the data signal and the human reason behind it. I move from deciding who we are building for and what problem is worth solving to shaping what gets built, how it reaches the market, and why users keep coming back.
I scope, design, and vibecode small products across content, launches, sales, and product marketing. Three are open source.
View GitHub profile ↗A Payload 3 and Next.js CMS built for non-technical marketing teams, with SEO capabilities built into the publishing workflow.
View on GitHub ↗An AI assistant that studies historical Product Hunt launches, recommends launch strategy, identifies relevant supporters, and creates launch playbooks with post-launch analysis.
View on GitHub ↗An AI-powered sales enablement assistant that turns internal documentation and product resources into account-specific battlecards.
View on GitHub ↗A prospecting tool that identifies the authentication provider used by an application, helping sales teams tailor outreach and competitive positioning.
View on GitHub ↗Negative net MRR churn was hiding 46.79% first-month churn. Cohort behavior exposed the problem and became an early-warning retention system.
Productising an internal generation engine into a partner-ready API exposed hidden assumptions across quality, reliability, developer experience, and observability.
A scenario-led pricing decision balancing ARPU upside against conversion, retention, expansion, annual mix, and downside risk.
Checkout completion was healthy. The real monetisation bottleneck sat one step earlier, in getting high-intent users into checkout.
Behavioral signals around character ownership, message depth, UGC, and image generation reshaped the product roadmap and retention loops.
A shared operating model connecting onboarding, activation, engagement, adoption, conversion, retention, and feedback.
Companion pieces to the case studies: one interactive retention model and one engagement diagnostic framework.
A rule-based early-warning system translating first-month behavior into risk bands and persona-specific retention interventions.
Try the model →A diagnostic model separating session, action, value, and repeat behavior to identify where engagement is actually breaking.
View framework →I define the ICP, buyer segments, and problem worth solving using customer conversations, market research, product data, and behavioural signals.
I translate what I learn into a clear outcome, product hypothesis, scope, trade-offs, success metrics, and the smallest credible version worth shipping.
I shape the experience, positioning, pricing, launch, sales enablement, lifecycle, and instrumentation alongside the product, not after it is built.
I track activation, adoption, retention, and revenue to understand what is working, then improve, expand, reposition, or stop.
I pull funnels, session replays, and cohort drops before forming any hypothesis. But numbers tell you what, user context tells you why. I don't move without both.
If a feature needs a lot of explanation at launch, something went wrong in discovery. I look for behavior that's already happening and remove the friction around it. The best ideas are usually hiding in what users are already doing.
Before full scoping, I look for a zero-eng or one-day proxy. If users don't respond to the proxy, they won't respond to the feature either.
Prompt pipelines, model evaluation, API architecture. Every choice at that layer shapes what users experience. I treat those choices like any other product decision.
Paywalls that feel punishing kill retention. The best upgrade moments feel like a natural next step, designed for the moment a user feels value, not the moment it's convenient for the business.
Activation metrics are vanity. D1/D7/D30 retention before celebrating any launch. A feature that brings users back is worth 10 features that only acquire them.
Selected articles on products, technology, and the systems behind them.
Seven real-world failures that show how agent permissions, secrets, tools, and identity break in practice.
How Cedar expresses authorization rules, why it goes beyond static scopes, and where policy-based access fits.
A practical guide to authentication choices, sessions, tokens, route protection, and implementation patterns in Next.js.
I'm always happy to connect with people building interesting things. I am interested in Product Marketing, Product Manager, and Product Growth roles, as well as collaborations and good conversations about users, growth, and what makes products work.
Selected articles on products, technology, and the systems behind them.
A step-by-step explanation of the authorization code flow, the roles involved, and why it remains the standard choice for many web applications.
Seven real-world failures that show how agent permissions, secrets, tools, and identity break in practice.
An accessible overview of OAuth 2.0, its core roles and grants, and how to decide when it is the right authorization framework.
A practical comparison of identity verification and access control, with examples of how the two work together in real products.
A clear guide to JWT structure, signing, validation, claims, common use cases, and the security mistakes teams should avoid.
How Cedar expresses authorization rules, why it goes beyond static scopes, and where policy-based access fits.
A practical guide to authentication choices, sessions, tokens, route protection, and implementation patterns in Next.js.
Case studies across AI platforms, consumer products, B2B APIs, SaaS monetisation, fintech, and growth.
Fableverse launched with curated story scenarios. Users had other ideas. I followed the behavioral signal, character ownership, message depth, image generation, and rebuilt the product arc around what was actually driving retention.
The Scene Engine worked perfectly for Fableverse because we knew where all the edges were. I productised it for external chat platforms, and every partner integration revealed an assumption we hadn't known we were making.
Before the Scene Engine could power external partners, it had to become a real platform. I built the quality systems, prompt infrastructure, and training pipeline that turned an internal experiment into something accountable to paying clients.
UGC wasn't the original plan. Users showed us that ownership drove retention more than anything we'd designed. The creation avatar became the seed image for generation — connecting the consumer product and the AI platform in a way we hadn't anticipated.
Trial-to-paid was stuck at 14%. Session data revealed two completely different user types being forced through the same flow. I built behaviorally-routed parallel paths — and the high-intent cohort had 83% higher ARPPU than before.
Users were leaving the platform for 45–60 minutes to use ChatGPT and Canva. The first AI Writer flopped because of blank-input anxiety. A pill-based prompting system fixed the entry point and drove $17.8K MRR within 60 days.
Fewer than 8% of free users were ever reaching premium features, not because they weren't interested, but because the paywall was in the way before they had any reason to believe it was worth paying for.
Our three plans had no clear story connecting them. I rebuilt the architecture around a hero plan, introduced modular add-ons, PPP-adjusted regional pricing, and a mobile-specific plan, 78% of paying users ended up on annual subscriptions.
Negative net MRR churn was hiding 46.79% first-month churn. Cohort behavior exposed the problem and became an early-warning retention system.
A scenario-led pricing decision balancing ARPU upside against conversion, retention, expansion, annual mix, and downside risk.
Checkout completion was healthy. The real bottleneck sat one step earlier, in getting high-intent users into checkout.
A shared operating model connecting onboarding, activation, engagement, adoption, conversion, retention, and feedback.
Exit-survey data became six churn segments, reason-specific treatments, and a 21-day recovery program instead of one generic win-back email.
Completion events looked healthy, but retained users behaved differently. Activation was rebuilt around the behaviors associated with repeat value.
A healthy-looking 5:1 ratio changed meaning once 8.5% monthly churn and a 2.4-month payback were read together.
Competitive research across five products reframed the question from plan prices to the unit of value customers were being asked to buy.
Product Manager · Platforms, APIs & Consumer Products · 0→1 Builder · 8+ years
Built the Fableverse AI platform from 0 → 150K+ users, leading 0→1 development of the image generation infrastructure (~1,000 images/day), internal model training and prompt intelligence systems, and APIs enabling external chat platforms to generate context-aware images.
Led product roadmap, monetization, and activation initiatives across web and mobile, contributing to $2M+ ARR. Owned feature delivery, lifecycle design, and PLG motion for a 25K+ MAU creator SaaS, combining user research, cohort analytics, and GTM execution.
Frameworks I think with. All run in the browser, no data saved. Try them.