Product.ai / Join / Projects / SimplyCodes Conversion-Uplift Initiative — pick one quantifiable lever, ship the experiment, measure the result
Project Open to Alpha Team

SimplyCodes Conversion-Uplift Initiative — pick one quantifiable lever, ship the experiment, measure the result

Pick one quantifiable conversion lever on SimplyCodes. Run the experiment. Measure the result against a clean baseline window. Ship the winner if the lever moved, retire it if it didn't, write a one-page learning doc either way. Real users, real conversion, real attribution.
Project Overview
Discipline
product-manager-simplycodes · founding-product-manager
Duration
2 weeks
Compensation
Your stated freelance rate
Surface
SimplyCodes · Revenue
Kernels
simplycodes · revenue
Outcomes
mlp-convert · sc-traffic · new-revenue
Tier
Applied
Alpha Team
Open to alpha members who want to take this on
Tooling
Claude Code or Co-work

Why we want this done

Per the recruiting-driver §6.4, the highest signal a PM can produce in a trial is shipped work that lands in production with a measurable outcome. The PM Phase 3 briefing names SimplyCodes as the default primary ownership target for the first PM (revenue engine, $22M ARR, $1B+ GMV, 45,000+ merchants — wrong PM hire is existential). VERDICT 1 in that briefing names a six-month mandate that includes "SimplyCodes conversion uplift on target store cohort." This project is the trial-window-sized version of that mandate. The candidate proves they can identify a real conversion lever (not a vanity metric), execute the experiment cleanly (not theater), measure the result against an actual baseline (not story-tell the result), and either ship the win or retire the loss without ambiguity. PMs who can do this loop tightly are rare; PMs who pretend to do it are common.

Scope

  1. Survey SimplyCodes funnel data — get the metric stack from Bri or whoever owns sc-traffic instrumentation
  2. Identify three to five candidate levers — argue for them on mechanism, not on "what could move"
  3. Pick one — the highest-leverage given trial-window constraint
  4. Design the experiment — A/B with sample size math, baseline window, measurement plan, kill criterion (a result that ends the experiment early)
  5. Ship — code merged or feature-flagged in production
  6. Run — collect data through the trial window
  7. Decide — ship the winner, retire the loser, or extend if signal is unclear
  8. One-page learning doc — what was tried, what moved, what didn't, mechanism update

What success looks like

  • The experiment ships in production — feature-flagged or behind a clean rollout
  • A baseline window is captured before the experiment starts (or argued why it isn't possible)
  • The result is measured on a real metric, not a self-reported one — sc-traffic, mlp-convert, code-acceptance, or another instrumented metric
  • The candidate ships the winner OR retires the loser — no ambiguous "let's see how it goes"
  • The learning doc explicitly updates the candidate's mental model — "I thought X would move; it didn't because Y"

References

references.md
PM Phase 3 briefing axiom B3 (Revenue-Engine Default), C2 (Onboarding Calendar), VERDICT 1 (SimplyCodes Senior PM mandate)
SimplyCodes kernel — verification fleet, monetization architecture, conversion physics
Revenue kernel — pricing, sales motion
Existing SimplyCodes A/B testing infrastructure (or note the absence)
sc-traffic.md and mlp-convert.md outcome files

Constraints

  • Claude Code or Co-work as primary substrate
  • Real metric, real baseline, real attribution — no vanity metrics
  • Sample size argued explicitly; if the trial window is too short for statistical confidence, the candidate makes that explicit and ships an early-signal interpretation with the right caveats
  • Kill criterion must be set before the experiment starts (not after the fact)
  • The decision (ship / retire / extend) must happen during the trial window — not "we need another two weeks"
  • IP separation: SimplyCodes consumer surfaces are application-layer; pricing/payments physics are out of scope unless explicitly negotiated
Apply
01

Read the Codex (10 min)

The operating principles we work by. If they resonate, the rest of this will land. Open the Codex →

02

12-minute video screen

Hireflix, async. Questions are calibrated to this project specifically.

03

Chemistry call (30-60 min)

Direct call with the CEO. Strategic alignment and mutual fit. No problem-solving exercise.

04

Project begins within 2-3 weeks

1099 contractor agreement, NDA, paid at your stated rate. Day 1 in Santa Monica.

Alpha Team members can take this project without the screen-and-call sequence. Reach out via the Alpha Team channel.