Quote / Estimate Generator

• CF Worker
• R2 (image storage)
• Claude Vision
• PDFKit / DocuSign API
• Resend

Working production examples. Read the code. Steal the pattern.

• ASP Pool Season Pool-opening intake → estimate workflow (closely related)

A real prospect. A real demo. A real outbound message — all before 5pm.

1. 09:00–09:30 Pick a contractor whose quote process is broken.

   Roofing, HVAC, painting, marine, pool. Call them as a fake customer at 9am. Time the path from call → estimate-in-hand. The slower their existing flow, the bigger your wedge.

2. 09:30–10:30 Map their actual estimate logic.

   Get them to walk through how they price a typical job. Labor units? Per-square-foot? Materials markup? Tier (residential / commercial)? Travel surcharge? Write down the formula. Claude doesn't invent prices — it reads the formula you give it.

3. 10:30–11:00 Stand up the photo-upload form.

   CF Worker + R2 for storage. Form: photo (required, multiple), address, contact, "describe the job" textarea. Mobile-first, drag-drop on desktop, camera-capture on mobile.

4. 11:00–12:00 Wire Claude Vision for the read.

   Use claude-opus-4 with vision. Prompt asks for: dimensions estimate, materials needed, condition rating, complications visible. Output JSON. Always require 2-3 photos minimum (different angles).

5. 12:00–13:00 Build the pricing engine.

   Pure JS function: takes Vision JSON + the contractor's formula → returns labor + materials + total + a price RANGE (not point estimate). Always include a "tech will confirm on site ±20%" line.

6. 13:00–14:00 PDF generation + email out.

   PDFKit generates a branded estimate. Resend emails it to the customer + the contractor simultaneously. Subject: "Estimate for [JOB] at [ADDRESS] · [PRICE RANGE]". Include the photos.

7. 14:00–15:00 Build the contractor approval gate.

   V1 sends to customer immediately. V2 (recommended): contractor gets a one-click approve/edit email FIRST, then it goes to customer. The approval gate is what they'll pay for once they trust the system. Build the toggle on Day 1.

8. 15:00–16:00 Three-job test pass.

   Take 3 photos yourself: a roof, a wall needing paint, a ceiling water stain. Submit each. Verify range, formatting, PDF, email. Note every fault — fix the showstoppers.

9. 16:00–17:00 Send the cold pitch with a real estimate.

   Take a photo of THEIR own truck or shop sign. Run it through your form. Email them the resulting estimate as your proof: "this is what your customers would have gotten in 90 seconds."

• Always require 2-3 photos from different angles. Reject single-photo submissions.

  Why: Vision models confidently hallucinate from one photo. Two angles cuts the error rate in half. Three is the sweet spot. Build the multi-upload as a hard gate, not optional.

• Quote ranges, never point estimates. Always include "tech confirms on site ±20%."

  Why: Customers anchor on the number you give them. A point estimate of "$2,400" becomes "you said $2,400" when the tech sees the actual job is $3,100. A range "$2,200–$2,800" + the disclaimer protects the contractor and is more honest.

