# Product and analytics: requirements and decisions > A space without code for product managers, analysts and stakeholders: one question, one answer from the team’s documents, with a link to the source. Use case # Product and analytics: requirements and decisions The product manager at “Zametki” asks: “What is in the roadmap for the fourth quarter, and does it conflict with the export requirements and the release policy?” The roadmap is in one folder, the requirements in another, the policy in a third, and the developers are busy — every such question costs a day. [Create a space](https://buff.systems/app) [All use cases](https://buff.systems/en/use-cases) For product teams whose knowledge lives in documents, not in code **Ask in the space** three documents ← scroll the frame → **Three documents, one answer (outlined):** what is planned for the quarter and who owns it, where the roadmap agrees with the requirements and the release policy and where it does not — with links to the files. Situation ## Three documents, three different answers What gets in the way - Knowledge is scattered across Notion, Confluence, Google Drive, network folders and colleagues’ heads. - The answer to “how we actually do it” is written down somewhere, but finding it takes longer than asking in chat. - Documents contradict each other, and nobody knows which one is right. - Every question from the business either distracts a developer or waits until tomorrow. - Agreements leave together with the people who made them. - The team has no code — or the code is beside the point — and tools “for developers” start with code. Solution 01 ## A space without code — the team’s workplace A space is created from a single name and needs no access to code. Inside are “Ask”, deep research, the knowledge base and connections to knowledge sources; there are no code sections. The example shows the product team space of “Zametki”, set up next to the development projects of the same organisation. [How a space works](https://buff.systems/en/docs/quickstart/space) **Team space** no code ← scroll the frame → **What is inside:** on the left (outlined) — “Ask”, “Deep research”, connections (“Connectors”), “Knowledge base” and “Development sessions”, the log of programmers’ work in Buff Code; there are no project code sections. Solution 02 ## “Ask” — an answer from the documents, with a link to the source The product manager asks what response time is promised to clients on the “Business” plan and whether it matches what support says. The model reads the support policy, the contracts and the FAQ, gives 4 working hours, notices that the support FAQ promises 8 hours and is out of date, and names every file with its section. Read-only: nothing in the documents changes. [How to ask a question](https://buff.systems/en/docs/ask) **An answer across several documents** discrepancy found ← scroll the frame → **Sources named (outlined):** the policy and the contract say 4 working hours, the support FAQ says 8 and is out of date; every document is named with its section. Solution 03 ## Knowledge sources — your documents where they already are Notion, Confluence, Google Drive, Figma, files on a server and network folders — and, if needed, the public internet — are connected through the connector, a small program your IT specialist installs in your network once. Nothing is copied in advance: the model reads only what the answer needs. Questions can also be asked in trackers, as a comment on a ticket. Knowledge sources - [Confluence](https://buff.systems/en/marketplace/confluence) - [Figma](https://buff.systems/en/marketplace/figma) - [Files on disk](https://buff.systems/en/marketplace/files) - [Google Drive](https://buff.systems/en/marketplace/google-drive) - [Notion](https://buff.systems/en/marketplace/notion) - [Internet](https://buff.systems/en/marketplace/web) - Your own internal service Trackers and discussions — a question as a comment, the answer in the same place - [Bitbucket Cloud](https://buff.systems/en/marketplace/bitbucket-cloud) - [Bitbucket Data Center](https://buff.systems/en/marketplace/bitbucket-dc) - [Gitea](https://buff.systems/en/marketplace/gitea) - [GitHub](https://buff.systems/en/marketplace/github) - [GitLab](https://buff.systems/en/marketplace/gitlab) - [Jira](https://buff.systems/en/marketplace/jira) - [Jira Cloud](https://buff.systems/en/marketplace/jira-cloud) - [Redmine](https://buff.systems/en/marketplace/redmine) What is read - Word - Excel - PowerPoint - PDF - Google Docs - Google Sheets - Google Slides - network folders - text files - attachments to a question 14 integrations in the catalogue, installed into a program you already have, with no new software; a system outside the catalogue — a CRM, Bitrix24, 1C, a messenger — your IT specialist connects with your own tool, and it is available to the AI agent at once. Documents are read where they are — nothing is copied in advance. [Full catalogue →](https://buff.systems/en/marketplace) [Which sources can be connected](https://buff.systems/en/docs/connector/knowledge) Solution 04 ## A question where the team already works A comment on a Notion or Confluence page, on a document in Google Drive or on a tracker ticket that mentions the bot is a question, and the answer arrives in the same discussion. Research is ordered the same way — the finished document, or a link to it, arrives there too. There is no need to open the app. [How to ask from a tracker](https://buff.systems/en/docs/connector/trackers) **A tracker ticket** in the discussion ← scroll the frame → **Two comments from the bot:** below — “received, starting the research”; above — the finished document right in the ticket discussion. Solution 05 ## Knowledge base — what must outlast staff changes The team’s rules, facts and pitfalls in one place, in the same form for people and for the model. The model sees them in every question and research and adds what it learns along the way; only a person writes rules. [What to put in the knowledge base](https://buff.systems/en/docs/knowledge) **Knowledge base** rules · facts · pitfalls ← scroll the frame → **Three team entries:** the rule “quote deadlines to clients only from the contract”, a fact about where the documents are, a pitfall about the outdated FAQ — only the space’s own entries. Solution 06 ## Deep research — a document, not a chat answer For when you need analysis rather than an answer. Two model roles: the analyst reads the sources and writes the document; the reviewer checks every statement against the same sources and raises remarks; the analyst corrects. The result is a document with links and with the discrepancies named. *01* #### The analyst writes Builds the document from policies, requirements, contracts and knowledge base entries; every statement comes with a link. *02* #### The reviewer checks Rereads the sources, finds what is unproven and where documents disagree, and raises remarks. *03* #### The document goes to you A PDF or a text file; ordered from Notion, it arrives there as a page; from Google Drive, as a new document next to the original. [How to order research](https://buff.systems/en/docs/research) Outcome The product manager, the analyst and the stakeholder have one place where questions about the product are answered from the team’s documents with a link to the source — without distracting developers and without access to code. The first step is a name ## Create a space and ask your first question Sign up by email and the space is ready at once. Until sources are connected, the model answers from the knowledge base and from files you attach to the question. A starting balance is provided to try it out. [Create a space](https://buff.systems/app) [Write to us](mailto:info@buff.systems) Until sources are connected, attach a document to the question