North America growth operations

05 / NORTH AMERICA USER GROWTH

North American user growth.

From market and user research to brand communications, acquisition, conversion and retention. I plan goals, people and budget together.

OPERATOR NOTES / METHODS & IMPLEMENTATION

Understand why users stay before scaling acquisition.

Establish how customers solve the problem today and what would make them switch. Define a first useful outcome, assign acquisition, onboarding, repeat use and payment to clear owners, then review what happens to the same user cohorts.

01Teams describe the product differently

Align alternatives, differences, best-fit customers and evidence across product, marketing, sales and support—not just a tagline.

02Sign-ups without useful outcomes

Review device, source and first-task steps. Guided creation can help complex products; do not burden simple tasks with advanced onboarding.

03How ads, PR and community divide the work

Ads test audience and economics; PR supplies factual stories; community supports onboarding, answers and co-creation. Share a goal, not one simplistic metric.

04How retention and payment are reviewed

Define user versus team, core action and natural usage cadence. Compare mature cohorts; recent users are not churned because renewal has not arrived.

WORKFLOWCustomer alternativesBest-fit usersAds / PR / CommunityFirst useful outcomeRepeat / PayTeam review

Implementation, inputs and local checks

De-identify approved feedback, event and CRM exports. The model groups problems and drafts tasks; deterministic code checks cohort denominators and maturity. Assign one owner, output, dependency, deadline and acceptance check per task.

python3 scripts/review.py examples.json --example cohorts

This runs synthetic input checks, not a live account integration or an experiment proving lift.

Skill + Flow ↗Review code ↗JSON inputs ↗

Define activation and retention around the product's job. Advertising, PR, community and product need distinct deliverables and checks; connect their work through sources, first value, continued use and revenue.

MY APPROACH TO GROWTH

Set the growth goal, then organize advertising, PR and community.

I start with the target audience, product value and goals for the current stage. From there, I plan the brand message, acquisition approach, path to conversion and budget. Advertising, PR and community serve the same users and business goal, rather than running as separate projects.

Advertising tests demand and acquisition efficiency. PR builds awareness and trust through the brand story, product evidence and industry perspectives. Community supports seed users, co-creation, questions and continued use. The team connects all three to product experience, payment and retention: useful content feeds advertising, user feedback informs product improvements, and reviews guide the next allocation of resources.

PLANDefine the audience, positioning, stage goals and budget, then break the goal down across the user journey.

ORGANIZEGive each task an owner, deliverable, deadline and success measure. Coordinate advertising, PR, community and product.

REVIEWReview acquisition quality, conversion, retention and payback before deciding to invest more, revise or stop.

USER JOURNEYAudience & NeedAwareness & TrustFirst valuePayRetainRefer

TEAM LOOPGoal & BudgetAds / PR / CommunityProduct experienceOutcome reviewResource decisionNext test

GEO independently covers content discovery and citation. In the growth outcome table it is one source, evaluated like every other source on first value, repeat use, and revenue; the two systems do not share one blended metric.

WEB & APP / CHANNEL MAP

Plan channels for Web and App separately.

Start with where the customer buys or uses the product, then choose channels. Web campaigns follow visits through to leads and sales; App campaigns continue through installation, first use, retention and payment. The same platform can serve both, with different destinations and success measures.

Channel	Typical placements	Role in the growth plan
Google Ads ↗	Google Search, YouTube and the Display Network	Capture active search demand, demonstrate products and drive website conversions.
Meta Ads ↗	Facebook and Instagram	Acquire customers for consumer products, commerce and subscriptions.
Microsoft Ads ↗	Bing Search and the Microsoft Advertising Network	Extend search acquisition beyond Google.
TikTok Ads ↗	Short-form video feeds	Use product demonstrations to bring visitors to a website.
LinkedIn Ads ↗	Professional feeds and other LinkedIn placements	Reach buyers for B2B SaaS and business services, and generate sales leads.
Reddit Ads ↗	Interest communities and discussion feeds	Find audiences for specialist tools, interest-led products and niche categories.
Pinterest Ads ↗	Visual discovery and search	Introduce visually led products and lifestyle offers.
Snapchat Ads ↗	Social and video placements	Add an acquisition channel for consumer products.

Channel	Typical placements	Role in the growth plan
Meta Ads ↗	Facebook and Instagram feeds, Stories and Reels	Show the product through images and video to acquire users.
Google App Campaigns ↗	Google Search, Google Play, YouTube, Discover and the Display Network	Acquire installs and in-app conversions across multiple placements.
Apple Ads often called ASA ↗	App Store search and discovery placements	Acquire iPhone and iPad users, including people actively searching for an app.
TikTok Ads ↗	TikTok short-form video feeds	Use demonstrations and experience-led videos to drive downloads and use.
Snapchat Ads ↗	Video and other Snapchat placements	Acquire installs and complement other social-platform traffic.
Reddit Ads ↗	Community feeds and conversation placements	Reach users through interests and specialist topics.
AppLovin ↗	Advertising inventory inside other apps	Acquire users through in-app advertising.
Unity Ads ↗	Placements inside games and apps	Acquire users for game apps, with install and return-on-ad-spend optimization goals.

Apple Ads here means App Store advertising; ASA is the familiar shorthand from Apple Search Ads. AppLovin’s in-app inventory includes mobile games, and Unity Ads can also reach users in other apps. Available install, in-app-event and return goals depend on current account eligibility and measurement setup.

Channel map · checked September 2026. Channel names link to official documentation. Placements and capabilities follow those sources; uses are planning guidance, not claims that I have run every channel or achieved campaign results. Availability varies by market, account and campaign objective.

Different responsibilities, reviewed together.

