THE SPRINT BUILDER / FROM WHAT IF TO WHAT NEXT
Good work starts
with a clear plan.
A few details. The right people. A budget you can understand. Let’s put some shape around your idea.
What are we building?
One developer-day = one person’s full working day. Include build, testing and integration.
We budget whole sprints, with five working days per week.
Bring the right people.
Start with this example team. Change the roles, day rates and time each person spends on your project.
| Role / focus | People | £ / day | Time % | Project cost | Remove |
|---|---|---|---|---|---|
| £11,000.00 | |||||
| £2,600.00 | |||||
| £3,750.00 |
Rates are illustrative examples in GBP. Adjust them freely. A 50% allocation means half of each working day, averaged across the sprint.
A starting point, not a promise.
Only developer rows count towards engineering capacity. Product management and team leadership are costed separately. The estimate assumes the work can be shared between developers and that the team is available throughout. We’ll agree the scope and real rates together before work begins.
Hosting, cloud and AI usage, licences, third-party costs and VAT are excluded. The 15% allowance is a budget reserve; it doesn’t add planned sprint days.