Create your requirements document online.
Guided step by step: goals, users, features, quality criteria — prioritized, numbered and delivered as a clean PDF straight to your inbox. Free, in about 15 minutes.
- Free
- Finished PDF by email
- About 15 minutes
What is this about?
The key facts of your project — they become the cover page of your requirements document.
Saved automatically — you can come back anytime.
What is a requirements document — and why does it decide your project?
A requirements specification (in German: Pflichtenheft, in French: cahier des charges) describes what a piece of software must do before anyone builds it: the goals, the users, the functional requirements with priorities, the quality criteria and the technical constraints. It is the document a vendor quotes against — and the document you accept the finished software against.
Projects rarely fail in the code. They fail in the gap between what was meant and what was written down. A clear, prioritized spec closes that gap: vendors can quote precisely instead of padding for uncertainty, and "we assumed that was included" stops being an argument.
Lastenheft vs. Pflichtenheft — the short version
- Lastenheft (customer requirements)
- Written by the client: WHAT is needed and WHY. Goals and requirements — no solution yet.
- Pflichtenheft (functional spec)
- The response: HOW and WITH WHAT the requirements will be implemented. Traditionally written by the vendor.
In practice, small and mid-sized projects combine both into one requirements document that the client drafts and the vendor refines — exactly what this generator produces.
What belongs in it
The generator walks you through the structure professionals use:
- Current situation and measurable goals — plus explicit non-goals that protect scope, budget and timeline
- User groups, platforms and languages
- Functional requirements — numbered (F-01, F-02 …) and prioritized must / should / could
- Non-functional requirements: performance, security & GDPR, availability, usability, backups
- Interfaces to existing systems and data migration
- Technical constraints, timeline, budget range, deliverables and acceptance criteria
How it works
- 1
Answer guided questions
Six short steps in plain language — no method knowledge needed. Typical requirements can be added with one click and edited.
- 2
Review the live document
Your answers become a numbered, prioritized specification with a proper structure — visible at any time.
- 3
Receive it by email
Tell us where to send it: the finished PDF lands in your inbox. View, refine and export it right here — or have us review it for free.
Frequently asked questions
Is the generator really free?
Yes — completely free, no trial, no hidden costs. It is our showcase: if you ever need someone to build what your document describes, you know where we are.
What happens to my data?
Your document is emailed to you and stored with us so we can review it on request. No sharing with third parties, no newsletter without your consent — and we delete your data any time on request (see the privacy policy).
What is the difference between a Lastenheft and a Pflichtenheft?
The Lastenheft states WHAT the client needs and why; the Pflichtenheft answers HOW the vendor will implement it. In small and mid-sized projects both are usually combined into one requirements document — which is what this tool creates.
How detailed should the requirements be?
Concrete enough that a stranger could quote against them. "F-04: Import orders from Excel with duplicate detection (Must)" is quotable; "the system should be flexible" is not. The must/should/could priorities matter more than sheer volume.
Can I export to Word?
Export as PDF directly, or copy the document as Markdown and paste it into Word or Google Docs — headings and structure carry over.
Which projects does it suit?
Custom software, replacing an old tool (e.g. Excel or Access), extending an existing system, or automation and integration projects — from small internal tools to six-figure builds.
The document is the start. The build is the point.
When your requirements document is ready, we will review it free of charge — realistic effort, hidden risks, missing pieces. And if you want it built: automation, custom software and applied AI are literally what we do.
Talk to us