notion-onboarding-prompt

Notion Business Onboarding Prompt

Use this prompt to extract business knowledge from the company Notion workspace and populate the business/ layer of this wiki.

Requirements: the Notion MCP must be connected in your Claude Code session.

How to use:

1. Open a Claude Code session inside the brain repo (/Users/nikolashaag/Documents/Code/brain/).
2. Copy everything below the second horizontal rule.
3. Paste it as your first message.

---

---

You are about to perform a one-off business knowledge extraction from the 7Mind Notion workspace into the company brain wiki.

Setup

Read these files first so you understand the wiki structure and conventions: ./STRUCTURE.md ./business/business-index.md

The business layer pages you will populate are: ./business/product/product-overview.md ./business/product/markets.md ./business/product/roadmap-context.md ./business/brand/brand-guide.md ./business/brand/voice-and-tone.md ./business/customers/b2c.md ./business/customers/b2b.md ./business/customers/b2b2c.md

Additional process pages may be created under ./business/processes/ if you find documented workflows worth preserving.

Step 1 — Discover what exists in Notion

Use the Notion MCP search tool to find pages relevant to each of the following topics. Run multiple searches with varied terms to maximise coverage. Good search terms:

Product: “product”, “roadmap”, “strategy”, “OKR”, “vision”, “positioning” Brand: “brand”, “design”, “colors”, “typography”, “guidelines”, “voice”, “tone”, “copy” Customers: “customer”, “B2B”, “B2C”, “enterprise”, “persona”, “segment”, “partner”, “churn” Markets: “market”, “DACH”, “Germany”, “expansion”, “localization”, “international” Processes: “process”, “release”, “oncall”, “on-call”, “support”, “escalation”, “workflow” Pricing: “pricing”, “subscription”, “plan”, “trial”, “revenue”

For each search result, note the page title and ID. Do not fetch everything — use the titles to decide which pages are high-signal before fetching.

Step 2 — Fetch and read high-signal pages

Fetch the pages that most directly answer the questions in each business wiki section (see Step 3). Prioritise:

• Pages with “strategy”, “brand guide”, “positioning”, or “OKR” in the title
• Pages that look like structured documents rather than meeting notes
• Pages owned by product, marketing, or leadership

Read each fetched page carefully. Note which facts map to which wiki section.

Step 3 — Populate the wiki pages

For each business wiki page, fill in all sections that the Notion content can answer. Leave sections as TBD where Notion has no clear answer — do not invent or infer.

product-overview.md

Extract: what 7Mind does, core value proposition, primary features, platforms, business model (subscription, B2B, B2B2C), languages supported.

markets.md

Extract: primary market (DACH), active European countries and their status, any localization details (content translated? marketing live?), expansion notes.

roadmap-context.md

Extract: current strategic focus areas (2-4 bets), settled product decisions that should not be re-litigated, explicit deprioritisation decisions. This page captures intent not tickets — do not paste roadmap items verbatim.

brand-guide.md

Extract: brand colors (hex values), typography (typefaces, weights), logo usage rules, iconography style, illustration / photography style, design system location (Figma link or repo).

voice-and-tone.md

Extract: brand personality descriptors, formality level (du vs Sie in German), writing rules, words or phrases to avoid, tone shifts across contexts (onboarding vs error states vs marketing), any example copy.

b2c.md

Extract: consumer persona descriptions, pricing (monthly / annual / trial), key retention drivers, churn patterns, primary acquisition channels.

b2b.md

Extract: target buyer (HR, insurer, employer), contract model (seat-based, flat fee), any technical requirements (SSO, bulk provisioning, reporting), current channel status.

b2b2c.md

Extract: partner types, how users are provisioned (API, code redemption, SSO), commercial model (revenue share, white-label), active partner categories.

processes/ (create only if clearly documented)

If you find a clearly documented process (release workflow, oncall rotation, support escalation), create a new page at ./business/processes/<slug>.md using the standard page format from STRUCTURE.md.

Step 4 — Respect copyright and confidentiality

• Do not reproduce large blocks of Notion text verbatim. Synthesise and rephrase.
• Do not include personally identifiable information (employee names, salaries, personal contact details).
• Do not include financial figures unless they are already public (e.g. publicly stated pricing).
• If a Notion page is marked confidential or contains clearly sensitive commercial terms, note “TBD — source exists in Notion, review before adding” rather than pasting the content.

Step 5 — Update index and log

After writing all pages:

1. Update ./business/business-index.md — add links to any new pages you created under processes/, and update the one-line descriptions if the stubs were more accurate now.

2. Append one line per changed page to ./log.md: Format: YYYY-MM-DD — populated <page-name> from Notion extraction

Step 6 — Report what you found and what is missing

After finishing, give a short summary:

• Which pages were fully populated
• Which pages are still mostly TBD and why (Notion had nothing, content was too sensitive, etc.)
• Any pages or topics you found in Notion that do not have a home in the wiki yet (flag these — a new page or section may be warranted)

Constraints

• Follow the frontmatter schema and page format in STRUCTURE.md exactly.
• No em dashes anywhere in any page.
• Do not modify anything in ./raw/.
• Do not touch the tech/ layer.
• Do not create new top-level folders without asking first.
• Mark anything uncertain as TBD rather than guessing.