Take-Home
You just built a real analytics stack in 20 minutes.
You walk out of Vibe Coding with a governed CloudKicks dashboard on your own Salesforce org — plus whichever CloudKicks adventures you chose along the way (an Agentforce sales analyst, a rep scorecard, a territory map, and more). This page is your certificate. Below is a look at what everyone leaves with, plus what to do Monday morning at your desk.
You built this today. — [Your Name].
A governed Tableau Next dashboard on your own Salesforce org — from a plain-English conversation with Claude Code.
What you shipped in 3 hours
-
Your CloudKicks storyline
CloudKicks — the sneaker brand with a wholesale pipeline drop. -
An executive dashboard
Governed KPIs, hero chart, at-risk table, AI briefing card — all on your Salesforce org.
Open your dashboard → -
Your own Agentforce agent (if you ran that adventure)
CloudKicksSalesAnalyst
Wired to a read action (semantic-query your data) and a write action (log a follow-up task). -
An extended semantic model
One new governed metric authored on the SDM. Row-level security intact. Audit trail intact. -
A fork of the workshop repo
Skills, 142 LWC bundles, CloudKicks sample data kit. Yours to run against your own customers on Monday.
Your Monday morning.
Clone the repo. Run another CloudKicks adventure. Send me a screenshot.
Workshop Team · workshop@example.com
The wow moments
Your dashboard, plus whichever adventures you picked.
An executive dashboard
Governed KPI tiles, hero chart, at-risk table — all on your Salesforce org. No forked template, no glue code.
Your Agentforce agent (Beat 2 adventure)
Namespaced to your session. One read action against your semantic model, one write action to log a follow-up. Ready to hand off to your team.
A rep scorecard or territory map (Beat 2 adventures)
Drop a status-colored rep ranking or a Leaflet map of your wholesale accounts right onto the dashboard you built in Beat 1 — same governed data, no new tab.
Monday morning at your desk
Do these four things before lunch.
- Open your dashboard. It's still on your org. Refresh — the data is live. Screenshot it and send to your director.
- Fork the repo.
git clone https://github.com/tcufrogger/tableau-vibe-coding-workshop-starter-kit— then open it in VS Code and start a Claude Code session. - Try another adventure. Re-open your CloudKicks org, run the Beat 1 chain on your own Salesforce data, then say "what's next" to pick a fresh adventure from the menu.
- Send us the screenshot.
workshop@example.com. We're building the alumni gallery — your work goes on the wall.
Your take-home window
Your workshop org stays live.
The Salesforce org you built on today stays wired up for fifteen days after the workshop. Same dashboard, same agent, same data. Long enough to show your team, run a peer-review, and decide if this is worth a real pilot.
Day 16 the org spins down. Fork the repo before then — the code is yours forever.
You're not alone
Join the Tableau Community Slack.
22,000 practitioners already live there — data engineers, BI leaders, analytics architects. Post what you shipped, ask what broke, trade CloudKicks adventure ideas. Kevin Hodgkins and the workshop team are in the channel too.
Join the Tableau Community Slack
Post in #tableau-and-ai — share your dashboard, the adventures you picked, your questions.
Tell us how it went
Two-minute post-event survey. Your feedback shapes the next workshop.
Take the survey →
Office hours run every other week in #tableau-and-ai — Kevin Hodgkins
and the workshop team are on to answer questions live. Watch the channel for the schedule.