PROMPT BRO
Sales desk

Weekly sales report from your CRM

Monday sales review: the CRM says open, the rep says almost closed, finance says nothing booked.

Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the practice files

By hand2–3 hrs
With AI20 min
Each time · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Export deal rows

Use deal ID, customer code, stage, value, expected close date and previous stage. Use one currency and period.

First time? Try it on fake data first:

Confirm stage names

Agree which stages mean won, lost and open. Don't treat pipeline as booked revenue.

Privacy Remove phone numbers, email IDs and payment details where not needed. Use only approved business names and facts.

Fill the orange boxes
You send (the "prompt": the message you paste into your AI tool)
weekly-sales.xlsx

Whenever I send weekly CRM rows for [Reporting week], report using [Stage mapping]. Basis: [Value basis]. A. Count deals and sum value by current stage; show open pipeline, wins and losses separately. Flag missing amount or date for open deals and duplicate IDs. B. List stage changes from previous stage, open deals without expected close, and deal value missing. Do not forecast probability without supplied data. C. Five-line report: facts and separate suggested next checks. No invented reasons for wins/losses. Use only supplied facts. Never invent customer names, testimonials, urgency, prices, discounts, delivery dates or credit terms. A person reviews before sending or deciding.

Set it up once. Save stage mapping and report format. Pick your tool at the top to see how.

After that, each time: send the weekly CRM export and reporting dates.

First time? Try it in a normal chat: paste and send.

Which model? Use your tool's strongest model with thinking turned on.

In your AI tool: attach the files with the + button, paste, send.

What you'll get back (example, from the practice files)
₹1.2 Lopen known
₹50,000won
₹30,000lost
  • D2Open date missing. ₹40,000 pipeline; confirm expected close.
  • D4Lost this week. ₹30,000, previous Open; reason not supplied.
  • D5Open value missing. Pipeline total partial; ask rep.
Before you trust it

Then send this: Recount deal rows and stage changes, sum known values per stage, and verify missing amounts are not zero.

If it goes wrong
It forecasts revenue

Reply: "Open pipeline only; no probability supplied."

It assumes missing value zero

Reply: "Known total, partial."

It guesses loss reason

Reply: "State change only; ask rep."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?