How do you measure product-market fit for a developer tool? A PMF scoring model from Evil Martians—a product development consultancy for developer tools startups—built on data from 37 devtools companies across AI, infrastructure, and cybersecurity. Five metrics, real benchmarks, and a dual score that tells you whether to invest in product or go-to-market.

The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

Evil Martians presents a PMF scoring model built on data from 37 devtools companies including Cursor, Supabase, Linear, and Twilio. The model uses five weighted metrics—time to first value, retention, net revenue retention, free-to-paid conversion, and organic signups—to produce a dual score separating product signal (0–7) from revenue stage (0–7). The gap between the two scores diagnoses whether a company has a product problem or a go-to-market problem. Devtools benchmarks differ significantly from generic SaaS: higher conversion rates (7%+ vs 2–4%), higher NRR (130%+ exceptional), and faster time to value. The post maps seven PMF levels from $0 ARR to $200M+, with real company examples at each stage, and introduces the PMF Compass tool on the Evil Martians homepage.

Product-market fit methodology for early-stage devtool companies—Martian Chronicles, Evil Martians’ team blog