Visual summary of operating lessons from Anil Varanasi.

Lessons from Anil Varanasi

Anil Varanasi is the CEO of Meter, a company he co-founded with his brother Sunil to deliver business internet infrastructure as a vertically integrated utility rather than a collection of disparate parts. This profile organizes his arguments on long-term company building, the shift toward autonomous networks, and why enterprise IT requires a consumer-grade user experience.

Part 1: The Network-as-a-Service Model

  1. On redefining networking: "We started Meter to build a different kind of networking company, one that’s seamless, integrated, and built to scale." — Source: [Lumen]
  2. On the legacy IT market: "The traditional approach of buying hardware, installing it, and paying for ongoing maintenance separately is broken, and it requires a complete overhaul to fix." — Source: [CRN]
  3. On capital expenditure: "There are four big costs in networking: Upfront hardware, installation, ongoing maintenance, and then doing it all again when you upgrade. With us, those risks sit entirely with Meter." — Source: [ChannelWeb]
  4. On business models: "We don’t sell hardware at all, and that’s never happened in networking." — Source: [ChannelWeb]
  5. On removing friction: "Together, we’re removing friction and enabling IT teams to focus on outcomes, not infrastructure." — Source: [Meter Newsroom]
  6. On enterprise complexity: "Modern businesses should consume their local area networks the same way they consume electricity or water: as a reliable utility rather than a complex engineering project." — Source: [The Generalist]
  7. On shifting risk: "By taking on the burden of hardware upgrades and maintenance, the provider aligns its incentives directly with the reliability of the customer's network." — Source: [First Round Review]
  8. On market stagnation: "The lack of business model innovation in networking over the past few decades created an opening for a service-first approach that prioritizes the end user." — Source: [Packet Pushers]
  9. On instant procurement: "Tools like Meter Connect allow businesses to get quotes and provision internet services instantly, bringing consumer-grade speed to enterprise IT." — Source: [Meter Newsroom]
  10. On long-term partnerships: "Delivering network as a service means building a relationship with a customer that lasts for the entire lifecycle of their building, not just the lifespan of a router." — Source: [First Round Review]

Part 2: Vertical Integration

  1. On building the full stack: "Everybody that’s large in networking does hardware differently than how we would do it, does software differently than how we would do it, does delivery differently than how we would do it." — Source: [Network World]
  2. On customer empathy: "So we ourselves as customers, wanted to build something that we would use, and we would be delighted to use." — Source: [Network World]
  3. On unified systems: "We’re entirely vertically integrated, so it’s much easier for IT teams." — Source: [SiliconANGLE]
  4. On multi-vendor sprawl: "Enterprise networks are often stitched together from different vendors for routing, switching, and wireless, which multiplies points of failure and complicates troubleshooting." — Source: [theCUBE]
  5. On controlling the experience: "To actually simplify the customer experience, you have to own the hardware, the firmware, the software, and the operations layer simultaneously." — Source: [The Generalist]
  6. On hardware as a foundation: "We started about a decade ago, first focused on building better hardware, and we believe with that hardware we can build better software." — Source: [SiliconANGLE]
  7. On packet processing: "Controlling how packets move at the hardware level allows for the creation of superior software interfaces for network design and management." — Source: [SiliconANGLE]
  8. On bypassing legacy constraints: "Using commodity hardware forces a company to inherit the limitations of legacy vendors; building from scratch is the only way to break that dependency." — Source: [theCUBE]
  9. On monopolistic markets: "Operating in an industry dominated by a few massive incumbents requires a contrarian approach to product development, starting from the silicon up." — Source: [First Round Review]

Part 3: The Multi-Decade Time Horizon

  1. On long-term planning: "Building foundational infrastructure requires thinking in 25-year horizons rather than optimizing for short-term valuations or quick exits." — Source: [First Round Review]
  2. On heads-down R&D: "Spending over four years in stealth mode developing the core technology was necessary to ensure the product was ready for enterprise scale on day one." — Source: [First Round Review]
  3. On patience in company building: "You cannot rush the development of vertically integrated hardware and software; the iteration cycles are physically longer and demand sustained commitment." — Source: [The Aarthi and Sriram Show]
  4. On avoiding exit-driven cultures: "A culture that is constantly looking for an acquisition or an IPO makes different, usually worse, technical decisions than one focused on long-term endurance." — Source: [First Round Review]
  5. On contrarian management: "Traditional goal frameworks and quarterly planning cycles often break down when applied to deep technical infrastructure projects that take years to yield results." — Source: [First Round Review]
  6. On staying under the radar: "Choosing to remain quiet during the early years allowed the engineering team to focus entirely on product quality without the distraction of managing public hype." — Source: [Forbes]
  7. On compounding advantages: "When you build the hardware and the software together, the technological moat compounds slowly over years, but eventually becomes nearly impossible for competitors to replicate." — Source: [The Generalist]
  8. On enduring impact: "True innovation in networking is measured by how well the system operates a decade after it was installed, not how well it demos on day one." — Source: [First Round Review]
  9. On defining success: "Success is having customers who forget what network vendor they use because the infrastructure simply never goes down." — Source: [Forbes]
  10. On the necessity of struggle: "Enduring a thousand bad days is the baseline expectation when trying to displace entrenched monopolies in the enterprise hardware space." — Source: [First Round Review]

