> ## Documentation Index
> Fetch the complete documentation index at: https://docs.archways.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Capture demand

**Turn a one-line request into structured requirements, checked against what you already own.**

Business requests for new software or AI tools usually arrive as a single vague line — "we need something for X." Archways turns that line into structured requirements and checks it against your existing stack before anyone starts evaluating vendors.

​Use it when:

* A team submits a request for new software or an AI tool
* Procurement needs requests structured consistently before they're actioned
* You want to catch a request that could already be met by something you own, before it becomes a new purchase

​What's included:

* **Conversational intake** — Archways AI takes a vague one-line request and asks the questions needed to turn it into structured requirements
* **Automatic overlap check** — every incoming request is checked against your existing software stack, so a request that duplicates something already owned is caught at intake, not after an evaluation
* **A direct path into Software Evaluations** — once requirements are structured, the request can move straight into scoring and shortlisting if a new tool is genuinely needed

#### **​Quick answers**

**What happens when someone submits a vague software request?** Arch AI turns it into structured requirements through a guided conversation, then checks those requirements against the organisation's existing stack before anyone starts evaluating new vendors.

**Does intake catch duplicate requests?** Yes — every request is checked against what the organisation already owns at the point of intake, so overlap is caught before a new evaluation or purchase starts, not after.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.