The primary reason for calculating software size is for an accurate cost estimate to build custom software. The tricky part is that there is no standard measurement. A few options are: Lines of Code (LOC) which, as you might be able to guess, is where you count the lines of source code. You estimate this by comparing it with a similar application. Or you can count processes in a data flow diagram (DFD). Maybe more accurate but it’s a lot of extra work to calculate. In fact, there are many complex ways to calculate software size – most of them boil down to an educated guess. Instead, we break software down into its features (we worked out that around 500 features make up 80% of all apps – and we coded these already in a library). We’ve also mapped all the possible relationships between features. So when you add an extra one, we know all the other features it’ll interact with – to make your app more complex. This means when we calculate your price and timeline; it isn’t a guess. And if you need to add extra functions, it isn’t a question of estimating how many lines of extra code it’ll need, we can see how long those changes will take and give you an accurate estimate – before you even decide to make the change!