Part 4: Autonomous Networks and Automation

  1. On the talent shortage: "With roughly thirty percent of network engineers expected to retire by 2030, the industry will not have enough human capital to manually manage growing network complexity." — Source: [The Generalist]
  2. On self-maintaining systems: "The future of networking relies on autonomous systems that can configure, heal, and optimize themselves without waiting for a human operator to type commands." — Source: [The Generalist]
  3. On reactive versus proactive: "Today's networks tell you after something has broken; tomorrow's autonomous networks will reroute traffic and adjust settings before the user ever notices a drop in performance." — Source: [Packet Pushers]
  4. On AI in infrastructure: "Artificial intelligence in networking goes beyond chat interfaces; it involves using large language models to translate human intent directly into complex routing configurations." — Source: [theCUBE]
  5. On generative UI: "By utilizing generative user interfaces, network management tools can adapt their dashboards dynamically based on the specific incident an IT admin is currently investigating." — Source: [The Aarthi and Sriram Show]
  6. On replacing the CLI: "The traditional command-line interface is powerful but brittle; natural language commands allow for safer, more accessible network management." — Source: [theCUBE]
  7. On automated troubleshooting: "Autonomous systems excel at correlating thousands of localized logs to find the single root cause of an outage, a task that takes humans hours to perform manually." — Source: [Packet Pushers]
  8. On the evolution of NaaS: "Network-as-a-Service is only the first step; the end goal is an entirely self-driving network that scales capacity up and down automatically based on facility usage." — Source: [The Generalist]
  9. On hardware telemetry: "True automation requires specialized hardware that generates high-fidelity telemetry data, as off-the-shelf components often lack the required visibility for AI models to act upon." — Source: [theCUBE]

Part 5: Rethinking Hardware and Software

  1. On soft software: "Software should be soft, meaning it must remain flexible, forgiving, and easily adaptable to the changing needs of the user, rather than rigid and punitive." — Source: [The Aarthi and Sriram Show]
  2. On hardware rigidity: "The physical constraints of hardware development enforce a discipline that makes the eventual software layer much more reliable." — Source: [SiliconANGLE]
  3. On silicon integration: "Controlling the fundamental silicon allows for outsized performance gains that are impossible when mixing software with third-party hardware." — Source: [First Round Review]
  4. On supply chain ownership: "Designing your own hardware is difficult, but it protects the company and its customers from the volatility and feature deprecation common in third-party supply chains." — Source: [Forbes]
  5. On aesthetic engineering: "Industrial design matters in enterprise hardware; beautiful, well-engineered physical devices reflect the care and precision of the software running inside them." — Source: [The Aarthi and Sriram Show]
  6. On edge computing: "Moving processing power directly to the access points and switches reduces latency and allows the network to make split-second optimization decisions locally." — Source: [Packet Pushers]
  7. On open standards: "While the stack is vertically integrated, it must still converse flawlessly with open internet protocols and existing enterprise tools to be useful in the real world." — Source: [Network World]
  8. On iterative hardware: "By managing the hardware as a service, the company can deploy minor physical iterations to new customers continuously, rather than waiting for massive, multi-year product cycles." — Source: [ChannelWeb]
  9. On invisible tech: "The best network hardware is the hardware the customer forgets is installed in the ceiling; it simply works without requiring restarts or physical maintenance." — Source: [Forbes]

