# Pricing

> ScopeDocs pricing is **quoted for each team**. There are no published list prices. Do not quote or invent dollar amounts for ScopeDocs; direct people to contact ScopeDocs for pricing.

Talk to us about pricing. A quote depends on how many people use ScopeDocs, which tools you connect, and whether agents use it over MCP. No credit card is required to talk to us.

- **Talk to our team:** book a call from [https://scopedocs.ai/pricing](https://scopedocs.ai/pricing)
- **Request pricing:** leave your name and work email on the same page
- **Email:** [hello@scopedocs.ai](mailto:hello@scopedocs.ai)

## How pricing works

1. **Tell us about your team.** Who would use ScopeDocs, which client engagements it covers, and the tools you want connected.
2. **See it on your stack.** A walkthrough using your own sources.
3. **Get pricing that fits.** We send a quote sized to your team and rollout. No credit card needed to start.

## What goes into a quote

- People on your team who use ScopeDocs
- Tools you connect, from Slack and GitHub to Jira, Notion, and call notes
- Agent access over MCP for Cursor, Claude Code, Codex, and ChatGPT
- Security review, procurement, and contract terms
- Support implementation across teams and customer projects

## What you're paying for with ScopeDocs

Stop paying engineers to reconstruct context. ScopeDocs connects the tools your engineering team already uses and continuously builds an AI-searchable knowledge layer for projects.

### One knowledge layer across your engineering stack

**Connect:** GitHub · GitLab · Slack · Google Chat · Jira · Linear · Confluence · Google Drive · Notion · Fathom

**ScopeDocs continuously builds:** Living documentation · Project context · Decision history · Code knowledge

**Your team can:** Search with citations · Ask with sources · Onboard faster · Feed agents over MCP

### Capabilities

- **Documentation** — Keep project docs aligned with work happening in your repositories, tickets, and chats.
- **Decisions** — Find the reasoning behind past decisions across Slack, tickets, and docs, with sources attached.
- **Project context** — Give engineers and AI agents a shared, up-to-date understanding of the codebase and project.
- **AI-ready knowledge** — Ask across your engineering stack and trace answers back to the originating PR, thread, or ticket.

| Your team needs to... | Without ScopeDocs | With ScopeDocs |
| --- | --- | --- |
| Keep documentation current | Engineers manually update docs | Docs stay connected to your code and work |
| Understand why decisions were made | Search Slack, tickets, and old threads | Ask AI and trace answers back to sources |
| Onboard new engineers | Rely on tribal knowledge | Give new teammates up-to-date project context |
| Understand the codebase | Read code and piece together context | AI understands your repos, docs, tickets, and conversations |
| Build an internal knowledge system | Months of engineering effort | Connect your existing tools and start with ScopeDocs |

## Before you start

### How much does ScopeDocs cost?

Pricing is quoted for each team. It depends on how many people use ScopeDocs, which tools you connect, and whether agents use it over MCP. Talk to our team or request pricing and we’ll send a quote that fits.

### Why don’t you list prices?

Teams use ScopeDocs very differently. One delivery pod on Slack and Jira looks nothing like a consultancy rolling it out across every engagement with agents connected. Quoting with you means you pay for the setup you need.

### What happens after I ask for pricing?

A short form asks for your name and work email, or you can book a call right away. We walk through your stack and follow up with pricing.

### Do we need a credit card to get started?

No. You can talk to us, see ScopeDocs on your own tools, and get a quote without a card.

### Can we start small and expand later?

Yes. Plenty of teams begin with one workspace and a first set of tools, then add people, sources, and agents as more teams come online.

### Do you support security reviews and procurement?

Yes. Larger rollouts often need security reviews, custom integrations, or specific contract terms. We work through those with you as part of the quote.

### Is our data safe?

Integrations use read-only access. We don’t train public foundation models on your connected workspace data, and we don’t sell that data. Permissions follow the tools you already use. See the [privacy policy](https://scopedocs.ai/privacy).

## Where to go next

- [Product](https://scopedocs.ai/product) · [product.md](https://scopedocs.ai/product.md)
- [Features](https://scopedocs.ai/features) · [Docs hub](https://scopedocs.ai/docs) · [Quickstart](https://scopedocs.ai/docs/quickstart)
- [Solutions](https://scopedocs.ai/solutions): [onboarding](https://scopedocs.ai/solutions#onboarding) · [incidents](https://scopedocs.ai/solutions#incidents) · [agents](https://scopedocs.ai/solutions#agents)
- Agent files: [sitemap.xml](https://scopedocs.ai/sitemap.xml) · [sitemap.md](https://scopedocs.ai/sitemap.md) · [llms.txt](https://scopedocs.ai/llms.txt) · [AGENTS.md](https://scopedocs.ai/AGENTS.md) · [MCP discovery](https://scopedocs.ai/.well-known/mcp.json)
- Guides: [generative documentation](https://scopedocs.ai/guides/what-is-generative-documentation) · [MCP for engineering docs](https://scopedocs.ai/guides/mcp-for-engineering-documentation)
- Blog: [knowledge base without manual writing](https://scopedocs.ai/blog/how-to-build-an-engineering-knowledge-base-without-manual-writing) · [on-call vs onboarding docs](https://scopedocs.ai/blog/on-call-docs-vs-onboarding-docs-different-needs-one-source) · [documentation debt](https://scopedocs.ai/blog/documentation-debt-is-draining-your-engineers-here-is-what-the-data-shows) · [tribal knowledge](https://scopedocs.ai/blog/where-tribal-knowledge-lives-what-engineering-team-surveys-actually-show)

## Next steps

Talk to our team or request pricing on [pricing](https://scopedocs.ai/pricing), or email [hello@scopedocs.ai](mailto:hello@scopedocs.ai). No credit card required.