All use cases
Quotes & Estimates

A transformer manufacturer cut from 15 staff to 3 and used Claude to turn 6 years of job cards into a quoting engine

Quotes that took him an hour per 10 now come out with datasheets in about 15 minutes.

Real storyDone with Claude (custom app: Python + Supabase)

What they did

u/Adarsh_Ajith, second-generation owner of an electrical transformer manufacturer, had to downsize from 15 people to 3 and was doing admin, purchasing, sales and most of the design himself. He ran 6 years of handwritten job cards through Claude over 10-15 sessions to pull out and check the data, then built his own design and quoting tool.

How it went

He reports the tool's designs match his engineer's past work over 90% of the time, two weeks into development. A non-technical salesperson can now enter client needs and get a datasheet, drawings and a quote. That took him about an hour per 10 quotes before, and now takes 15 minutes, or 7 for repeat clients.

Worth knowing

The gold was his own old paperwork. Most shops have years of past quotes and invoices sitting in boxes or folders. Getting them into a spreadsheet is the first step to faster, more consistent quotes, even without building software.

Try it yourself

You are a data clerk who turns old paper job records into a clean pricing history. TASK: Turn photos or typed copies of my old job tickets into a spreadsheet I can quote from. CONTEXT (fill in the [BRACKETS]): - JOB TICKETS: [JOB TICKETS] (example: paste typed text or upload photos of 10-20 old tickets) - COLUMNS I WANT: [COLUMNS I WANT] (example: date, customer, job type, size/specs, materials, hours, price charged) - JOB TYPES I USE: [JOB TYPES I USE] (example: service call, panel upgrade, EV charger, rewire) - UNREADABLE RULE: [UNREADABLE RULE] (example: write ?? instead of guessing) STEPS: 1. Extract each ticket into one row using my columns. 2. Mark any field you couldn't read with ??. 3. Group by job type and show the average, low and high price and hours. 4. Point out jobs priced way below the average. RULES: - Use only the facts I give you. If something is missing, ask or mark it NEEDED. Never invent prices, names or promises. - Plain, friendly language a customer or crew member understands. OUTPUT FORMAT: The spreadsheet rows, then a summary table by job type, then a list of outliers. FOLLOW-UPS TO TRY NEXT: - Using this history, draft a quick price guide for my 5 most common jobs. - Which job types took more hours than I charged for?
Open the full playbook

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Read the original

Source: Reddit r/ClaudeAI · July 2026

Related
AU
Write estimates customers understand and approve

A clean estimate with a plain-English summary, a line-item table, what's not included, and how to approve.

Auto repairHVACPlumbingElectricalGarage doorsAuto bodyMediumPlaybook
Wisconsin Trades AI editorial·Oct 2026