Albina Urubkina / Selected work
02 / AI Product Growth Lab · Analytics case · 2026

A better reason
to return.

A harder question about value.

Can daily AI credits improve meaningful retention without undermining product economics?

THE POLICY QUESTION
$5
$1$1$1$1$1
One entitlement. Two allocation policies.
Illustration of the mechanism, not a result.
Synthetic analytical simulation · No claimed company experiment or business results
MODEL POPULATION10,000 users
OBSERVATION90 calendar days
ANALYTICAL STACKSQL · Python · Statistics
SEPARATE REAL-DATA STUDY12,330 UCI sessions
The analytical workspace

Inspect the behavior. Challenge the economics.

Actual published Streamlit dashboard showing synthetic growth metrics and the D7 interpretation boundary
Actual published Streamlit browser capture · seeded synthetic results · interface before this case-page redesign
01 / VALUE

Measure useful return.

Visits and successful AI usage answer different questions.

02 / ECONOMICS

Make the trade-off visible.

Retention gains must survive contribution guardrails.

03 / INTERPRETATION

Question the checkpoint.

D7 also reflects unequal credit-expiry timing.

01 / Context

The Product Challenge

Free AI credits remove the first barrier. They do not necessarily create the next habit.

In her work on Monolit Network, Albina encountered a product question: new users received $5 in free tokens, many spent their balance in a single session, and some did not return afterward. A daily allocation was considered as an alternative.

No retained Monolit analytics or verified experiment results are available. Whether the proposed mechanic was implemented is unverified. This independent project uses that experience to formulate a research question and builds a new analytical simulation around it.

The decision is not simply “which reward increases visits?”
It is “which reward supports useful behavior at a sustainable cost?”
02 / Mechanism

Behavioral Hypothesis

Distributing the same $5 entitlement across five eligible days may provide repeated opportunities to discover value. It may also attract visits that exist only to claim a bonus.

Control

$5 upfront

$5————

One grant at signup.
The user chooses when to spend it.

Treatment

$1 × five eligible days

$1$1$1$1$1

Five bounded grants.
Entitlement is comparable at baseline.

Credits are issued on schedule while the user is eligible; issuance does not require a visit and does not guarantee one. Grant expiry, actual consumption and request-level inference costs are tracked separately.

Meaningful usage requires at least two successful AI requests on a day. It is a transparent, testable proxy—not evidence that a user's underlying task was completed. Bonus-only activity is tracked as a counter-metric.

03 / Method

Simulation Methodology

The model follows users forward in time. Acquisition channels select different segment distributions; random assignment is independent of those characteristics. Product value, prior usage, available balance, seasonality and scenario assumptions affect later behavior.

  • 01
    Generate a heterogeneous population.

    Model differences in intensity, willingness to pay and discovery of value. Keep inactive users in eligible denominators.

  • 02
    Simulate connected behavior and ledgers.

    Sessions produce requests, requests consume funded credits and incur inference cost; subscriptions generate explicit payments and can cancel.

  • 03
    Observe a fixed calendar window.

    Late signup cohorts have less follow-up. D30 requires day 30 to be observed; first-30-day economics use ages 0–29.

  • 04
    Stress the assumptions.

    A fixed seed reproduces each configuration. Positive, neutral and negative scenarios explore different mechanisms without guaranteeing a winner.

Synthetic statistical significance describes random variation within this model. Model assumptions remain an additional, unquantified source of uncertainty.
04 / System

Data Architecture

One coherent data model supports SQL, Python, the dashboard and statistical analysis. The analytical unit remains the randomized user rather than a convenient sample of active sessions.

users + experiment assignments
↓
events & sessionsAI requestscredit ledgersubscriptions & payments
↓
daily user outcomes → SQL / Python → experiment report

Validation checks primary-key uniqueness, referential integrity, observation windows, ledger balances and request-to-cost reconciliation. SQL uses CTEs, conditional aggregation and window functions where the metric requires them. Independent Python calculations provide parity checks.

Core pipeline: seeded simulator → linked CSV + SQLite → validated metric tables → Streamlit / Plotly. No API key is needed.
05 / Behavioral evidence

Retention Analysis

Exact-day retention asks whether an eligible user returned on a specific age day. Cohort heatmaps expose maturation instead of treating censored cells as zero. Rolling retention answers a separate question: whether a user returned at or after a target day within the common observation window.

Verified model results

Run the reproducible pipeline to populate this section with calculated results. The dashboard reads the generated tables and exposes every denominator.

python -m scripts.pipeline

Compare D1, D7 and D30 with meaningful retention, return frequency and successful requests. A rise in visits accompanied by bonus-only activity may indicate an incentive loop rather than growing product usefulness.

Each retention rate includes all users assigned to the arm who have enough follow-up, including users with no activity. “Active users only” would distort the denominator.
06 / Decision discipline

Experiment Design

A user-level, 50/50 randomized experiment compares a $5 upfront entitlement with $1 on each of five eligible days. The primary endpoint is meaningful D7 retention; the population includes all eligible assigned users.

Predeclared experiment framework
Primary endpointMeaningful D7 retention; treatment minus control
Practical thresholdAt least +2 percentage points absolute lift
InferenceTwo-sided α = 0.05; Newcombe score interval; user-level comparison
Integrity checkSample ratio mismatch; investigate if p < 0.001
Secondary endpointsD1 / D7 / D30 and first-30-day paid conversion; Holm adjustment
Economic guardrailsContribution per user no worse than −$0.25; conversion no worse than −1 pp, assessed using interval lower bounds
Behavior guardrailBonus-only activity increase no greater than +10 pp

