Disagree. Fogbugz gives a greater and greater savings per employee as your employee count goes up. Here's a Perl script I wrote to visualize the idea. Feed the

Disagree. Fogbugz gives a greater and greater savings per employee as your employee count goes up. Here's a Perl script I wrote to visualize the idea. Feed the output into gnuplot and you'll see what I mean. use warnings; use strict; use 5.010; use POSIX qw(ceil floor); # Let's start at 100 employees and walk up by 25. for(my $count = 100; $count < 1000; $count+=25) { # Flat rate for fogbugz/kiln. my $fb = 15000 / $count; # ceil(number of users / 20) * blocks of 20-seats to buy. my $gh = (ceil($count / 20) * 5000) / $count; say "$count $fb $gh"; } This asymptotically trends towards about $20/employee for Fogbugz; GitHub hangs around $250 per. At no point in these calculations is GitHub cheaper per than FogBugz. Now, in the < 100 employee range where the different FogCreek pricings apply, I am not sure who wins, I'd guess it trades off back and forth depending on the # of employees. edit: awkward formatting. Also, if I've biffed my formulas, let me know and I'll update it! edit2: forgot to comparatively do analysis