• Separate labor and materials in the output. Always.

  Why: Customers read materials as a fixed cost (it is) and labor as negotiable (it isn't, but they think so). Showing the breakdown makes the price feel earned, not invented.

• Detect customer language from the address + name + textarea. Default to bilingual output.

  Why: In Miami a "Garcia, 1200 SW 8th St, paint mi pared trasera" submission gets an English-only PDF and the customer ghosts. Generate both languages by default.

• Store every photo in R2 forever. Tag with submission ID + timestamp.

  Why: Insurance disputes, "the damage wasn't there before," contractor liability cases all hinge on what the original submission showed. Storage is $0.015/GB/mo. Never delete.

• Require photo + address + contact for triage. Reject submissions missing any one.

  Why: Photo without address = can't price travel. Address without photo = no scope. Either without contact = unable to follow up. Building the gate at submit-time saves the contractor from chasing 30% of his leads.

• Build the contractor approval gate from Day 1, even if v1 ships without it.

  Why: V1 may auto-send to customer for speed. The day you have a wrong-by-2x estimate go out, the contractor wants the gate. Adding it later is a re-architecture; building it as a feature flag from day 1 is twenty extra lines.

Drop these into Claude Code. Replace the [BRACKETED] fields with the prospect's details.

You are a quoting assistant for [BUSINESS NAME], a [trade] contractor in Miami. You read 2-3 photos of a job and return a structured estimate.

Pricing formula:
- Base labor: [$X per hour OR $Y per square foot OR $Z per unit]
- Materials markup: [X%]
- Travel surcharge by zone: [list zones + flat fees]
- Job tiers: residential / light commercial / commercial — multiplier [X / Y / Z]
- Standard disclaimers: minimum charge $[X], dispatch fee $[Y], emergency rate +[X%]

Inputs:
- 2-3 photos of the job site
- Address + zip
- Customer language (auto-detected)
- Optional: customer description

Output JSON only:
{
  "scope_summary": "1-2 sentences",
  "dimensions": { "estimate": "...", "confidence": "low|medium|high" },
  "materials": [ { "item": "...", "qty": ..., "unit_price": ..., "subtotal": ... } ],
  "labor_hours_estimate": { "low": ..., "high": ... },
  "labor_subtotal_range": { "low": ..., "high": ... },
  "materials_subtotal": ...,
  "travel_surcharge": ...,
  "total_range": { "low": ..., "high": ... },
  "complications_visible": [ "..." ],
  "needs_site_visit_for": [ "..." ],
  "disclaimer": "tech will confirm pricing on site ±20%",
  "language": "en|es"
}

If fewer than 2 photos, return: { "error": "need_more_photos", "instructions": "Please add a wider angle and a closeup." }
Never invent dimensions. If you can't estimate, mark confidence: "low" and add to needs_site_visit_for.

Build me a Cloudflare Worker that handles photo-upload quoting for [BUSINESS NAME].

Endpoints:
- POST /api/quote → multipart/form-data (2-3 photos + address + contact + language). Stores in R2. Calls Claude Vision. Runs pricing formula. Generates branded PDF. Sends to customer via Resend AND to contractor for approval (configurable via env CONTRACTOR_APPROVAL_REQUIRED).
- GET /api/quote/:id → contractor-approval view (one-click approve/edit/reject), emails customer on approve.
- GET /api/quote/:id/pdf → returns the PDF directly from R2 cache.

D1: quotes (id, ts, customer_name, customer_contact, address, language, photos_r2_keys[], vision_extracted_json, pricing_json, pdf_r2_key, status, contractor_response_at, customer_received_at)

Bindings: D1 QUOTES_DB, R2 QUOTES_R2, secrets ANTHROPIC_API_KEY + RESEND_KEY + CONTRACTOR_EMAIL + CONTRACTOR_PHONE, var CONTRACTOR_APPROVAL_REQUIRED + PRICING_FORMULA_JSON.

PDF: use @cf/svg2pdf approach OR Resend's rendered-email PDF attachment. Brand: [BUSINESS LOGO URL], [BRAND COLOR], typography Inter/Fraunces.

Output complete worker.js + wrangler.jsonc additions + D1 migration + public upload form HTML.

Generate an HTML/CSS PDF template for a contractor estimate from [BUSINESS NAME].

Layout (8.5x11 portrait, half-inch margins):
- Header: business logo (left, 60px tall), business name + address + license # (right). Bottom border 1px solid.
- Customer block: "Prepared for: [NAME], [ADDRESS], [DATE]." Reference number top-right.
- Scope section: header + 2-3 sentence summary, then thumbnail grid of submitted photos (4 max, 1.5x1.5).
- Pricing table: 3 columns (item / qty / price-range). Labor and materials separated. Subtotals bold. Total range with $X,XXX – $X,XXX format.
- Complications: bulleted list of "we noticed..." items.
- Disclaimer: "Estimate valid 30 days. Subject to on-site confirmation ±20%. Permits, change orders, hidden conditions billed separately."
- Footer: signature line + date + business contact.

Style: cream #FDF9F2, ink #1A1814, [BUSINESS ACCENT]. Fraunces headers, Inter body, JetBrains Mono prices. Print-optimized.

Output: complete index.html with inline <style>, ready for puppeteer / wkhtmltopdf / @cf/pdf.

Write me a 4-sentence cold email + 2-sentence WhatsApp follow-up to [OWNER NAME] at [BUSINESS NAME].

Setup: I took a photo of [their work van OR shop sign OR a sample wall on their site] and ran it through a quote generator I built. Attached is the resulting PDF estimate (in their name, with their formula, branded for their company). It took 90 seconds end-to-end.

Email:
- Open with specific photo + 90-second timestamp ("I photographed your van outside the Hialeah Home Depot at 4:14pm. By 4:15pm…")
- Reference what the estimate priced
- Plain-text the price range from the PDF
- Name: $3k setup, $500/mo, 3 days to live
- Ask one yes/no: "want me to wire this into your existing Stripe so customers can deposit-and-confirm?"

WhatsApp: acknowledges email + offers a 15-min Loom walking through how a customer would use it on mobile.

No emojis. No "circle back." Attach the PDF. Don't describe it — let it speak.

Anchor on lead-to-quote time. Most trades quote in 24-72 hours; this quotes in 90 seconds. Single-job conversion improvement of 3 percentage points on a 30-job/mo pipeline pays for the full year. Per-quote cost: $0.30-0.60 in Vision tokens + R2 + Resend = under $0.65. Setup includes: photo upload form, vision integration, pricing engine, PDF template branded, contractor approval gate. Does NOT include: Stripe deposit collection ($1k), CRM sync to ServiceTitan ($2k), multi-trade routing ($1.5k). Upsell: bundle Block 02 → "estimate-to-job" pipeline at $700/mo combined.