Category: FAQ

Your job is the judgment. The AI writes the code and runs the ads. You write down what only you know.

That is the knowledge: your methodology, your rules, and the answers that make your service yours. Per the site, it gets designed once, and every AI worker runs against it. This is the real work; everything else is execution.

What to write down:

1. What you sell, in one plain sentence. Who it is for and what it costs.
2. Your method. The steps you follow and the order you follow them in.
3. Your rules. What you always do, what you never do, and where you say no.
4. Your voice. Real examples of how you talk to customers, so the ads and follow-ups sound like you.
5. Your answers. The questions buyers ask before they pay, and your response to each one.
6. Your line. When a refund, exception, or edge case needs a human call, that call is yours.

The kit itself is free. The 206-page PDF or the AI crawl token costs nothing. The paid path is the 3 week program and the community, and there is a paid product like Prigmar if you want packaged AI employees. No team, no funding, no permission needed. Start with the free kit.

Mouldi

Divide revenue by hours worked. That's it. If you made $4,000 in month three and spent 60 hours, your rate is $66.67 an hour. Total revenue tells you nothing about whether the business is worth your evenings.

Here's the loop I use.

1. Log every hour you touch the business. Building, marketing, support, invoices. One number per week.
2. Log revenue collected, not booked. Cash that landed is the only revenue that counts.
3. Divide. Revenue collected divided by hours logged. That's your real rate for the period.
4. Track it monthly for 12 months on one row of a spreadsheet.
5. Compare months. Early months are ugly. Weekends of setup with no sales means a low rate. That's normal, not failure.
6. Watch the trend, not the first number. If month six pays more per hour than month two with the same effort, the automation is working.

The 12 systems in the Free Builder kit cover the whole loop. The free version is a 206-page PDF or an AI crawl token, no card. Paid options are the $19 AI employees guide and the 3 week program. The number you want gets honest around month four, once the early build hours stop repeating.

Record it. Adjust. Keep going.

Mouldi

You write one document before the AI worker starts. That is the knowledge file: your methodology, your rules, and the answers that make your service yours. Everything else gets generated in the loop.

Here is the order that keeps you from writing too much or too little.

1. Name the one thing you sell and who buys it. One paragraph.
2. Write the rules your work follows. The non-negotiables. Ten to twenty bullets is common.
3. Write the answers to your five most asked customer questions, in your own words.
4. Write three examples of work you would sign your name to. Real ones, not descriptions of them.
5. Stop there. Take it to the AI worker and let it start. Add to the file as gaps show up.

That file is the real work. The 206-page PDF and the AI crawl token do not replace it and they do not write it for you. They give your worker the architecture, the module spec, and the scaffold so your context lands in something coherent instead of a pile of one-off prompts.

The kit is free. The AI crawl token fetches every chapter, module spec and file straight from the server so your worker reads it while it works. The 3 week program and Prigmar are paid, $19 for the AI employees guide.

Keep the file short at the start. You will edit it more than you write it.

Mouldi

The token is an access credential, not a meter, so an AI worker crawling the kit chapters fetches what it asks for. Nothing in the kit spec says the token counts fetches or expires after a set number of them. If you want to know what your worker read, ask it to list the files it pulled, or have it write a short summary per chapter after each fetch. That record lives in your worker's output, not in a dashboard on my side.

If a run goes sideways, stop it. You control the worker, so kill the process or revoke the token from your side and restart with a narrower instruction.

A tight loop:

1. Give the worker a short task that names the chapters and module specs it needs.
2. Have it log each URL it fetches, one line per fetch, with the file name.
3. After the run, read the log and compare against the 12 modules.
4. If it wandered, narrow the prompt to the exact files and run again.

What is free: the 206-page PDF, the reference codebase, the AI crawl token and prompt. What is paid: the 3 week program, the $19 Prigmar prompt set, and community tools when you choose them. I do not have a published fetch limit for the token yet. When I do, it goes on the site.

Keep the loop small. Check the log. Move on.

Mouldi

Yes, but only in part, and I will not pretend otherwise. What you can see today: the AI crawl token fetches every chapter, module spec and file straight from our server, so the worker pulls the whole kit rather than whichever piece it decides to open. The 206-page PDF is also yours as a 13 MB zip if you would rather read the pages yourself.

What I cannot hand you yet: a page-by-page crawl log or timestamp of which file your worker touched and when. That record is still being recorded. I will say so plainly instead of inventing a dashboard.

How to check what your worker pulled right now:

1. Generate the AI crawl token from free-builder.com.
2. Paste the token and prompt into your AI worker.
3. Ask the worker to list the chapters and module files it read.
4. Compare that list against the 12-module spec at /kit-documentation/.
5. Download the zip too, so you have the same source on your machine.

The token and the kit are free. One email gets you both, and you can unsubscribe in one click. The paid pieces are separate: the 3 Week Program, and packaged AI employees like Prigmar at $19.

