You got the yes. Now run the work around it.
You're already building or selling sites. Now you need a repeatable way to deliver them, catch leads, report back, and keep the client. You get the four-prompt build chain, a site skeleton that runs, lead handling and the operating procedures. Each one says what runs on its own and what needs you.
Haven't contacted a business yet? Start with Build First, $27. Learn the first move before buying the operation.
Get the Whole Machine, $197 Instant download. Runnable PHP, checklists, and all five downloads included.People who stopped reading and went and got one.
These are comments from viewers of the free videos. They aren't reviews of The Whole Machine.
“…your story is very much inspiring and your strategies helped me land my first client, gg's man 💪🔥”
“I recently contacted a nearby school to inquire if they had a website, and they informed me that they did not. I offered to build one for them and explained the benefits of having a website. They accepted my offer and agreed to let me create a website for them. I got the confidence from your videos sir, thank u!”
“Some of us have such little experience with sales that these 'baby-step' videos are actually eye-opening. I've already gotten two leads since your last video.”
“Got my first client a week ago, sold the site for 210, working on another right now. It really is all about confidence! You just gotta pick up that phone📱and get to talkin”
A contractor site, running on your laptop.
200 /
200 /services
200 /areas-we-serve eleven routes, all serving
200 /sitemap.xml built off one copied city block
$ submit the contact form
wrote leads.jsonl before it tried to email
sent will@heywillray.com
In plain English: an hour in you stop reading, because there's a contractor site running on your own laptop.
That lead form writes to disk before it tries to send anything, so a submission survives a broken mail server. It's the difference between losing a client's lead and not, and it's the kind of thing you only build after you've lost one.
Three things to know.
If you already bought the book or the bundle, you already own part of this.
THE-BOOK.html in the box is Build First, lightly edited. Nothing new. Buy this for the rest of the shop, not to read the book twice.
Every download I sell comes with it. Nothing to tick at checkout.
Since August 2026 the $197 includes the lot: 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 itself. Three of those don't sell separately any more. This is the only place to get them.
No refunds. So read the part about who this is wrong for.
The whole box downloads the second you pay, so there's nothing to send back. That puts it on me to be straight about who shouldn't buy this, and there's a section below that does nothing else. If one of those is you, don't buy it. I'd rather you came back in six months.
Six parts, from the first client to the first hire.
Getting clients
Find a contractor with a weak or missing site. Ask if he wants to see a better direction. Build the demo after he replies yes, show it, then discuss price and close. You send the messages and handle the follow-up.
Building the site
The four-prompt build chain and data-driven skeleton. The lead form saves the submission before it tries to email. You review the pre-launch checks, deploy, and verify against the live URL.
Getting them found
A keyword map per client and a running order for what to write. You interpret the search data and write the posts in the client's voice.
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.
Running the shop
The weekly review, filing, dashboards, content batching. Forty-five minutes a week, same time, off a fixed list.
Hiring help
The build test and grading. Twenty minutes, and you see someone's work before your name goes on it.
Four labels. Every file in the box wears one.
One test decides the label: if you did nothing, what would still happen?
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.
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.
You, doing the job.
Sending outreach. Discovery, pricing, closing. Deploying and verifying against the live URL. Writing blog posts. The forty-five-minute weekly review.
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.
What's built but not running, and why.
Five pieces are built but not running. The blockers include carrier registration for automated textback, platform review for a comment-to-DM autoresponder, and API access for business-profile numbers. Each ships with the reason, a manual version you can use today, and what I'd do differently.
You'll know if this is you.
Who it's for
- You're already building or selling sites and need a repeatable operation after the sale.
- You want a small agency that leaves room for your life, with fewer loose ends to chase.
- You want to see the whole shop, including the parts that don't run yet.
- You've read Build First and you're ready for the rest of it: what happens after the sale.
Two reasons not to.
- You haven't sent a message to a business yet. Build First, $27, teaches the first move. Start there.
- You want sales, discovery, and pricing conversations done for you. You still handle those conversations and close the work.
Three ways in.
Own the book and you already have part of what's included. Buy this for the operation around it.
Haven't sent a message to a business yet? Start with the $27 book.
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 to run the site skeleton locally.
- An evening for setup and the reading around it.
Nothing else.
- No framework, no React, no build tools.
- No subscription and no account. One payment, files on your disk.
- No hosting for setup. You run it on your own machine.
Everything in the box. All 170 files of it.
A contractor site you can run and adapt.
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.
HERE
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.
In plain English: it stops you building a hundred pages that get the site buried.
HERE
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.
In plain English: the client gets a blog that fills itself and you never log into WordPress.
HERE
Prospect to live demo in four prompts.
After the owner replies yes, research his business, build the demo, run the checklist, and deploy it so he can see it. Verify against the live URL. You get the prompts in order and the checks between them.
HERE
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.
HERE
Per-site email breaks once you've got a few clients, 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.
The operation manual, with each job's status.
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.
HERE
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.
HERE
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.
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.
I charge $1,000 to do this build for a client. The Whole Machine costs $197, less than a fifth of that. Buying the files doesn't bring you a client.
You can piece this together yourself. I tried that first, one shiny object after another.
Scattered
Forty videos, six Discords and a bookmarks folder. Nothing in there tells you what to do first, or which two things cancel each other out.
Untested
Conflicting outreach advice. You still have to pick an approach, send the message, and see what the owner says.
Outdated
A build tutorial from three years ago on a stack that has moved twice since. Nobody goes back and updates the video.
Unsent
You can finish a whole target list and still never send the first message. I've watched people stop there. Ask if one owner wants to see a better direction. Build after he answers yes.
The information's all out there. The order to run it in isn't, and that's what's in the box.
The sending is yours.
What happens next depends on how many messages you send and how you handle the first call that goes sideways. I'm handing over the routes, the prompts, the files, the SOPs and a site that runs on your machine tonight.
It's all built on US local contractors, the ones with a truck and a phone. Somewhere else the numbers are different. The move still works.
The Whole Machine.
The site skeleton, lead handling, delivery checks, operating procedures, and all five downloads. Your setup starts with a site running locally.
Get Instant Access, $197Instant download, all six of them. Questions? Email will@heywillray.com. Buying also puts you on one useful email a week about building sites, finding clients, and running the business. Unsubscribe anytime.
The questions I get.
So how do you find clients?
Find a contractor whose site is weak or missing. Ask if he wants to see a better direction. Build the demo after he replies yes, then send the link. He can judge the work before you discuss the price, close, and deliver. If you haven't sent any outreach yet, start with Build First.
Why $197?
I charge $1,000 to do this build for a client. The Whole Machine is $197, less than a fifth of that. The SOP library was scoped as a $97 product and the downloads carried $98 in price tags.
Same stuff is free on Google though.
The information is, yeah. The assembly isn't. 170 files, 21 SOPs, a skeleton that runs, 56 webhook rules and a hiring test with a graded answer key, in the order you need them, with the dead ends taken out.
I already bought the book or the bundle. Am I buying it twice?
No. THE-BOOK.html inside the box is Build First with a contractions pass, nothing more. If you bought the book, you already have that piece. Buy this for the rest of the shop, not to read the book again.
What happens after I buy? What's the upsell?
There isn't one. $197, the button goes to Stripe, the download links are on the next screen and in your inbox. No call, no application, no coaching tier waiting behind it. I don't do sales calls.
How long until I sign someone?
I don't know. Your market, outreach, and work rate decide that. You get the first month laid out day by day and twenty new messages a day to send, so you know what to work on.
Any ongoing costs I don't know about?
There's a file that names every tool in the stack, including the two paid ones and what they run. Flat PHP hosting is a few dollars a month. No CRM subscription to start, and nothing in here needs one.
Does this work outside the US?
The move does. The numbers don't transfer. All of this is built on US local contractors, so treat the prices in it as a shape rather than a rate card and check what a site actually goes for where you are.
I've got no degree and no background in this.
Neither did I. Prison before any of it. If you can run a command and open a folder you can run what's in here, and the site is data-driven, so most of the work is editing rows, not writing code.
Do you do refunds?
No. The whole box downloads the second you pay, so there's nothing to send back. Read the two reasons not to buy it further up before you decide. I'd rather lose the sale today than have you feel taken.
Not buying today? Start with the free playbook.
The First Client Playbook is free and stays free. Build First, $27, is the smaller first step toward this if you're not ready for the whole shop yet. Go send your first messages. This will be here.