Turn your pricing knowledge into estimates that take minutes instead of days.
Hand me your cost codes, your job costing, and your past estimates. I build the way your company already prices work into an AI estimating skill that runs on your machine, then install it with you.
Are you still spending days on every estimate?
You want a faster way to get a solid budget number in front of a homeowner.
You know you should be using AI for this by now, and you have no idea where to start.
You have tried it, and you did not trust the number it gave you.
Your estimating method is cobbled together out of spreadsheets and memory, and you have always wondered how other builders actually do this.
I built an AI estimating tool for builders. Then I found out why most of them never got it working.
I spent 21 years building custom homes and remodels, and I have priced well over a thousand projects.
When I started using Claude, the first thing I thought was that there had to be a way to codify all of it. Every rule I follow pricing a renovation, a remodel or a custom build, written down once, so the machine could run the process instead of me running it from memory.
So I built it. Then I put it in the hands of builders across North America.
I watched what happened.
After hearing back from enough of them, I started to see why so many capable builders never got it working.
The problem wasn't the tool, the training, or their effort. It was that every one of them was missing the same thing.
That was when I realized builders don't need a third-party estimating service, and they don't need a course to figure it out themselves.
Someone who can take your cost codes, your job costing, and your past estimates, and turn all of it into one working system.
Someone who knows which calculation belongs on which line, and gets it right the first time.
But building the system is only half the job.
It has to be tested against a real project, corrected where it's wrong, and installed on your machine by you, with me right there guiding you.
That is why I created the AI Estimating Build.
Here is what it is.
You send me your files. I turn the way your company already prices work into an AI estimating skill that runs on your own machine. It reads your drawings, does the takeoff, writes the scope in your words, and prices the job against your own numbers. Four weeks from start to finish.
Your cost index
I build your cost index from your own cost codes and your own job costing.
The test run
I run it against one of your real projects, so we find out where it's wrong on a job you already know the answer to.
The install
We get on one screenshare, install it on your machine, and price a second job together.
So how do we get twenty years of pricing out of your head and into a tool that runs without you?
Apply for an AI Estimating Build →How I get your estimating out of your head, and into the AI skill
We establish how you price
You fill out an intake form covering how your company actually runs work:
- What you self-perform and what you sub out
- Your internal labor positions and rates
- What markup you charge and how it's applied
- Contract type: fixed price, cost plus, or both
- What format your estimate has to land in
You also send me four things: your cost code set, job costing from 3 to 5 completed projects, 3 to 5 past estimates that show your written scope and the math behind it, and one live project with a dimensioned drawing set and schedules. Then I take it from there.
I build your estimating system
Working from your files, I build:
- Your cost index, the spine the skill prices from. Every item you carry, priced off your completed jobs, with the right calculation on every line: unit rate, area, volume, recipe, or labor hours.
- The judgment calls underneath it, including every place one of your cost codes has to absorb several of mine, or split into more than I carry.
- Your writing voice, section by section, pulled from your own past estimates.
- Your self-perform defaults, labor rates, and markup wired in.
- The export format your software actually needs.
This is judgment work, not data entry. It's why I only take five a month.
We test it on your real project
I run the full estimate on the job you sent. A job you already know the answer to, so you can see exactly where it's off.
You mark it up and tell me where the numbers are wrong. You get five days. Every correction gets written back into your cost index, so it's right on that line for every job you ever price after this one.
This step is the difference between a tool that's close and a tool you'd actually send a homeowner a number from.
We install it together
One screenshare, sixty minutes. On that call we:
- Install the skill on your machine
- Price a second job live
You don't get a zip file and a set of instructions. You leave that call having produced an estimate yourself, on your own machine, with your own numbers. That's the whole point of it.
What you own when this is done
Four weeks from the day you start, here is what is sitting on your machine:
Your cost index
Every cost item you carry, priced from your own job costing, with the right calculation attached to every line. The spreadsheet you've been meaning to build for years, finished.
Your writing voice
Scope written the way your company writes scope, section by section, built from your own past estimates.
Your estimating skill
The whole system packaged to run on your machine in Claude Cowork. Reads the drawings, does the takeoff, prices it against your index, and writes the scope in your words.
Three deliverables on every job
Your estimate in your software's format, your inclusions, exclusions and assumptions document, and your allowances schedule. Every time, without you having to assemble any of it.
A tested estimate on a real project
Corrected against your own numbers, so you start from a system that's already been proven on one of your jobs rather than one that's never been used.
The install session
Sixty minutes, screenshare, and you finish it having run the thing yourself.
I only take five builds a month.
I accept a maximum of five builds each month, and I do every one of them myself.
Because mapping your cost codes onto the right calculations is judgment work. Your codes don't line up with anyone else's.
That part can't be delegated, automated, or rushed.
If you have your cost code set, job costing from 3 to 5 completed projects, 3 to 5 past estimates that show your written scope and the math behind it, and one live project with a dimensioned drawing set and schedules, you can apply below.
Watch it price a real custom home, start to finish
An estimate on a custom home used to take me 24 to 36 hours. In the video below I do one in under 30 minutes.
How I use Claude Cowork to estimate custom home builds in under 30 minutes
Real drawings, real cost codes, real outputs.
The number at the end isn't the point. Where it came from is. Every price in it was already in a cost index built from jobs that were actually completed and actually costed, which is the only reason it could move that fast.
That index is the critical thing I build for you.
The AI Estimating Build isn't for everyone
This is built for established custom builders and remodelers who already have a costing structure in place, and who are losing days to estimating by hand.
This is for you if
- You have a cost code set you already use
- You track costs by job, with 3 to 5 completed projects you can pull real numbers from
- You have 3 to 5 past estimates that show your written scope and the math behind it
- You have a live project with a dimensioned drawing set and schedules
- You're prepared to tell me where my numbers are wrong when you review them
This is not for you if
- You price from experience with nothing written down
- You don't cost jobs, or every cost lands in one bucket
- You've never closed out a job with final numbers
- You want someone to estimate your jobs for you
- You want ongoing calls
The AI Estimating Build is for builders who already know how they price work, and want it out of their head and into something that runs without them.
The questions builders actually ask.
No. I build your estimating system and install it with you. There are no modules, no group calls and no community. You end up with a working tool that holds your prices, not a folder of videos you'll never finish.
No. I run one estimate during the build, and that estimate exists to test and correct the system. What you're buying is the system. After the install, you run it on your jobs and keep tweaking as needed.
About four hours across four weeks. Twenty minutes on the intake, fifteen minutes sending files, a few hours reviewing the test estimate, and sixty minutes on the install call. Everything else is mine.
Four things: your cost code set, job costing from 3 to 5 completed projects, 3 to 5 past estimates that show your written scope and the math behind it, and one live project with a dimensioned drawing set and schedules. If you have all four, you have everything this needs.
Messy is fine. Missing is not. If your codes exist and your job costing is real, we can work with it, and part of what you get back is a cost code set that's been straightened out by someone who was a professional builder for 21 years.
By email. Send me the outputs that come back wrong, and I'll fix your skill and send you a new version.
No responsible estimator would guarantee somebody else's numbers. What I can do is tell you exactly where it can get off course, because there are three places.
One: a cost item that doesn't have a complete calculation method behind it. That is what the build is for, and it's why we test the whole thing on one of your real jobs before you rely on it.
Two: something appears in the plans that it has no reference for. Corten steel cladding on a house where you've never installed corten. It will price it, but it's working from a general figure rather than your history.
Three: the takeoff. Poor drawings with dimensions scattered across sheets, or no drawings at all, mean it's interpreting rather than reading. It stops and asks you rather than guessing, and every assumption it makes is written into the deliverable so nothing is buried.
No. You need a Claude account and the ability to follow along on one screenshare. We install it and price a job together so you leave that call having done it yourself. That's the entire technical requirement.
Because I do them myself and the cost code work is judgment, not data entry. I'd rather five builders finish with something that works than fifteen finish with something that nearly does.
Buildwise CSV or a generic spreadsheet CSV, set during the build. If you run something else, say so on the application, and we'll look at the column format.
You own everything. There's an optional ongoing arrangement where I keep your skill current as your prices, trades, and cost codes change. Entirely optional, and there are no calls in that either.
I take five builds a month. If there's capacity and your data can carry a build, I'll tell you the next available start date when I come back on your application, which is within two business days.
You're still the only one who can price a job
You'd hand it to somebody else if you could.
Most builders can't, because nobody else in the company prices work the way you do, and a wrong number costs a lot more than a slow number.
You already know AI should be able to carry some of this. You just don't know where to start, and the last thing you want is a fast number you can't stand behind.
That's why this exists. I take the way you already price work, build it into a skill that runs on your machine, and test it on one of your real projects before you ever rely on it.
If you have your cost code set, job costing from 3 to 5 completed projects, 3 to 5 past estimates that show your written scope and the math behind it, and one live project with a dimensioned drawing set and schedules, you can apply below.
Apply for an AI Estimating Build below
- Five minutes. Enough for me to see whether your data can carry a build.
- You hear back within two business days, including if it is a no, and why.
- If it is a fit, I will send the details and the next available start date.
- Your cost code set
- Job costing from 3 to 5 completed projects
- 3 to 5 past estimates that show your written scope and the math behind it
- One live project with a dimensioned drawing set and schedules
Application received
I read every one myself. You will hear back within two business days, including if it is a no and why.