Jakub (HER, Mapy) shares how he rebuilt a subscription app’s MarTech stack from near-zero after joining MAPY (hiking & biking maps): picking an MMP, adding revenue infra, standing up in-app messaging/“HTML onboarding,” and using surveys + activation signals to decide what to monetize. We also cover build vs. buy, cutting tool noise, deep links, web vs. mobile behavior, and clever Figma automation for instant multi-language screenshots.

What you’ll learn

• The essential MarTech stack for a subscription app (MMP, revenue infra, analytics/BI, lifecycle—in-app first)
• How to choose an MMP (AppsFlyer vs. Branch) and why deep links usually live there
• Why in-app messaging (HTML modals) can stand in for onboarding, surveys, and roadmap validation
• Methods to discover what users will pay for (surveys, activation metrics, contextual upsells)
• When to buy vs. build (and how investor expectations affect that choice)
• Managing tool costs in freemium: country-scoped SDKs, MAU-based pricing tradeoffs
• Web vs. mobile behavior differences and how that shapes monetization & UX
• How to filter vendor hype: pricing page tells, documentation over demos, avoid vague “AI” pitches
• A fast path to localized store creatives with Figma + CopyDoc

Key Takeaways

• Start with measurement. Without an MMP and clean revenue signals you can’t scale UA or judge payback—set those up first.
• In-app > email early. For new/lean teams, prioritize in-app messaging and “HTML onboarding” to collect motivations, segment users (hiker/biker/driver/general), and guide activation.
• Show the paywall. Track launch→paywall impression; aim for ~90%+ so you’re reliably creating purchase opportunities, then layer contextual upsells (Strava-style).
• Monetize what matters. Use quick surveys + early actions to identify features people value; validate with smoke tests (CTA → deep link) before committing roadmap.
• Buy the boring stuff. For attribution, lifecycle, and payments, buy (standards, support, investor-friendly metrics). Build only where you truly differentiate.
• Control analytics cost. Scope product analytics SDKs to priority countries (or sample) to align MAU-priced tools with freemium economics.
• Deep links live with your MMP. Standalone options are thin, Google Dynamic Links is sunset—lean on AppsFlyer/Branch for reliability.
• iOS privacy changed the game. Deferred deep linking and deterministic tracking are less reliable; plan for modeling and guardrails.
• Cut through tool noise. If a vendor hides pricing or leads with vague “AI,” proceed with caution; read docs & pricing matrices, not just landing pages.
• Automate localization. Use Figma + CopyDoc to export/import copy and auto-generate hundreds of localized screenshots in minutes.

Links & Resources

• MAPY (hiking & biking maps): search “MAPY hiking app” in your store
• CopyDoc for Figma (bulk copy import/export): https://www.figma.com/community/plugin/900893606648879767/copydoc-text-kit
• Connect with Jakub on LinkedIn: https://www.linkedin.com/in/jakubchour/

Ashley Black, founder of Candid Consulting and former longtime Googler, breaks down how (and when) subscription apps should switch Google App Campaigns from CPA to tROAS, the pitfalls that stall performance, and how to feed better signals (activation/retention events) for durable scale. We also dig into iOS vs. Android realities, exclusions that actually matter, and why “automated” ≠ “set-and-forget.”

What you’ll learn

• The most common mistakes when moving from CPI/CPA to tROAS (targets too high, windows too long)
• How to set a realistic ROAS target (start ~20% below goal) and ramp it without killing volume
• Volume prerequisites for value bidding (why you need revenue events, not just trials)
• When tROAS fits (risk tolerance, trial length, budget) and when to stay with CPA
• Android vs. iOS with Google: inventory, tracking constraints, and creative needs (YouTube/Shorts)
• The right exclusions to apply (existing users, brand, re-installs) and why CPM rising can be good
• Using early activation/retention events to improve optimization when trial-start isn’t predictive

Key Takeaways

