New data point that stopped me cold: the average small business owner runs their company on more than 40 separate tools. Stripe, PayPal, Google Analytics, Facebook Ads, hosting, and on and on. So when someone asks “how’s your business actually doing?”, most owners answer with a gut feeling, because pulling the real numbers means logging into five systems and stitching it all together by hand.
I came across a walkthrough from Helena, an AI and automation creator, that fixes this in a way I found genuinely clever. The original poster shows how to build one unified dashboard that answers “how healthy is my business?” at a glance, using Claude Code plus the new Zapier SDK, with no real coding required. I was impressed at how approachable she made it, so let me break down what she did and why it matters.
The big idea: start with the pain, not the tech
Here’s the move I liked most. The creator didn’t open with code. She opened with the problem. She framed her whole business as a funnel and asked which numbers matter at each stage: attract, engage, convert, monetize, delight, retain.
Then she just talked to Claude Code in plain English. Her prompt told it to build a unified dashboard for her business, map the funnel stages, pull in tools she already uses, and add things like YouTube views and Instagram follower counts. She even told Claude she’s not a data analyst, so it had to design the layout for her and answer that one question: how well is my business doing?
About ten minutes later, she had a working first version with dummy data: MRR, cash collected, new customers, plus stats for every funnel stage. Not perfect. She gave feedback in plain English, asked for tighter columns and fewer metrics per block, and the second version looked sharp.
How she actually wired it up
The build broke into three clean steps:
- 📊 Design the dashboard. Describe what you want to Claude Code in everyday language, iterate on layout and colors until it fits.
- 🔗 Deploy it free. She connected the project to a GitHub repository, then used GitHub Pages (Settings → Pages → deploy from a branch, root folder) to push it live. First deploy takes about five minutes. You can keep it private so the whole internet doesn’t see your numbers.
- ⚙️ Connect real data. This is where the Zapier SDK comes in, replacing all that mock data with live figures from Stripe, Google Analytics, GoHighLevel, YouTube, WordPress, and more.
The SDK part is the real unlock. Instead of building 20 separate webhooks and juggling 20 API keys, the creator connected one thing. Zapier’s SDK plugs into over 9,000 tools it already supports. You manage a single connection, and your dashboard reads from everything.
Automation vs MCP vs SDK, made simple
The author clears up a confusion a lot of people share, and I think this is the most valuable nugget in the whole video:
- Automation runs on webhooks. Fine for one task, painful when you need dozens of connections.
- MCP is for agents. Think of it as a folder of tools an AI employee picks from to complete a request, hosted on Zapier.
- SDK is for when you’re building a tool or app yourself. You host the integrations on your own server and tap into all those native connections directly.
Her rule of thumb: building an app or tool? Use SDK. Building an agent or AI employee? Use MCP. Simple as that.
3 practical ways to use this
- The business health dashboard. The headline use case. One screen that answers how your funnel is performing, no more logging into five systems.
- Add payments to a vibe-coded app. The creator points out that platforms like Lovable or Replit often stumble on payment processing. Connect Stripe to the Zapier SDK, tell Claude to start collecting payments, and that gap closes.
- Build software that leans on other software. Want an AI video app that uses HeyGen’s API? Connect HeyGen through the SDK and call it directly, no automation sitting in the middle.
Tips and pitfalls worth knowing
- Be patient with iterations. The original poster stresses it takes a few back-and-forth rounds to get the layout right. That’s normal, not a failure.
- Pick the root folder on GitHub Pages, not the documents folder, or your deploy won’t show. And remember Claude names its branch something random each time, so select the right one.
- Connect your tools inside Zapier first. OAuth tools just need a login, others need an API key. The terminal then shows what the SDK can read and write for each connection.
- Make it private if it holds sensitive business data.
- Mind the read/write scope. If an action isn’t available, go back to Zapier app connections and fix it there before expecting the dashboard to pull it.
One thing that stuck with me: the creator mentioned that a few years back, people were charging around a hundred grand to build dashboards like this with no-code tools. Now it’s a plain-English conversation with Claude Code and one Zapier connection. That pace of change is wild.
If you want the exact prompts, the terminal commands, and the click-by-click setup, the full video walks through every step. Worth a watch before you build your own.