Ten years after selling Periscope to Twitter for $100 million, Kayvon Beykpour is back with a $40 million funding round for Macroscope, a startup that promises to solve the problem that plagued him at Twitter: understanding what developers are actually working on. The funding from GV, Lightspeed, and Thrive Capital signals serious investor confidence in tackling enterprise software development visibility.
The most successful startup founders often build their next company to solve problems from their previous gig. For Kayvon Beykpour, that problem was crystal clear during his seven years at Twitter after selling Periscope for a reported $100 million.
"So much of my job as the head of product at Twitter was just understanding what the hell was happening," Beykpour told CNBC in an interview. "You have all these engineers at the company and all these very important things that we need to get done with absolute opaqueness around, like, What progress did we make? What are all these people working on?"
That frustration has now become Macroscope, which just closed a $40 million Series A from heavyweight investors including Google's GV, Lightspeed Venture Partners, and Thrive Capital. The funding round puts serious financial muscle behind a deceptively simple premise: most companies have no idea what their developers are actually doing.
While Twitter shuttered Periscope in 2021 and pivoted to Spaces under Elon Musk's ownership, Beykpour was quietly building the antithesis of his consumer-focused livestreaming app. Macroscope goes directly after enterprise customers with a platform that integrates Microsoft's GitHub repositories, project management tools from Atlassian, and AI models from Anthropic, Google, and OpenAI.
The technical approach sets Macroscope apart from existing code review tools like GitHub Copilot or Cursor's BugBot. According to Beykpour, internal testing shows Macroscope outperforms competitors at identifying known software bugs - a claim that will face scrutiny as the platform scales to enterprise deployments.
But the real innovation isn't in code analysis. It's in solving what Beykpour calls the "meeting problem" - the endless status updates that drain engineering productivity. "They're solving it with meetings," he said of current management approaches. "If we cannot surpass the bar of, people call a meeting to ask a bunch of engineers what's happening, we've failed miserably."
