By Danijel Balog, Founder, Fragon Studios · Last updated: 2026-11-17
Have your requirements document written
You know which problem the software should solve, but not how to write it down so that providers make comparable quotes. We talk to the people who know the process and write the requirements document from that. It is yours, and you can use it to ask us or any other provider.
- 2-10 daysis how long a requirements document takes, depending on the size of the project.
- €1,100a day, billed by effort, so €2,200 to €11,000 net.
- 30 minutesfree first call, after which you know how many days to expect.
In short
- We write the requirements document with you, in 2 to 10 days at a day rate of €1,100.
- The result is yours. You can use it to get quotes from several providers, not just from us.
- It follows the structure of our template in ten sections, from the starting point to operation.
- If your project is small, a workshop from €1,500 is often enough instead of a full requirements document.
When is it worth having the requirements document written?
When you want to compare quotes from several providers, when several departments have a say, or when nobody in-house has the time to write it.
With the template
- one person knows the whole process
- you have a few days for it
- the project is manageable
Then use our free requirements document template.
With us
- several departments want different things
- you want to compare quotes from different providers
- nobody in-house has the time
How is the requirements document written?
From conversations with the people who do the work today, not from a questionnaire.
- 30 minutes, free
First call
What it is about and how many days to expect.
Conversations
With management, the department and the people doing the daily work, on site or remote.
Draft
Processes, roles, requirements as must, should and could, data and interfaces.
Review
You check the draft, we work in your comments.
Handover
The finished requirements document is yours.
What is in the requirements document?
What the software should do and why, from your point of view. How it is built technically goes into the provider’s specification.
- Starting point and goal
- Users and roles
- Processes today
- Requirements as must, should and could
- Data and interfaces
- Quality, data protection and hosting
- Constraints, acceptance and operation
The full structure with all guiding questions and a filled-in example is in the requirements document template.
Do you have to hire us afterwards?
No. The requirements document is a service of its own and it is yours.
If you come to us with it, the analysis before the quote is shorter, because much is already settled. If a ready-made product fits better than custom software, we write that into the document and tell you.
Frequently asked questions
What does a requirements document cost?
€2,200 to €11,000 net, depending on scope.
We bill by effort at a day rate of €1,100, and a requirements document takes 2 to 10 days. After the first call we tell you the expected number of days.
What is the difference between a requirements document and a specification?
The requirements document says what is needed, the specification how it is built.
The client writes the requirements document (Lastenheft), the contractor the specification (Pflichtenheft). Both terms are defined in the German standard DIN 69901-5.
Can it be smaller?
Yes, with a workshop from €1,500.
For manageable projects a workshop replaces the requirements document. Afterwards you know what should be built and what effort to expect.
Who writes the requirements document?
Danijel Balog, founder of Fragon Studios.
He holds the conversations himself and writes the document, without passing it on to anyone else.
Further reading
Let's talk.
Tell us about your project
In the first call we clarify whether you need a requirements document and how many days to expect. 30 minutes, no obligation.