← Back to File

House board Public Estimates Start this File

HouseOperator file

Revenue · House · Estimates

Next 10 estimates go out at the new number

Next 10 estimates go out at the new number. Not a rebrand. Not a new offer.

Fit They already sell 3 to 8 job types, work books, and they are underpricing.

Unfit No book. Wants a new service line. That is not this File.

The map

Does

Next 10 estimates go out at the new number. Not a rebrand. Not a new offer.

Stack

GHL last 90 days three SKUs one-line reason estimate script today's form File log

Logic

IF 20% would stall the book → smaller number that still matters
IF they flinch → smaller scope or later date, not a discount
IF 7 or more of 10 book → the number stays
IF under 5 book → drop only the SKU that died

The journey

Start here

GoHighLevel last 90 days · circle 3

Live 01

Open last 90 days. Circle 3.

The three that sold the most or ate the most labor. Do not invent a fourth.

Bot opens last 90 days and circles 3 You GHL login / 2FA / pay

Open GHL

Three SKUs old · new · why

Three SKUs

Old. New. Why.

Price the job. If 20% would stall the book, pick the smaller number that still matters. Leave the rest of the book alone.

Bot writes old / new / why for exactly 3 You nothing

SKU 01

Old number. New number. One sentence why this one. Bot fills from the book. No invented fourth.

SKU 02

Old number. New number. One sentence why this one.

SKU 03

Old number. New number. One sentence why this one.

The one-line reason they can say out loud

A line they can say out loud

Plain English. No "market conditions." The same line on every estimate this week.

Bot writes the one line from the three SKUs You nothing

Estimate script 6 lines + flinch

The script

Read it once out loud

The only non-login human work on this File. Not a discount. Flinch is a smaller scope or a later date.

Bot writes the 6-line script and the flinch line You read it once out loud

The 6 lines

Greet. Name the job. Name the new number. The reason. The start date. The ask.

If they flinch

One sentence. Not a discount. A smaller scope, or a later date.

Today's estimate form the form they already use

Put the new numbers on today's form

The estimate they send today. Do not wait for a new template. No new calendar. No ads.

Bot puts the three numbers on the form they already use You nothing

File log 10-estimate tracker

Ready 06

Log the next 10

Date, job, old, new, yes or no, note. Rule: 7 or more book, the number stays. Under 5, drop only the SKU that died. Do not roll all three back.

Bot writes the 10-estimate tracker and the keep-or-drop rule You nothing

Done

The File is closed

10 estimates have gone out at the new number.

Free · Operator SOP

Run the three SKUs

If you already sell 3 to 8 job types and you are underpricing, do this. You only do login, 2FA, or pay, plus one read-aloud.

Fit gate

If you already sell 3 to 8 job types, the book works, and you are underpricing, stay.
If you have no book, stop.
If you want a new service line or a rebrand, stop. That is not this File.

Tools in order

GoHighLevel (last 90 days)
Three SKUs (old / new / why)
One-line reason
6-line estimate script + flinch
Today's estimate form
File log (10-estimate tracker)

No Stripe. No ads. No new calendar.

Numbered run

Open GoHighLevel. You: login / 2FA / pay. Bot: open last 90 days. Circle the 3 that sold the most or ate the most labor. Do not invent a fourth.
Bot opens last 90 days and circles 3You GHL login / 2FA / pay
Bot writes old number, new number, one sentence why, for exactly those 3. Price the job. No hourly-rate philosophy. If a 20% jump would stall the book, pick the smaller number that still matters. Leave the rest of the book alone this week.
Bot writes old / new / why for exactly 3You nothing
Bot writes one line they can say out loud when someone asks why it went up. Plain English. No "market conditions." The same line on every estimate this week.
Bot writes the one line from the three SKUsYou nothing
Bot writes the 6-line estimate script: greet, name the job, name the new number, the reason, the start date, the ask. Bot writes the flinch line. One sentence. Not a discount. A smaller scope or a later date. You: read it once out loud. This is the only non-login human work on this File.
Bot writes the 6-line script and the flinch lineYou read it once out loud
Bot puts the three new numbers on the estimate form they already use. Do not wait for a new template. No new calendar. No ads.
Bot puts the three numbers on the form they already useYou nothing
Bot stands up the 10-estimate tracker: date, job, SKU, old, new, yes/no, note. Rule: 7 or more book, the number stays. Under 5, drop only the SKU that died. Do not roll all three back.
Bot writes the 10-estimate tracker and the keep-or-drop ruleYou nothing

File log columns

date · job · SKU · old · new · yes/no · note

Done rule

Stop when 10 estimates have gone out at the new number.

Do not

Do not invent a fourth SKU.
Do not add Stripe, ads, or a new calendar.
Do not roll all three prices back if one dies.
Do not use "market conditions" as the reason.

Free · Run it in your AI

Prompt pack

Free means they use the AI they already have. Paid is the installer that walks it for them.

You are the operator bot for Raise the three SKUs already selling. This Demand File is for {{shop}} in {{city}}. They sell {{sell}}.

Your job: stand up the price raise. I only do login, 2FA, or pay, plus one read-aloud. You drive the named tools. Do not invent URLs.

Fit gate first.
Fit: they already sell 3 to 8 job types, work books, and they are underpricing.
Unfit: no book, or they want a new service line. Stop.

Tools in order:
1. GHL last 90 days
2. Three SKUs (old / new / why)
3. One-line reason
4. 6-line estimate script + flinch
5. Today's estimate form
6. File log (10-estimate tracker)

No Stripe. No ads. No new calendar.

Walk me click by click. At each step say Bot vs You.
1. Open GHL. Stop for login / 2FA / pay. Circle the 3 that sold the most or ate the most labor. Do not invent a fourth.
2. Write old, new, one sentence why, for exactly those 3. Price the job. If 20% would stall the book, pick the smaller number that still matters. Leave the rest of the book alone.
3. Write one line they can say out loud. Plain English. No "market conditions."
4. Write the 6-line script: greet, name the job, name the new number, the reason, the start date, the ask. Write the flinch line. Not a discount. A smaller scope or a later date. Then tell me to read it once out loud.
5. Put the three new numbers on the form they already use. Do not wait for a new template.
6. Stand up the tracker: date, job, SKU, old, new, yes/no, note. Rule: 7 or more book, the number stays. Under 5, drop only the SKU that died. Do not roll all three back.

Ask AI

Paid

Installer builds it

We take the shop, enrich it, they upload, the agent connects what it needs and stands GHL up. They only tap login, 2FA, or pay. The installer runs the house skill.

Skill

Enrich Upload Connect Stand up GHL Installer builds it

For

They already sell 3 to 8 job types and the book works.
They are underpricing work that already books.
The next 10 estimates can go out this week.

Not for

No book. Nothing already selling.
Wants a new service line or a rebrand.
Someone who will not say the new number out loud.

Next board

Recover the job they turn down

When the new number still fills the book, hold the overflow.

Open Recover Prepaid work for the month you already know goes quiet