Functional spec generator: turn your client’s requirements spec into a functional spec.
Upload the requirements spec (German: Lastenheft) and answer ten questions at most. You get a structured draft functional spec with your logo, as Word and PDF. Free, no account needed.
- 1Upload
- 2Check
- 32Questions
- 43Branding
- 54SpecSend
Upload the requirements spec
Confidential spec? If in doubt, upload only an excerpt. Remove names and prices first; we don’t need them. We delete the requirements spec once the functional spec has been created, and the functional spec after 30 days. For analysis, the text goes via OpenRouter, a service that passes it on to an AI model running in Europe. A person from our team reads it too. Privacy policy
Drag a file here or
PDF, Word or text, up to 10 MB or about 40 pages Fictional example from the book “Projects that pay off.”Checking the requirements spec …
- 12 pages read
- 48 requirements found
- Structuring into epics and packages
- Checklist “Is the spec solid enough?”
What the spec contains
Proposed structure
- Basic set-up: companies, roles
- Corporate design
- Languages
- Data migration from the broker portal
- CRM integration
- Training, testing, go-live
Is the spec solid enough?
- Goal stated in one sentence
- Clear when a requirement is met 11 of 48
- Quantities given users yes, records no
- Interfaces described CRM without description
- Data migration described
- Client responsibilities agreed
- Deadline justified “end of May”, no reason given
- Clear who decides and accepts the result
- No one-word requirements 6 found, e.g. “multilingual”
- Call possible before the quote not stated
Nine questions change the effort. We mark everything else as open in the spec.
In the example, the answers are already selected so you can click through quickly, and apart from line 7 the line numbers are made up. With your own spec, you choose them yourself.
Branding (optional)
Functional specification
for Auenhof · Draft of 11 Nov 2026
Created with the Leadtime spec generator
Your functional spec draft is ready.
6 epics, 18 work packages, 7 assumptions, 5 open points. The status shows how certain each epic is. The “effort” column is empty: you estimate the hours.
- Background and goal
- People involved
- Scope by epic
- Exclusions
- Assumptions
- Client responsibilities
- Dependencies
- Schedule from order
- Acceptance
- Changes
3 · Scope by epic
| Epic | Packages | Status | Effort |
|---|---|---|---|
| Basic set-up: companies, roles | 4 | firm | |
| Corporate design | 2 | firm | |
| Languages | 3 | assumption | |
| Data migration | 3 | range | |
| CRM integration | 1 | open, analysis needed | |
| Training, testing, go-live | 5 | firm |
Open points
- No description of the CRM interface. Suggestion: a separate “CRM integration analysis” package up front.
- Number of records in the broker portal unknown. Effort as a range, binding after data analysis.
- It is not stated who accepts the result on the client side.
- Deadline end of May: no reason given. Suggestion: plan backwards, core by the date.
- What the client supplies (content, data, testing) is not agreed.
Some packages come back in many of your projects. We call them building blocks: if you record them with their questions and their effort, you don’t have to estimate them from scratch every time. Lukas Ebner is happy to talk this through with you for 30 minutes. Book a call →
We read your requirements spec, structure it into epics and work packages and add your answers. A person on our team checks every functional spec before it goes out. You will get it as Word and PDF at . If it takes longer, we will let you know.
Frequently asked questions
Before you upload.
What does the generator cost?
Nothing. You do not need an account. To keep it from being used as a bulk tool, there is a monthly limit.
What happens to my requirements spec?
We need it to create this functional spec. The requirements spec is deleted once the functional spec has been created, and the finished functional spec after 30 days. For analysis, the text is sent via OpenRouter to an AI model running in Europe. We don’t need names or prices; feel free to remove them first. More in our privacy policy.
Why only ten questions?
A few questions you can answer straight away help more than 80 that nobody fills in. We only ask what changes the effort: quantities, interfaces, who supplies what, how firm the deadline is. Everything else goes into the spec as an open point for you to clarify with the client. Christof Ebert likewise advises clarifying requirements as far as a start with acceptable risk requires. In his experience, trying to clarify everything before anything begins paralyses the project.
Does the generator estimate the hours?
No. It structures the work into epics and packages, each with a testable result and a status. You estimate the hours yourself, because only you know your team and your past projects. This fits a piece of advice from the specialist literature: experts tend to underestimate, because they assume everyone works the way they do. So have a colleague estimate as well, and compare estimate and actual effort once the project is over. Your figures then get more accurate with every project.
I am the client. Does this help me too?
The generator is built for service providers who have received a requirements spec. If you are writing one, check it against the checklist “Is the spec solid enough?”. That makes it easier for a provider to quote it at a fixed price.
What is a building block?
A package that comes back in many of your projects, such as “set up a language”, with its questions and its effort. With building blocks you do not have to break down and estimate the next similar project from scratch. Part III of the book shows how.