Session kit · markdown

Starter: sales leader

What you build

You build a deal-risk brief for the key deals in your H2 plan. The brief shows each key deal, the risk flags on it and the reason for each flag. It then drafts the follow-up to each deal owner.

What you need

  • The file pipeline.csv in the H2-Command-Center folder. See Export your Salesforce reports.
  • The file closed-won.csv in the same folder.
  • The file h2-plan.md with your key deals. See the H2 plan template.
  • The columns Opportunity Owner, Stage, Amount, Close Date, Next Step, Last Activity and Last Stage Change Date.

If you use the sample files, tell Claude. Claude then writes "sample data" in each title.

1. Build the view

This step gives you rung 1. The view is on rung 2 when it rebuilds from a new export.

Read pipeline.csv, closed-won.csv and h2-plan.md in the H2-Command-Center folder. Do not change these files.
Find each key deal from part 1 of my plan in pipeline.csv. Compare the Opportunity Name first, then the Account Name.
Build a table with one row for each key deal. Use these columns: Opportunity Name, Account Name, Opportunity Owner, Stage, Amount, Close Date, Next Step, Last Activity.
Sort the table by Amount, largest first. Show the number of deals and the total Amount below the table.
If a key deal is not in pipeline.csv, look in closed-won.csv. Show it in a section named "Closed won".
List each key deal that is in neither file in a section named "Not in the export".
State the export date at the top. Use the date of the file pipeline.csv.
Save the result as deal-risk-brief.md. Rebuild the file from the newest export each time I ask.

Make sure that the total agrees with your plan before you continue.

2. Add one alert

This step gives you rung 3. The prompt holds four rules. Delete a rule that you do not want. Change a threshold to fit your sales cycle.

Add risk flags to deal-risk-brief.md. Use the export date as "today" in each rule.
Rule 1, slipped: the Close Date is before the export date, or the Close Date is later than in the last run.
Rule 2, stalled: the Last Activity is 14 days or more before the export date.
Rule 3, no next step: the Next Step is empty.
Rule 4, stuck: the Last Stage Change Date is 30 days or more before the export date.
At each run, save the Opportunity Name and the Close Date of each key deal to close-dates.csv.
At the next run, compare the new export with close-dates.csv to find a Close Date that moved. At the first run, use only the first part of rule 1.
Put a section named "Needs me" at the top of the brief. List each key deal that has one flag or more.
For each flag, give the reason in one line. Show the value from the export that caused the flag.
If a column is not in the export, tell me which rule you cannot run. Do not guess a value.
Run the rules now and show me what they found.

3. Add one action

This step gives you rung 4. Claude writes the drafts. You read each draft and you send it.

Draft one follow-up message from me to each Opportunity Owner who has a deal in "Needs me".
For each deal of that owner, give the deal name, the flags and one question about the next step.
Keep each deal to two lines. Use plain words. Use only facts from the export and from my plan.
End each draft with the date that I need the answer. Ask me for that date.
Save the drafts in deal-risk-brief.md in a section named "Drafts". Keep the export date at the top of the file.
Do not send a message. Only draft.

4. Schedule it

Follow the steps in Schedule it. Change the day and the time to fit your week.

Schedule a task that repeats every Monday at 7:00 AM. The task rebuilds deal-risk-brief.md from the newest pipeline.csv, runs my four rules and writes the drafts. The task states the export date at the top. The task does not send a message. Run the task one time now.

5. Post it

Post these results to my page. Use the same title each time, so that a new version replaces the old version.
1. Title "Deal-risk brief", kind "view", rung 2: the table of key deals and the export date.
2. Title "Deal-risk alert", kind "alert", rung 3: the rules and what they found.
3. Title "Deal follow-up draft", kind "action", rung 4: one example draft.
4. Title "Deal-risk schedule", kind "schedule", rung 4: what runs, when it runs, what it reads and what it writes.
State the export date at the top of each result. Do not post an email address or a phone number.
Mark the steps "view", "alert", "act" and "schedule" as done.

What good looks like

  • The brief shows the export date at the top, and the total agrees with Salesforce.
  • Each flag has a reason that you can check in the export in one minute.
  • Each draft is short, and you can send it with one edit or none.