# Demo script: from a pasted plan to a rung 4 brief This script is for Tom. The live demo starts at 2:55 PM and takes 15 minutes. It shows one path from a plan and a Salesforce export to rung 4. The demo uses made-up data: the [sample plan](/kit/21-sample-plan) and the two sample files. - `https://cro-offsite.sc.rhapsody.health/kit/files/sample-pipeline.csv` - `https://cro-offsite.sc.rhapsody.health/kit/files/sample-closed-won.csv` Technical names in this script: Cowork, Claude Code, Salesforce, CSV, connector, board, rung. ## The demo at a glance | Minute | Stage | Result on the board | |---|---|---| | 0 to 2 | Join the site and point Claude at it | A new card | | 2 to 5 | Load the plan and the export | Steps `plan` and `data` done | | 5 to 8 | Build the deal watchlist | A view, rung 2 | | 8 to 11 | Add one alert rule | An alert, rung 3 | | 11 to 13 | Draft the follow-up for each flagged deal | An action, rung 4 | | 13 to 15 | Schedule the Monday brief | A schedule | ## Before you start Do this checklist on Tuesday morning. **CAUTION:** Use a demo folder that holds no real export. The projector shows each file that Claude reads. 1. Make a folder named `H2-Command-Center` for the demo. 2. Save `sample-pipeline.csv` and `sample-closed-won.csv` in the folder. 3. Open the [sample plan](/kit/21-sample-plan) in a browser tab. 4. Open `https://cro-offsite.sc.rhapsody.health/board` on the second screen. 5. Open Cowork, and give Claude access to the demo folder. 6. Do one dry run of this script from start to end. 7. Make sure that the dry run gives the numbers in this script. 8. Keep the results of the dry run in a second folder as a backup. 9. Use the name "Tom (dry run)" for the dry run. Remove that card on the facilitator page before the session. 10. Put this script on your laptop screen, not on the projector. ## Minute 0 to 2: join the site **Say:** "Your Claude reads one page on this site, and then it runs the session with you." 1. Open `https://cro-offsite.sc.rhapsody.health/join`. 2. Enter the room code, the name "Tom (demo)" and the function "Sales". 3. On your page, copy the prompt under **Point your Claude here**. 4. Paste the prompt into Cowork, and send it. 5. Send the prompt below. ``` The setup check is done. This is a demo for the room, and all data is made up. Mark the steps "setup" and "join" as done. Write "sample data" in the title of each result. Keep each reply short. ``` 6. Show the board. The card "Tom (demo)" is there, and its progress dots show the first two steps as done. ## Minute 2 to 5: load the plan and the export **Say:** "I give Claude the plan from this morning and the export. Then I check the numbers before I build." 1. Copy the sample plan from the browser tab. 2. Send the prompt below, with the plan pasted below it. ``` This is my H2 plan. All data in it is made up. Save it as h2-plan.md in the H2-Command-Center folder. Keep the five parts. Do not change a number. I build the part "key deals" first. Mark the step "plan" as done. ``` 3. Send the prompt below. ``` Read sample-pipeline.csv and sample-closed-won.csv in the H2-Command-Center folder. For each file, tell me the row count, the column names and the total of the Amount column. Tell me which rows have an empty Amount. Do not change the files. ``` 4. Compare the reply with this table. Read the numbers aloud. | File | Rows | Total of Amount | Empty Amount | |---|---|---|---| | `sample-pipeline.csv` | 30 | 6,778,000 | 1 row: Bellhaven Labs - Interface Migration | | `sample-closed-won.csv` | 14 | 2,400,000 | None | 5. Send the prompt below. ``` The numbers agree with my plan. Mark the step "data" as done. ``` ## Minute 5 to 8: build the deal watchlist (rung 2) **Say:** "This is the dashboard. It is rung 2 because it builds again from the newest export." 1. Send the prompt below. ``` Build a deal watchlist from sample-pipeline.csv. Put the five key deals from h2-plan.md at the top. Then list the other open deals, largest amount first. Show the account, the owner, the stage, the amount, the close date and the next step. Add one line of totals for each forecast category. Build the watchlist again from the file each time I ask for it. Post it to my page as a result of kind "view", rung 2. Use the title "Deal watchlist (sample data)". Then mark the step "view" as done. ``` 2. Compare the totals with this table. | Forecast category | Deals | Amount | |---|---|---| | Commit | 12 | 3,690,000 | | Best Case | 9 | 2,233,000 | | Pipeline | 9 | 855,000 | 3. Show the board. The card shows the watchlist, and the activity feed shows the post. ## Minute 8 to 11: add one alert rule (rung 3) **Say:** "A dashboard waits for me. A rule tells me which deals changed, and that is rung 3." 1. Send the prompt below. ``` Add one alert rule to the watchlist. Use 11/17/2026 as the date of today. Flag a deal as "slipped" when the Close Date is in the past. Flag a deal as "stalled" when the Last Activity is more than 14 days old. Flag a deal as "no next step" when the Next Step is empty. Run the rule on sample-pipeline.csv now. List each flagged deal with the owner, the amount and the reason. Put the key deals first. Post the rule and the list to my page as a result of kind "alert", rung 3. Use the title "Deal alerts (sample data)". Then mark the step "alert" as done. ``` 2. Compare the reply with this table. The rule flags 10 deals that total 2,300,000. | Deal | Owner | Amount | Reason | |---|---|---|---| | Tannerfield Clinics - Cloud Migration (key deal) | Jorge Batista | 410,000 | Slipped | | Fennick Health Network - Enterprise Identity Index (key deal) | Lena Farrow | 480,000 | Stalled, no next step | | Osprey Bay Diagnostics - Lab Results Exchange | Hannah Okafor | 330,000 | Slipped, stalled, no next step | | Fennick Health Network - Integration Platform Expansion | Lena Farrow | 295,000 | Slipped | | Arden Vale Medical - Cloud Migration | Hannah Okafor | 280,000 | Stalled | | Stoneleigh Health IT - Integration Platform Renewal | Devin Marsh | 175,000 | Slipped | | Marlowe Imaging Group - Image Exchange Services | Devin Marsh | 120,000 | Stalled | | Bellhaven Labs - Managed Services Renewal | Maya Ellison | 95,000 | Slipped, stalled, no next step | | Tannerfield Clinics - Interface Build Services | Jorge Batista | 60,000 | No next step | | Stoneleigh Health IT - Developer Services | Devin Marsh | 55,000 | Stalled, no next step | 3. Tell the room the counts: 5 slipped, 6 stalled, 5 with no next step. 4. Tell the room that two of the five key deals are on the list. 5. Tell the room that three slipped deals are in the Commit category. They total 880,000. ## Minute 11 to 13: draft the follow-up (rung 4) **Say:** "Rung 4 does the first draft of my work. It drafts, and I decide what to send." 1. Send the prompt below. ``` For each flagged deal, draft a follow-up to the deal owner. Each draft has three parts: what the data shows, one question for the owner, and a date for the answer. Keep each draft to four lines. Do not send a draft. Save the drafts as follow-ups-sample.md in the H2-Command-Center folder. Post one draft to my page: the draft for "Fennick Health Network - Enterprise Identity Index". Make it a result of kind "action", rung 4. Use the title "Follow-up draft (sample data)". Then mark the step "act" as done. ``` 2. Open `follow-ups-sample.md`. Show that the file has 10 drafts. 3. Read the Fennick draft aloud. 4. Show the board. The card shows rung 4. ## Minute 13 to 15: schedule the Monday brief **Say:** "Now it runs without me. Each Monday the brief and the drafts are ready before my first call." 1. Send the prompt below. ``` Schedule this as a task that repeats every Monday at 7:00 AM. 1. Read the newest pipeline export in the H2-Command-Center folder. 2. Run my alert rule from this conversation. Use the date of the run as the date of today. 3. Write the result to brief-.md in the same folder. Show the date of the export at the top. Then list the items that need me. 4. For each item, draft the follow-up to the deal owner. Do not send it. Save the drafts in the same file. Show me the schedule when it is set. Then run the task one time now so that I can see the output. ``` 2. Open the brief file. Show the date of the export and the first item. 3. Send the prompt below. ``` Post a result of kind "schedule" to my page: what runs, when it runs, what it reads and what it writes. Then mark the step "schedule" as done. ``` 4. Show the board. The card shows a view, an alert, an action and a schedule. 5. Tell the room the result of the scheduled-task test from the setup check. 6. Tell the room that the steps `share` and `commit` stay open in the demo. **Say:** "That took 15 minutes with made-up data. You have 50 minutes and your own plan. Build one part." ## If it goes wrong Do not repair a problem in front of the room. Use the fallback, say what occurred in one line, and continue. ### The connector is off 1. Tell Claude to use HTTPS. The guide gives the `curl` commands. 2. If HTTPS does not work, open your page at `https://cro-offsite.sc.rhapsody.health/u/`. 3. Select **Done** on the step by hand. 4. Paste the result from Claude into **Post a result**. 5. Tell the room that each leader can do the same. ### The schedule fails 1. Show the schedule prompt on the screen. 2. Open a brief file from the dry run in the backup folder. 3. Tell the room that the task drafts and does not send. 4. Tell the room that a Cowork task needs the app open and the laptop awake. 5. Continue to the board. ### The wifi is down 1. Continue the demo in Cowork. Claude saves each result in the demo folder. 2. Show the files in the folder in place of the board. 3. Post the results to your page after the wifi returns. ### The numbers do not agree 1. Make sure that Claude read the two sample files and not a different file. 2. Make sure that the alert rule uses 11/17/2026 as the date of today. 3. If the numbers still do not agree, show the tables in this script and continue. ### The demo runs long 1. At minute 13, stop the stage that you are in. 2. Show the schedule prompt, and do not run it. 3. Show the board, and start build time at 3:10 PM.