Video transcript
Introduction
This video shows how projects work in Leadtime. The idea behind it: even custom projects follow a recurring sequence. Capturing requirements, specification, quote, delivery, acceptance and billing. Leadtime maps exactly this sequence, step by step.
Components in the library
It all starts in the component library. Here you store your services as reusable components, for example rolling out a test system. A component consists of work packages, arranged in a tree. Each work package describes what is delivered. These descriptions later become the specification.
Capturing requirements
Every work package has a questionnaire. It asks the client exactly what matters for this package. For example: should the system run on their own infrastructure or in the cloud? Who is the technical contact? And when should it go live? On the right is the internal note: how your team approaches this package. That way the know-how lives in the component, not in individual heads.
Specification and quote
For a project you take components from the library. Here, rolling out a test system for a large client, with every work package and its estimated hours, plus the hourly rate and the price. This planning produces the documents: the specification, which records the agreed scope, and the quote with hours and prices. Both come from the same work packages. You only choose the type of document, the contact person, the language, and whether a table of contents and a title page are included. You save each planning state as a version. That keeps track of what was agreed and what was added later.
Delivery
Once the order is in, every work package becomes a task for your team. You create it right on the work package or link it to an existing task. The project progress shows for each package how far along it is and what budget it has. In the pipeline you spread the tasks across the week and across your team. And on every task you see how much time is booked and how much was planned.
Acceptance
Before handover comes acceptance. Test cases with steps and expected results are already part of the component, so every project is checked just as thoroughly.
Billing
Billing is based on the quote. Down payments are stored in the project and deducted from the final invoice. That is how every project follows the same pattern: components, requirements, specification and quote, delivery, acceptance and billing, in one system.