AI assistants and search decision
Pmprompts
A small static site with a prompt library is straightforward for one technical user to build and maintain; nothing on the site appears to require proprietary data, models, or large-scale operations.
Visit website↗Built by Rahul K, who ships 15 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off21 h to build
$0/mo3 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Serve a browsable prompt library, let users copy prompts, download a prompt pack, and link to recommended tools.
What it still won’t have
- Network placements handled through the BacklinkRocket bundle
- The curation claim: 'Every prompt is tested and optimized for real-world results.' (curation & testing provenance)
- Existing SEO, domain authority, and any audience the live site has
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Pmprompts 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
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
Build a static prompt-library site using Next.js + Tailwind, markdown files for prompts stored in a Git repo, and Vercel for hosting. In scope: a paginated prompt index, tag-based filtering, client-side full-text search (Lunr or Fuse.js), prompt detail pages with 'Copy Prompt' button, a serverless endpoint that zips selected prompts for 'Download Prompt Pack', a Tools directory page linking to external tools, sitemap and robots.txt, basic analytics with Plausible or Matomo, and a simple admin workflow via GitHub PRs. Out of scope: paid listings integration, BacklinkRocket network placements, multi-tenant accounts. Include error handling for failed downloads, tests for search and download endpoints, and CI deploy pipeline.
How we checked
How the score was reached
- Build verdict base78
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score85
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.
- official productPM Prompts — Free AI Prompts for Product Managers
- official productPM Prompts — network note
- official productPM Prompts — curation claim
Integrity checks
What held up, and what did not.
