Recipes / Sales & support
Grok BotSkillSales & support

Site-walk photos → client-ready proposal

A construction PM walks the job, exports annotated photos as a PDF, and Grok Bot turns it into a formatted proposal for his review.

Setup time1–2 hours to teach, minutes per job
CostIncluded in plan
RunsWhen you send a job-site photo report
NeedsGrok Bot, photo report export (e.g. CompanyCam PDF), your price list + proposal template
Last updated2026-10-17
XSource

I'm a project manager in multifamily construction. With Grok Bot I've automated nearly my entire computer workflow.

by Travis Cardwell (@txghost91) · 2026-10-11

✓ Opened via the X API on 2026-10-17

Read the original ↗
Part 1 · What the source did

A construction PM walks the job, exports annotated photos as a PDF, and Grok Bot turns it into a formatted proposal for his review.

  • Taught the bots his pricing and typical timelines once.
  • Trained a spreadsheet bot on exactly how his proposals should be formatted.
  • On site, takes photos in CompanyCam with measurements and descriptions, then hands the PDF export to Grok Bot.
  • Gets back a polished proposal to review before it goes to the client; says this replaced about half his workday.
“Out comes a polished proposal for my review, and then it's off to the client.”— Travis Cardwell (@txghost91), X

Summary written by Agent Cookbook. See the original for the full context.

Part 2 · Our copy-paste version

Adapted by us from what the source described. Fill in the [BRACKETS].

The prompt

Skill: "Photo report → proposal". Inputs: a photo-report PDF from [PHOTO APP] with measurements and notes per photo. Reference files (saved on the box): [PRICE LIST / UNIT RATES], [TYPICAL TIMELINES], [PROPOSAL TEMPLATE]. 1. Read every photo caption. Build a scope table: location, item, quantity + unit, notes. Flag any photo with no measurement or an unclear description as a QUESTION instead of guessing. 2. Price each line ONLY from my price list. If an item isn't on the list, mark it "NEEDS PRICE" and leave it blank. 3. Estimate a timeline from my typical timelines and list the assumptions it depends on. 4. Fill my proposal template (same layout, fonts, sections, terms) and save it as [FORMAT] in [FOLDER], named [CLIENT]-[SITE]-[DATE]. 5. Message me: total, the questions list, NEEDS PRICE lines, and a link to the draft. Never send anything to a client, never change my rates, and never delete files. Sending, buying, posting and deleting always wait for me.
🛡
Approval ruleDrafts only. You review every proposal; the bot never sends it to a client or changes prices on its own.

Set it up

  1. Put your price list, timelines and one or two past proposals you liked on the box.
  2. Walk the bot through one real job end to end and correct the output.
  3. Save it as a skill; send each new photo report to that bot.
  4. Review, fix questions, and send the proposal yourself.

Common failures

⚠
What usually goes wrong
  • Captions without units ("about 12") produce wrong quantities; make units part of your photo habit.
  • The bot invents a price for an item not on your list; the NEEDS PRICE rule catches it, so keep the list current.
  • Template formatting drifts after a few runs; keep a "golden" past proposal on the box for it to match.

Variations

  • Change orders: compare a new photo report to the original scope and draft only the delta.
  • Punch lists: turn walk-through photos into a task list per trade.
  • Insurance or inspection reports from the same photo export.

Related recipes