Skip to main content

4. Deploy a Dashboard From Slack

Action Step

Complete this before moving on.

Deploy a live dashboard to Netlify entirely from a Slack thread — give your agent data, tell it what charts to build, and get back a working URL you can share.

Comment in Slack

Post your answer in your onboarding channel.

You deployed a live website without seeing any code or files. What does this tell you about where the real value lives — in the tools or in knowing what to ask for?

Training Guide

In Section 3, you built a dashboard in Claude Code, deployed it to Netlify, and got a live URL. Full cockpit — you could see the files, the code, the diffs, everything. Now do it blind. From Slack. Same result.

Exercise​

Step 1: Give your agent the data

Paste or describe the data you want to visualize. Options:

  • Use the BrightLoop Salesforce metadata from S3 (if you still have it)
  • Use any real client data you've been working with
  • Ask your agent to generate sample data: "Generate realistic Salesforce pipeline data for a Series B SaaS company — 30 opportunities across 5 stages, 3 reps, with close dates and amounts"

Step 2: Build the dashboard

"Build me a single-page HTML dashboard with embedded CSS and JavaScript. Include: pipeline value by stage (bar chart), forecast by rep (table), deal velocity (average days in each stage), and a summary card showing total pipeline value and weighted forecast."

Your agent will write the HTML file on its server.

Step 3: Deploy to Netlify

"Deploy this dashboard to Netlify and give me the live URL."

Your agent will install the Netlify CLI (if not already installed), authenticate, and deploy. You get a live URL — a real website, deployed from a Slack message.

Step 4: Iterate

  • "Add a filter dropdown for rep name"
  • "Change the color scheme to match LeanScale brand colors"
  • "Add a 'deals stuck > 30 days' warning section"

Each iteration: agent edits the file and redeploys — you get a new URL or the same one updates.

Step 5: The Reflection

You just deployed a live website from a Slack thread. No VS Code. No terminal. No file explorer. You couldn't see the code, you couldn't see the diffs, you couldn't see the file structure. And you got the same result.

This is what "same engine, different car" actually means. The power was never in the cockpit — it was in the engine.

What to Submit​

  • Live Netlify URL
  • Screenshot of the deployed dashboard
  • Screenshot of the Slack thread that built it