Web Application Build Sprint

A two-week delivery window on a new web application, ending in something deployed, monitored, and handed over with its source code. What you are buying is a fixed allocation of senior engineering time inside those two weeks, worked top-down against a scope list agreed before the sprint starts. It is a fixed amount of work rather than a finished product, and most applications worth having take more than one sprint — we would rather say that here than in week two.

What you get

• A scope list agreed and written down in priority order before the sprint starts
• The sprint worked from the top of that list down, with progress visible to you as it goes
• A deployed environment with monitoring and backups configured, not a demonstration on a laptop
• The source code in a repository you own, with a README that lets somebody else carry on
• A handover session and a written account of what was built, what was not, and what a second sprint would cover

What this does not cover

• A finished application, and a commitment to a launch date. Two weeks buys what two weeks buys, taken from the top of the agreed list; whatever is still below the line at the end of the sprint is still below the line, and the next sprint is another purchase at the same price. If your list plainly does not look like one sprint’s worth, we say so before you buy and scope the work properly instead of selling a sprint that cannot land.
• Full-time attention for ten working days. The sprint is a two-week calendar window carrying a fixed allocation of senior time, and at this price that allocation is a defined number of days rather than all of them. We tell you its size in the scope summary before you buy, not after.
• Scope added mid-sprint. Anything new displaces something already on the list, in writing and with your agreement — it does not extend the two weeks.
• Design, content, and the decisions that have to come from you. A sprint waiting on an answer is still a sprint being spent.
• Maintenance after handover, and third-party costs such as hosting, domains and any paid service the application depends on. The Application Maintenance Retainer covers the first from the day it ships.

Who it fits

A small, clearly bounded application where two weeks of work genuinely is enough, or a deliberate first slice of something larger you intend to keep funding. If you already have an application and the problem is that it is broken rather than missing, a $380 Bug Fix Block is the right purchase and this is not; and if you are weighing a rebuild against repairing what you have, the $560 Annual Technical Debt Review answers that for less than this costs.