You won't find this section as its own module in Leadtime, but you use the existing information from project components, efforts, and the document system to show clients a realistic timeline. This guide shows you how to present schedules pragmatically and ready for negotiation, without locking in too many details too early.
In our workshop example "Website EcoNomic Innovators," Web4Coach reaches the contract negotiation point. The client expects a concrete timeline. Leadtime provides all the necessary effort data for this, but we recommend communicating a plan with clear milestones to the client instead.
Project initiation
The timeline only starts with the order.
If the decision is delayed, planning moves back automatically.
This logic protects against unrealistic expectations.
Specification approval
Depends on scope, speed of feedback, and customer availability.
If info stops flowing, the project start gets noticeably delayed.
Implementation
The sum of all work packages defines the total effort.
Example from the workshop:
Total effort: 400 hours
One full-time developer: around 10 weeks
Planned buffer: 2 weeks
Total duration: about 3 months
Basis: Efforts from the configured project tree in Leadtime.
Testing phase
Internal and by the customer.
Recommended: at least 15% of implementation duration.
Includes functional, integration, and acceptance tests.
If the deadline is the priority: If sticking to the deadline is the customer's top priority, it's best to work backwards from that date when making the project plan. Think about what steps need to be done by when. If you need extra resources, either the price has to go up—or you'll have to cut the scope for go-live.
If the budget is the priority: If the customer says the budget is the top priority, your plan should focus fully on efficiency. Kick off the project when you've got enough capacity to pull it off with minimal effort.
If quality is the priority: If there's a realistic budget and no tough deadline, make sure to build in generous buffers in your schedule—this way you can guarantee quality and keep stress to a minimum.
For use as a conversation guide in the workshop:
Agree in writing that the schedule will shift if feedback comes in late.
Let them know that quality and meeting deadlines can sometimes clash.
Use versioning in Leadtime to transparently show offer changes.
Here’s where you’ll find part 12 of the workshop:
Work packages, tasks and how to get it done (Workshop part 12)