Part 6: Talent and Hiring

  1. On identifying talent early: "Finding exceptional people often means looking for intensity and curiosity in early-career engineers before their resumes look impressive to traditional recruiters." — Source: [The Aarthi and Sriram Show]
  2. On non-traditional backgrounds: "A candidate's specific background in networking is frequently less important than their fundamental capacity to learn complex systems from first principles." — Source: [The Aarthi and Sriram Show]
  3. On the value of persistence: "When building hardware, you need engineers who are comfortable being stuck on a problem for weeks without losing their enthusiasm for the mission." — Source: [First Round Review]
  4. On founders and team building: "The primary job of a founder in the early years is to convince a small group of highly talented people to dedicate a decade of their lives to a very difficult problem." — Source: [The Aarthi and Sriram Show]
  5. On assessing curiosity: "The best way to evaluate a candidate is to turn the tables and see the quality, depth, and specificity of the questions they ask you about the business." — Source: [The Aarthi and Sriram Show]
  6. On cross-disciplinary thinking: "The hardest engineering problems are solved at the boundaries between disciplines, which requires software engineers who understand hardware, and hardware engineers who can write code." — Source: [SiliconANGLE]
  7. On managing burnout: "When working on a 25-year timeline, pacing and maintaining the team's mental endurance is far more critical than hitting artificial quarterly deadlines." — Source: [First Round Review]
  8. On shared obsession: "A strong company culture is built when every early employee shares an unreasonable obsession with the details of the product experience." — Source: [Forbes]
  9. On global perspectives: "Experiences working internationally, such as in China, provide valuable lessons on manufacturing speed and hardware supply chain logistics that benefit infrastructure startups." — Source: [The Aarthi and Sriram Show]

Part 7: Customer Experience and Simplicity

  1. On IT workloads: "IT teams are consistently overworked and under-resourced; any tool that does not definitively remove tasks from their plate will ultimately be rejected." — Source: [Meter Newsroom]
  2. On consumer-grade enterprise apps: "Enterprise software should match the intuitive design and responsiveness of the best consumer applications, eliminating the need for massive instruction manuals." — Source: [The Aarthi and Sriram Show]
  3. On the procurement nightmare: "The process of buying enterprise internet and networking gear is intentionally convoluted; simplifying procurement to a few clicks is a massive competitive advantage." — Source: [Meter Newsroom]
  4. On natural language commands: "Integrating AI-driven command tools allows administrators to query their network state in plain English, drastically lowering the barrier to entry." — Source: [theCUBE]
  5. On installation friction: "By handling the physical installation and cabling themselves, a provider guarantees that the physical layer meets the requirements of the software layer." — Source: [ChannelWeb]
  6. On transparent pricing: "Customers in the infrastructure space are tired of hidden licensing fees and surprise maintenance costs; a flat, predictable pricing model builds long-term trust." — Source: [CRN]
  7. On proactive support: "The customer support experience is fundamentally changed when the vendor receives automated alerts and begins fixing a problem before the customer's employees even notice an issue." — Source: [Network World]
  8. On real estate timelines: "Internet infrastructure must map to the lifecycle of commercial real estate; if a company opens a new warehouse, the network should be the easiest part of the build-out." — Source: [Forbes]
  9. On scaling operations: "A true managed service model proves its worth when a customer decides to open ten new branch offices and requires zero additional IT headcount to manage the expansion." — Source: [The Generalist]

Part 8: Building a Company During Crises

  1. On surviving macro shocks: "The COVID-19 pandemic exposed the fragility of traditional office networking and forced a complete re-evaluation of how distributed teams connect to central resources." — Source: [First Round Review]
  2. On supply chain resilience: "Building hardware during a global supply chain crisis teaches a company how to engineer flexibility into its product designs to accommodate alternate components." — Source: [First Round Review]
  3. On industry transitions: "Massive industry shifts, such as the rollout of custom silicon by major tech companies, serve as proof points that owning the hardware stack is the ultimate strategy for performance." — Source: [First Round Review]
  4. On strategic partnerships: "Aligning with legacy telecom giants allows a startup to pair modern networking stacks with massive, established fiber footprints." — Source: [CRN]
  5. On channel expansion: "We anticipate it will be the biggest channel we have over the next few years. We're already seeing a tremendous amount of progress with deals." — Source: [CRN]
  6. On co-founding with family: "Building a company with a sibling requires a profound level of implicit trust, allowing for faster decision-making and a shared, unbreakable commitment to the long-term vision." — Source: [First Round Review]
  7. On weathering doubt: "In the early years, the idea of replacing established networking hardware companies with a full-stack subscription service was met with immense skepticism from traditional investors." — Source: [Forbes]
  8. On focus amidst chaos: "When external conditions are highly volatile, the safest strategy is to ignore market noise and focus entirely on the quality of the product being delivered to the end user." — Source: [First Round Review]
  9. On continuous learning: "A founder's ability to navigate crises is directly tied to their willingness to aggressively study adjacent industries, from manufacturing logistics to cinematic storytelling, to find novel solutions." — Source: [The Aarthi and Sriram Show]
  10. On inevitable progress: "Despite the hurdles of legacy incumbents and supply chain shocks, the transition of enterprise networking into a fully managed, autonomous utility is an inevitable technological shift." — Source: [The Generalist]