Ive used it before, but instead of having to rebuild fresh each time i have to rebuild a system, I build my system back from an image through a drive to drive clone process using Macrium Reflect. If you are not setting off to the side a spare hard drive with a clean build to be able to revert back from a image, then ninite works good. I havent used it much though because I install spare hard drives in my desktop computers to keep as a quick system recovery.
I got a great deal on 160GB SATA HDD's for $12 each through newegg and most drives contain less than 50GB data. These extra drives are mounted in the case and left disconnected until needed. I build the system on these smaller drives for OS and all necessary software. Then when its built to a point that I am satisfied with it becoming the recovery state for the system for the future, I then clone this 160GB drive to say a 500GB drive. Then when clone is complete resize the C: partition to take up all remaining space to be used for C:. Disconnect power and SATA communication cable from the 160GB drive and run on the 500GB drive. When the 500GB drive is in need of a wipe and make clean state, I just attach both drives and run Macrium Reflect and clone the 160GB stomping on top of the 500GB drives data and resize the C: partition after first getting any important data off of the 500GB drive.
Years ago back during Windows 2000 Professional and Windows XP, I use to use Ghost 2003 and burn a DVD-R Ghost Image after the build is complete for the OS and Software and place it into a jewel case and then place that in a ziplock bag and lay it in the bottom of the computer tower making my own system recovery media set for my own builds. So that I never had to go through the boring process of feeding software to a tower and updates.
Both required me to still perform updates to software and OS as for the recovery state was locked in time and anything from that date forward for software that was out of date would need to be updated. I could always also turn on the 160GB drive and run it through updates and then disconnect it so that the next time its used to clone the drive it is that much more up to date requiring lesser updates.
For my large game library of steam games I made a copy of the games on my 4TB external and so I dont have to redownload large games over again. I just tell steam to install the game, and then kill my network connection, and manually copy the game contents to the target directory, then enable the network connection in which it picks up where it left off with install in which it detects that the game is there, it then goes to 100% complete for the game and I am able to run the games. Havent had to do this in about 2 years but last time I did this it worked for steam.