Skip to content

What the network is

For users: the Venture Network is a place where people who want to start ventures find each other. Founders, operators, investors, idea people, and business owners, drawn from Georgia Tech and the Atlanta ecosystem first.

Georgia Tech has every ingredient of a strong venture ecosystem, but the ingredients sit disconnected early in the process. Ideas stay inside labs and classes, technical founders lack business partners, and operator-minded students lack technical cofounders. Before this product, the network ran on Excel trackers, a prospectus PDF, posters, and a set of Claude skills. This product stitches the fragmented network together into one place.

You reach the network through:

  • The web app, at venturenetwork.ai.
  • The vn CLI, for a terminal or a script.
  • An MCP server, for an AI client like Claude Code, claude.ai, or Cursor.

All three sit on top of the same NestJS API and the same sign-in. Whichever surface you use, you are the same member with the same organizations and the same permissions. A profile edit from the CLI shows up on the web immediately, and an MCP client sees exactly what you would see signed in yourself. See The CLI and MCP to set those up.

Identity is global, organizations are communities

Section titled “Identity is global, organizations are communities”

Your account is not tied to any one group. You build one profile and say what you are looking for, and you join organizations as communities inside the network. The GT Venture Network is the first one, and every early member lands there. Read Organizations for how joining, roles, and invitations work.

The network is in its early phase. Today a member can:

  • Build a profile that says who they are, what they do, and what they are looking for. See Your profile.
  • Join and browse organizations. See Organizations.
  • Search the member directory by role, skill, and what people are looking for. See The directory.

Later phases add events (an org or an individual can publish one), posts (asks like “cofounder wanted” or “seeking investors”), and intro requests (ask to be introduced to another member, with email carrying the notification). Each of those ships to the web app, the CLI, and MCP at the same time, so the three surfaces never drift apart.