Product.ai / Join / Projects / Six-Month SimplyCodes Roadmap with Two Kill Decisions — Day 90 Phase 0 deliverable
Project Open to Alpha Team

Six-Month SimplyCodes Roadmap with Two Kill Decisions — Day 90 Phase 0 deliverable

Build the six-month SimplyCodes product roadmap. Three to five initiatives, prioritized, sequenced, with success criteria and named owners. Two of those initiatives must be explicit kills — currently-scheduled work the candidate would stop, with the alternative use of the freed time argued explicitly. One-page roadmap document plus one-page kill-decisions argument doc.
Project Overview
Discipline
product-manager-simplycodes · founding-product-manager
Duration
2 weeks
Compensation
Your stated freelance rate
Surface
SimplyCodes · Revenue · Product.ai
Kernels
simplycodes · revenue · productai
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

The PM Phase 3 briefing names this as the Day 90 deliverable for the first SimplyCodes PM (along with the Day 30 State-of-Product memo and the Day 60 shipped initiative). Kill discipline is the rarest PM skill in 2026 because compression-era PMs were never trained to say no — every prioritization framework optimizes for what to add, not what to subtract. The PM briefing's Probe 3 (Eval-That-Was-Wrong) and Probe 5 (Work-Sample Live) are the hiring-stage proxies; this project is the working-day-90 proxy. The roadmap-with-kills tests strategic judgment under bootstrapped-economics constraints — a wrong "let's do everything" produces drift; a wrong "let's kill the wrong thing" loses revenue. Both are visible in this artifact. The CEO can read the doc and either accept the kills or argue them; the artifact carries the argument either way.

Scope

  1. Inherit the State-of-Product memo (PRJ-21 if shipped) and the conversion-uplift learnings (PRJ-24 if shipped) — argue from them, don't re-derive
  2. Survey current SimplyCodes work — engineering backlog, product debt, open initiatives, customer requests
  3. Identify three to five initiatives the candidate would prioritize over the next 6 months
  4. Identify two currently-scheduled initiatives the candidate would kill — name them
  5. For each kept initiative — JTBD, success criterion, named owner, sequencing rationale
  6. For each killed initiative — what's currently in flight, why it's the wrong thing, what the freed time goes to instead
  7. One-page roadmap (the kept initiatives, sequenced)
  8. One-page kill-argument doc (the two kills + alternative use of time)

What success looks like

  • The roadmap is one page (hard constraint)
  • The kill-decisions doc is one page (hard constraint)
  • Each kept initiative has a measurable success criterion on existing instrumentation
  • Each kill has a named alternative use of time — "stop X" without "start Y instead" is incomplete
  • The candidate explicitly defends the kills — does not negotiate them away under CEO pushback in the trial review
  • The CEO can read both docs in 10 minutes and understand the strategy

References

references.md
PM Phase 3 briefing axiom B6 (Live Demonstration Beats Proxy Filters), C2 (Onboarding Calendar), VERDICT 1 (SimplyCodes Senior PM mandate)
The State-of-Product memo (PRJ-21) and conversion-uplift learnings (PRJ-24) if shipped
SimplyCodes kernel and engineering backlog
Linear's Nan Yu first-PM precedent

Constraints

  • Claude Code or Co-work as primary substrate
  • One page each for roadmap and kill-argument — text overflow is a fail
  • Each kill must have a named alternative use of time — "stop X" without "start Y instead" is incomplete and a fail
  • The candidate may not negotiate the kills away under CEO trial review pressure — defending them IS the deliverable
  • Success criteria must be measurable on existing instrumentation
  • IP separation: SimplyCodes is application-layer; out-of-scope work stays out
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.