Anastasiya Fedarava

Open to senior product roles

Selected work / 01

EyeXP

An AI coach that watches your technique. Before launch, I set out to watch the product the same way.

Role
Product ManagerMetrics, analytics, research and growth experiments — next to the product design
Product
AI technique coachPose analysis for boxing and fitness drills
Stage
Closed alphaPre-launch, iOS
Stack
PostHogAnalytics, session replays, surveys, feature flags
Focus
Activation · RetentionAnd one growth experiment before launch

Measure now, while it is cheap.

Before the alpha, I defined what we would need to know at launch — and made the case for building it in now.

How I put it to them

I put it to the founders as their gain, not my process: before launch we need to see where people get lost and what brings them back. Events added after launch mean rework — and the first weeks, the most telling ones, are never recorded at all.

  1. AlphaA few days of one engineer
  2. BetaRework in screens already shipped
  3. LaunchThe first cohorts, never recorded
  4. ScaleDecisions made on guesses

Three things we agreed

  1. 01

    Who builds it

    One mobile engineer, a fixed budget of hours, events shipped with the alpha build.

  2. 02

    Which tool

    Chosen on criteria, not habit — see below.

  3. 03

    How we use it

    A weekly review with the founders: the funnel, the cohorts — and one decision taken from them.

One number to steer by.

One number the whole team steers by, four that move it, and two we never trade for growth.

North Star

Completed workouts per active user, per week

  • Activation

    First workout done within 72 h
  • Retention

    Back on day 1, 7, 30
  • Frequency

    Workouts per week
  • Quality

    Cues applied on the next attempt

Guardrails

  • Analysis failures per workout
  • Time from upload to feedback
  1. 01Downloaded
  2. 02Signed up
  3. 03Onboarding done
  4. 04Plan ready
  5. 05First workout started
  6. 06First workout finished

Not chosen as the North Star: downloads (they measure marketing), sessions (opening the app is not training), the precision score (someone can score well and never come back).

Every event named before it is built.

One table the engineers could build from, and one rule they could remember.

object_action — lower case, underscores, past tense.

EventFires whenPropertiesServes
signup_completedAn account is createdmethodFunnel
onboarding_step_viewedEach onboarding screen opensstepstep_nameFunnel
onboarding_completedThe last step is doneduration_sskipped_stepsFunnel
plan_generatedThe first plan is readygoallevelsessions_per_weekFunnel
workout_startedThe first rep is recordedworkout_typesourceActivation
workout_completedEvery set is finishedworkout_typeduration_ssets_doneNorth Star
analysis_completedFeedback is readyprecisioncues_countprocessing_mscamera_stableGuardrail
feedback_viewedA result is openedcue_identryQuality
ai_coach_message_sentA question goes to the coachtopiclength_bucketEngagement
feedback_submittedAn in-app survey is answeredsurvey_idratingResearch
result_sharedA result card is exporteddestinationGrowth

One tool, chosen on purpose.

The questions of the alpha and the experiments of the launch should live in the same data.

PostHogFirebase Analytics
Funnels and cohortsYesPartly
Session replaysYesNo
In-app surveysYesNo
Feature flags and experimentsYesYes
Free tier covers an alphaYesYes
Already in the appNoNo

Decision

PostHog: analytics, replays, surveys and flags in one place — what we learn in the alpha and what we test after launch, in one dataset.

Had the app already shipped Firebase, I would have kept it: one SDK fewer is worth more than one feature more.

I walked every path myself.

Analytics break quietly. Before the first tester arrived, I installed the alpha and went through every route, watching each event land.

A phone on a low stand, filming someone train.
  1. Fires onceNo duplicates on re-render, background or retry.
  2. Properties completeEvery property present, with the right type and values.
  3. One person, one IDThe anonymous visitor and the signed-up user merge into one.
  4. Time is rightTimestamps and time zones survive offline sessions.
  5. Nothing personalNo video, text or body data in any payload.
Why this matters

This is the dull step, and the one where most tracking plans fail: a duplicated event inflates a funnel, a missing property hides a segment, a broken identity merge turns one person into two. Each would have poisoned every chart that followed.

Two views, read every week.

The onboarding funnel up to the first finished workout, and retention by weekly cohort.

