Network Right

Network Right is a San Francisco-based fractional IT and compliance provider for startups and growth companies. It positions itself as an embedded, human-led IT partner rather than a traditional rigid MSP.

Snapshot

  • Category: fractional IT, managed IT, cybersecurity, compliance, service desk, AI readiness.
  • Public positioning: “your fractional IT team for start-ups” and an in-house-feeling IT team that grows with the customer.
  • Leadership contact: Anthony Garcia, Co-Founder and CTO.
  • Public service surface: service desk, onboarding/offboarding, asset management, SaaS management, network support, IT strategy, cybersecurity, vCISO/compliance guidance, AI readiness, office/network buildouts.
  • Public metrics: 100K+ tickets handled by humans, 99% SLA adherence, 4.95/5 satisfaction/NPS messaging, 5+ year average customer retention on the homepage.
  • Pricing signals: startup plan from 170/user/month, enterprise custom.

Operating Model

Network Right’s model is to act as the customer’s internal IT and compliance function until the customer has enough complexity to hire internal IT leadership. It aims to help startups get from early headcount into the hundreds with lean, well-structured IT systems.

The company rejects the classic MSP pattern of forcing all customers into the provider’s standardized tool stack. Instead, it works with customer-owned startup stacks and integrates around the customer’s preferred tools, such as Google Workspace, Slack, Notion, Zoom, Kandji, CrowdStrike, SentinelOne, 1Password, and adjacent SaaS/security systems.

What Makes Them Strategically Important

Network Right is a useful operator lens for Init Intelligence because it exposes the gap between single-tenant AI ITSM products and the needs of multi-customer fractional IT providers.

The meeting-derived thesis is that modern startup-oriented MSPs need an operating system that is:

  • Multi-tenant by default.
  • Strict about customer data isolation.
  • Flexible across customer-owned SaaS, identity, endpoint, and documentation stacks.
  • Useful to human technicians, not just end users.
  • Able to compress context gathering, triage, routing, and routine execution without breaking the human-led service promise.

Bottlenecks

  • There is no clear “Serval for modern MSPs” that independent fractional IT providers can buy without joining a portfolio or being acquired.
  • Existing PSA/RMM tools such as legacy MSP platforms are too rigid, standardized, and Microsoft/Windows-heavy for many startup customer environments.
  • Jira is workable but not purpose-built as a multi-tenant fractional IT service delivery backend.
  • AI service-desk products tested by Network Right did not fit the multi-tenant provider pattern well enough, especially when they assumed Okta-centric or single-customer deployment.
  • The unacceptable failure mode is cross-customer knowledge bleed: an AI system must never retrieve another customer’s documentation or secrets while answering a request.

Implications For Init Intelligence

  • Network Right is a potential design partner for MSP AI enablement, especially if Init Intelligence explores a multi-tenant AI operating layer for fractional IT providers.
  • The strongest wedge may be technician leverage and tenant-safe context, not pure end-user ticket deflection.
  • Their workflow suggests a product surface around per-customer LLM/context containers, connector management, access matrices, runbook freshness, Slack/Jira intake, and human escalation.
  • A deeper relationship could be strategically valuable, but the near-term path should be framed as learning, design partnership, and workflow leverage rather than acquisition. ^[inferred]

Open Questions

  • Which exact ticket categories consume the most technician time?
  • What does their Jira schema look like across customers, SLAs, request types, and escalations?
  • How do they currently isolate customer documentation and credentials?
  • Which tools are common enough across their customers to justify first-class integrations?
  • Would they buy an MSP OS, co-build it, resell it, or prefer a services/software partnership? ^[inferred]