Learning and careers decision

FREE-resume.net

A small team or single competent developer can reproduce the core functionality (client-side parsing, editor, templates, PDF export, basic ATS and an LLM hook) in a few weeks; no durable moats prevent replacement and strong open-source prior art exists.

Visit website

Built by Nicolae Maties, who ships 9 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off60 h to build

$20/mo3 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All FREE-resume.net alternatives, with the arithmetic →

What a replacement has to do

  • Upload LinkedIn PDF or start blank → parse/import fields → edit in-browser using templates → optionally run ATS/AI checks → export PDF

What it still won’t have

  • Hosted donations/funding model and public trust indicators (donor list)
  • The current site's existing user base and brand recognition
  • Any proprietary internal tooling or model choices the vendor actually runs (not documented)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

FREE-resume.net does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a privacy-first, client-side resume builder as a static web app (React + TypeScript + Tailwind, client-side PDF parsing with pdf-lib or pdf.js, PDF export via html-to-pdf or browser print, localStorage for persistence). In scope: LinkedIn PDF import and field extraction, editable resume editor with 4 templates, in-browser PDF export, ATS keyword scoring (simple keyword matching + scoring), integration with one LLM API (OpenAI or similar) for optional text polishing. Out of scope: user accounts, server-side storage, analytics collection, team/collaboration features. Include error handling for malformed PDFs, unit/integration tests for parser and export, and CI to produce a deployable static site.
How we checked5 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Evidence score60

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded