Tales from Fleep: Estimations and Commitments

I’m sure that most developers reading this post are painfully aware that when building something new from scratch, such as Fleep, estimating things can be quite hard. When you’re doing something for the first time you won’t have the backing experience behind you that would allow you to precisely determine how much time creating a new feature exactly takes.

Three weeks ago, before we launched the Fleep native apps and Android, our presence features in the new client were at stake. Regardless of the fact that making an estimation would have been close to impossible the feature was still required. Andres, our web wizard, committed to delivering it before the end of the week.

“Fine”, said Henn, “I’ll bring you 2 cases of beer and you can gladly go on your skiing vacation if you think you can get the presence features done by the end of the week”. And so a commitment was made between Henn and Andres.

Here’s a picture from yesterday with Andres and his two cases of beer earned fair and square. You can guess how this commitment played out. Well played, isn’t it?  :)


Running a start-up can be a tricky business, in the beginning all it takes a slice of free pizza and a few bottles of beer to keep the momentum going. The longer you do it, the higher the stakes, but challenging people still seems to work wonders!