Analyze your business in 10 minutes. A panel of six experts in Claude.

MCP × CRM × Any System

Connect your system — amoCRM, Bitrix24, Ozon, Wildberries, Amazon, or anything else — to Claude via MCP and run an audit worthy of a top consulting firm. Claude figures out your niche from the data, verifies its accuracy, asks questions about your business, and delivers findings with priorities and a roadmap. Real numbers, nothing made up.

What you'll get

STEP 01 — Connect Any of your systems hooked up to Claude via MCP in ~15 minutes

STEP 02 — Data check A control export of the last 5 hours — before you trust any numbers

STEP 03 — Niche detected automatically 6 experts: finance, sales, marketing, operations, CRM

STEP 04 — Roadmap Top 5 money leaks, ICE priorities, a 30/60/90 plan

What you'll need

• › Claude in Chrome — the browser extension — we'll use it to create the keys
• › Claude Code — the terminal — we'll use it to connect MCP and run the audit
• › Access to your system — plus your phone nearby for the SMS code

*Nothing else to install ahead of time — Claude will set up the rest itself.*

01 · Part One · Connect

Connect any system to Claude via MCP

One flow for every system: get the keys → hand them to Claude Code → verify. Only the first step is system-specific — where to get the key. Switch the tab to your system.

The same method connects Amazon, Wildberries, amoCRM, Bitrix24, or any other system with an API — a CRM, accounting software (MoySklad, 1C), a marketplace, analytics, telephony. Below are tabs with ready-made prompts; for everything else, use the "Any system" tab.

Pick your system — only step 1 changes

Tab switcher (interactive): amoCRM · Bitrix24 · Ozon · Wildberries · Amazon · Any system

Step 1. Get the keys — {system} ({type})

This happens in the browser via Claude in Chrome. Claude does the walking through the dashboard — you only log into the account (you enter the phone number and SMS code yourself).

Below are the details for each system (they change as you switch tabs):

amoCRM (CRM) - Dashboard: your-account.amocrm.ru - Path: Settings → Integrations → create an integration → grant read permissions and grab a long-lived token - Save to a note: - AMOCRM_SUBDOMAIN = the subdomain (your-account from the URL) - AMOCRM_ACCESS_TOKEN = the long-lived access token (shown only once)