A sample-size calculation links the desired effect, baseline rate and 80% power. A/A checks evaluate test calibration; a behavioral A/A scenario checks whether treatment assignment alone changes generated behavior. Novelty is modeled explicitly and mature results deserve more weight than an early incentive spike.

Segment views are exploratory. Passing a synthetic decision rule supports prioritizing a real pilot; it does not justify a production launch.

07 / Economic evidence

Monetization & Unit Economics

A retail credit dollar is not an inference-cost dollar. Free entitlement, consumed balance, subscription receipts and modeled provider cost belong to different ledgers.

Contribution=Subscription revenue−Estimated inference cost

ARPU includes every mature assigned user; ARPPU includes only paying users. Financial comparisons use each mature user's first 30 days so early signup users do not receive a longer revenue opportunity. Contribution margin is undefined when revenue is zero.

The dashboard displays paid conversion, cost per user, credit consumption and profitability alongside retention. Acquisition, payroll, hosting, support, refunds and taxes are outside this contribution definition. It should not be presented as full profit or lifetime value.

08 / Sensitivity

Scenario Comparison

Rather than selecting one convenient set of assumptions, the lab makes the economic trade-off visible.

Three mechanisms to stress—not three real-world forecasts
ScenarioBehavioral assumptionQuestion to investigate
PositiveRepeated discovery supports useful behavior and purchase propensity.Does meaningful retention improve while guardrails remain intact?
NeutralReturn incentives create some activity, with limited value learning.Is the practical lift distinguishable from uncertainty?
NegativeBonus seeking displaces meaningful usage and willingness to pay.Can engagement increase while contribution deteriorates?

The interactive lab varies credit size, grant frequency, expiry, inference cost, subscription price, return propensity and purchase propensity. A run compares with a neutral baseline using the same seed and population size. Assignment and channel draws are shared; latent behavior is re-simulated, so sensitivity differences are unpaired. Saved runs support deliberate comparisons; changing credit size changes total entitlement and must be interpreted accordingly.

09 / Product judgment

Product Recommendations

Treat daily credits as a discovery mechanism. Validate the value created, not just the visits attracted.

  1. Instrument useful outcomes before scaling incentives. Track successful requests, task completion where possible, bonus claims, expiry and inference spend in separate events.
  2. Keep the default budget bounded. Compare equal total entitlements first. Test larger budgets only under an explicit economic hypothesis.
  3. Advance only with aligned evidence. Require a practical improvement in meaningful retention, assignment integrity and acceptable economic guardrails.
  4. Study high-cost and low-value segments. Use exploratory segments to design new hypotheses, then validate those hypotheses prospectively.
  5. Run a real pilot before making a company claim. Preregister outcomes, collect complete follow-up and examine persistence after the five-day reward ends.
Recommendations are conditional on measurement quality and model assumptions. The generated statistical report contains the actual decision for each run.
10 / Honest boundaries

Limitations & Learnings

The model encodes plausible mechanisms rather than learning them from Monolit records. It does not model competition, network effects, fraud, full lifetime value or verified task success. Short-run return rates may overstate enduring value. Model uncertainty cannot be repaired by increasing the simulated sample.

“Meaningful” activity is an operational proxy. A real product would need qualitative discovery and instrumented task outcomes to establish what users value.

A separate real-data exercise

12,330 e-commerce sessions.
A different question, a different domain.

The UCI Online Shoppers Purchasing Intention dataset is analyzed independently under CC BY 4.0. Session purchase rates and their uncertainty can be estimated; absent stable user IDs and event timestamps, user retention and causal effects cannot.

Missingness and repeated feature rows are inspected explicitly. Repeated rows are not automatically deleted because identical session features need not imply duplicate records. These results are never transferred to an AI SaaS conclusion.

Explore the independent real-data study ↗
Inspect dataset provenance and license ↗

The central learning: credible analytics begins with the observation unit, eligible denominator and decision boundary—not with a persuasive chart.

11 / Portfolio authorship

My Contribution

This independent portfolio project connects a product question from Albina's Monolit experience with a reproducible analytical system: behavioral modeling, connected data design, SQL metrics, Python validation, experimentation, sensitivity analysis and a working interface.

It complements her Hotel Guest Experience Platform, which demonstrates UX research, business analysis, UML and MVP design. The growth lab centers on analytical reasoning, uncertainty and economic decisions.

The source and accompanying interview materials document what the simulation can establish and what would require real product evidence. Development used AI assistance; the project is designed for its author to reproduce, explain and critically assess.

Product AnalyticsSQLPythonA/B TestingGrowthAI Unit Economics
Reproduce / inspect / challenge

Explore the growth lab.

The Streamlit dashboard contains working filters, cohort views, uncertainty estimates, downloads and a bounded scenario simulator.

Open the live dashboard ↗
Explore the interactive research preview ↗
Open locally running Streamlit dashboard ↗

The public dashboard runs the Python model. First startup can take a moment if the free host is asleep. Use the commands alongside to reproduce the analysis locally.

From the repository root
python -m pip install -r requirements.txt
python -m scripts.pipeline
streamlit run dashboard/app.py
Inspect the source on GitHub ↗

Reproduce the analysis and inspect the implementation, validation and publication guides.