Work with me
Find the growth constraint before you spend around it.
I help B2C and subscription app teams diagnose where growth is actually breaking, then turn that read into a fix path across acquisition quality, UA signal quality, store promise, reviews, onboarding, paywall timing, lifecycle, and the economics underneath it all.
First step
Start with a diagnostic, not a giant strategy deck.
Most teams do not need more growth ideas. They need to know which constraint is binding, which metric is lying, and what has to be true before the next round of effort or spend is worth it. Then they need a fix that changes the system, not another opinion about the dashboard.
What situation are you in?
Choose the closest problem. The point is to find the next decision, not to pick from a services menu.
Launching or about to test paid traffic
You are close to launch, considering paid traffic, or trying to understand whether a paid test will teach anything useful.
Running UA and the result does not make sense
Installs, trials, CPA, ROAS, creative tests, or dashboards look active, but the business result is not following.
Store page, screenshots, or ASO are not producing healthy users
Conversion, rankings, featuring, paid creative, competitor reviews, or post-install behavior do not add up.
Funnel, paywall, or trial quality is leaking
Users say yes, start trials, pass onboarding, or hit the paywall, but the next business signal is weak.
Growth activity exists, but nobody knows the constraint
The team has ideas across acquisition, store, funnel, paywall, lifecycle, or creative, but nobody knows which one is allowed to matter first.
The existing growth machine is not producing the required result
UA, product, monetization, ASO, analytics, lifecycle, and team routines already exist, but the business result is still not moving.
What you get
Constraint map
The likely growth constraint, the evidence behind it, and which surface is probably not the real problem even if it is the loudest one.
Fix path
What to change next, what not to touch yet, and whether the fix belongs in acquisition structure, signal quality, creative, store promise, funnel, paywall, or economics.
Commitment Flow read
A practical read on what the user is being asked to give at each step: attention, data, trust, money, time, and whether the product gives enough back.
Scope boundary
A clean recommendation on whether you need a call, compact memo, fuller strategy, or ongoing advisory instead of accidentally buying the wrong size of work.
What I diagnose
App growth constraint
Where the business is actually stuck: acquisition quality, conversion architecture, retention, monetization, channel fit, or unit economics.
Store promise and ASO
Whether the App Store or Google Play listing attracts demand the product can actually cash, not just traffic that looks good in rankings.
Reviews and trust breaks
What users already say about product friction, false expectations, cancellation, pricing, competitor gaps, and growth opportunities.
UA signal and learning system
Whether campaigns, events, attribution, creative buckets, and optimization signals are teaching the platform to find future customers or just cheaper surface conversions.
Commitment Flow
Where the product asks for attention, data, trust, payment, or repeat behavior before it has earned the next commitment.
How it works
I read the growth path as a sequence of commitments.
The diagnostic looks at what the user is being asked to do next, how heavy that ask is, what proof or value they have received, and which condition breaks first: relevance, desire, trust, or ability. If acquisition is already running, I also look at what the paid system is learning: which users the creative attracts, which events the platform optimizes for, and whether the funnel turns that traffic into payer quality. The output is not "make everything better." It is the smallest useful fix.
Formats
Diagnostic call
A paid first conversation for a directional read, problem framing, and next-step decision. Best when you need senior judgment before commissioning a bigger piece of work.
Compact diagnostic memo
A short written diagnosis with the likely constraint, evidence, priority fixes, and what to test or not test next.
Launch / paid-testing readiness check
A bounded blocker read: whether the current product, measurement, and test setup can teach anything useful. It names the gap and direction; it does not build analytics, campaigns, paywalls, or the testing plan.
First launch testing plan
A practical four-to-six-week sequence for what to test, what to measure, which signal is cheap enough to learn from first, and what would stop the plan.
Review intelligence sprint
A specialist written route after context: App Store, Google Play, or competitor review evidence translated into the product, ASO, positioning, monetization, or subscription decision it needs to change. Start with the public Google Play review analysis workflow, the subscription review mining workflow, or the guide to competitor reviews vs customer interviews if you want the shape of the read first.
Growth system fix or strategy
A fuller strategy for teams preparing to scale, launch, relaunch, or fix a growth system where acquisition, funnel, monetization, and measurement are pulling in different directions.
Advisory
Ongoing support when the team needs a sharper growth brain in the room while execution keeps moving.
What to send
Send the messy context, not a perfect brief.
Send the app or website link, the decision you are trying to make, what currently feels stuck, and any numbers you are comfortable sharing. If it is an app, include the App Store or Google Play link. If paid acquisition is already running, include the channels, current optimization event, attribution setup, campaign structure, creative families, and any trial, purchase, cancellation, renewal, ROAS, or cohort signals you are comfortable sharing. If you already know the format you want, say whether this is a call, compact memo, or fuller strategy.
Brain as a Service
I am also testing a bigger idea: renting the judgment system, not just the hours.
Companies are building internal second brains. Individuals are copying more of their thinking into machines. The obvious next question is when that becomes commercial: can a team rent a strategist's brain as a recurring decision layer? That should not be the first thing you buy cold. Start with one diagnostic. If the way I think is useful, the recurring version becomes easier to define.
Good fit
This is for teams that want the diagnosis before the activity.
Useful if you are about to spend on paid traffic, already spending but not getting the result you expected, redesigning onboarding, rewriting a store page, changing the paywall, running ASO tests, or building a growth plan and you are not sure which move will actually change the business.