[REQ] https://heywillray.com

[Jach Priboi]

You can already build the site.

Getting someone to pay for it is the whole game.

That's what the comment section on every one of my videos says, over and over, in different words.

Nobody argues the build is hard. They stall on the client.

This is the whole shop: the four-prompt build chain, the demo-first outreach, the lead form that writes to disk before it tries to send anything, and every SOP after the sale, marked plainly by what runs without me and what I still do by hand.

What you get
Six parts. Get clients, build the site, get found, keep the client, run the shop, hire help.
01
Getting clients
Finding and researching a prospect, the demo site you lead with, the outreach message, and the follow-up cadence. The outreach itself is by hand, deliberately. Bulk-sent messages are why that channel is dying.

02
Building the site
The four-prompt build chain and the data-driven skeleton, the same one you'll be running an hour from now. The lead form writes to disk before it tries to deliver, which is the single most important line in the box. Pre-launch QA runs with a human reading the output. Deploy, then verify against the live URL, is by hand, on purpose.

03
Getting them found
A keyword map per client and a running order for what to write, built for you. Reading what the search data means and writing the posts stays by hand. No tool here writes a blog post for a client whose voice it doesn't have.

04
Keeping the client
Onboarding checklist, tracking setup, the monthly report that assembles itself and then gets read and forwarded by a person before it goes out. Nothing about a client's inbox or a client's site sends without you looking at it first.

05
Running the shop
The weekly review, filing, dashboards, content batching. Forty-five minutes a week, same time, off a fixed list.

06
Hiring help
The build test and grading, twenty minutes, the cheapest insurance there is before you hand your name to someone else's work.

The split
Four labels. Every file in the box wears one.
One test decides the label: if you did nothing, what would still happen?

Runs on its own
It happens while you're not looking.
The site skeleton: add one row of data, the pages exist. The lead form, including the disk write that saves a lead before it tries to email you. The dashboards, once your data files are current.

Runs, you approve
Software assembles it. You press send.
Prospect research, the four-prompt demo build, pre-launch QA, the keyword map, the monthly client report. The work gets done in seconds and then waits on you, because nothing touches a client's inbox without a person reading it first.

By hand, on purpose
You, doing the job.
Sending the outreach. Discovery, pricing, closing. Deploying and verifying against the live URL. Writing the blog posts. The weekly review, forty-five minutes. These are the parts you'd be doing by hand in any version of this business, and the box says so instead of pretending.

Built, not running
Five pieces, each with the reason written down.
Code that exists and was tested but isn't switched on, every one stuck behind somebody else's approval queue. Each ships with the manual version that works today. The next section is about exactly this.

Half-built is fine. Hidden is not.
Every one of these carries a label, right in the file: runs unattended, runs with a person approving, built but switched off with the reason written down, or by hand. There's no label for "coming soon." If something in the box claims a status it doesn't have, that's a bug, and it's the kind I want to hear about.

Five pieces are built and not running yet, and every one of them is stuck behind someone else's approval queue, not my code: carrier registration for automated textback, a platform review for a comment-to-DM autoresponder, an API request for pulling business-profile numbers. Each one ships with the manual version that works today and what I'd do differently. Nothing in that list is hidden from you. That's the whole point of writing it down this way.

Who it's for
You'll know if this is you.
Who it's for
You can already build a site. The client is what's stopping you, not the code.
You want a first client, not a ten-person agency. $2,000 a month and your weekends back is a real goal, not a small one.
You'd rather see the whole shop, including the parts that don't run yet, than buy a course that pretends everything is finished.
You've read Build First and you're ready for the rest of it: what happens after the sale.
Before you buy
Two reasons not to.
You haven't sent a message to a real business yet. Build First, $27, is the smaller commitment and it's the same first move this box also teaches. Start there.
You want the client-side sales, discovery calls and pricing conversations done for you. They're by hand here, on purpose. Nobody should automate the first ten minutes of a relationship, and this box won't pretend to.
Which one
Four ways in.
Own a step below this one and you already have part of what's in here. Nothing gets sold to you twice.

$0
Second Brain Starter Kit. Get your own head straight first.
Free, stays free
$27
Build First. Pick a contractor, build the demo, send the message.
1 download
$79
30-Day Execution Bundle. The book, the Loop, the Swipe File, the Vault and the 30 Day Workbook.
5 downloads
$197
The Whole Machine. Everything above, plus the part nobody sells: what happens after the sale.
← You're here
Haven't sent a message to a real business yet? Take the $27 one. It's the same first move and it's a smaller thing to be wrong about.

