Code Story
Code Story

S8 E14: Dan Lines, LinearB

Dan Lines is married, with a 3 year old daughter and a baby on the way. He has lived all over the US - 7 years in Boston, 5 years in LA, and he now lives in Upstate New York. He has always been into the creation of things, being the kid in high school burning and selling CD's, building computer

Featured Speakers

Noah Labhart - Startup Founder & CTO HostDan Lyons Guest

Topics Discussed

Episode Summary

Executive Summary: Dan Lyons, co-founder and COO of Linear B, explains how the company evolved from manual, slide-based engineering metrics for managers into a SaaS platform serving developers and large enterprises. The conversation covers MVP development, customer-led roadmap decisions, hiring for resilience, scalable growth, a failed PLG motion, and the culture and product vision driving Linear B’s future.

Main Topics: Origin story and founder pain points (Priority: 5/5): Linear B was born from Dan’s experience as an engineering leader managing large teams and feeling the operational pain of measuring and improving software delivery. MVP evolution from manual analysis to SaaS (Priority: 5/5): The first version was a manually assembled metrics deck for design partners, then evolved into a real-time SaaS product after strong validation. Customer-driven roadmap and product strategy (Priority: 4/5): Dan emphasizes listening to customers, balancing enhancement of existing features with innovation, and using design partners to validate new ideas. Hiring, culture, and resilience (Priority: 5/5): The company prioritizes character, adaptability, and innovation; internal culture is built on transparency and a hands-on mentality where no task is beneath leadership. Scalability and growth management (Priority: 4/5): Linear B grew responsibly on both the people and product sides, avoiding overhiring and progressively adapting the product as customer size increased. Go-to-market lessons and persona shift (Priority: 5/5): A key mistake was an early free tool for engineering managers; the company later shifted the free motion to developers, requiring cross-functional adaptation. Future focus: developer experience and enterprise resource allocation (Priority: 4/5): The next phase centers on improving developer workflow/DevEx and scaling resource allocation capabilities for Fortune 500 organizations.

Key Arguments: The best early validation came from manual, high-touch interactions with design partners before building full SaaS functionality. Customer feedback should drive roadmap decisions; if feedback is absent, founders should question product-market fit or outreach strategy. A successful roadmap should split effort between improving what already works and pursuing new innovation. Hiring for character and adaptability matters more than a rigid formula because startups face constant change and setbacks. Scalability should be progressive rather than planned as a one-size-fits-all system from day one, because customer needs change as the company grows. An early PLG motion can hit a cap if the product is aimed at the wrong persona; shifting to developers expanded reach and fit the market better. Company culture and transparency are core competitive advantages, especially when teams need to execute through growth and change.

Data Points: Design partners: 10 to 15 - Linear B’s first manual MVP was presented to an initial group of design partners. Manual MVP phase duration: About 6 months - Time needed to build the SaaS platform after the slide-deck prototype. Engineering team size at prior company: About 100 engineers - Dan’s experience as VP of engineering shaped the pains that inspired Linear B. Roadmap allocation to enhancement: Two-thirds - Linear B dedicates most roadmap effort to improving existing features and customer experience. Roadmap allocation to innovation: One-third (about 33%) - Linear B reserves a portion of roadmap for new ideas with promising prospects/design partners. Early free-tool adoption: Thousands of teams - The initial free tool for engineering managers achieved significant usage but had a limit as a go-to-market motion. Developer population estimate: 32 to 50 million developers - Dan cites the much larger developer persona as a reason for shifting the free tool strategy. Customer stage early in company: 20 to 50 engineers - Linear B initially served smaller engineering organizations.

Pivotal Quotes: "The most important thing you can do is listen to your customers." — Dan Lyons: He explains how Linear B prioritizes roadmap decisions and product validation. "Nothing is beneath you." — Dan Lyons: Dan describes Linear B’s culture of transparency and hands-on leadership. "Stay humble and stay level headed." — Dan Lyons: His advice to a young entrepreneur about navigating startup highs and lows.

Implications: For founders, the episode reinforces that product-market fit is iterative, customer feedback is essential, and persona selection can make or break PLG. For the industry, it highlights growing demand for DevEx and engineering operations tooling.

🔓 Sign Up for Unlimited Episode Search

About Code Story

Code Story is a podcast featuring startup founders, tech leaders, CTO's, CEO's, and software architects, reflecting on their human story in creating world changing innovation, disruptive digital products. Their tech. Their products. Their stories.

View all episodes from Code Story