This is a very rare situation. If you link to GPL code, then your code has to, at least, grant GPL rights to your users. However, just using GPL code to build your code is not. I use Emacs to write code that is either interpreted by Python or compiled by GCC and nothing I write needs to be licensed as GPL. A lot of OSX is compiled with GCC and many programs on the OSX install DVD are BSD licensed.
Unless you link to a GPL-only library, you are probably safe.
As for other licenses, there are licenses like BSD and Apache. You can pick code licensed under them and use it as part of proprietary code you release. OTOH, your competitor may use the BSD-ish code you release as parts of your competing product.
What it boils down to is that GPL by itself does not allow reuse without similar disclosures of code, etc. and only a different license (like LGPL) or a documented exception to the license (like in GCC) will change that.
[1] http://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html
[2] http://www.gnu.org/s/libc/manual/html_mono/libc.html#Copying
I think you discovered the answer I needed. I'm now confident that the GPL won't be an issue for the time being since most of the code will be staying on our servers. In the future, other licenses may be worth my time to investigate for new products.
For example, basing a business on GPL as you stated may be a problem because it would compel everything in the stack (including something unique built on top of established code) to be opened up...so it would be hard to build something truly competitive without showing all your cards to your competitors. Other open source licenses such as MIT's have fewer restrictions and amount to preserving copyrights and the right to reuse but without any warranties.
Of course you can only build on code that is "compatible" with the license you choose. There may be solutions that are only available under GPL licenses, in which case you have to decide to live with those restrictions or build your own.