Patryk Smakosz for Colibrity

Work record and
current balance

What has been delivered since April, what has been settled, and what is still open. This is a record rather than an invoice. Every hour on it traces to a commit in Colibrity's own GitHub organisation, a time-tracker entry, or both.

What that works out at

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 charged

Extracted 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

Hours per month, by project. May and June are the two fixed-price builds running alongside each other; the tail from late July is support and the front-end standard.

Vocalcom

estimate

Scoped 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.