# Technology request intake

> Asks every "can we buy X?" request the same six questions, exposes overlap with tools already owned, and decides which records the request creates.

Canonical: https://mikereams.com/ai/technology-request-intake

Skill · Original · Enterprise architecture · updated 2026-11-12. Part of the [AI Library](https://mikereams.com/ai).

What you get: A review summary written for the request itself: six answers, a net-new or overlap verdict, a recommendation and the records to create.

When to use it: For software, SaaS and tool requests, before anyone signs anything.

Ask for it like this: "Review this request for a new survey tool against our approved products and application list."

Limits: It recommends and a person decides. What it could not check against your portfolio is marked not checked, never guessed.

- Written from two posts in my application portfolio series: the six questions, and the rule for which record a request becomes.
- Question three does the work: one primary technical class, the incumbents already in that branch, and a verdict.

Files (MIT): [SKILL.md](https://mikereams.com/ai-files/technology-request-intake/SKILL.md)

Install with the skills CLI, from https://github.com/solventarchitect/skills:

```
npx skills add solventarchitect/skills --skill technology-request-intake
```

The reasoning: [Six Questions for Every Technology Request](https://mikereams.com/writing/six-questions-for-every-technology-request), [Software Product or Business Application?](https://mikereams.com/writing/software-product-or-business-application)

Tags: APM, technology acquisition, governance, CSDM