Product.ai / Join / Projects / SimplyCodes Working-Code-Rate Lift — drive measurable improvement on the verification accuracy metric
Project Open to Alpha Team

SimplyCodes Working-Code-Rate Lift — drive measurable improvement on the verification accuracy metric

Pick one mechanism limiting SimplyCodes' working-code rate (currently 67%) or the surrounding 96% availability metric. Diagnose the failure modes via trace review against real coupon verification outputs. Ship a measurable improvement — a model retrain, a feature addition, a heuristic correction, or an instrumentation gap closed. Measure the lift against a clean baseline window. Real revenue impact, real attribution, real production deploy.
Project Overview
Discipline
AI Systems — Data Scientist / ML Engineer · founding-product-manager
Duration
2 weeks
Compensation
Your stated freelance rate
Surface
SimplyCodes · Revenue · Truth Graph
Kernels
simplycodes · revenue · truth-graph
Outcomes
sc-traffic · mlp-convert · 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

Bootstrapped economics forces strategic-before-technical sequencing. The Data Science Phase 3 briefing names this as the Day-60 deliverable: "drive measurable lift on SimplyCodes coupon verification accuracy and conversion." A senior DS at $200K + signing + equity + on-costs ≈ $300K all-in year 1. To repay: ~5% conversion lift attributable to working-code-rate improvement applied to SimplyCodes' revenue base generates >$300K within year 1. Working-code rate is the highest-leverage DS surface in Product.ai today. The candidate proves they can absorb a real production data system, diagnose real failure modes (not theoretical ones), ship a measurable improvement (not a research write-up), and measure the lift cleanly (not story-tell the result).

Scope

  1. Day 1-2 — survey the verification fleet output, trace logs, and instrumentation
  2. Day 3-5 — failure-mode analysis: review N=100+ verification traces, open-code failure modes, axial-code into mechanism-distinct categories
  3. Day 6-7 — pick the highest-leverage mechanism (one, not three), defend the choice
  4. Day 8-12 — design + ship the improvement (model change, feature, heuristic, instrumentation gap)
  5. Day 13-14 — measure against a clean baseline window; document the result
  6. One-page write-up: the failure mode diagnosed, the improvement shipped, the measured lift, the residual mechanisms not addressed

What success looks like

  • One mechanism is shipped to production (feature-flagged or staged rollout)
  • A baseline window is captured before the change; the lift is measured against it
  • The result is honestly reported — if the lift is small or zero, the candidate names the mechanism that didn't move and why
  • The trace review artifacts (open-coding annotations) are captured — not just the conclusion
  • The candidate explicitly NOTES which residual failure modes they did not address (gap-flagged, not hidden)

References

references.md
Data Science Phase 3 briefing axiom A8 (SimplyCodes-First Sequencing), A9 (Bootstrap Economics Strategic-Before-Technical), VERDICT 1 (Hire mandate)
SimplyCodes kernel — verification fleet architecture, monetization, code-validity primitives
Truth-graph kernel — verdict semantics
sc-traffic.md and mlp-convert.md outcome files
Existing SimplyCodes verification telemetry / data dashboards

Constraints

  • Claude Code or Co-work as primary substrate
  • Production deploy is a deliverable — not "I wrote a model that could be deployed"
  • Baseline-window discipline — the lift must be measured against a clean baseline, not a story-told number
  • Self-hostable infrastructure only (Phoenix or Langfuse if eval substrate is touched)
  • Privacy-respecting trace handling
  • IP separation: SimplyCodes verification fleet is application-layer; methodology paths are out of scope
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.