The prompt

Copy it into Claude Code. It starts with a full interview so the dashboard fits your business, then builds it one piece at a time.

You are my business systems builder. Help me design and build a team of AI employees (automated jobs and Claude scheduled tasks) that run my marketing, reporting and daily operations, plus a private dashboard where their work shows up and I make the decisions. I am not technical: ask one question at a time, explain things in one or two plain sentences, suggest a sensible default when I'm unsure, and do every technical step yourself. Check with me before anything that posts publicly, spends money or changes an account.

PHASE 1: PURPOSE AND GOALS
1. What does my business sell, to whom, and where?
2. Why do I want a dashboard? What decisions should it help me make (for example: which ads to keep, which leads to call, what to post, whether marketing is paying off)?
3. What are my top 3 goals for the next 6 to 12 months, with numbers if I have them (leads a month, sales, cost per lead, followers, bookings)?
4. What does a "good week" look like in numbers? What would worry me?

PHASE 2: PEOPLE AND ACCESS
1. Is this just for me, or for a team? How many people, and what are their roles?
2. Who needs a login, and what should each person see or do (owner sees everything; a salesperson sees leads; a marketer approves posts; an outside partner sees only their region or project)?
3. How should it be accessed: phone, computer or both? Any need for separate views per location, brand or project?
4. Does my team use Claude? If yes, which plan, and would they like Claude to draft posts, memos or follow-ups from the dashboard data?

PHASE 3: MY TOOLS (ask about each and note which I use)
- Website: platform (Wix, Squarespace, WordPress, Shopify, custom), Google Analytics 4, Google Tag Manager, Google Search Console, Google Business Profile.
- Social: Facebook Page, Instagram business account, LinkedIn company page, TikTok, YouTube, Pinterest.
- Ads: Google Ads, Meta Ads, LinkedIn Ads; monthly budget per platform.
- Leads and sales: website forms, CRM (HubSpot, Salesforce, Airtable, Google Sheets, other), booking tools, e-commerce, Stripe, phone system (call tracking, RingCentral, others), email marketing.
- Team and tasks: Slack, Microsoft Teams, Asana, Trello, Monday, ClickUp, Notion, Airtable, Google Calendar.
- Creative: brand kit (logo, colors, fonts), photo library (Google Drive, Dropbox), Canva.
- Offline marketing: events, mailers, flyers, QR codes, sponsorships.

PHASE 4: CHOOSE THE PAGES AND CHARTS
Based on my answers, recommend the pages I need (from: Overview, AI team, Leads and follow-up, Website, Search and SEO, Social, Paid ads, Ad center, Creative studio, Content calendar, Campaign impact, Insights and memo, Tasks, Setup and spending safety) and explain in one line why each one matters to my goals. For each page, propose 3 to 5 charts or lists, and tell me which question each one answers. Explain the trade-offs: start small with 4 to 6 pages. Show me a one-page plan (pages, charts, who sees what, which tools connect in which order) and wait for my OK.

PHASE 5: FOUNDATION (free and secure)
- Host on Cloudflare (Workers or Pages with a D1 database and KV cache, free tier) unless I already use something else. Save the code in a new PRIVATE GitHub repo with Dependabot alerts and a secret scan.
- Logins: real authentication with roles from Phase 2, two-factor for admins, and sessions that expire. The dashboard is never public; add noindex.
- Secrets (API keys and tokens) live only in Cloudflare secrets, never in the code or the browser.
- Data: pull numbers on a schedule (for example 6 am daily), store only what charts need, and keep no customer personal data beyond what's required (use counts and scrambled IDs where you can).
- Spending safety: list every service that could bill, use free tiers, set hard caps and alerts at 70% and 90%, and never use a paid AI API unless I approve a written monthly budget. Insights can be rules-based, or written by Claude through a scheduled task in the Claude app.
- Build mobile first, accessible (WCAG 2.2 AA), fast, and clear: plain labels, every number with its date range, and charts that start at zero.

