ProductWhy LeadtimeClientsProjectsServiceTeamMoneyAgents
MoreOverviewIntegrationsSecurityCalculatorFracto Field
Who it’s forPricing
ResourcesBook: Projects that pay offSwitchingTutorialsRequirements managementHelp centreBlogAbout usContact
Sign in
Start free trialBook a call
Eine Projektleiterin geht mit zwei Leuten vom Kunden am großen Bildschirm den Umfang des neuen Projekts durch.

Every project delivered the way it was sold.

Your standard services sit in the catalogue as building blocks. You go through the questionnaire with your client, and the quote, the specification and your team’s tickets come out of it. The margin stays in the project, and the next one starts on time.

The problem

A project that runs three weeks over costs you twice.

It starts with a quote. You commit to a price and a date, often before you know every step. Only then does the real work begin, and only then do you see how complicated it gets.

If it takes longer, the client is annoyed, and it costs you money. Every hour beyond the quote comes off your margin. And the people still stuck in the old project are missing from the next one. That is the second price: new business has to wait because your capacity is tied up.

It works like a railway timetable. If one train at the front is late, every train behind it is late too. One project that runs long turns into two postponed start dates and a new contract that slips into the next quarter. The delays add up to a bottleneck.

That is why the margin is decided before the project starts. The salesperson’s commitment becomes a quote, and the quote becomes a complete scope of work. The client signs it off, without arguments and without side agreements. If you manage your requirements properly, you deliver more reliably and earn more on your projects.

Your timetable for the quarter

An example: the dealer portal takes three weeks longer. See what that means for the projects behind it.

Chart: four projects follow each other in a quarter’s timetable. The first takes three weeks longer, so each of the two that follow starts three weeks later, and the new contract slips into the next quarter.

  • Margin: three weeks of work that nobody pays for
  • Dates: two more clients wait longer
  • New business: the next contract only starts next quarter

What it looks like

The Projects area in four minutes, in the real app.

From the building block in the catalogue through questions, quote and specification to acceptance and invoicing. Jump straight to the part you care about.

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.

Photo: The managing director of a web agency sits at his desk, hand on his chin, doing the maths on a project that is running over again.

Managing director of a web agency

“Are we actually still making money on this project?”

How the margin stays in the project

How Leadtime solves it

What you sell again and again becomes a building block in the catalogue.

The building block brings everything you need to deliver: work packages with hours, the questions for the client and the test cases for acceptance. We show how it works with a web agency selling its dealer portal to Brandt & Söhne.

  1. CatalogueThe dealer portal is a building block with work packages and hours.
  2. QuestionnaireThe project lead goes through it with the client.
  3. Quote and specificationBoth come from the answers.
  4. TicketsYour team can start right away.

Product catalogue

The dealer portal sits in the catalogue, set up properly once.

The agency set up its dealer portal once as a building block: six work packages from kick-off to go-live, each with hours and, where needed, questions and test cases. For the new project, the project lead pulls the building block from the catalogue with one click. She then adapts the copy, and the catalogue stays as it is.

What you get: Every project starts with what worked last time. No service is forgotten, and the hours come from experience rather than gut feeling.

1Choose the building block from the catalogue
2Work packages with hours are in the project

Questionnaire

You settle the open questions in a workshop, not in 14 emails.

Every work package comes with the questions that need answers before the start. In the workshop, the project lead goes through them with Brandt & Söhne: how many price groups are there? Do dealers need to buy on account from launch? The answers are stored on the work package. Depending on the answers, work packages are switched on or off, and the effort adjusts.

What you get: What the client wants is settled before you name a price. And nobody has to dig the answer out of an email thread later.

RE: RE: RE: RE: Dealer portal – open questions14 messages
Matthias B.

Prices as discussed, three groups. Ms Kessler will send the list.

Sabine K.

Quick addition: wholesalers get their own terms. And do we need ordering on account from day one?

Matthias B.

On account yes, but only from autumn. Our IT team will send the dealer logos.

You

Thanks! Just to be sure, how many price groups is it now?

Matthias B.

See my email from the 12th.

Quote and specification

The quote and the specification come from the same answers.

From the project version, Leadtime creates the quote and the specification, with your template, in German or English, as a Word file to send on. Both use the same work packages and hours. What Brandt & Söhne answered in the workshop is in the specification, and the hours for it are in the quote.

What you get: The client signs off what is in the specification. Anything added later is a change request, not an argument.

1Quote, 2 pages
Quote · version 2
17 March 2026

Brandt & Söhne GmbH · Matthias Brandt

Quote

Dealer portal for Brandt & Söhne

Built on the existing shop, for around 40 dealers. Based on the specification, version 2. Hourly rate €160.

ItemHoursAmount
Dealer portal basics6 work packages, including price lists per dealer: 18 h112€17,920
Shopware integration96€15,360
ERP interface121€19,360
Requirements workshop16€2,560
Training and handover20€3,200
Total, excl. VAT365€58,400

Services not included in the specification are offered separately as a change request.

Page 1 of 2
2Specification, 14 pages
Specification · version 2
Brandt & Söhne dealer portal

Work package 3 of 6

Price lists per dealer

Every dealer sees the prices of their price group in the portal.

Answer from the workshop on 17 March

“Three: A, B and C. Wholesalers get group A.”

TaskEffort
Set up price groups A, B and C10 h
Assign dealers to the groups8 h
Work package total18 h

Input from Brandt & Söhne

Ms Kessler supplies the price list for each group by 31 March.

Acceptance criterion

A group B dealer sees the prices from the list on three products.

Page 6 of 14

Tickets

The specification turns into tickets your team can start on right away.

The project lead turns the work packages into tasks. Leadtime uses AI to write the briefing for the team from the client’s answers. Estimate, assignee and status are included, and everyone books their time directly on the task.

What you get: Fewer questions at the start. Whoever opens the ticket knows what to do and how much time is planned for it.

Photo: The managing director of an IT agency stands with her phone in hand in front of a wall planner full of sticky notes, working out when the next project can start.

Managing director of an IT agency

“The client wants to start next month. Do we even have people free for that?”

The answer is in the planning

Planning

Every client is priority one. Everyone on the team still has only 40 hours a week.

So that things don’t shift like in the timetable, you plan in four stages. In the Big Picture you rank a project’s tasks by priority, ideally together with the client. The Pool shows each person’s order of work across all projects. The Pipeline shows the team’s week, and you see straight away what no longer fits. In the Stack, everyone sees their own week.

What you get: If a week overflows, you see it in the Pipeline before the next project starts to slip.

  1. What first? Big PictureDecide with your client what comes first in the project.
  2. What’s next? PoolFor each person, the order across all the projects they work on.
  3. Who, when? PipelineThe team’s week, person by person. You see straight away what no longer fits.
  4. This week? StackEveryone sees their week: to do, give feedback, get feedback.

Versions and change requests

“But that’s what we agreed” is settled with one look at the project.

Every version of the project records what has changed since the last one. Leadtime writes the list of changes itself; you just give the version a name. Anything added after the specification is marked as a change request: it sits in the project with its effort and is invoiced separately.

What you get: Additions get paid for instead of given away. And there are no side agreements that only one person remembers.

Acceptance tests

What gets signed off is what was agreed.

The test cases are already stored in the building block. You go through them with your client step by step. Each one ends as passed, passed with restrictions or failed. Anything new that comes up at acceptance becomes a change request.

What you get: Acceptance is a meeting with an outcome, not an open end. Then you write the final invoice.

What you save

Half the time spent coordinating and searching.

Questions, answers, hours and documents live on the project, not in emails. Example: an agency with 20 employees. Today, each person spends around 3 hours a week coordinating, searching and retyping. With the status kept on the project, it is 1.5 hours.*

1,200fewer hours a year spent coordinating and searching

2×faster at coordinating and searching3 hours today, 1.5 with Leadtime, per person and week

€56,000less in staff costs a yearapproximately, at €75,000 per full-time role and 1,600 hours a year

* Model calculation for the “coordinate, search, retype” process with our calculator and mid-range assumptions, not a promise of results.

Everything at a glance

Every feature for projects.

Each feature comes with a sentence on what it does for you.

  • Projects from building blocks

    What you deliver often is stored as a building block with work packages and effort. You put new projects together from them.

  • One-off and support projects

    A project with a fixed end or ongoing support, both with the same tasks, time tracking and invoices.

  • Project phases

    Sales, requirements, delivery, quality, invoicing, done. Everyone can see where a project stands.

  • Versions

    Each version records what has changed since the last one. Leadtime writes the list of changes itself.

  • Project documentation

    All the project's pages in one place. You decide page by page which ones your client can see.

  • Journal

    Every change is logged, including whether it came from the app, the API or an agent.

Photo: A project lead stands at a standing desk, her hand on a thick stack of printed requirements, looking sceptically across the room.

Project lead at a web agency

“The client sent 40 pages of requirements. Who’s going to read that by Monday?”

The answer: the agent

The agent

The requirements document becomes a draft quote built from your building blocks.

Until now that meant a weekend of reading, gathering building blocks, estimating, and writing the quote and the specification. The agent reads the requirements, assembles the project from your building blocks and gives you the quote and the specification as a draft. You check what it had to estimate itself, and send it off.

The agent stays at hand afterwards: press ⌘K (Ctrl+K on Windows) to ask Leadtime things like which projects are running over budget or what is waiting for client feedback. The answer draws on your projects, tasks, times and planning, and shows only what you are already allowed to see.

From the client

EEElbwerk Energie AGPower · Gas · HeatPage 12 of 40

Requirements · New customer portal · Version 1.2

4. Functional requirements

    The agent

    Turn these requirements into a project, a quote and a specification.

    1. Read0 requirements found
    2. Match41 match your building blocks
    3. Estimate5 without a block, estimated and flagged
    4. QuoteDraft with prices from your catalogue, new items at your hourly rate
    5. Specificationevery requirement with implementation and acceptance criterion
    6. Youcheck the five flagged items and send it off

    To the client

    The quote and the specification appear here.

    Your logoEntwurf

    Quote

    Elbwerk Energie AG · Customer portal

    ItemEffortPrice
    Net total0 €
    Your logoVersion 1 · Draft

    Specification

    Elbwerk Energie AG · Customer portal · based on requirements v1.2

    2. Requirements and implementation

    The agent can only do what its role allows. You can look up every change it makes. You start it from the chat in Leadtime or from Claude, Codex and Cursor.

    More about agents

    Next step

    Let us show you on one
    of your projects.

    30 minutes, one real project from your day-to-day work. Ideally the one that has been almost finished for six weeks.