ExecNet Origins

Founding and Early Vision

ExecNet, officially known as The Executive Network, was founded in 1986 by Andy Keeves. Initially conceived as a platform to facilitate information exchange between LAN professionals, Keeves drew on his extensive computing experience dating back to the 1970s, spanning mainframes, minicomputers, and early microcomputers.
“Although we were running on a Novell NetWare server even at that time, our nodes were 8088 machines,” Keeves recalled. “Everyone currently involved with ExecNet had been involved in the computer field either on the hardware or software side for well over a decade. As a Novell Gold system integrator, our focus was on local and wide area networking. The system was nothing more than an extension of this in the late ’80s.”
ExecNet was designed as a professional, business-oriented BBS, distinguishing itself from hobbyist systems by treating its callers as customers rather than guests. “After all, as a business, we must cater to our customers. And yes, our callers are indeed our customers,” Keeves emphasized.

Technical Foundations and Innovation

ExecNet initially ran on Novell NetWare servers using 8088 and 80286-based systems. This early architecture prioritized stability, performance, and Multi-node access across Local Area Networks, allowing IT professionals to collaborate efficiently in a shared environment.
By leveraging PCBoard software, ExecNet became an alpha site for new features and extensions, frequently developing third-party add-ons that expanded system functionality beyond standard BBS implementations.
“We began incorporating some of our own ideas into the system by developing third-party add-on software, and over the first few years, ExecNet had become known as the system where you were likely to find new features,” Keeves said.
As system demands increased, ExecNet transitioned from DOS-based nodes to OS/2, allowing multiple BBS nodes to operate concurrently on a single machine rather than requiring separate DOS systems per Node. This migration significantly improved scalability, stability, and resource utilization while supporting ExecNet’s expanding user base.

ExecNet introduced several technical advancements that were uncommon for bulletin board systems of the era:

  • Removal of restrictive daily session limits common on most BBS platforms
  • Support for hundreds of thousands of stored messages and large-scale file libraries
  • Multi-node, conference-style message areas designed for professional collaboration
  • Early Internet connectivity including Telnet, FTP, Gopher, and full SLIP and PPP access
  • Progressive migration from DOS to OS/2 to support higher Node density and reliability

Commercial Evolution

Originally serving LAN and networking professionals, ExecNet gradually evolved into a commercial service. Subscriber access helped offset hardware, telecommunications, and operational costs while enabling continued expansion of system capabilities.
At its peak, ExecNet operated multiple servers, including Novell and Unix-based systems, supported by more than 15 gigabytes of storage and over 40 active nodes. This infrastructure allowed ExecNet to maintain performance and reliability while introducing business-focused services and advanced networking features.
The system expanded to include full Internet access, multiple T1 circuits, business and technical news resources, and peer collaboration tools, creating a hybrid environment that bridged traditional BBS functionality with emerging Internet technologies.

Philosophy and Community

ExecNet’s success was driven less by any single technical feature and more by responsiveness to its user community. Keeves emphasized that most enhancements were implemented directly from user feedback and real-world operational needs.
“Most of the features one finds on the system are a by-product of listening to those who use the system and attempting to implement their ideas and wish lists,” Keeves explained.
Voice support, timely technical assistance, and close interaction with members remained central to ExecNet’s operation. The system fostered an environment where IT professionals could exchange knowledge, troubleshoot complex networking issues, and access a highly curated software archive.

Legacy and Historical Significance

ExecNet represents a significant milestone in the evolution of professional online networking. By combining enterprise-grade infrastructure, user-driven development, and early Internet integration, it helped define what a serious, business-oriented online community could be.

Its legacy includes:

  • Early adoption and advanced use of PCBoard and Novell NetWare technologies
  • Migration from DOS to OS/2 to support higher-density Multi-node operation
  • Unrestricted session access and large-scale file distribution
  • Early convergence of BBS systems with Internet services
  • Creation of a professional collaboration environment for IT specialists and LAN administrators

Notable Recognition and Media Coverage

ExecNet’s software library and file archive earned the Dvorak Telecommunications Award for Excellence and received coverage in the following publications:
ExecNet also received television coverage from CBS, NBC, ABC, and CNN, further establishing its reputation as a trusted professional resource.

The Technology Behind ExecNet