Session kit · markdown

Starter: Marketing

What you build

You build two views. The first view is a digest of sourced pipeline by campaign or lead source. The second view is a HIMSS readiness tracker that shows the open tasks and the owners. The target for this starter is rung 2 and rung 3.

What you need

The standard export in this kit has no campaign column. Do one of these two things before you start.

  • Add the column Lead Source or Primary Campaign Source to both reports, and export them again. See Export your Salesforce reports.
  • Or export a campaign report, and save it as campaigns.csv in the H2-Command-Center folder.

You also need these items.

  • The files pipeline.csv and closed-won.csv in the H2-Command-Center folder.
  • Your HIMSS task list. You paste it into Claude. Each task needs a name, an owner, a due date and a status.
  • The date of the event.

If you use the sample files, tell Claude. Claude then writes "sample data" in each title. The sample files have no source column, so start with the tracker.

1. Build the view

This step gives you rung 1. The view is on rung 2 when it rebuilds from a new export. Send the first prompt for the digest.

Read pipeline.csv and closed-won.csv in the H2-Command-Center folder. Do not change these files.
Find the column Lead Source or Primary Campaign Source. If neither column is there, look for campaigns.csv.
If you find no source data, stop and tell me. Do not guess a source from a deal name.
Build a table with one row for each source. Show the number of open opportunities and the total open Amount.
Add the number of opportunities with a Created Date in the last 30 days, and their total Amount.
Add the number of closed-won opportunities and the total closed-won Amount.
Sort the table by total open Amount, largest first. Show records with an empty source in a row named "No source".
State the export date at the top. Use the date of the file pipeline.csv.
Save the result as pipeline-digest.md. Rebuild the file from the newest export each time I ask.

Send the second prompt for the tracker. Paste your task list below the prompt, and put in the date of the event.

Build a HIMSS readiness tracker from the task list below. The event date is <event date>.
Build a table with one row for each task. Use these columns: Task, Owner, Due Date, Status, Days to Event.
Sort the table by Due Date, earliest first. Show the number of open tasks for each owner below the table.
Mark each gap in my list with "MISSING". Do not fill a gap with a guess.
State the date of the task list at the top. Save the result as himss-tracker.md.
Save my task list as himss-tasks.md, so that I can update it and you can rebuild the tracker.

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 plan.

Add a section named "Needs me" at the top of himss-tracker.md and at the top of pipeline-digest.md.
Rule 1, late: a task is open and the Due Date is before today.
Rule 2, no owner: a task has an empty Owner.
Rule 3, at risk: a task has a Due Date in 7 days or fewer and the Status is "not started".
Rule 4, quiet source: a source has open pipeline, but no opportunity with a Created Date in the last 30 days.
For each item, give the rule and the reason in one line.
If a column is not in the data, 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 is a stretch. It gives you rung 4. Claude writes the drafts. You read each draft and you send it.

Draft one reminder from me to each Owner who has a task in "Needs me".
For each task of that owner, give the task name, the due date and one question about the blocker.
Keep each draft to five lines or fewer. Use only facts from my task list.
Save the drafts in himss-tracker.md in a section named "Drafts". Keep the date of the task list at the top.
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 pipeline-digest.md from the newest exports and himss-tracker.md from himss-tasks.md, then runs my four rules. The task states the export date at the top of each file. 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 "Sourced pipeline digest", kind "view", rung 2: the table by source and the export date.
2. Title "HIMSS readiness tracker", kind "view", rung 2: the task table and the date of the task list.
3. Title "HIMSS and source alert", kind "alert", rung 3: the rules and what they found.
4. Title "Digest and tracker schedule", kind "schedule", rung 3: what runs, when it runs, what it reads and what it writes.
If I did step 3, post one example draft with the title "HIMSS reminder draft", kind "action", rung 4.
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" and "schedule" as done. Mark the step "act" as done only if I did step 3.

What good looks like

  • The digest shows the export date at the top, and the totals agree with Salesforce.
  • Each HIMSS task has an owner and a due date, or it is in "Needs me".
  • You learn about a late task from the brief, and not at the event.