You aren't dumb, but you don't have all the facts, and what seems SHOULD make sense, often doesn't.
Drivers are tricky, since they work below the user level of the OS, and oftne have strange installation proceedures that require that they be loaded before other things.
You certainly could add the driver pack files to the image, and then use the OS tools to scan for and load drivers, but some of them might require a reboot before working OK. Now we have a catch 22, since a PE is read only, and not persistent.
Some of them can be managed OK (i.e. plug-n-play) and some you can pre-load the data into the PE, but for others you need to have the actual hardware present in order to get the values you need in order to actually add them to the image.
So, it's not that simple...BUT, as we pointed out, do a bit more digging around, and...
A fairly quick google of "winbuilder load driver" turned up the following links.
This one is more geared to vista, and quite old, but gives you an idea of what goes on in trying to load a driver.
On the other hand, this link leads to "al.jo" site (he did quite a lot with winbuilder 82 and made pre-packaged builds that are fairly complete and a good starting point). Just search for drivers inside the posting - see reply #2)
This leads (as mentioned to al.jo's site) to a posting that talks more about drivers in context of win7PE, and from there you can link to the Win7PE or even Win8PE project he made which has a specific drivers section and some scripts to add specific drivers
and we even had some threads HERE on reboot.pro...http://reboot.pro/to...s-to-win7pe-se/
Again, often it is the case that you don't know if what you find on these results is worth reading - but the above, especially the ones from al.jo should get you closer to what your are asking for. At least for thigns like networks and disk drives, etc.