Filling a resume template and improving the wording with an LLM call is a genuinely simple combination — a form, a PDF template, and one well-crafted prompt.
Build it
Effort: an eveningRunning cost: $0/mo to start
Why CanICodeThis says Build it
A form collecting work history, education, and skills, rendered into a clean PDF template, is well-documented templating work
One LLM API call to tighten up bullet-point wording (given the job title and description) is a bounded, well-understood prompt pattern
Saving and editing multiple resume versions is ordinary CRUD
The parts that'll cause problems
Multiple polished template designs take real design iteration to look genuinely good, not just functional
Tailoring a resume automatically to a specific job posting (parsing the posting and re-weighting content) is a step beyond simple wording improvement
ATS (applicant tracking system) compatibility checking is a real, separate feature if you want it
How I'd build this
frontend
Next.js
database
Supabase
auth
Supabase Auth
hosting
Vercel / Cloudflare Pages
MVP scope
A form for work history, education, and skills
One clean PDF template
An LLM call to improve bullet-point wording
Save and edit multiple versions
Postpone to v2
Multiple template designs
Auto-tailoring to a specific job posting
ATS compatibility scoring
What it actually costs to build
AI agent — with a subscription (Claude Pro/Max, Cursor, etc.)
$0 marginal
AI agent — pay-per-use API, no subscription
$16–$27 one-time
Hosting, once it's running
$0/mo (free tier)
Domain name, if you want your own
~$12/yr
The build prompt
Build me a resume builder: a form for work history, education, and skills, rendered into a clean single PDF template. A 'polish my bullet points' button that sends the raw text plus a target job title to an LLM API and returns tightened wording I can accept or edit. Save multiple resume versions per account. SQLite or Supabase behind a small API, single-user login.