Free Builder Kit — illustrated PDF + reference codebase

How much can I actually save on tools and hiring if I use the free kit instead of a technical cofounder or paid stack?

I can't put a dollar figure on it because I track what I spend, not what someone else spends on a cofounder. What I can tell you is what the kit costs you: nothing. The 206-page PDF and the AI crawl token are free. You pay for your own AI worker and your infrastructure, and that's it.

What it replaces:

  • A technical cofounder. The scaffold ships with frontend, backend, database, auth and payments already wired. Your AI workers build inside those boundaries. You read and approve code, you don't write it.
  • The course and program stack. The full 12-module spec is published at /kit-documentation/ so you can read the whole path before you spend anything.
  • Tool subscriptions. Marketing and support run on whatever you already pay for, Claude or GPT, Buffer plus Intercom, or a packaged product like Prigmar. The framework doesn't lock you into one path.

The real cost of waiting is the three weeks. The MVP takes about that long in evenings and weekends. Every month you pay someone else to decide what to build is a month you're not keeping the customers or the revenue.

Mouldi

What exactly will I never be charged for, and what is the one thing that actually costs money?

You get the Free Builder kit for free. That's the 206-page PDF or the AI crawl token. You also get the system for free. That's the framework and the AI employees. The prompt for your AI worker is free too.

The one thing that costs money is the AI crawl token plus prompt. That is $19. It's the fastest way to get your AI worker crawling the kit. You can also download the files for free.

There are no other costs. You keep all the revenue. No team needed. No code needed. No funding needed.

When does my 30-day crawl token actually start counting down, and can my AI worker burn through it by accident?

The token starts counting the moment you get it, so grab it when you're ready to work, not weeks before. And yes, a careless worker can burn through fetches, so point it only at what you need.

The crawl token is one of two ways into the free kit. One is the 206-page PDF you read yourself. The other is the token your AI worker uses to fetch every chapter, module spec and file straight from the server while it works. The kit itself is free. There's no paid tier behind it, nothing to unlock.

Here's how I'd keep the token from getting eaten:

  1. Decide what the worker fetches before you start it. Chapters it needs, module specs it needs, nothing else.
  2. Run it in a bounded spec so it does not loop back through the same files.
  3. Check the worker's output after the first pass, not at the end.
  4. Keep the 12-module spec handy at /kit-documentation/ so it has a map and stops guessing.

I don't publish an exact fetch count or a per-request breakdown. That detail is still being recorded, so I won't quote a number I can't back. Watch your own usage in the first session and you'll know your pace.

The cost of waiting is simple. The token is free now. Spend months deciding and you ship nothing, which is the only real bill here.

Get the kit, point the worker at one module, review it. That's the first evening.

Mouldi

Can my AI worker keep working on the build while I’m away or dealing with something in real life?

Yes. Your AI worker can keep going while you step away. You're the operator, not the typist. You give the worker the kit and the module spec, it writes code inside the scaffold, and you review and approve when you're back.

The catch is judgment, not typing. The worker builds inside boundaries you set. It won't decide what to sell or why it's worth money. Those calls stay with you, and that's fine, because you can make them in ten minutes, not ten hours.

The free kit is the PDF and the reference scaffold. The AI crawl token is free too, if you want your worker to fetch chapters and file specs straight from the server instead of you reading them. Paid stuff: the 3 Week Program and Prigmar at $19 for AI employees. No team, no funding, no code required.

The cost of waiting: every week you don't ship, that's a week of customers you never get to serve. Nothing moves until you point the worker at something.

Start with the kit. Hand the token to your worker. Check in when life lets you.

Mouldi

P.S. The 12 chapters take about 3 weeks of evenings and weekends, so a few days away won't break the run.

If I can’t code, at what point do I actually have to make a decision myself instead of letting my AI worker handle it?

You make the decision at the start of each module, not in the middle of the code. Your AI worker writes and fixes code. You decide what gets built and why it is worth money.

So the moments where you step in:

  1. Before any building. You define what you sell and who buys it. The AI cannot pick your business for you.
  2. When you approve the plan. The 206-page PDF walks you through 12 modules in plain English. Each one ends with a choice only you can make.
  3. When you review the code. You read it like an editor reads a manuscript. You do not type it. You approve it or send it back.
  4. When the scaffold asks for a business call. Prices, refund rules, what goes in an email. Your judgment, not the AI's.
  5. When something breaks in a way the AI loops on. You stop it, restate the goal, and let it retry inside the scaffold boundaries.

The kit is free as a PDF or an AI crawl token. The 3 Week Program and the community are paid. Waiting costs you nothing but time, and time is the one thing the program compresses to about 3 weeks of evenings and weekends.

You are the operator. That never gets delegated.