What you need
An AI that can read and write files on your computer. Claude Code, Cursor, or Claude Desktop all work.
Enough HTML and CSS to copy a block and edit it. The book inside teaches the rest.
PHP on your machine for the site skeleton. The first hour has you run it locally.
An evening for the first hour and the reading around it.
What you don't need
Nothing else.
No framework, no React, no build tools.
No subscription and no account. One payment, files on your disk.
No hosting yet. The first hour runs on your own machine; you buy hosting when a client says yes.
Itemized, so you don't have to email me
Everything in the box. All 161 files of it.
$1,000
CLIENT PAYS
01 · The site skeleton + working lead form
A real contractor site, running on your machine in the first hour.
Runnable PHP, data-driven: add one row of data and the pages exist. The lead form writes every lead to disk before it tries to email anyone, so an outage never eats a lead. This is the same build my clients pay for. You get the shop that makes it.

ONLY
HERE
02 · The service-area matrix
Everybody tells you to build the city pages. Nobody tells you which ones not to.
One file lists every town the client works and every service he sells. Cross them and you've got a few hundred combinations, and most of them are junk. Build them all and Google reads the whole site as thin. The file marks the ones that earn a page. The sitemap lists only those, everything else gets a noindex on it automatically, and the chapter on how to decide is one question long.

EN
In plain English: it stops you building a hundred pages that get the site buried.

ONLY
HERE
03 · The blog publish endpoint
Posts go up on their own. No WordPress anywhere near it.
The skeleton ships with a publish endpoint behind a key. Point whatever you automate with at it, send a post as JSON, and it writes the file, registers it, and the post is live. There's a drafts folder for the ones that aren't ready yet. That's how a client site runs eight posts a month without you writing eight posts a month.

EN
In plain English: the client gets a blog that fills itself and you never log into WordPress.

ONLY
HERE
04 · The four-prompt build chain
Prospect to live demo in four prompts.
Research the prospect, build the demo, run pre-launch QA against a checklist, deploy and verify against the live URL. The exact prompts, in order, with what to check between each.

ONLY
HERE
05 · The SEO operation
How a client site gets found after it exists.
A keyword map per client, the running order for what to write first, and the Search Console routine that tells you what's working. The part agencies charge monthly retainers to do.

ONLY
HERE
06 · The lead hub build
Somewhere around the third client, per-site email dies and nobody tells you.
You get the build session for one hub every client site posts into, and the standards it's built on, which are a list of leads somebody already lost. You're not getting my hub. Mine is shaped by my clients and it would teach you my mess. You're building yours, in the same plain PHP the skeleton already taught you.

$97
OWN PRICE
07 · The 21 SOPs, seven folders
The operation manual, with the honest labels on.
Every SOP for running the shop: prospect research, outreach cadence, onboarding, tracking setup, the monthly client report, the 45-minute weekly review, filing, content batching. Each one carries a Status line saying whether it runs itself or you do it, and most carry “How I decide.” This was about to launch as its own $97 product. It got folded in here instead.

ONLY
HERE
08 · The hiring kit, with answer key
For the day the work outgrows you.
A twenty-minute build test with grading, so you know what someone's work looks like before you hand them your name. The cheapest insurance there is.

ONLY
HERE
09 · YOUR-FIRST-CLIENT.md
The zero-to-one roadmap.
If you've never been paid for a site, this is the file you open first. It sequences everything else in the box toward one goal: the first yes.

$98
OLD TAGS
10 · All five downloads
Every product I sell, included.
Build First, the Demo Site Loop, the Outreach Swipe File, the Filled-In Vault, and the 30 Day Workbook, each as its own download next to the machine. Three of the five don't sell separately any more. Nothing to tick at checkout, no upsell waiting behind the buy button.

And the rest of what's in the six folders.
A QA gate you run before a site goes live. It tells you what's broken instead of the client telling you.
Schema helpers wired into the templates, not bolted on after.
An llms.txt, which most contractor sites still don't have.
Nearby-areas linking, so city pages point at each other instead of sitting there alone.
The mobile call bar. On a contractor site it's the highest-converting thing on the page.
Reviews, projects and awards run off data files. Add a row, the section exists.
A finished site as the answer key, so you can grade a hire against a real one.
The deploy checklist. A fix isn't done until the live URL says it is.
Two more build sessions: the weekly autopilot and the monthly report assembler.
The monthly client report. It's the thing that makes a client keep paying you next month.
Business profile, review requests, churn recovery. Written out, step by step.
Cold outreach through to getting paid. Six documents, in the order you'll need them.
Local ranking factors by trade, because what moves a plumber isn't what moves a roofer.
A business profile and a gap audit for your AI, so it stops guessing at your shop.
What runs and what doesn't. How I decide. The stack. The glossary.
The first month, laid out.
The site build a client pays for
$1,000
The SOP library, at its own scoped price
$97
The five downloads, at their old tags
$98
The build chain, the matrix, the publish endpoint, the hub, the SEO operation, the hiring kit, the roadmap
only sold here
Bought the way these have actually been paid for
$1,195+
The Whole Machine, today
$197
$1,000 is what a client pays for the site build that's in this box. Read the page backwards and that's the other thing it says: your first client covers this five times over.

The free route
You can piece this together yourself. Here's what that looks like.
Six months of working it out on your own, described the way it actually goes.

Sales Page Link - https://heywillray.com/whole-machine?fro...machine-yt