Connect Claude Code to your business tools. Let AI audit your workflows and tell you exactly what software to build. Includes the full prompt and step-by-step MCP setup.
What's inside
The exact prompt from the video, ready to copy and paste
Step-by-step setup for connecting Claude Code to your business tools
How to read the results and pick what to build first
A starter list of MCP connectors for common tools
The Internal Platform Team Prompt
Last updated April 7, 2026
Most people who try vibe coding open a blank page and guess what to build. This guide shows you a better starting point: connect AI to your actual business tools, let it audit your workflows, and have it tell you exactly what software would save you the most time. Then build it.
Step 1
Get Claude Code
Claude Code is Anthropic's command-line tool for Claude. It runs on your computer, reads your files, connects to your tools, and builds software for you.
You need a Claude Pro subscription ($20/month) or a Claude Max subscription to use it.
To install it:
Open your terminal (Terminal on Mac, Command Prompt or PowerShell on Windows)
Run: npm install -g @anthropic-ai/claude-code
Run: claude to start it
It will walk you through signing in with your Anthropic account
If you don't have Node.js installed, grab it from nodejs.org first.
MCP stands for Model Context Protocol. It's a standard that lets AI tools plug into your existing software. Think of connectors like USB ports for AI. Once you connect a tool, Claude can read from it, search it, and use it to understand how your business runs.
How to add connectors in Claude Code:
Run claude mcp add and follow the prompts, or edit your configuration file directly. Anthropic maintains a full walkthrough in the Claude Code MCP setup guide.
Start with the tools that hold your day-to-day work. Your project management boards, your documents, your communication logs. The more context Claude has, the better its recommendations will be.
Step 3
Run the Prompt
Once your tools are connected, paste this into Claude Code:
The Internal Platform Team Prompt
I want you to act as my internal platform team. You're connected to my business tools. Here's what I need you to do:
1. Look through everything you have access to. My documents, databases, project boards, messages, files, software tools connected via connectors, all of it.
2. Map out the workflows you can see. How does work move through my business? Where does information go from one tool to another?
3. Find the problems. Where am I losing time? What's being done manually that could be automated? Where is data being copied between tools by hand? What processes are slow, messy, or breaking down?
4. For each problem, suggest a specific piece of software you could build for me. Tell me what it would do, which of my current tools it would replace or connect to, and how much time it would save me.
5. Rank them. What should I build first based on impact and how quickly you could build it?
Be specific. Reference the actual data and workflows you can see in my tools. I don't want generic suggestions. I want recommendations based on how my business actually runs.
Step 4
What to Do with the Results
Claude will come back with a ranked list of problems and proposed solutions. Here's how to use it:
Start with number one. The first item is what Claude thinks will save you the most time relative to how quickly it can build it. That's your first build.
Ask Claude to build it. You don't need to write a detailed specification. Just tell Claude to go ahead. It already has all the context from the audit.
Test it for a few days. Use the tool in your real workflow. See if it actually saves time. If something's off, tell Claude what's not working and it will fix it.
Then move to number two. Each tool you build removes a bottleneck. Over a few weeks, you'll have a set of custom tools built specifically for how your business runs.
Bonus
Starter MCP Connector List
Here are some of the most common business tools with available MCP connectors. Search for these on the MCP server registry:
You don't need a dev team. You don't need a six-figure SaaS contract. You need your tools connected and a clear picture of where you're losing time. Claude handles the rest.
For more guides, tutorials, and practical AI tips: