Every webinar leaves its numbers in three places: your webinar tool, your checkout and your head. In 30 minutes you can have them on one dashboard, with every number traced back to your own files. Then you reuse it for every webinar after this one.
What you’ll need.
Get these set up first. Everything below uses them.
Claude
The AI assistant I use for writing, building and thinking things through.Free planZoom
Video calls with cloud recording and transcripts.Stripe
Take card payments online and see every sale in one place.
Some of these are affiliate links. If you sign up through one, I may earn a commission, at no extra cost to you. See every tool I use.
Tell this page about your webinar
Your answers write the build prompt and your export checklist. They stay in your browser and nobody else sees them.
Export your three files
Claude counts what’s in your files. Registrations, attendance and sales are the three it needs.
From your webinar tool
Look for a registration report and an attendee report, and export each one as a CSV. Wait until the webinar has ended before you export attendance, so it has everyone in it.
In Zoom, sign in on the web, click Reports, then run "Meeting and webinar registrations" for the registration list and "Meeting and webinar history" for attendance. Search by date or webinar ID and click Export.
From your checkout tool
Export your payments from the day the webinar ran onwards, as a CSV. In Stripe, open your payments list, set the date range and click Export.
If you track offer clicks anywhere, export those too.
Switch on file creation in Claude
Claude needs this setting to open spreadsheets and build charts from them. It takes ten seconds.
- Open claude.ai and go to Settings, then Capabilities.
- Turn on code execution and file creation.
- On a Team or Enterprise plan, it lives in Organization settings, then Capabilities, and is usually on already.
Paste your build prompt
Claude checks your files first and tells you what it found. You only say "Build it" once the counts look right.
- Start a new chat in Claude.
- Click the + button and attach your three CSV files.
- Copy your prompt below, paste it in and send it.
- Read Claude’s file check. If the row counts look right, type "Build it".
I've attached the exports from my webinar. Build me a dashboard of the results. THE WEBINAR - Name: [WEBINAR NAME] - Date: [DATE IT RAN] - Offer price: [OFFER PRICE] - Webinar tool: [YOUR WEBINAR TOOL] - Checkout tool: [YOUR CHECKOUT TOOL] 1. CHECK THE FILES FIRST Before building anything, read every file and tell me: - What each file is and how many rows it has - Which columns you'll use, and which column links people across files (usually email) - Any duplicates you found, like one person who registered twice or joined twice - Which of the numbers below you can work out from my files, and which you can't Then wait for me to type "Build it". 2. THE DASHBOARD When I type "Build it", make an interactive dashboard as an artifact with these numbers across the top: - Registrations (unique people, counted by email) - Attended (unique people who joined live) - Show-up rate (attended divided by registrations) - Average watch time, if my files have join and leave times or a duration column - Offer clicks, if my files have them - Sales (orders from my checkout file) - Revenue (total from my checkout file) - Revenue per registrant (revenue divided by registrations) Under the numbers: - A funnel chart: registered, attended, clicked (if I have it), bought - A chart of when people registered, by day - A watch time chart showing how many people were still watching through the session, if my files allow it - A table of buyers: name, email, amount, and whether they attended live 3. RULES - Only use numbers from my files. Never estimate or fill a gap. If a number can't be worked out, show the tile with "Not in your files". - Show the sum behind each number when I hover over it, so I can check it. - Sales from people who never registered go in their own line, so the webinar numbers stay clean. - Keep it clean and easy to read on a laptop. Big numbers, short labels.
Check three numbers by hand
One wrong column can throw every number off. Two minutes of checking means you can trust it from now on.
- Compare registrations with the total your webinar tool shows.
- Compare revenue with the total in your checkout tool for the same dates.
- Pick three buyers from the table and look them up in your checkout tool.
Registrations should be [number]. Show me how you counted them and fix it. Revenue includes a refund. Take out refunded payments. Count someone who joined twice as one attendee.
Reuse it for your next webinar
The second dashboard takes five minutes, and now you can see webinars side by side.
Go back to the same chat after your next webinar. Attach the new exports and paste this.
Here are the exports from my next webinar. Same dashboard, same rules. Add a switch at the top so I can flip between webinars, and a table that puts the main numbers for each webinar side by side. Check the files first and wait for me to type "Build it".
Take your downloads
Tick what you want. Each file is written from your answers in step 1.
Your tools, one more time.
If something goes wrong.
Claude says it can’t open my files
Check that code execution and file creation is on in Settings, then Capabilities. If you exported Excel files, they work too once that setting is on.
My attendance number is higher than it should be
People who dropped out and rejoined can appear twice in attendance reports. Type: "Count each email once in attendance, and add up their time across every join."
Some buyers aren’t showing as registrants
They may have bought with a different email from the one they registered with. Claude lists them on their own line. Match them by name yourself and tell Claude which ones belong.
There’s no watch time on my dashboard
Your attendance export needs join and leave times or a duration column. Re-export the attendee report and look for those columns before you upload.
The dashboard shows an error or a blank panel
Type: "The dashboard isn’t showing. Fix the error and rebuild it." Claude reads its own error and corrects it.