Chargebacks rarely start where they show up.
I find the real cause.
I'm the operator subscription apps and SaaS founders call when chargebacks spike, a card network comes knocking, or they need AI shipped to production — not a deck about it. Deep work on payments fraud and AI. Production artifacts, not strategy decks. Product Manager since 2020 at a privacy-focused subscription app with 200,000+ users.
Flagship engagements
Two flagship engagements for teams that need a specific outcome, not generic advice. Each one ends with production artifacts — code, live rules, or audit-ready documents.
Chargeback Rescue & ECM Exit
Escape Mastercard ECM or Visa VAMP before the processor pulls the account. Stripe Radar rebuild, 3DS gating, dispute interception, and compliance documents that actually get accepted.
AI Automations & Claude Implementation
Ship production AI end-to-end: Claude-powered chat widgets, semantic knowledge bases, and agentic coding workflows via SKILL.md files. Branded, deployed, working on your stack.
Chargebacks rarely start at the chargeback.
A dispute spike might be a sign-up filter letting card-testers in. A "didn't recognize the charge" wave might be a billing-descriptor problem. Treat the symptom and the ratio keeps climbing toward ECM or VAMP. I trace each dispute to the layer it actually came from.
Card testing & fake accounts
Velocity abuse, BIN-IP mismatch, and disposable-email signups that become tomorrow's disputes. Scored and tiered so real users get through.
3DS gaps & Link bypass
Where liability shift is missed and CVC/AVS checks get skipped. The two Radar rules that almost always false-positive — and the ones that don't.
Descriptors & dunning
Unrecognized billing descriptors and failed-payment retries that convert into "I didn't authorize this" disputes weeks later.
Interception & representment
Ethoca and Verifi alerts, Verifi RDR auto-resolution, and representment packages that actually win. Stop the dispute before it counts.
ECM & VAMP thresholds
The ratios Mastercard and Visa actually watch, where you sit against them, and the 90-day path back under the line.
Trace it to the real layer
"Your chargeback ratio isn't a checkout problem — your sign-up flow is letting card-testers in, and they dispute 30 days later." Operator-grade diagnosis finds the actual cause.
Real outcomes.
Engagements end with deployed code, live campaigns, and audit-ready documents — not strategy decks.
Chargeback reduction & ECM exit
Subscription app entered Mastercard ECM. Five systemic issues identified and remediated.
AI chat widget deployment
Help center transformed into a production AI experience with Claude-powered chat via Vercel Edge.
I work best with
- ✓Subscription mobile apps (iOS & Android) spending $10K+/mo on acquisition
- ✓SaaS companies with existing ad spend or growth teams needing specialist support
- ✓D2C brands with chargeback or fraud problems
- ✓Founders and growth leaders at Series A through Series C
- ✓Product teams wanting to ship AI features without hiring a full AI team
I don't work with
- ✕Pre-product companies looking for free advice
- ✕Agencies looking to resell my time
- ✕Clients seeking generic marketing strategy
Common questions
What size companies do you work with?+
Most clients are between Series A and Series C — companies with existing revenue, existing teams, and specific problems to solve. I occasionally work with bootstrapped subscription apps doing $1M+ ARR.
What does a typical engagement look like?+
Most engagements are either a fixed-scope sprint (one to four weeks) or a monthly retainer. Scope, deliverables, and timeline are defined upfront. No hourly billing.
How do you charge?+
Sprint engagements are fixed-price. Retainers are monthly. Day rates are available for specific audits. Engagements typically start at $3,500 for audits and $7,500 for sprints. Pricing is shared on the introductory call after scope is understood.
Can you work with my existing team?+
Yes. Most engagements involve embedding with an existing growth, product, or engineering team. I don't replace teams — I augment them.
Will you sign an NDA?+
Yes, a mutual NDA is standard before any commercially-sensitive discovery work.
What time zones do you work in?+
Based in Lebanon (GMT+3). Working hours are 12:00 to 23:00 Beirut time, which provides meaningful overlap with European business hours, US East Coast mornings and afternoons, US West Coast mornings, and late APAC.
Do you work with agencies?+
No. I work directly with founders, product leaders, and growth leaders inside operating companies.