How the two lines moved apart
Value delivered and value charged, both counted in euro at the same an hour, month by month.
What each project worked out at, per hour
Each fixed price divided by the hours it actually took, against the rate agreed for support work. Shown because it is the clearest single measure of the gap.
What was delivered
Three sites. Two are finished, live and paid for; the third is finished and still open. Measured results, with the date each measurement was taken.
The toolkit you also got
not chargedExtracted from your three sites and given back to all of them. It is the reason the Vocalcom estimate below is 160 hours rather than the 218 DriveBerry took.
What it is
When the work happened
Vocalcom
estimateScoped against the client brief of 14 August: four regions, four languages, region-aware blocks, all content new. The architecture is settled and two spikes have passed. There are three ways to price it, and they are on their own page so this one stays a record rather than a pitch.
How the hours were counted
Two records, reconciled day by day. Where they disagree, the more conservative figure is the one used.
- The time tracker's total is the figure of record: across 82 days.
- A day split across two projects is divided by that day's share of work, not assigned whole to one of them.
- Research, testing and measurement runs, deploys, calls and written reports are only counted where they left a record. A good deal of the work does not appear in the commit counts at all.