Simplified rebuild of a web application

Overview

A client asked for a simplified version of an existing web application: the core functionality, a straightforward interface, basic user registration, and nothing else. The brief was estimated at one month. The engagement ran for seventeen.

What actually happened

Nothing went wrong. The client’s own posting said the budget was flexible and that a successful first delivery “may lead to future collaborations and further feature expansions”. That is exactly what happened: the simplified version worked, and the work kept extending from there.

Why it is here

This is the most honest example I have of the gap between a brief and an engagement. “A very simplified version” is a real starting point and a poor predictor of where a project ends up. The useful skill is not estimating the first month accurately, it is building the first month so that month seventeen is still possible: keeping the structure open, not hard-coding assumptions that the original scope made look safe, and staying willing to say what a new request will actually cost.

Long engagements are where most of my work happens, and they rarely start out looking long.