Mesmer Gives CTOs X-Ray Vision Into Their Engineering Org

The Macro: Engineering Visibility Is a Solved Problem That Nobody Has Solved

Every engineering leader I have ever talked to has the same complaint. They do not know what is actually happening in their codebase without sitting through meetings, reading standups, or chasing people on Slack. The irony is thick: the people building the most sophisticated software in the world are tracking their own work with status updates typed into text boxes.

The engineering analytics space has been around for a while. LinearB, Jellyfish, Haystack, Pluralsight Flow, they have all taken a run at measuring developer productivity and giving engineering leaders better visibility. The results have been mixed, partly because the category has a PR problem. Developers do not want to be surveilled. The moment you start measuring lines of code or commit frequency, you get Goodhart’s Law in action. People optimize for the metric, not the outcome.

The broader developer tools market is enormous. Estimates put it somewhere around $30 billion and growing, with infrastructure and productivity tooling absorbing a disproportionate share of venture dollars. But the visibility sub-category has struggled to find product-market fit in a way that both leadership and individual contributors accept.

The fundamental tension is real. CTOs need to know what is moving and what is stuck. Engineers need to not feel like their commit history is being weaponized against them. Most products in this space have landed on one side of that tension and alienated the other.

What I find interesting about the current moment is that AI changes the equation. If a tool can actually read and understand the code, not just count commits and PRs, it can provide context that raw metrics never could. The difference between “this developer made 3 commits” and “this developer refactored the auth module and unblocked two other engineers” is the difference between surveillance and understanding.

The Micro: Repeat Founders, Read-Only Access, Week-One Revenue

Mesmer (Y Combinator S25) was founded by three repeat entrepreneurs out of San Francisco. Joao de Paula is the CEO with 15 years of experience building companies. He previously co-founded Origin Financial, which scaled to eight-figure ARR and a $400 million valuation, and before that co-founded Glio, which was in the S13 YC batch and was the first Latin American company accepted into the program. Sergio Oliveira Bergmann is the VP of Engineering, also formerly at Origin Financial, with 15+ years in fintech and digital banking engineering leadership. Lucas Silva is the CTO with 18 years as an engineering leader, previously co-founding Qual Farmacia and serving as Director of Engineering at Origin Financial.

Three co-founders. All of them from the same previous company. All of them senior engineering leaders. That is not a typical founding team. That is a team that lived through the scaling problems they are now selling a solution for.

The product connects to GitHub, GitLab, Bitbucket, Linear, Jira, and Slack. It reads every line of code. Then it delivers daily summaries, risk detection for stalled commits and inactive contributors, performance tracking across workload distribution and shipping velocity, and real-time alerts. The key product decision: read-only access. Mesmer cannot modify your code, your tickets, or your tools. It just watches. That is a deliberate architectural choice designed to address the surveillance concern head-on.

The traction numbers are striking. Six-figure ARR within a week of launching, with customers including Webflow and Origin Financial. Combined customer value exceeding $8 billion. For a company this early, that is unusually fast revenue, and it suggests the founders’ networks from their previous company are converting into customers. That is not a criticism. It is an advantage. Selling enterprise software is hard, and having relationships with engineering leaders at well-known companies compresses the sales cycle dramatically.

SOC 2 certification is already in place, which matters for the enterprise buyers they are targeting. The website is clean, with a demo booking flow and an embedded video walkthrough.

The “Cursor for CTOs” tagline is clever positioning. Cursor gave individual developers superpowers. Mesmer is trying to give engineering leaders the same kind of AI-enhanced capability, but for organizational understanding instead of code generation.

The Verdict

I think the founding team is the strongest signal here. These are not first-time founders guessing at what engineering leaders need. They built and scaled an engineering org to hundreds of millions in valuation, and they built this product because they could not find it when they needed it. That origin story tends to produce products that solve real problems.

The read-only architecture is smart. It removes the biggest objection engineers have to these tools before the conversation even starts. If Mesmer cannot change anything, it cannot break anything, and the surveillance framing becomes harder to sustain.

The risk is category fatigue. Engineering leaders have been pitched “visibility” and “productivity analytics” tools for years, and many of them have scar tissue from products that promised clarity and delivered dashboards full of vanity metrics. Mesmer needs to prove that AI-powered code understanding is a meaningful upgrade from commit counting, and they need to prove it fast.

At 30 days, I would want to know the retention story. Week-one ARR is impressive, but the question is whether the daily summaries remain useful or become another notification to ignore.

At 60 days, the product needs to demonstrate that it catches real problems. A stalled commit that would have become a missed deadline. A contributor who is overloaded before they burn out. Those stories are what will drive expansion revenue.

At 90 days, the competitive picture is the question. LinearB, Jellyfish, and the rest are not going to sit still while Mesmer takes their pitch and adds AI. The advantage of the founding team’s network has a shelf life. Product quality has to carry it from there.

Week-one revenue from Webflow is a strong starting hand. Now they need to play it.