Cost of waiting: nothing breaks. Your worker still fetches the whole kit. You just cannot audit the request path yet.

The log is on the list. Until it ships, keep your own notes.

Mouldi

You supply the knowledge. The kit gives your AI worker the code scaffold, the module spec, and the build order. It cannot give it your business.

Here is what only you can bring:

• The problem you solve and who pays to have it solved.
• Your rules. How you price, how you qualify a customer, what you refuse to do.
• Your voice. How you talk in emails, on the sales page, in follow-ups.
• Your answers. The 20 questions a customer asks before buying, in your words.
• Your judgment calls. When the AI worker proposes something, you approve or kill it.

The kit says this plainly: the knowledge is the methodology, rules, and answers that make your service yours. Designed once, every AI worker runs against it. That is the real work. Everything else is execution.

The framework is free. The 206-page PDF and the AI crawl token cost nothing. The 3 week program is paid, and the community is where operators trade the prompts and AI employees that work.

The cost of waiting: every week you do not write your knowledge down is a week your AI worker builds someone else's generic version.

Start with one page. Write your rules.

Mouldi

I don't have the exact crawl token expiry number published yet. It's still being recorded, so I won't guess. What I can tell you from the site: the token is a separate paid item from the free kit. The core kit is free as a 206-page PDF or as files in a 13 MB zip. The AI crawl token plus prompt is the paid path that lets your AI worker fetch every chapter, module spec and file straight from the server while it works.

On when the clock starts, I don't have a confirmed policy to point you to. Two common setups exist: from delivery, or from first use. I'm not going to tell you which one applies until it's written down.

What to do right now:

1. Start with the free kit. Download the zip or the PDF. Read chapter one tonight.
2. If you want the token, buy it and note the date you receive it.
3. Email contact through the site and ask for the start date and length in writing.
4. Keep that reply. If the answer is from first use, note the day you point your AI worker at it.
5. Check the FAQ and /kit-documentation/ for the update when it lands.

The cost of waiting is real. Every week you don't ship the MVP is a week without paying customers. The kit is free. Start there.

Mouldi

You do not write code. You direct AI workers, and they write it.

I did four products over 13 years. The part that matters: you read the code, review it, and approve it. Like an editor with a manuscript. You never type it.

Free Builder ships a battle-tested scaffold: frontend, backend, database, auth, payments. MERN plus Next.js. Your AI worker builds inside those boundaries instead of producing a pile of random prompts.

The 206-page PDF walks every layer in plain English. The AI crawl token lets your worker pull each chapter, module spec, and file straight from the server while it works.

Here is how it goes:

1. Get the free kit. PDF or crawl token.
2. Decide what you sell and why it is worth money.
3. Direct your AI worker through the 12-module spec.
4. Read the code it writes and approve it.
5. Wire payments and auth from the scaffold.
6. Start selling. Auto marketing, follow-up, invoicing.

Where it actually runs: 12 systems, 12 chapters, about 3 weeks of evenings and weekends to ship the MVP. Runs alongside a full-time job.

Free: the kit. Paid: packaged AI employees like Prigmar if you want them.

Signing off.
Mouldi

The PDF is for you to read. The crawl token is for your AI worker to read. Same kit, different reader.

Download the .zip and you get the 13 MB illustrated PDF, 206 pages. You open it, you learn the 12 systems, you decide what to build. That is the free path and it works.

The AI crawl token is the same material served so your AI worker fetches it directly while it works. Every chapter, every module spec, every file. No PDF to read yourself. You paste the prompt, hand the token over, and the worker pulls from our server instead of guessing.

What that changes in practice:

1. Your worker reads the real spec, not your summary of it.
2. The scaffold stays coherent because the AI builds inside the boundaries, not from one-off prompts.
3. You spend your evenings directing and approving, not transcribing chapters.
4. You still read code. You just do not write it.

Cost: the kit itself is free either way. The token is a separate paid item from the site, priced there. If you are building solo with an AI worker, the token saves you the copy-paste tax. If you want to learn the framework first, take the PDF.

Mouldi

Your AI worker can read the whole kit from the server: every chapter, every module spec, and the reference codebase files, fetched with the AI crawl token. That is the 12-module spec at /kit-documentation/, the 206-page PDF content, the scaffold (frontend, backend, database, auth, payments), and the prompts that come with the token. No PDF for you to read first.

What you still give it:

1. Your knowledge. The methodology, rules, and answers that make your service yours. That is the real work.
2. Your decisions. What gets built, who it is for, and why it is worth money. Your judgment stays the one asset that cannot be automated.
3. Your voice. The material the AI worker markets in.
4. Your review. You read and approve the code. You do not write it.

So the kit gives the worker structure and starting points. You give it the thing it cannot invent: your expertise and your calls.

Cost: the kit is free, PDF or crawl token. The AI workers are yours to pick, roll your own with Claude or GPT, or use a packaged product. The 3 Week Program and community are separate.

Mouldi