That's true of Debian, too, though. We can disagree on which project does a better job at it, but they're both full systems, compatibility tested and with long-term support for stable releases.
Basically, Debian integrates everything, but only loosely, while FreeBSD has tighter integration, but only of a smaller subset.
The merits of each method are up for debate, however they are pretty distinct.
However, once you start adding some additional packages, Debian tends to do the integration-testing more pervasively across the entire userland, "Debianizing" packages so that they all store things in the standard locations, are started/stopped using the same methods, follow the same configuration policies, etc. Once you get out into ports, the BSDs tend to give you more of an as-is set of 3rd-party packages, and are pretty lax about integration testing.
Although I think the effort is misguided, they are working pretty hard on that one. There is some considerable effort going on to get pcc as the default compiler for the BSDs, specifically so that they don't have to rely on another upstream (and so they don't have to use a GPL'd compiler).
However, once you start considering obviously 3rd party packages, then not even windows could be considered a single project piece of software.
The most prominent in recent time being their absolutely braindead patching of OpenSSL which dramatically reduced the entropy in key generation, which would have never made it through the peer review process of the upstream... Debian likes to think that they are the upstream of the projects they use, but unlike the BSDs they really are not.
To me the biggest advantage is that BSD is fully integrated (it's a full system, not just a kernel) and there are compatibility guarantees. For example a binary built for 8.0 will stay compatible with the whole 8.x series.