Bitrix24 (CRM) - Dashboard: your-portal.bitrix24.ru - Path: Applications → For developers → Other → Inbound webhook → grant CRM permissions → copy the webhook URL - Save to a note: - BITRIX_WEBHOOK_URL = the inbound webhook URL (https://your-portal.bitrix24.ru/rest/1/xxxx/)

Ozon (marketplace) - Dashboard: seller.ozon.ru/app/settings/api-keys - Path: Settings → API keys → create a key with the Admin role - Save to a note: - OZON_CLIENT_ID = Client Id - OZON_API_KEY = API key (shown only once)

Wildberries (marketplace) - Dashboard: seller.wildberries.ru - Path: Profile (your organization name, top right) → Settings → API access - Save to a note: - WB_API_TOKEN = the token (shown only once, valid for 180 days)

Amazon (marketplace) - Dashboard: sellercentral.amazon.com - Path: Settings → User Permissions → Developer profile → register an SP-API app and get your credentials (LWA) - Save to a note: - AMAZON_REFRESH_TOKEN = LWA refresh token - AMAZON_CLIENT_ID = LWA client id - AMAZON_CLIENT_SECRET = LWA client secret (shown only once)

Any system (CRM / accounting / marketplace / analytics) - Dashboard: your system's admin area - Path: Settings → the "API" / "Integrations" / "Webhooks" section → create a key with read-only access - Save to a note: - SYSTEM_API_KEY = the key / access token (save it exactly as the dashboard shows it)

Prompt for Claude in Chrome · {system} ("copy" button) Open Claude in Chrome and paste the prompt in full. Claude will walk through the dashboard on its own and stop wherever your action is needed. *(Full texts of all 6 prompts are in the prompts section.)*

Step 2. Connect to Claude (one time)

Done in the terminal via Claude Code. Drop your keys from step 1 into the prompt and send it — Claude will install and configure everything itself.

A note about the connector (varies by system):

• amoCRM: There may be no proven, ready-made MCP server for amoCRM — so the prompt asks Claude to find a current connector and confirm the choice with you. If there's no reliable one, Claude will wire up the amoCRM REST API directly through a universal connector (Bearer token auth). That's more honest than hardcoding a repo that might not work.
• Bitrix24: The easiest way to connect Bitrix24 is an "inbound webhook" — a single URL with CRM permissions, no OAuth. There may be no proven ready-made MCP — the prompt asks Claude to find a current connector or wire up REST through that webhook URL.
• Ozon: Ozon has a ready-made MCP server — github.com/PCDCK/ozon-mcp (466 Seller API methods). The prompt below installs exactly that one.
• Wildberries: There may be no proven, ready-made MCP server for WB — so the prompt asks Claude to find a current connector and confirm the choice with you before installing. That's more honest than hardcoding a repo that might not work.
• Amazon: Amazon SP-API is trickier than the rest: you need a developer profile and app registration (LWA). The prompt will walk you through getting the credentials and ask you to confirm each step; if a ready-made MCP connector for SP-API exists, Claude will suggest it — otherwise it wires up SP-API directly. App registration can take longer; that's normal.
• Any system: The flow is identical for any system with an API: a CRM (RetailCRM, HubSpot), accounting software (MoySklad, 1C), a marketplace (Megamarket, Avito, Lamoda), analytics, telephony. Only that first step changes — where to get the key. From there, Claude finds a connector on its own or wires up the API directly.

Prompt for Claude Code · {system} ("copy" button) Before sending, put your keys where it says PASTE_… *(Full texts of all 6 prompts are in the prompts section.)*

Step 3. Verify it works

Restart Claude Code and send a test query. If real numbers from your dashboard come back — you're connected.

Test query ("copy" button) *(Full texts of all 6 test queries are in the prompts section.)*

✓ Got real numbers from your system? Then it's connected — move on to part two, the audit prompt.

If something goes wrong

Security

Keys and tokens are access to your business. Keep them to yourself, don't post them in public chats, and don't forward them to strangers. The prompt explicitly forbids Claude from writing keys into files that would end up in git.

02 · Part Two · The Audit

The "Expert Panel" prompt

One prompt turns Claude into a panel of six experts. The niche isn't set in advance — Claude figures it out from the data. First it verifies data accuracy on a 5-hour slice and waits for your confirmation, and only then asks questions about your business and delivers an audit with priorities.

How to use it — 3 steps:

1. Fill in 4 fields at the top of the prompt CRM, goal, period, access type. Claude will figure out the niche and everything else from the data.

2. Paste the prompt into Claude in full Best results on the most capable model (Opus). The prompt is reusable: paste it once, then it's a conversation.

3. Answer the questions From there the expert panel handles everything itself — from the data check to the roadmap.

Data check comes first. The prompt pulls a control slice of the last 5 hours and asks for your "checks out". Only after that — niche detection, business questions, and the audit itself. It's your protection against pretty but wrong numbers.

The panel · 6 roles

• 01 · Financial analyst — Revenue, margin, average order value, expenses, unit economics, cash flow, seasonality, revenue concentration by customer and product.
• 02 · Sales & funnel analyst — Deal stages, stage-to-stage conversion, cycle length, win rate, loss reasons, deal sources, forecasting and closing.
• 03 · Acquisition marketer — Channels and lead sources, cost per lead and CAC, channel payback (ROMI), lead quality, lead-to-sale follow-through.
• 04 · Operations expert — Request processing speed, bottlenecks and idle time, SLAs and deadlines, team workload, repetitive manual busywork.
• 05 · RevOps / CRM hygiene — Duplicates, empty fields, "dead" deals, status accuracy, deal owners, automation, retention, repeat sales, LTV.
• 06 · Moderator & synthesizer — Merges the conclusions, resolves contradictions, prioritizes, builds the roadmap, owns the final report.

The master prompt · copy it in full and fill in 4 fields

Business audit through your CRM — the "Expert Panel"

6 experts in one prompt · detects the niche itself · 5-hour data check · ICE priorities · 30/60/90 roadmap. Best results on the top model. ("copy" button)

*(The full text of the master prompt is in the prompts section.)*

What happens after you paste it · 6 stages

• 0. MCP and data accuracy check first — A control export of the last 5 hours from your CRM. Claude shows a table and waits for your "checks out". Until you confirm, it doesn't move on.
• 1. Full data and niche detection — A full slice for the period (deals, leads, amounts, statuses, sources, customers). Claude determines your niche and business model from the data itself.
• 2. Questions driven by the data — Claude forms a hypothesis about the business and asks 5-7 questions only about what the data didn't explain. Then it stops and waits.
• 3. Role-by-role breakdown — Experts 1-5: 2-5 findings each, in the format Problem → Evidence → Impact in $ → Recommendation → Effort/Payoff.
• 4. Synthesis — Scores by area (0-100): Economics, Sales/Funnel, Marketing, Operations, CRM hygiene. Top 5 money leaks, an ICE table, a 30/60/90 roadmap.
• 5. Implementation plan — Asks which item you want expanded in detail or turned into a step-by-step implementation plan.

The prompt's core rules

• ◆ No made-up numbers. Real data only. Whatever's missing gets flagged "no data".
• ◆ Every conclusion is backed by evidence. Problem → Evidence → Impact in $ or % → Recommendation → Effort/Payoff.
• ◆ ICE priorities. Impact, Confidence, Ease (1-10) — it scores and sorts.
• ◆ Quick wins vs strategy. Splits findings into 1-2 weeks and 1-3 months.
• ◆ Plain human language, respectful tone. No fluff, no corporate-speak.

The prompt is reusable: paste it once — then it's a conversation. Keys and data are access to your business; keep them to yourself. Wait until you've confirmed data accuracy: Claude moves on to niche detection, business questions, and the audit only after that.

What's next

• Top MCP servers → — More connectors to hook up to Claude
• Claude Code from scratch → — If you haven't installed terminal Claude yet

*Footer:*