Mouldi

How do I stop my AI worker from being blocked while I sit on approvals, does the kit actually ship decision points?

Yes, the kit ships decision points, but they are not a separate approvals module. The 12-module spec walks through every layer with defined checkpoints where you review and approve what an AI worker produced. The PDF shows the sequence and the scaffold keeps the AI inside coherent boundaries, so it does not stall waiting on a blocked branch while you are away.

Here is how I keep a worker moving between approvals:

  1. Read the module spec first. Each module lists what the worker delivers and where your sign-off sits.
  2. Approve the spec, not each keystroke. The worker runs against the module reference and stops only at the named checkpoint.
  3. Batch your review into one evening or weekend block. A few focused sessions is the pace the program is designed for.
  4. Keep the scaffold in place. It holds frontend, backend, database, auth and payments steady, so the worker is not improvising and waiting on you.
  5. Trade prompts in the community when a worker gets stuck.

The core kit is free: the 206-page PDF or the AI crawl token. Paid: the 3 Week Program at $19 and the community. The cost of waiting is simple: another month of evenings where nothing ships. The approvals do not disappear. You just stop being the bottleneck.

Mouldi

Do I actually need to pay for a technical cofounder or a contractor, or can the token and the 85-file codebase replace that?

You do not need a technical cofounder or a contractor to ship the MVP. You direct AI workers and they write the code. Whether that replaces a contractor for every job later is a separate question, and I would not pretend the kit covers everything a person does.

What you get free: the 206-page PDF and the AI crawl token. The token lets your AI worker fetch every chapter, module spec and file straight from the server while it works. No PDF to read yourself. Both cost nothing.

The codebase is the 85 files you mentioned. It ships a scaffold for frontend, backend, database, auth and payments, built on MERN plus Next.js for the marketing site. Your AI builds inside those boundaries instead of producing a pile of one-off prompts. You read the code and approve it. You do not write it.

Where you still spend money: AI tooling like Claude or GPT, or a packaged product like Prigmar at $19. Marketing and customer service can start with Buffer and Intercom, or humans when it makes sense.

The cost of waiting is the weeks you spend hunting for a cofounder and equity you give away before you have a single customer. The free kit ships in roughly three weeks of evenings and weekends.

Start with the kit. Hire only when a real bottleneck shows up.

Mouldi

Does the 30-day crawl token start counting down the day I download it?

I don't know yet, and I won't guess. The token start date isn't recorded in what I have here. The token paperwork gets written now, so treat that as pending until I post the exact terms.

What I can tell you plainly:

  • The kit is free. The 206-page PDF and the 13 MB zip cost nothing.
  • The AI crawl token is the paid piece. It fetches every chapter, module spec and file from my server so your AI worker works from the source instead of you reading a PDF.
  • I don't have a confirmed number for the token's price or its start date in front of me. When those are set, they go on the site, not in a comment.

Why it matters: if the clock starts at download, you lose days to setup before your AI worker does anything. If it starts at first fetch, you download whenever and start when you're ready. Different answers, different costs for you. Waiting on my answer costs you nothing, because the free kit is the same today either way.

My plain advice: grab the free PDF now, map your 12 modules, and don't pay for a token until I publish the terms.

I'll post the terms here when they're written.

Mouldi

If the kit and token are free, what exactly am I choosing between when I check out?

The free kit is one thing: the 12-module playbook. You pick how it reaches you. Nothing at this checkout costs money.

Here are the two paths:

  1. The PDF (.zip, 13 MB). You download a 206-page illustrated guide plus the reference codebase. You read it yourself and point your AI worker at chapter specs as you go. Cost: $0.
  1. The AI crawl token. Your AI worker gets a token and pulls every chapter, module spec and file straight from the server while it works. No PDF to read yourself. Cost: $0.

Pick the PDF if you want to read the framework first and understand the loop before you run anything. Pick the token if you already have your AI worker set up and want it reading the source material directly instead of you copying chunks into prompts. Either way you get the same scaffold: frontend, backend, database, auth, payments.

The cost is your evenings. About three weeks of them to ship, per the program. The cost of waiting is that you spend those same evenings reading about AI replacing jobs instead of selling something.

What's paid: the 3 Week Program, the community, and products like Prigmar at $19. The kit and token are free. One email, unsubscribe in one click.

Go download one and see which fits how you work.

Mouldi

Second Sale at Zero Extra Hours

Here Is the Number: $900 for One Answer, Repeat

A consultant I know answers the same compliance question six times a month. She bills $150 an hour. Each answer takes about an hour once you count the email, the follow-up, and the call. That is $900 a month for one answer she already knows by heart. She has given that answer for two years. The number does not change because the question does not change.

Continue reading “Second Sale at Zero Extra Hours”