0→1 PHP, MySQL, JavaScript

Resume AI — Waitlist Landing Page

Resume AI started in June 2019 from a narrow frustration: one generic resume for every application, or hours rebuilding a Word doc for each posting. I wanted one universal resume for job boards and dedicated variants per role — without starting from a blank page every time.

Initial plan

Goal

Validate whether people would sign up for ATS-aware, per-application resume variants before building a generator.

Assumptions

  • Pricing tiers on a landing page would signal a real product, not a throwaway page
  • Email waitlist signups would be enough evidence to justify building the backend
  • A purchased marketing template would not block learning about demand

Planned scope

  • Landing copy focused on ATS filters and dedicated resumes
  • Pricing tiers (Free / Passive / Active)
  • Email-only waitlist signup
  • Login and payment-plan scaffolding for a later launch

Architecture

High-level architecture

flowchart LR
  Visitor --> Landing["PHP landing"]
  Landing --> MySQL[(MySQL waitlist)]
  Landing --> Analytics["GA / Pixel"]

What I learned

  • A waitlist can prove interest before you invent a generation pipeline
  • Scaffolding login and payments early created surface area without teaching anything new
  • Keeping the stack thin forced the real question: would anyone care?

Status

First commit June 12, 2019. Most of the landing and waitlist shipped within that week. Waitlist only; product backend never shipped in this repo. I document it as early product thinking, not a finished SaaS.

Landing page is back up at resumeai.oscarestrada.dev — same waitlist shell, no generator behind it.