Learning and careers decision

PCM Notes: JEE & NEET

A competent developer can reproduce the useful functionality (hosted indexed archive of scanned notes) in about a week and maintain it cheaply; the official site shows no durable moat that prevents replacement.

Visit website

Built by Apoorv, who ships 5 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-off36 h to build

$0/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 PCM Notes: JEE & NEET alternatives, with the arithmetic →

What a replacement has to do

  • Serve an indexed archive of scanned handwritten notes (browse by subject/chapter, view pages, download PDF/image).

What it still won’t have

  • Polish and QA of the official mobile (App Store) app
  • Brand, discoverability and any curated UX optimizations
  • Existing audience and optional paid-support or donation integrations shown on the site

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

PCM Notes: JEE & NEET 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 lightweight archival web app using Next.js (React) + SQLite deployed to Vercel (or a static S3+CloudFront site) that serves scanned handwritten notes from object storage. Core features in scope: (1) import/upload script to batch ingest folders of page images and generate per-chapter PDF, (2) metadata schema and small SQLite DB with subjects, chapters, pages and download URLs, (3) simple full-text index over chapter titles and optional OCR text using Tesseract for searchable text, (4) responsive SPA to browse subjects → chapters → page viewer (image viewer + PDF download), (5) JSON API endpoints for subjects/chapters/pages and signed/download URLs. Out of scope: native iOS app, payment processing, user accounts, heavy analytics. Include error handling for missing files and bad metadata, logging, and automated tests for ingestion, API endpoints, and UI routing.
How we checked3 sources · 2/3 runs agreed · evidence score 86

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 3 cited sources+3
  • Evidence score86

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 · 3

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