4. Custom App - Activity
Note: The video covers material not in the guide below — please watch in full.
Action Step
Complete this before moving on.
Follow along with the video and build your own app. Replicate the prompt Yasin gives Claude — give it client data (or use the BrightLoop files from earlier trainings) and tell it to build an app inside a folder in your repo. Sign up for a free Netlify account, have Claude install the Netlify CLI, and deploy the app live. This is a co-working session — play at 2x speed if needed while your app builds alongside his. Once your first app is deployed, try building a second one to see how fast it goes when the setup is already done.
Training Guide
This is the hands-on companion to the walkthrough. Yasin picks up exactly where he left off — Claude has already scoped out the BrightLoop Engagement Command Center. Now it's time to build it, deploy it, and see it live.
Replicating the Prompt
Before Claude can build, it needs the same context Yasin gave it: the kickoff prep doc, the Salesforce metadata, and a prompt telling it to build an app inside a folder in your repo and deploy it via Netlify. You want to get to the point where Claude is giving you suggestions for the app and asking if you want it to start building.
It doesn't have to be the exact same prompt word for word — the key pieces are: here's my data, build something valuable for these stakeholders, put it in this folder, and deploy it through Netlify.
Setting Up Netlify
Yasin signs up for a fresh Netlify account live in the video. The signup is straightforward — email, a couple of questions, pick a project name. The important part: once the account exists, you don't need to manually deploy through the Netlify UI. Instead, Claude installs the Netlify CLI directly and handles the deployment from the terminal.
Yasin asks Claude to install the CLI rather than doing it himself. Claude runs the install, authenticates against the Netlify account, creates the site, and deploys — all without Yasin touching the Netlify dashboard.
The First App: BrightLoop Command Center
Claude spawns multiple subagents to work in parallel — building the app code while also handling the Netlify setup. The entire process from "go ahead and build" to "your app is live" takes about 13 minutes, including the time spent creating the Netlify account from scratch.
The result: a fully interactive Engagement Command Center with a Salesforce health assessment, stakeholder map with hover details, pipeline data visualization, a risk tracker with collapsible fields, and week-one action items. All built from the kickoff prep doc and metadata — no manual coding.
Continuous Deployment
After the first manual deploy, Yasin sets up continuous deployment — connecting the GitHub repo to Netlify so that every push automatically redeploys the site. This is done through the Netlify UI: go to Deploy Settings, Link Repository, select GitHub, authorize, pick the repo, and hit deploy. Once connected, any change Claude makes to the code in your repo auto-deploys when pushed.
The Second App in Minutes
To prove the point, Yasin builds a second app in a separate folder — a Revenue Operations Command Center for LeanScale itself. He gives Claude the company avatar, foundational context, and customer pain points, then tells it to build and auto-deploy via the CLI it already has access to.
Because the Netlify setup is already done, the second app deploys in just a couple minutes. The first app took longer only because of the one-time account setup. From here on out, it's one prompt to build and deploy.
How the Data Works
Yasin digs into an important architectural question: is the data hardcoded into the app, or does it pull from the source files? The answer: the data lives in a JavaScript file inside the app. It's not dynamically pulling from the markdown files or any external source. To update the app, you'd tell Claude to edit the data in the JS file and push.
For dynamic data that updates without redeploying, you'd need a backend like Supabase — a free database service. The architecture would be Netlify for the frontend and Supabase for the backend. Claude can set this up via CLI and API on the free tier. That's actually how the Academy Site handles Google OAuth login — Supabase runs the authentication behind the scenes.
CLI vs API
Yasin asks Claude to explain the difference in plain language. CLI (Command Line Interface) is like texting commands one at a time — you type netlify deploy, hit enter, get a result. API (Application Programming Interface) is machine-to-machine communication — programs talking to each other automatically. For Claude Code, both work. CLI is great for one-off actions. API is more efficient when dealing with large amounts of data because you can request exactly what you need instead of getting 200 lines of logs.
The real win is automation: once the GitHub-to-Netlify pipeline is set up, neither you nor Claude needs to manually deploy anything. Push code, site updates automatically.