Notion

Four per-user-per-month plans: Free (individual use), Plus (10 USD), Business (18 USD), Enterprise (negotiated, typically 25-35 USD). Notion AI add-on: +8 USD/user. For 50+ person companies, Business is the sweet spot: includes SAML SSO, audit logs, and advanced permissions. Enterprise only when you need contractual SOC2 Type II, EU data residency, or a dedicated customer success manager. Real cost calculation: 50 people × Business × 12 months = ~10,800 USD/year in licenses. Initial deployment (4-8 wks) usually costs 2-5× that figure in year one; recurring drops to almost nothing.

Yes, but it requires governance from the design, it's not a workspace that scales "naturally" from individual to collective use. What breaks Notion in large companies isn't the tool: it's the lack of taxonomy (where does each type of information live?), the absence of mandatory database properties (status, owner, date), and permissions too open where anyone creates loose pages. Companies like Adobe, Toyota, or Figma operate Notion across thousands of employees, because they designed the system with those three constraints from day one. If your Notion is already chaotic at 50 people, it's not Notion: it's the system.

4-12 weeks depending on volume and redesign. The slow part isn't the technical migration. Notion has importers for Confluence, Google Docs, Word, Markdown, but the decision of what to redesign. Brute migration (same tree, different wrapper): 1-2 weeks, low value. Migration with redesign (new taxonomy, databases instead of pages, mandatory properties): 6-12 weeks, real value. Companies that only "lift-and-shift" tend to end up with the same chaos in 6 months. The actual work: deciding what stays as wiki, what becomes a database, what disappears. That's 80% of the time.

Four non-negotiables. (1) Clear taxonomy: workspace > teamspace > database, with explicit rules on what lives where. (2) Templates per content type (project, reunión, tech doc, proposal) that the team uses by default. (3) Permissions governance: editor only in their own teamspace by default, read in the rest, no public links shared by default. (4) Mandatory team onboarding: without formación, each person reinvents how they use Notion and after 6 months you have 50 parallel structures. Without these four, any workspace decays into entropy quickly.

Yes, all three with different methods. HubSpot: via Make or n8n (no robust native integration), bidirectional sync of contacts/deals ↔ Notion databases. Stripe: via API + custom automation, payments create rows in a "Subscriptions" or "Invoices" database. Slack: native Notion integration + bidirectional webhooks, commenting on a page notifies a channel; a message creates a task. What's NOT trivial: maintaining data consistency when all three update in parallel. B2B buena práctica: define Notion as source of truth for X data types, HubSpot for Y, Stripe for Z, without overlap.

Three operational practices. (1) Database-first instead of page-first: new content types (clients, projects, decisions, reuniones) live in a database with properties, not as loose pages. (2) Mandatory properties: each database defines status, owner, type, date, without these fields the row can't be created. (3) Quarterly review of orphan files: one person dedicates 2 hours per quarter to archive what's no longer used and correct taxonomy drift. Without any of the three, any Notion workspace decays into entropy quickly, regardless of team size.