We used FinalBuilder to automate a highly specialised XML workflow. Formerly, this workflow would have required an enormous amount of manual labour. The problem with manual labour, as everyone knows, is that it is highly error prone. The game designers on our team would regularly "bork" the XML files by doing too many manual edits under pressure. We could not change the XML schema due to it being consumed by 3rd party tools, so we were forced to work with this less than ideal situation until we hit upon the idea to use Final Builder to automate everything. A few tweaks, some research into the FinalBuilder documentation, and viola, a highly functioning tool! We could now perform the same task flawlessly in seconds, that formerly took up to 30 minutes and was highly error prone. No more anxious game designers, and the programmers could focus on more productive work. We also used FinalBuilder to automate our build pipeline processes later on, as it had already proved itself quite nicely during our testing with the XML automation. The main comment I would make is that the FinalBuilder interface is very intuitive and very well documented, with plenty of tips and examples that make putting together complex workflows like XML schema rewrites a breeze compared to using command-line utilities or other build tools. The wonderful "block by block" flow tools allow even non-programmers to easily change the workflows and designs once a more experienced developer has written the initial workflow. Review collected by and hosted on G2.com.

I think Final Builder's UX design could be updated a little bit more for 2020 with a cleaner design. Review collected by and hosted on G2.com.