Onboarding → first workoutAlpha cohort 1 · 57 sign-ups
  1. Downloaded64
  2. Signed up5789%
  3. Onboarding done3154%
  4. Plan ready3097%
  5. First workout started2480%
  6. First workout finished1979%
Weekly retention by cohort% still training, by week since sign-up
CohortW0W1W2W3W4
W38n=1810044332822
W39n=21100483829
W40n=181003933
W41n=2410058
W42n=25100

07Numbers & voices

The data and the people said the same thing.

Seven alpha testers, 20–30 minutes each: what was unclear, why they stopped, what they liked.

The interview guide
  1. Walk me through the first time you opened EyeXP.
  2. Where did you hesitate?
  3. When did you stop — and what were you doing then?
  4. What did you expect to get back?
  5. What would make you open it tomorrow?
Onboarding, step by step
  1. 57Step 1
  2. 54Step 2
  3. 52Step 3
  4. 33Step 4
  5. 31Step 5

−37% after step 3

  • “I hadn’t thrown a single punch yet, and it wanted me to film my whole body.”

    Tester, 29
  • “I thought it would record me all the time. That felt like a lot.”

    Tester, 34
  • “Propping the phone up in my kitchen — I closed it and said I’d do it at the gym.”

    Tester, 24
  • “I didn’t know what I’d get back for it.”

    Tester, 41
  • “Once I saw the cue on a jab, I got it. I just saw it too late.”

    Tester, 31
  • “The one tip with a timestamp is the best part.”

    Tester, 27
  • “I wanted a plan for the week, not just one drill.”

    Tester, 36

In the data, about four in ten testers left at step 3. In the interviews, five of seven said they didn’t see why the app needed the camera before it had shown them anything.

Show the value, then ask.

Step three asked people to prop up the phone and film their whole body before they had seen anything in return.

BeforeCamera calibration at step 3, before any value.
AfterA 10-second sample analysis at step 3; calibration moves to the first workout, and can wait.

Next cohort, same build otherwise

Onboarding completed

54%Cohort 1 · n=57

78%Cohort 2 · n=49

+24 pts

Activated within 72 h

33%Cohort 1 · n=57

47%Cohort 2 · n=49

+14 pts

DirectionalSmall samples: the direction is clear, the size is not. The next cohort checks it again — with a feature flag, once there is traffic.

What stayed the same

Kept the same, to compare like with like: the invite channel, the rest of the build, the tester profile.

Test the promise before the product.

Two landing pages, one waitlist form, two promises. Meta ads with the same audience and budget on each.

Variant A

“An AI coach that adapts to you.”

Ad CTR
1.1%
Landing → waitlist
18%
Cost per lead
€3.90

Variant B

“20-minute workouts. No gym.”

Ad CTR
1.6%
Landing → waitlist
24%
Cost per lead
€2.10

The concrete promise won on every measure: people respond to time and place before they respond to technology. The AI becomes the reason it works — not the headline.

01 Review

Check the take before it counts.

A shaky camera is named calmly, with a retake — bad input never becomes bad feedback.

attempt_recordedcamera_stable: falseattempt_retaken

02 Analysis

Work you can watch.

Frames, keypoints, comparison — progress you can trust, and permission to leave.

analysis_startedanalysis_completedprocessing_ms

03 Feedback

One cue first.

The most important correction on top, pinned to the moment in the clip; the rest wait their turn.

feedback_viewedcue_idworkout_completed

04 Share

A result worth posting.

Progress turned into a card — and a growth loop we can count.

result_shareddestination

An empty boxing ring in a dark gym.

A habit of measuring, before there was anything to lose.

  1. Defined the North Star, activation and retention for a pre-launch AI fitness app
  2. Wrote the tracking plan: eleven events, their properties and one naming rule
  3. Chose the tool on criteria and verified every event by hand
  4. Built the funnel and cohort dashboards the team reads weekly
  5. Found the onboarding leak where the numbers and seven interviews agreed
  6. Fixed it and compared the next cohort — honestly, as a direction
  7. Designed a value-proposition smoke test to run before launch

Next

  1. Run the onboarding change as a flagged A/B once traffic allows.
  2. Link cue quality to retention: do people who apply cues come back more?
  3. Add a guardrail alert when analysis failures rise.

Next case

Work Saudi

A national employment platform for Saudi Arabia, in Arabic and English.