PHASE 6: CONNECT EACH SOURCE, ONE AT A TIME
For each tool I use, in the order we agreed: explain what we'll connect and why, walk me click by click through creating the access (admin settings, API access, service accounts, app review if required), have me paste keys only into the secure secret prompt (never into chat), test the connection, and show me the first real numbers before moving on. Be honest about which platforms need approval and how long it takes:
- Google Analytics 4 and Search Console: a Google Cloud service account with read access.
- Google Tag Manager: a tracking plan (calls, texts, emails, forms, outbound clicks, purchases) published with Consent Mode, plus hidden form fields so every lead keeps its source (UTMs, ad click IDs).
- Meta (Facebook and Instagram): a Business Manager system user and token; reading insights first, then post publishing and ads management after Meta app review.
- LinkedIn: page analytics and posting require LinkedIn's marketing API application and approval; until approved, plan manual posting with reminders.
- Google Ads: developer token and account access; read first, then paused drafts.
- CRM, Airtable or Sheets, forms, phone system, Stripe and booking tools: read-only connections first.
- Offline campaigns: QR codes and short links that count scans and tag leads.

PHASE 7: CREATIVE, CONTENT AND POSTING (if I want it)
- Brand kit: my logo, colors and fonts saved once; post and ad templates that use my real photos (no AI images of my products or property unless I say so).
- A brand check before anything is posted: banned words, prices, claims, spelling, image sizes.
- A content calendar where posts go Draft, Needs approval, Approved, Scheduled, Posted. Nothing posts until I approve it. Then publish approved posts to the platforms that allow it and remind me for the rest.

PHASE 8: ADS (if I want it)
- Ad ideas from my goals, events and best organic posts.
- Ads are created PAUSED. Launching needs my explicit approval, a confirmed budget, a check against my monthly cap, and the platform's own spending limit set.
- Optimization: weekly recommendations (pause, scale, change audience or creative) with the numbers behind them. Never change live budgets or turn ads on by yourself.
- Respect ad rules for my industry (for example housing, credit and employment ads have special categories).

PHASE 9: HIRE MY AI EMPLOYEES
Recommend which AI employees I need (for example: data analyst, reporting assistant, lead coordinator, content strategist, designer, brand checker, social publisher, ad manager, operations assistant, watchdog). For each one I choose, write a one-paragraph job description: what it does, when it runs, what it reads, what it writes, who it hands work to, and what it is never allowed to do. Then build it as the cheapest reliable option: a free scheduled job in the dashboard for data pulls and rules, or a Claude scheduled task in the Claude app for writing and judgment (reports, insights, drafts, follow-ups). Add an "AI team" page listing every employee with its status (working, needs setup, stuck), last run, and what it's waiting on. Nothing an employee makes goes public or spends money without my approval.

PHASE 10: INSIGHTS AND ROUTINES
- A morning refresh, an Overview with alerts (leads not contacted in 24 hours, cost per lead over target, budget pace, broken connections), and a Monday memo in plain English.
- Show me how to set up a Claude scheduled task that reads the dashboard and writes weekly insights and next steps, with no paid AI API.

PHASE 11: LAUNCH CHECK AND HANDOFF
Test every login and role, every connection and AI employee, a phone and desktop view, the accessibility check, the spending caps and alerts, and that nothing can post or spend without approval. Then write README.md and HOW-TO-USE.md: every account, connection and AI employee, who owns it, how to add a user, how to rotate a key, what each page means, and what to do when something breaks. Give me a short list of what to build next.

Tip: do it in stages. Say "let's just do Phase 1 to 4 today" to get your plan first.

Add-on: task management

Paste this into the same Claude Code session once your dashboard is running. It adds a Tasks page and an operations assistant that work with the tools your team already uses.

Add task management to my dashboard. Ask me one question at a time:
1. Where do my tasks live today: Asana, Trello, Monday, ClickUp, Notion, Airtable, Slack, Microsoft Teams, Google Tasks, paper, or nowhere yet? Should the dashboard sync with that tool (two-way, newest edit wins) or become the main task list?
2. Who's on the team, who assigns tasks, and who should see whose tasks?
3. What should a task have: owner, due date, priority, status, project or location, related lead or campaign, notes?
4. Which statuses do we use (for example To do, In progress, Waiting, Done)?
5. Should tasks be created automatically from the dashboard: a lead not contacted in 24 hours, a post waiting for approval, an ad over budget, a broken connection?
6. How should people be reminded: Slack or Teams message, email, a daily digest, or only on the dashboard?
7. Do we use Claude? If yes, should Claude turn meeting notes and emails into tasks, or draft a daily "what's due" summary through a scheduled task?
Then show me the plan and wait for my OK. Build it with the same logins and roles, connect the tool (walk me through its API key or OAuth, stored only as a secret), test with 3 real tasks, and add a "My tasks today" box to the Overview. Nothing gets deleted in the other tool without my approval.