How to Define System Requirements with AI

You can organize system requirements by talking with AI. Tell it what the system is for and who it’s for, and AI lays out the functional requirements, non-functional requirements, and screen structure — with this flow, even someone who can’t put requirements into words can make a draft. That said, what AI produces is a first-pass draft before ordering, not a complete spec ready to commission.

I’m Naohiro Hayashi, creator of Soreda!. I built a system requirements AI myself and have run it, practicing the flow of “idea → AI first-pass → firm up with the dev company → order.” From that experience, I’ll lay out how to organize requirements by talking with AI.

System requirements can be organized by talking with AI

System requirements can be organized by talking with AI, even without specialist knowledge. Tell it what you want, and AI shapes it into the form of requirements, so it’s easier to put your idea into words.

You have the “want to build,” but can’t make it a requirement

You may have an image of “I want a system like this,” but turning it into requirements as words is hard. Not knowing what to write as a function, or how to organize it, stalls the conversation with a dev company — a common struggle. The gap between “I know what I want” and “I can describe it precisely” is exactly where most projects get stuck before they even begin.

AI asks the purpose and lays out functions, non-functionals, screens

AI asks “what for” and “who uses it” through dialogue, and lays out the necessary functions (functional requirements), the conditions of performance and operation (non-functional requirements), and the screen structure. Rather than facing a requirements document alone, you just answer the questions, so it’s far easier to give it shape.

The flow of organizing requirements with AI

The flow is: tell the purpose → AI lays out the requirements → a human checks. Let’s go in order.

Tell what the system is for and who it’s for

First, tell it “what this system is for” and “who uses it.” For example, “to make reservation management easier,” “used by store staff.” The more concrete the purpose, the better AI can aim its organizing.

AI lays out functional, non-functional requirements and screens/data

Based on what you told it, AI lays out functional requirements (what it can do), non-functional requirements (conditions like speed and security), and screens and data items. It also becomes a chance to notice gaps, and your thinking becomes visible as a list.

Organize system requirements with AI on Soreda! →

What it can do is a “first-pass” — ordering means firming up with the dev company

This is the important point. What AI can do is a “first-pass” before ordering. Ordering means firming up the details with a dev company.

What AI produces is a first-pass draft before ordering

What AI produces is a first-pass draft before ordering. It isn’t a complete spec ready to commission as-is. Receiving it as “a foundation to put your idea into words and start the conversation” is the right way to use it.

A foundation to firm up details with the dev company

The organized requirements are a foundation to firm up details with the dev company. Feasibility (whether it can be built technically) and cost (how much it will be) are confirmed with the dev company, not AI. AI-organized requirements are “the WHAT you want,” not “technically verified” — keep them separate. Detailed usage and caveats are covered in How to Use AI Requirements (and Caveats).

FAQ

Q. Can I use it without programming knowledge? A. Yes. You just tell it what you want in words, and AI shapes it into requirements. You can proceed without knowing technical terms, since the AI handles translating your intent into the right structure.

Q. Can I commission it as-is? A. No. What AI produces is a first-pass draft before ordering. Ordering means firming up the details with a dev company.

Q. What should I hand the dev company? A. The organized requirements draft becomes your material to convey. How to hand it over is covered in Organizing Requirements to Tell a Developer.

Q. How much does it cost? A. System requirements is ticket-based, counted per run. See the official site for current details.

System requirements can be organized by talking with AI. Tell it what you want, and you can shape it into functions, non-functionals, and screens. But what AI makes is a first-pass draft before ordering. Confirm feasibility and cost with the dev company, and firm up the details before ordering. Start by telling the AI the purpose of the system you want to build.

Organize system requirements with AI on Soreda! →