Free Builder Kit — illustrated PDF + reference codebase

My AI worker keeps failing when it tries to fetch the files, how do I get the kit into it reliably?

Skip crawling. Download the zip and hand your worker the files directly.

The AI crawl token is a convenience, not a requirement. It fetches every chapter, module spec and file from our server. When your worker chokes on that fetch, you lose a session and gain nothing. The zip is the same content, 13 MB, sitting on your disk.

Here is the reliable path:

  1. Go to free-builder.com and download the kit (.zip, 13 MB).
  2. Unzip it into your project folder.
  3. Point your AI worker at that folder instead of a URL.
  4. Feed it the 206-page PDF chapter by chapter if it has context limits.
  5. Keep the scaffold (frontend, backend, database, auth, payments) in view so it builds inside the boundaries.
  6. If a fetch fails again, stop retrying and check whether the token expired or the file count changed. Those are the two usual causes.

The kit, the PDF and the crawl token are free. One email, unsubscribe in one click. The paid pieces are the 3 week program and Prigmar at $19. Nothing about fetching is paid.

Build on the local copy. It never times out.

Mouldi

What can my AI worker actually crawl with the 30-day token, and what does it still need me to tell it?

Your AI worker crawls the kit itself: every chapter, every module spec, every file. It pulls them straight from our server. That means the 12-module spec, the 206-page PDF content, and the reference codebase files come in without you reading a PDF and retyping anything.

The token covers the framework and the scaffold, nothing more. It fetches from the server on each call, so the crawl stays current for as long as the token is live. Downloading the kit files works the same way if you skip the token, you just move them yourself.

What it still needs from you:

  1. Your knowledge. The methodology, rules, and answers that make your service yours. You design that once. Every AI worker runs against it.
  2. What you sell and why it is worth money. The AI writes code, you decide the product.
  3. Your voice for marketing. The worker markets in your voice, so it needs your voice first.
  4. Approval on code. You read and approve, the same way an editor reads a manuscript.

Stack is MERN plus Next.js. You direct, the AI workers write. The framework and token are free. Every customer and every dollar stay yours.

Mouldi

Stop Copy-Pasting Your Own Answers

The Five Questions You Answer Every Week Are Your Product

Every consultant has a personal top-five list. Mine was: How do I set up a website?, What should my pricing be?, How do I get more leads?, How do I write a proposal?, and How do I handle a difficult customer? I typed variations of those answers for thirteen years. Each time, I felt productive. Each time, I was selling my judgment for a one-time fee.

Continue reading “Stop Copy-Pasting Your Own Answers”

The Free 30-Minute Diagnosis Is a $200/mo Feature

The Diagnosis You Give Away Is the Product You Should Sell

Every consultant, coach, or freelancer knows this story. A prospect books a quick call. You walk them through their problem, diagnose the issue, and hand them a roadmap. They thank you. They say they'll be in touch. Then they disappear. You never hear from them again, and you never see a dollar.

Continue reading “The Free 30-Minute Diagnosis Is a $200/mo Feature”

You’ll spend 4 hours on a proposal. Your AI worker spends 4 minutes.

The Proposal Is a Product, Not a One-Off

You know the drill. An RFP lands, your heart rate spikes, and you carve out an afternoon to rewrite the same scope, price, and timeline you've written a hundred times. That proposal isn't a one-off. It's a product. Every time you hand-craft it, you burn judgment on work a machine could do.

Continue reading “You’ll spend 4 hours on a proposal. Your AI worker spends 4 minutes.”

What’s the difference between giving my AI worker a vague prompt and giving it a written brief with the target user?

A vague prompt makes your AI worker guess who the buyer is. A written brief with the target user tells it who to sell to, so the output stops being generic and starts being usable.

When I write the brief, the AI stops inventing a customer. It writes the landing page, the emails and the pricing for one person. You keep the judgment, it does the typing.

Here is the loop from Free Builder:

  1. Name one target user. Not "small businesses." A bookkeeper with 12 clients on spreadsheets.
  2. Write their problem in their words. One paragraph.
  3. List the answers only you have. That is your knowledge, and it is the real work.
  4. Hand that brief to your AI worker with the Free Builder scaffold. The scaffold keeps the code in bounds.
  5. Read the output. Approve or send it back. You are the editor, not the typist.

Cost of a vague prompt is evening after evening rewrites. Cost of the brief is one hour up front.

The kit is free: a 206-page PDF or the AI crawl token your worker crawls while it builds. Paid items are the 3 week program and the $19 AI employees book. Nothing else.

Write the brief first.

Mouldi

Can my AI worker only read the kit, or does it need something from me that it can’t get from the files?

The AI worker reads the kit. The judgment stays with you.

Your AI worker can crawl the whole kit with the AI crawl token. It fetches every chapter, module spec and file straight from the server. No PDF to read yourself.

What it can't get from the files is you. The knowledge is your methodology, your rules, and your answers. That part is not in any chapter. You design it once, and every AI worker runs against it, whichever tool you pick.

The split looks like this:

  1. You decide what you sell and why it's worth money.
  2. You write the methodology and rules that make the service yours.
  3. Your AI worker crawls the kit and reads the 12-module spec.
  4. You direct what gets built and review the code. You read it, you don't type it.
  5. Your AI worker writes the code inside the scaffold.
  6. You approve it and start selling.

The kit is free. The 206-page PDF or the crawl token, both free. The paid part is Prigmar at $19 if you want a packaged AI employee instead of rolling your own with Claude or GPT.

Budgets and timelines for custom knowledge work aren't recorded yet. I'll post real numbers when I have them.

Mouldi

Your AI worker just closed a lead while you were on vacation. Here’s how.

The Vacation Email That Changed How I Sell

Last summer, I was on a beach with no signal. My phone was off. My laptop was in a locker. I had set up an AI worker the week before, just to test it. I gave it my FAQ list, my pricing sheet, and a link to my calendar. I told it to answer questions and book calls for anyone who matched my ideal customer. Then I left.

Continue reading “Your AI worker just closed a lead while you were on vacation. Here’s how.”

Your 3 p.m. client call is the exact moment you lose money.

The 45-Minute Call That Cost You $112.50

You bill $150 an hour. The call runs 45 minutes. You give the same answer you gave Tuesday. That's $112.50 for a script you already own. Multiply that by three customers a week. You just lost $337.50. And that's just the money. You also lost the time you could have spent building a product.

Continue reading “Your 3 p.m. client call is the exact moment you lose money.”