First decide whom to reach and what they should do. Advertising tests efficiency, PR builds trust, and community develops user relationships. All three share the brand proposition and product facts, but clicks and impressions alone cannot evaluate them.

Work	Method	Deliverables	Outcomes
Advertising	Run small tests of audiences, messages, creative and destinations. Keep useful combinations and adjust budget against payback.	Test plans, creative and page versions, budget-change records.	Target-user share, acquisition cost, payment and payback; not cheap signups alone.
PR	Define the audience, message and supporting evidence, then develop media angles, product stories, customer cases and partner communications.	Brand narrative, fact sheets, story pitches, cases and coverage records.	Relevant audience reach, branded search, qualified referrals and assisted conversions; coverage counts are not revenue.
Community	Segment new, active, paying and core co-creation users. Plan onboarding, support, collaboration, re-engagement and referrals.	User segments, operating plans, feedback lists and follow-up.	First success, repeat use, paid retention and qualified referrals; report group size separately.

A customer case can inform PR, advertising and community, with a different treatment for each task. Retain primary sources and assisted touchpoints to avoid double-counting. Review long-term brand effects separately from short-term conversion.

Results become comparable only after the event definitions agree.

These event names are a reusable template; they do not imply that the historical backend used the same instrumentation. Each event needs a user, UTC timestamp, market, source, experiment, product version, and failure reason.

Event	Success definition	Key fields
qualified_visit	Qualified visit; internal, test, and bot traffic excluded by rule	session / market / source
authorization_succeeded	Required account authorization succeeds, not merely a click on Authorize	user / provider / success
core_job_succeeded	Core job reaches a successful terminal state and its result opens	user / job / result / version
outcome_exported / published	A genuine export or evidence of publication; record them separately	job / output / destination
second_core_action_completed	A second completed core job, not a login	user / job / cohort age
subscription_started / renewal_succeeded	First payment and renewal after the actual due date succeed	transaction / plan / period
refund_completed / cancelled	Refund and cancellation recorded separately with their timestamps	transaction / reason / amount

ACTIVATION · 7 DAYS: Complete required authorization, a successful outcome, and a genuine export/publication within 7×24 hours of signup; denominator: mature new-user cohort.

D7 CORE RETENTION: Complete a second core job in the fixed [168h, 192h) window after signup; exclude logins, community joins, and generic activity.

FIRST PAY · 30 DAYS: First successful charge within 30 days of signup. Mark users who have not completed the observation window as immature rather than failed.

FIRST RENEWAL: Successful renewal after the first billing period actually comes due / subscriptions actually due; reconcile refunds, cancellations, and net revenue separately.

How the team responds to different breakpoints

State	Next-round action	Do not
Not authorized / authorization failed	Show the available outcome, explain the permission, and provide a recovery path	Buy more traffic to fill a product failure
Clicked, no outcome	Shorten the first task and repair failure and local-editing paths	Explain every problem by changing the creative
Succeeded once, did not return	Use the first outcome to suggest the next job, template, and behavioral prompt	Send undifferentiated promotional blasts
Strong retention, weak payment	Explain the plan, allowance, and practical value after success	Treat usage volume or allowance consumption as willingness to pay
Payment grows, refunds rise	Reconcile the promise, quality, billing period, and unit cost	Show gross revenue alone

Assign work by outcome, not by the number of tasks completed.

I break down goals, allocate budgets, coordinate responsibilities and review outcomes. The roles below describe ownership, not a fixed headcount. People can cover multiple roles, but every deliverable needs a clear owner.

Role	Outcome owned	Deliverable
Growth lead	Stage goals, budget, priorities and resource trade-offs	One primary problem + experiment brief + decision log
Product / Engineering	Authorization, first task, quality, and failure recovery	Reproducible issue + fixed version + acceptance result
Data	Events, identity deduplication, windows, and mature cohorts	Event dictionary + reconciliation result + cohort table
Paid growth	Channel quality and paid acquisition cost	Spend and downstream outcomes segmented by creative/audience
Creative / Content	Hook, page, demonstration, and case	Asset pack with hypothesis, version, and supporting references
Brand / PR	Brand message, supporting evidence and relevant audience reach	Brand narrative + story pitches and cases + coverage review
Community / Lifecycle	User segments, co-creation, activation and continued use	Failure reasons + trigger matrix + user feedback
Finance / Monetization	Subscription, renewal, refund, cost, and gross margin	Net revenue and unit-economics review

WEEKLYMON · BottleneckTUE · ExperimentWED · User evidenceTHU · Ship changeFRI · Decision

Monday selects one largest breakpoint; Tuesday defines the hypothesis, primary variable, and owner; Wednesday examines how failed users actually moved through the product; Thursday ships the creative, page, product, or outreach change; Friday records continue, change, or stop. Authorization, task, export, payment, and tracking failures are checked daily.

Scaling requires reliable data, target-user quality, first value, D7, mature paid acquisition cost, renewal, and refunds to pass together. Complete the observation window and confirm that useful results recur in later user cohorts before increasing investment gradually. Set thresholds around the business costs and user cycle.

ENGLISH / REUSABLE PLAYBOOKDownload the operating templates ↓User jobs, event dictionary, cohort table, experiment brief, lifecycle triggers, and weekly handoff MY CODE / GITHUBcreator-outreach-ai-kit ↗Creator scoring, outreach drafts, and follow-up queue

Method basis: my work in North American user growth, brand operations, content commercialization and team management, together with user research and project reviews. Event definitions and weekly routines are reusable examples to adapt to the business.

COMMERCE PLATFORMS

Explore commerce by platform.

Publishing, listings, product videos and advertising for TikTok, Amazon, Shopify, AliExpress, Mercado Libre and Shopee.

Methods for six platforms ↗Amazon daily analysis ↗

North America growth operations.