FIRST 100 PRDS ARE FREE
Tell us your idea. Get a plan an AI can build from.
You write down what you want to build. We ask a few questions. About an hour later you get a PRD — a product requirements document, usually 6,000 to 12,000 lines, that an AI coding agent can build from.
The first 100 are free. Free ones get posted publicly for anyone to read.
free PRDs left. Free ones get posted publicly.
what you watch while it writes
Lightweight CRM PRD
WHERE THIS CAME FROM
I build software with AI agents. This is the first half of how.
I run Zero Point Studio. We build and run our own products, and we build software for other companies. For months now, our new products have been built the same way: we write the plan, then a team of AI agents builds it in one run.
The agents are not the hard part. The plan is. Give an agent a vague plan and you get vague software back. So we stopped treating the plan as paperwork and made it the whole job. It got long — thousands of lines, every table, every screen, every step in order.
This site is the first half of that, for your idea. It writes the plan. The second half is building it, and that is a separate job — I go through both below.
Andrej Simunaj · Zero Point Studio · zeropointstudio.io
Find me on X →HOW IT WORKS
Two steps. That's it.
Step 1 is this site: you get the plan. Step 2 is a builder agent that turns the plan into a working product. You can stop after step 1 and take the file anywhere.
STEP 1
How your plan gets written
This is the real process, in the order it runs. It happens on our servers and you watch it live.
You describe it. An agent asks questions.
Write your idea in one box, in as much detail as you have. An agent reads it and comes back with a short list of questions. Answer the ones you care about, skip the rest. Then you get a summary of what it plans to write. Fix anything that is wrong and press go. This is the only part where you steer, so take your time here.
Draft one.
Agents split the document between them and write the first version: what you are building, what to build it with, the database tables, every feature in detail, the API, security, the design, and the order to build in.
Reviewers pull draft one apart.
Draft one then gets read by reviewers who did not write it. One reads it as the architect: does it contradict itself, is anything left vague, is anything missing. Another comes at it from a different angle — security, testing, the parts people forget. They write up everything they find.
Draft two.
Every finding gets fixed. Not just the easy ones. All of them.
A second review, deeper.
Draft two gets read again, with fresh eyes. This pass goes further, because the obvious problems are already gone and there is more room to look at the hard parts.
Draft three, checked against your words.
The last fixes go in. Then the finished document is read back against what you asked for in step 1, to make sure it is still your product and not the one the agents found easier to write. That is your PRD.
3 drafts · 2 review rounds · 60 to 90 minutes · one file at the end
STEP 2
Then you hand the plan to a builder
A PRD is not a prompt. It is a build order: exact tables, exact API calls, numbered steps, and a finish line for each one. That is what an agent needs to work on its own for hours without asking you anything.
We use an agent called Project Builder. It reads the plan, breaks it into jobs, and hands each job to another agent. It tests the code that comes back, sends the failures out to be fixed, and tests again. At the end it reads through the whole thing and tidies it up. This runs for hours, not minutes.
For that to work, the platform has to let one agent hand work to other agents and wait for them. Ours is built for CRHQ.ai, which takes a finished PRD and runs the whole build in one go.
Works where agents can hand off work · built for CRHQ.ai
SEE A REAL ONE
Here's one we made. Read it.
This is the plan this site was built from. GeneratePRD was written as a PRD first, then built from it by a team of agents — 6,667 lines, covering every database table, every API call, every screen, and the order to build them in. Read the real thing instead of taking our word for it.
GeneratePRD.com — Product Requirements Document #
Version: 3.0 (Final) Type: AI-Agent-Executable PRD Executor: CRHQ Project Builder agent Status: Ready for Execution Date: 2026-07-31
Table of Contents #
- 1. Before You Start — User Customization
- 1.1 Purpose & Rules for the Executing Agent
- 1.2 Customization Q&A
- Q1: Production Domain
- Q2: Product Name, Tagline & Funnel Constants — LOCKED (brief-confirmed)
- Q3: Brand Accent Color — LOCKED (drafting decision, committed)
- Q4: UI Theme — LOCKED (drafting decision, committed)
- Q5: Application Port
- Q6: Database Name & Connection
- Q7: Stripe Mode & Keys
- Q8: GitHub OAuth App Configuration
- Q9: Resend Sending Domain & From Address
- Q10: CRHQ Backend URL & API Key
- Q11: Concurrency Limit — LOCKED default, env-tunable
- Q12: Founding Free Pool Size — LOCKED default, env-seeded
- Q13: Price Ladder — Tiers, Prices & Capacities — LOCKED (brief-confirmed)
- Q14: Publish-Publicly Discount — LOCKED (brief-confirmed)
- Q15: Free-Eligibility Rules — LOCKED (brief-confirmed)
- Q16: Intake Caps — LOCKED (brief-confirmed)
- Q17: Session Cookie Name & Lifetime
- Q18: Support Email
- Q19: Analytics & Trackers — LOCKED default
- Q20: Bootstrap & Seed Behavior
- 1.3 THE Canonical Environment Variable Table
- 1.4 Post-Q&A Agent Behavior
- 2. Project Overview & Vision
- 3. Technology Stack & Architecture
- 3.1 Stack Summary (one table, no alternatives)
- 3.2 Decision: API Routes Inside Next.js (no separate Express service)
- 3.3 System Architecture Diagram
- 3.4 CRHQ Integration: The Real Surface (grounding)
- 3.5 THE AgentBackend Adapter (canonical contract)
- 3.6 SSE Transport (product → browser, canonical)
- 3.7 Queue Worker (
generateprd-worker, canonical) - 3.8 Process Topology (PM2)
- 3.9 nginx
- 3.10 Dockerized PostgreSQL
- 4. Coding Conventions & Best Practices
- 4.1 TypeScript Strictness & Build Setup
- 4.2 Project Folder Structure (full tree, canonical)
- 4.3 Naming Conventions
- 4.4 Error Handling
- 4.5 Logging (pino, structured)
- 4.6 Validation with zod (boundary rule)
- 4.7 Next.js Server/Client Discipline
- 4.8 Testing Conventions
- 4.9 Git Conventions
- 4.10 No-Dependency-Bloat Rule
- 5. Database Schema & Migrations
- 5.1 General Conventions
- 5.2 Entity-Relationship Diagram
- 5.3 The Generation State Machine (CANONICAL)
- 5.4 Table Definitions
- 5.5 Canonical Queries & Concurrency Patterns
- 5.5.1 Free Eligibility Check (read-only, no locks — UI display)
- 5.5.2 Atomic Free-Slot Claim (transition T4) — EXACT transaction
- 5.5.3 Current Tier Resolution & Tier Sale
- 5.5.4 Queue: Position Derivation & Worker Dequeue
- 5.5.5 Intake Guards: Active-Intake Limit and Message Caps
- 5.5.6 Stall Sweep and Hard-Timeout Sweep (transitions T11, T13/T14)
- 5.5.7 Orphan Reconcile Sweep (crash safety)
- 5.5.8 Free-Claim Release (ops recovery for a dead free generation)
- 5.5.9 Retention, Prune and Token-Expiry Jobs (daily, plus token prune nightly)
- 5.5.10 Moderation Cooldown Query
- 5.6 The
updated_atTrigger - 5.7 Migrations
- 5.8 Seed Script
- 6. Core Features
- 6.1 Authentication — GitHub OAuth
- 6.2 Intake Flow & Intake Agent
- 6.3 Pricing, Founding 100 & Stripe Checkout
- 6.4 Queue & Concurrency
- 6.5 Generation Orchestration & Generation Agent Prompt
- 6.6 Live Progress Experience
- 6.7 Delivery Page
- 6.8 Public Directory & SEO
- 6.9 Email Lifecycle (Resend)
- 6.10 Account & Settings
- 7. API Design
A second one, written the same way: a lightweight CRM, planned front to back. 10,365 lines, public on GitHub, free for anyone to use.
PROOF
Everything on this list was built this way.
These are real products with real users, not demos. Same process every time: write the plan, then let the agents build it.
- TranscriptAPI →
A YouTube transcript and search API. Around 15 million transcripts a month.
- YouTube2Transcript
Paste a YouTube link, get the transcript.
- Recapio →
Tools for YouTube: summaries, transcripts, chat and research. Tens of thousands of users.
- Zillapi →
US property data for developers and agents. Photos, taxes, schools, in one call.
- StayingAPI →
Live prices and availability across Airbnb, Booking.com and Vrbo, in one call.
- CRHQ →
The platform all of this runs on. Agents on real servers, working around the clock.
YOUR OPTIONS
Three ways to use this. One of them is free of us.
We are not the only way to get this done. Here is the honest list, cheapest first.
Run it yourself
The instructions our agents follow are open source. Take them, point your own agent at them, and do all of this without paying us anything. It takes setting up, and you supply the agent time.
Get the instructions →Get the plan here, build it anywhere
Pay for one PRD, download the file, and hand it to whatever coding agent you already use. We do not need to be in the second half. The file is yours.
Generate your PRD →Let CRHQ do both halves
Get the plan here, then hand it to Project Builder on CRHQ and let it build the product, put it online, and keep it running.
Open CRHQ.ai →WHY CRHQ
Why we build on CRHQ.
Here is what it does that matters when a build runs for hours.
Agents can hand work to other agents.
One agent runs the job and gives pieces of it to a team. They work at the same time and report back when they are done. A build this long does not finish without that.
It tests as it goes.
Code gets tested when it is written, not at the end. What fails goes back to the agent that wrote it, and then it gets tested again. That happens several times before anything is called done.
The product runs on the same server the agents do.
When a piece is finished it is already online. There is no separate launch day, and no handing files to somebody else to put up.
Agents can keep it running afterwards.
Once it is live, agents on that same server can fix things, add to it, and answer customer email on their own.
PRICING
The first 100 are free. Then the price goes up.
The first 100 PRDs cost nothing, and they get posted publicly. After that it's $19 for the next 50, then $29 for 50 more, then $49 from there on. You pay once per PRD. There is no subscription.
FIRST 100 — FREE
OPEN NOWFree
one PRD, one time
100 of 100 left
- Posted publicly, forever
- One per GitHub account, 6 months or older
- The same PRD paying customers get
TIER 1
CURRENT PRICE$19
one PRD, one time
50 of 50 left
- Private — only you can see it
- Post it publicly and pay $10 less
- Skips ahead of the free line
- Yours to use however you want
TIER 2
$29
one PRD, one time
then 50 at $29
- Private — only you can see it
- Post it publicly and pay $10 less
- Skips ahead of the free line
- Yours to use however you want
TIER 3
$49
one PRD, one time
this price stays
- Private — only you can see it
- Post it publicly and pay $10 less
- Skips ahead of the free line
- Yours to use however you want
One payment, one PRD. There are no do-overs, so put real detail into your answers up front.
PUBLIC LIBRARY
Read what other people got.
Lightweight CRM
A focused customer relationship manager for small teams that need pipeline clarity without enterprise complexity.
10,365 lines · Jul 25, 2026
dev toolGeneratePRD.com — the PRD this site was built from
The product requirements document GeneratePRD.com was planned from, published in full so the process can be checked rather than believed.
6,667 lines · Jul 24, 2026
FREE SPOTYours could be here
Every free PRD gets posted in this library.
100 free spots left
OPEN SOURCE
Everything we use is public.
The instructions our agents follow are on GitHub. You can read them, copy them, and run them yourself — that is option one above. What you pay us for is that it's already running: the questions, the queue, an hour of agent time, and a finished document at the end.
QUESTIONS
Questions people ask.
How long does it take?
About 60 to 90 minutes once your PRD starts, plus any time waiting in line. We write 10 at a time, and paid PRDs go first. You'll see your place in the line and watch the writing happen live. We email you when it starts and when it's done, so you can close the tab and go do something else.
What do I actually get?
One file. It's a markdown document, usually 6,000 to 12,000 lines depending on how big the product is. It covers what you're building, what to build it with, the database tables, every feature in detail, the API, security, the design, and a numbered build order written for an AI agent to follow. You can read it on the site, download it, or send someone a link.
Is this really how you build software?
Yes. Our products are planned this way and built this way, and the plan this site was built from is published here for you to read. It is not a demo of the process, it is the process.
What does "an agent can build from this" actually mean?
It means the plan covers the parts that break real products: the database, the API, login, payments, errors, security, and what order to do it in. A good coding agent gets a long way on that on its own. It does not mean nobody looks at the result. We review what our agents ship, and you should too.
Why is my free PRD public?
That's the trade. You get the whole thing for free. In return we post it in our public library and it stays there, with a small "Generated at GeneratePRD.com" line at the bottom. It's how we show people the product is real. If your idea needs to stay quiet, pay for one — paid PRDs are private.
Can other people use my public PRD?
Yes. Public PRDs are under a CC BY 4.0 license. Anyone can read it, build it, or sell what they build, as long as they credit GeneratePRD.com. Paid private PRDs are yours alone. We don't post them, and we don't claim anything you build from them.
Can I get changes, or a refund?
No changes. One payment buys one PRD, written once. There are no revision rounds. The questions at the start are where you shape it, so answer them properly. If it breaks on our end, we run it again for free. If we still can't deliver, email us and we'll make it right.
What tech will it pick?
Whatever fits your idea. If you name the tools you want, the PRD uses them. If you don't, our agents pick boring, popular technology that a coding agent is least likely to get wrong. Either way, the PRD names every choice and says why.
Can an AI really build from this?
That's the point of the format. Exact database tables, exact API calls, numbered steps, and a clear finish line for each one — written for an agent, not just for a person. The example on this page is the plan this site was built from, so you can see exactly what that looks like. A good coding agent gets a long way on its own. You should still check what it builds.
Why GitHub login only?
Two reasons. Most of our users already have a GitHub account. And free PRDs need a limit — one per account, and the account has to be at least 6 months old. It also means no passwords for us to keep safe.
What is CRHQ?
CRHQ.ai is the company behind this site, and the platform our writing agents run on. It also has an agent called Project Builder that takes a finished PRD and builds the product from it. That's step 2.
Ready? Tell us your idea.
It takes a few minutes to describe what you want. About an hour later the PRD is in your inbox.
100 of 100 free PRDs left. Free ones get posted publicly.