Confluence

What is Confluence?

Owned by Australian enterprise software giant Atlassian—founded in 2001 by Mike Cannon-Brookes and Scott Farquhar—Confluence was launched in 2004 as a pioneer in collaborative team workspaces. When an Indian startup reaches 200 employees, institutional knowledge begins to rot. A new engineer joins the team and asks, "Where is the documentation for the payment gateway API?" The answer is usually a broken Google Doc link buried in a Slack channel from two years ago. Information silos destroy velocity.

Confluence is a corporate Wiki designed to solve this. It organizes information into "Spaces" (e.g., The Engineering Space, The Marketing Space). Inside those spaces are infinitely nested pages. The Product Manager writes the PRD for a new feature in Confluence, detailing the user stories, the analytics requirements, and the go-to-market strategy. Because it is built by Atlassian, it talks directly to Jira, ensuring the documentation is intrinsically linked to the actual code being shipped.

6 Key Features That Matter

1. Deep Jira Integration: This is the only reason to use Confluence. You can type `/jira` inside a Confluence document and embed a live Jira ticket. As the engineer moves the ticket from "In Progress" to "Done" in Jira, the status updates dynamically inside the Confluence PRD.
2. Page Macros: Confluence allows you to insert dynamic blocks of content called Macros. You can embed an expanding table of contents, pull in live reporting charts from Jira dashboards, or embed Figma files directly into the page.
3. Page Trees & Hierarchy: Unlike Google Drive's folder system, Confluence relies on a left-hand navigation tree. Every page has a parent and can have infinite children. This forces teams to logically structure their documentation.
4. Enterprise Permissions: You can apply incredibly granular read/write permissions at the Space level or the individual Page level. This allows an enterprise to keep highly sensitive architectural documents completely hidden from external contractors, while keeping standard UI specs public.
5. Version History & Auditing: Every single keystroke is versioned. If an employee accidentally deletes a critical API spec, you can revert the page to its exact state from three weeks ago with one click. Essential for SOC2 compliance.
6. Templates: Standardize product thinking. You can enforce a rule that every time a PM clicks "Create New Product Spec," it pre-loads a mandatory template requiring them to fill out the Problem Statement, Target Audience, and Success Metrics.

Pricing Breakdown (INR Context)

Atlassian operates on a per-user, tiered pricing model. Note: Converted at 1 USD = ₹84. Excludes 18% GST.

• Free Tier: ₹0. Supports up to 10 users. A great way for a micro-startup to begin building habits, but it strictly limits permissions and storage.
• Standard: ~₹500/user/month ($6/mo). This scales up to 35,000 users. It unlocks granular page permissions, 250GB of storage, and basic analytics.
• Premium: ~₹960/user/month ($11.50/mo). Adds unlimited storage, 24/7 premium support, and advanced Atlassian Intelligence (AI summarization and generation features).
• Enterprise: Custom Pricing. For companies like Infosys or TCS, offering 99.95% uptime SLAs, dedicated data residency, and massive scale.

Who Should Use Confluence?

Any Indian company scaling past 100-200 employees that has standardized on Jira for issue tracking. At this scale, the administrative headache of managing scattered Google Docs or disjointed Notion workspaces is worse than dealing with Confluence's slightly sluggish UI.

Who should NOT use it: Pre-seed to Series A startups (under 50 people) that prize speed above all else. Confluence is heavy. Opening a page, clicking "Edit," waiting for the editor to load, and publishing changes creates friction. A 10-person team will move much faster using a unified, lightweight workspace like Notion or Coda.

First 5 Setup Steps for Product Teams

A messy Confluence instance is useless. Architecture is everything.

1. Define Spaces Logically: Do not create a new Space for every tiny project. Create broad Spaces by Department (e.g., "Product Management", "Engineering", "Design").
2. Establish the Root Page: The homepage of the "Product Management" space should immediately link to the active Quarterly OKRs and a directory of active PRDs.
3. Standardize the PRD Template: Go into the Space Settings and customize the default "Product Requirements Document" template to match your company's specific product philosophy.
4. Enforce Jira Linking: Train PMs that a PRD is not finished until the corresponding Jira Epic is embedded at the top of the page.
5. Use the "Decision" Macro: When a major architectural debate happens in a meeting, record the final outcome using the `/decision` macro. This logs who made the decision and when, preventing the same debate from happening again three months later.

Top Alternatives in the Indian Market

• Notion: The absolute favorite for modern startups. Notion is blisteringly fast, visually beautiful, and uses highly flexible databases instead of rigid page trees. However, it struggles with enterprise-grade permission management at massive scale.
• Coda: Focuses heavily on turning documents into powerful internal apps with deep API integrations (Packs) and formulas. Better for operational workflows than pure text wikis.
• Slite: A highly focused, minimalist wiki tool. It lacks the database power of Notion and the enterprise integrations of Confluence, but forces teams to write clean, simple, standardized documentation.