Requirements interviewer
Interview the client across 15 areas — the questions adapt to the answers. One click turns an answer into a draft requirement; every requirement has an ID, a source and acceptance criteria. Checks find contradictions and gaps, and an approved baseline records the agreement and shows everything that changed afterwards.
Free, no sign-up
Meetings and sources
Every requirement refers to a meeting, a person or a document — so you can see where it came from.
Data is stored only in this browser; nothing is sent to a server.
How it works
Project and meetings
Each meeting has a date, topic, participants and notes. Requirements refer to a meeting and to a person or document — that keeps them traceable.
Interview
Questions are grouped into 15 areas. A “yes” on payments opens questions on the provider, refunds and receipts; a “yes” on personal data opens consent, storage location and retention.
Requirements
An answer becomes a template-based draft; you can also add requirements by hand. IDs like REQ-001 / NFR-001 / CON-001 are stable and never reused, even after deletion.
Roles and permissions
A role × entity × action matrix (create, read, update, delete, approve, export).
Checks
Published rules with IDs: missing acceptance criteria, vague words, NFRs without numbers, probable duplicates and contradictions, roles outside the matrix, matrix inconsistencies, too many Musts, missing NFR categories.
Baseline
Approval with the approver’s name creates a pinned version. After that every change is visible: which requirement and which field changed, what was added and removed.
Rules
The tables below are generated from the same code as the checks — rules v1.0 (2026-10-13). There is no AI inside the tool: the same data always gives the same issues.
RI‑01
- What is checked
- A functional requirement without acceptance criteria
- Importance
- high
RI‑02
- What is checked
- Vague words with no measure (“fast”, “user-friendly”, “etc.”…) — not a single number
- Importance
- medium
RI‑03
- What is checked
- A non-functional requirement without a number and a unit
- Importance
- high
RI‑04
- What is checked
- Probable duplicate: Jaccard title similarity ≥ 0.6
- Importance
- medium
RI‑05
- What is checked
- Probable contradiction: a shared subject (similarity ≥ 0.3, at least 2 shared words), one requirement negated (“must not”, “forbidden”…), the other not
- Importance
- high
RI‑06
- What is checked
- A requirement refers to a role missing from the permissions matrix
- Importance
- medium
RI‑07
- What is checked
- Matrix: update, delete, approve or export without read access
- Importance
- medium
RI‑08
- What is checked
- Too many Musts: over 60% of requirements (excluding Won't) with 5 or more
- Importance
- medium
RI‑09
- What is checked
- No non-functional requirements for: security, performance, availability, backups (when there are roles or data)
- Importance
- medium
RI‑10
- What is checked
- A requirement without a source (meeting, person or document)
- Importance
- low
RI‑11
- What is checked
- An acceptance criterion is marked TO_CLARIFY / УТОЧНИТЬ
- Importance
- low
RI‑12
- What is checked
- A requirement without a title
- Importance
- high
Vague words (RI-02): быстро, быстрый, быстрая, быстрое, удобно, удобный, удобная, удобное, надёжно, надежно, надёжный, надежный, современный, современная, современное, интуитивно, интуитивный, понятный, простой, просто, красивый, эффективно, оптимально, гибкий, масштабируемый, и т. д., и т.д., и др., по возможности, при необходимости, как можно, fast, quick, quickly, user-friendly, easy, intuitive, robust, reliable, modern, flexible, efficient, seamless, scalable, etc, as needed, if possible, as soon as possible. The issue appears only when the requirement has no number at all.
security
- Words
- безопас, парол, шифр, прав доступ, ограничен доступ, авториз, аутентиф, вход в систем, 2fa, tls, https, security, password, encrypt, access control, permission, auth, sign-in
performance
- Words
- время ответа, секунд, нагрузк, одновремен, производит, response time, latency, concurrent, load, performance, throughput
availability
- Words
- доступност, uptime, sla, круглосуточ, 24/7, availability, available
backups
- Words
- резерв, бэкап, backup, rpo, rto, восстановл, restore, recovery
Functional
- Prefix
- REQ-001, REQ-002…
Non-functional
- Prefix
- NFR-001, NFR-002…
Constraint
- Prefix
- CON-001, CON-002…
Goals and scope
- Questions
- 3
- Conditional
- 0
- With a requirement template
- 2
Roles and access
- Questions
- 4
- Conditional
- 1
- With a requirement template
- 2
Data and entities
- Questions
- 4
- Conditional
- 1
- With a requirement template
- 2
Integrations
- Questions
- 3
- Conditional
- 2
- With a requirement template
- 2
Notifications
- Questions
- 2
- Conditional
- 1
- With a requirement template
- 1
Reporting
- Questions
- 3
- Conditional
- 2
- With a requirement template
- 2
Payments
- Questions
- 4
- Conditional
- 3
- With a requirement template
- 3
Performance
- Questions
- 3
- Conditional
- 0
- With a requirement template
- 3
Security
- Questions
- 2
- Conditional
- 0
- With a requirement template
- 2
Availability and backups
- Questions
- 2
- Conditional
- 0
- With a requirement template
- 2
Personal data and compliance
- Questions
- 4
- Conditional
- 3
- With a requirement template
- 3
Languages and regions
- Questions
- 2
- Conditional
- 0
- With a requirement template
- 2
Devices and browsers
- Questions
- 2
- Conditional
- 0
- With a requirement template
- 2
Migrating existing data
- Questions
- 3
- Conditional
- 2
- With a requirement template
- 2
Support and SLA
- Questions
- 2
- Conditional
- 1
- With a requirement template
- 1
Export
- A specification in Markdown and PDF (via print): overview, roles and permissions, functional requirements by role, non-functional requirements, constraints, acceptance criteria, open issues, changes since the baseline, a traceability table.
- A requirements CSV — for spreadsheets and trackers; formula-like cells are escaped.
- JSON of the whole project — to load it back or hand it to a colleague.
- requirements-baseline — a file for other tools (for example, code-vs-spec checks): the approved baseline, or the current list marked “not approved”. You can also load a file from Idea → Product here.
Limitations
- Duplicates and contradictions are found by word overlap — they are probable findings. Synonyms and different wordings of the same meaning may be missed, and some findings will be false.
- Requirement templates never invent numbers: where a measure is needed, they say TO_CLARIFY.
- Items on personal data, storage in Kazakhstan and fiscal receipts are questions to check with a lawyer and an accountant, not legal advice.
- There is no multi-user editing: the project file is shared with colleagues by hand (JSON).
Privacy
- Everything runs in your browser: the tool itself does not send answers or requirements to a server, and they never appear in the page address.
- The project, baselines and versions are stored only in this browser (localStorage); “Clear all” deletes them.
- Analytics receives only the fact of a baseline approval or an export, the file format and the requirement count range — never the text.
- The result reaches us only if you send a request yourself and keep the “Attach the result” box ticked — the form shows exactly what will be sent.
Related tools
All tools · 40
Idea → Product blueprintAn interview about your idea → roles, features, three MVP scope options, priorities and risks. You get a Product Blueprint to start development from.
MVP complexity estimateProduct type, platforms, modules and integrations → a complexity band, workstreams and the questions you need answered before any honest price.
Scope and cost calculatorModules, effort, your rates, complexity factors, dependencies and a risk reserve → a cost and timeline range with every number explained, plus estimate comparison.
Technical brief generatorBuild a brief step by step: goal, roles, scenarios, integrations, data, acceptance criteria. You get Markdown to copy or download.
Tech Stack AdvisorCompare technologies within one layer by product fit, team experience, maintenance cost, performance and security — with hard constraints, the conditions that change the answer, and an ADR export.
Architecture CanvasA visual graph of services, APIs, databases, auth and integrations with structural checks, versions and Mermaid/JSON export.Need help with requirements and development?
We will interview the client, bring requirements to a baseline and estimate development. The first conversation about the format is free; the cost is set after a brief and an agreed scope.
- The first short conversation is free — we choose the format
- NDA — yours or ours
- Pricing after a brief and an agreed scope