USE CASESalesAdvanced

“Roof measured, proposal staged, change orders signed”

Same two-day roofing run: it pulled roof measurements for a new inbound lead, built a full proposal/estimate with the contract staged pending his approval, then filled out, drafted, and emailed two change orders via e-signature.

Grok·0.0·0 saves·20 uses·via @pricefoulger

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Proposal** and connect Gmail.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: roofing estimator.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

Staging a full proposal pending approval, not sending it, is what keeps this useful for a business that can't afford a bot committing it to a price by accident. Drafting and e-signing two change orders in the same run shows the bot handling a whole deal lifecycle, not just the first quote.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Roofing estimator. Measure, propose, stage. I approve anything that binds the company.

Mission: For a new inbound lead, pull roof measurements, build a full proposal/estimate, and stage the contract pending my approval. When a job changes, draft change orders and send them via e-signature only after I say so.

Tools: Measurement tool (EagleView / Hover / whatever I connect), the proposal template, e-sign (DocuSign or the tool I use), Gmail.

What good looks like:
- Measurements with source. Line-item estimate that ties to those measurements and the materials list I gave you.
- Contract staged, not sent. I see the PDF first.
- Change orders: two-party e-sign packet, scoped to the change, not a rewritten original contract.

Never, without asking: send a contract or change order. Never change price or scope. Never sign as the company.

Stop if measurements and the photos disagree on squares — show both and wait.
Use withGrok

via @pricefoulger

Tips

  • ·Reconstructed from @pricefoulger's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Sales →

Fifty local businesses that need a new website

Ben Nash had spent months getting small, mediocre results asking ChatGPT and Gemini to find local businesses that could use a new website. One run with a Grok Bot returned 50 strong leads and a drafted outreach email for each — the leads exactly what he was looking for, the emails a solid first draft to personalize.

Sales·Simple·0 saves
Setup

The win-back bot that paid for its own subscription

Liam gave Grok Bot one job: win back churned customers. It found everyone who left in the last 6 months, emailed them, won several back, collected exit feedback, then overnight analysed why they left and built a 5-step plan. The bot covered its own subscription cost. 3.

Sales·Moderate·0 saves
Setup

It closed a $10k sponsorship from my inbox in 4 hours

Alex Finn gave a Grok Bot access to his business inbox and told it to answer and negotiate with legit companies. Within four hours it researched market rates and closed its first sponsorship deal on its own — turning the inbox he hates reading into revenue.

Sales·Moderate·0 saves
Setup