Waydev Agent

@alex_circei - this is very cool, sorely needed, & looks extraordinarily well designed.

With that said… I *ardently* wish you hadn’t chosen to conceal pricing data in the way thay you have. Well, I understand the philosophy, I didn’t tell you that for me it’s an immediate turn off and makes me wary to even engage the platform.

Simply: I don’t know if I’m gonna really Waydev, & at the end of seven days, be expected to spend four figures a month, or be locked into an annual contract, or pay some crazy additional amount per seat, or something else that makes this fundamentally untenable for me to use.

Again: great work here. This is definitely something special. I just think a little bit of transparency would go a long way.


The "AI Impact" piece is the hardest problem in this space and most tools quietly fudge it. Devs don't write code in clean buckets. They use Cursor to draft, rewrite half by hand, accept Claude's completion on three lines out of fifty, paste a ChatGPT snippet and edit it for an hour. What's Waydev's actual attribution method when AI authorship is partial, mixed, and deniable? IDE-plugin self-reporting, statistical fingerprinting on commits, or something else?

How does Waydev’s AI ROI approach differ from platforms like Jellyfish or Faros that also claim “AI impact/ROI”—specifically in how you model cost (licenses + tokens) against outcomes and how you handle confounders like team mix, project complexity, and seasonality?

This is super relevant right now. Everyone is pouring money into AI, but barely anyone knows what it’s actually returning. Love the shift from dashboards to conversations, feels way more natural for how teams want to work.

the 'ai adoption vs ai impact vs ai roi' split is the right decomposition. most teams collapse all three into 'are devs using cursor' which tells u nothing about whether the code actually shipped or got reverted. measuring the impact layer is where this gets interesting

Hey PH 👋Alex here, founder of Waydev. Thanks @rajiv_ayyangar for the hunt — and shoutout to the team at Deel for including us in Pitch by Deel NYC. Excited to be part of it.Nine years ago I started Waydev because engineering leaders were flying blind on what their teams actually shipped. Now half the code is written by Cursor, Claude Code, Copilot, and Devin — and the question from CFOs is the same one in different clothes: is the seven-figure AI bill actually paying off?Most teams don't know. They're guessing.Waydev is the measurement layer for AI-written code. We track three things across the full SDLC:AI Adoption — who's using which tool, how often, how deeplyAI Impact — does the AI-written code ship, get reverted, or rot in PRAI ROI — dollars in vs. throughput out, across humans, copilots, and autonomous agentsToday we're shipping three things that change how engineering leaders interact with their data:🤖 Ask Waydev — our agent. Ask in plain English, get a real answer. No more dashboards no one opens.📄 Skills — configure Ask Waydev with SKILL.md files. 🔌 Waydev MCP — your engineering feed, exposed to any external agent. Plug it into Claude, Cursor, your internal tools — whatever's already in your stack.The framing we keep coming back to: MCP is the data out. Skills are the instructions in. Ask Waydev is the conversation in the middle.The bet: engineering leaders would rather have conversations than dashboards.We've been covered by TechCrunch, TNW, and DevOps.com along the way. I'll be in the comments all day. Roast the product, ask the hard questions. That's how this gets better.— Alex