• Don’t over-ask early. Setting day-7 ROAS targets too high and using 30–90 day windows starves delivery. Start with a short window (≈7 days) and a lower target, then stair-step up.
• You need real revenue signals. For tROAS to learn, pass purchase/subscription events—trial-start alone won’t cut it. Rule of thumb: aim for ≥10 post-install revenue events/day (often more).
• Trial length matters. 30-day trials delay signals; tROAS may burn spend blind. Shorter trials or earlier monetization events make tROAS viable.
• Expect a ramp-up. Some accounts stabilize in days; aggressive targets can take weeks to unlock. Be patient and ready to lower targets to gain learning volume.
• Scale vs. profit trade-off. CPA often scales easier; tROAS can be more profitable once learned. Consider geo split tests to compare mixes.
• Inventory shifts under tROAS. Eligible placements are the same, but you may see more search/Play and higher CPMs—often a sign of higher-quality traffic, not waste.
• Exclude smartly. Add exclusions for current users, brand queries, and (optionally) re-installs to protect incrementality.
• iOS = different game. Google’s iOS performance lags Android; expect more YouTube/Shorts traffic and lean on strong UGC-style video. Treat iOS Google as a later-stage test.
• Optimize for activation. If trial-start users don’t retain, bid to an early in-app action (e.g., completed tutorial, first message) that correlates with D1/D7 retention and occurs fast enough for learning.
• Automation needs adults in the room. UAC/PMAX aren’t fire-and-forget—active tuning (targets, assets, exclusions) still moves the needle.

Links & Resources

• Ashley Black — Candid Consulting: https://www.candidconsultinggroup.com/
• Ashley’s guide to tROAS for subscription apps: https://www.botsi.com/blog-posts/value-based-bidding
• Connect with Ashley on LinkedIn: https://www.linkedin.com/in/ashleym-black/

Anthony Scarpaci, former Global VP of Growth at Acorns and senior leader at NerdWallet, Betterment, and Blue Apron, joins Jacob Rushfinn (CEO of Botsi) to break down how to build a referral program that performs. He shares his RIGHTT Framework—Relevance, Incentives, Guardrails, Human Centricity, Timing & Tracking—and real examples from fintech, meal kits, and subscription apps.

🧩 The RIGHT Framework

R = Relevance – Incentives should align with your product’s core value. Cash isn’t always king.

Example: GoHunt gives gear credits usable in-app and in its e-commerce store, keeping rewards tied to the customer experience.

I = Incentives – Make them motivating and credible. Urgency (limited-time offers) beats evergreen “set-and-forget” bonuses.

• Consumers are numb to “Give $10 Get $10.”
• Guaranteed rewards outperform sweepstakes—people act when they know they’ll get something.
• Tie incentives to meaningful product actions that predict retention.

G = Guardrails – Prevent gaming and fraud without killing usability.

The “optimal level of fraud is not zero.”
Every layer of anti-fraud friction hurts good users—accept some inefficiency for total-program scale.

• Analyze cohorts for retention / LTV gaps.
• Require real product usage (e.g., multiple deliveries in meal kits).

H = Human Centricity – Consistent, authentic, transparent experience across the entire journey.

• Map every touchpoint (ads → onboarding → referral share → reward delivery).
• Reinforce trust (“Your friend invited you”) and celebrate wins (“You earned $10—share again”).

T = Timing & Tracking –

• Launch after product-market fit and a healthy customer base.
• Introduce referral prompts at the right emotional moment: trial start or delight milestone.
• Maintain urgency windows for bursts of activity.
• Track cohorts, incremental lift, and blended CAC pre- / post-launch.

💡 Key Insights & Takeaways

• Referrals ≠ free users. Model unit economics and compare to your next-best acquisition channel (Meta, Google etc.).
• Halo & Cannibalization. Account for organic word-of-mouth you’d get anyway and the extra reach you gain when offers go viral.
• Accept some fraud. Zero-fraud programs over-optimize and add friction; “tolerable inefficiency” is a healthy cost of growth.
• Design for compounding. Great referrals create chains (friend → friend → friend), not single invites.
• Avoid conditioning. Don’t train users to expect giant promos forever—treat large bonuses as events, not defaults.
• Influencers as fuel. One creator’s post can 10× signups—plan for the viral halo but don’t depend on it.
• Higher-quality leads. Referred users retain better and cost less long-term—social proof raises both acquisition and retention.

🧠 AI Toolbox Anthony Uses

• Lovable / v0.dev / Replit V0 → No-code prototyping & mockups.
• Gemini transcription + Claude / ChatGPT → Strategy alignment & theme extraction from founder calls.
• OpusClip → Video editing & social creative velocity.
• Perplexity → Everyday research & voice-based learning.

🔗 Links & Resources

Anthony Scarpaci → https://www.linkedin.com/in/anthonyscarpaci/
Tunomatic → https://www.tunomatic.com/
Growth Notes Newsletter → https://tunomatic.substack.com/