Prepare a customer demo

Help me prepare a tailored Bigmind demo using Partner MCP.

Start with a short interview. Ask these questions in two small batches and wait for my answers before planning or creating anything:
1. Which partner sub-account should we populate, and which active workspace user's email should own the activities and receive inbox items?
2. What does the customer sell, to whom, and in which industry and region? Ask for their company name, product names, language, and currency. I can supply approved descriptions, or you can propose clearly fictional ones.
3. Who will watch the demo, and which two or three outcomes matter most: pipeline visibility, meeting insights, qualification, competitive selling, account signals, or sales preparation?
4. Which sales story should we show: a promising new deal, a stalled deal, a competitor evaluation, or a mix? Ask for relevant competitors and objections, or suggest fictional examples.
5. Should we use completed meetings only, or also email, calendar, and Slack fixtures where connections already exist? Default to completed meetings and a compact dataset.

Inspect the tools exposed by this connection and read their current schemas. Use partner tools to list accessible sub-accounts, resolve my choice to an exact organization ID, switch with partnerSwitchTenant, and confirm with whoami. Verify the active workspace user and inspect existing CRM and library content. Never invent IDs or use another tenant's records. If the choice is ambiguous or a required tool is missing, explain what I need to select or enable and wait.

Propose a brief plan showing the target organization name and ID, owner email, demo story, and records to create. Default to 3 fictional accounts, 2 contacts per account, 3 deals at different stages, 3 completed meetings, 1 ICP, 2 products, 2 competitor profiles with battlecards, and 2 demo signal inbox items. Keep the data relevant to my answers and below the sub-account's available capacity. Ask for my confirmation before making any changes.

After confirmation, enable demo mode for that exact sub-account with partnerSetDemoMode. Confirm the selected tenant again and keep this connection on it throughout setup. If the target changes or access fails, stop.

Build one coherent story across the dataset:
- Create an ICP with createIcp: target industries, company sizes, buyer roles, pain points, qualification criteria, and disqualifiers.
- Create products with createProduct: buyer value, use cases, differentiators, and clearly labeled illustrative pricing if needed.
- Create competitor profiles with createCompetitor. Find a suitable battlecard template or create one with createDocumentTemplate using purpose battlecard. Then use createBattlecard with the returned competitorId and templateId. Cover positioning, discovery questions, objections, and responses. Follow each tool's editor HTML schema. Use my supplied facts for real businesses; label invented comparisons as demo assumptions and never fabricate citations.
- Create accounts first, then contacts and deals with adminCreateDemoCrmRecord, always using destination workspace. Use the returned CRM IDs to link records. Use fictional prospect identities and reserved .example domains. Mark fixtures clearly as demo data. Do not create records in a connected CRM or modify existing customer records.
- Use adminCreateDemoActivity to create completed meetings with realistic transcripts and summaries linked to the actual account, contact, and deal IDs. Include a buyer pain point, product discussion, competitor objection, qualification gap, and next step where relevant to the story. Use the verified active owner's email. Keep completed meetings, email, and Slack timestamps in the past and all activity within the tool's allowed window relative to today. Add email, calendar, or Slack fixtures only if I selected them and the required connections exist; never create authentication connections or send messages.
- Use upsertSignalDefinition to create or reuse demo definitions with automations and notifications disabled where supported. Then use adminCreateDemoInboxItem with item.type signal, the returned signal IDs, actual CRM targets, and the verified user's email to add actionable demo inbox items. Do not call createSignal or trigger outreach, campaigns, or external notifications. If a definition cannot be configured without those side effects, skip it and explain.

Make retries safe: choose a stable demo run label, keep a manifest of every returned ID, and reuse activityKey and itemKey for the same fixtures. Before retrying CRM or library creation, check for the records already created in this run. Never overwrite unrelated content. If a tool fails, report the failure and preserve the successful results instead of starting over or claiming completion.

Finally, read back what you created where tools allow it. Summarize created, reused, skipped, and failed items with links or IDs. Give me a five-minute walkthrough tailored to the audience, showing which account, deal, meeting, library documents, and inbox items to open in order. Include the fixture manifest for cleanup and mention any analysis still processing. Ask whether to leave demo mode enabled for further preparation or turn it off; explain that turning it off does not delete the data.

#Review and finish

Open the populated sub-account and follow the assistant's walkthrough before presenting it. Meeting analysis may still be processing after the fixtures are created.

Keep the returned fixture IDs and keys. To remove an activity, use adminDeleteDemoActivity with its original activityKey, owner email, and activity type while demo mode is enabled. Other records and library documents need their own supported cleanup actions; there is no automatic undo for the whole setup.

When preparation is complete, use partnerSetDemoMode with enabled: false. This blocks further calls to the demo tools but leaves existing content in place. It does not disable regular library or signal tools.