Marcus Webb does not think of Stackline's pricing history as three failures and one success. He thinks of it as four experiments, three of which produced the information necessary to make the fourth one work. Stackline, his developer productivity platform for mid-market engineering teams, launched in early 2024 with per-seat pricing. By mid-2026, after three complete pricing rebuilds, the company was on a usage-hybrid model generating 34% more revenue per customer. The path between those two points was not linear.
Version one: per-seat pricing (January - August 2024)
Webb launched with per-seat pricing at $45 per user per month because that is what the competitive set used. "We looked at the market, saw seat-based pricing everywhere, and assumed the market had already solved this," he said. Within six months, two problems emerged. Engineering managers were limiting seats to control costs, which meant the tool was not reaching the developers who needed it most. And expansion revenue was capped by headcount growth, which was flat across the customer base.
The insight: per-seat pricing was punishing adoption. Customers who used the product more paid more, which created a perverse incentive to use it less.
Version two: flat tier pricing (September 2024 - March 2025)
Webb overcorrected. Stackline moved to three flat tiers: $500, $2,000, and $5,000 per month, based on team size bands. Adoption increased immediately because the per-seat penalty was gone. But a new problem appeared: the tiers did not map to value. A 30-person team using Stackline for one workflow was paying the same as a 30-person team using it for six. The heavy users felt they were getting a deal. The light users felt overcharged.
The insight: flat tiers removed the adoption penalty but created a value-alignment gap. The pricing did not reflect how different customers used the product, which meant the company could not distinguish between high-value and low-value accounts.
Version three: pure usage pricing (April - October 2025)
The third attempt was pure usage-based pricing: customers paid per CI/CD pipeline run. This aligned price with the core value action. Expansion revenue increased 40% because customers who used the product more paid more without any sales conversation. But procurement departments hated it. Budget predictability disappeared, and three enterprise prospects walked away because their finance teams could not forecast the annual spend.
The insight: usage pricing aligned with value but created buying friction. Enterprise buyers need predictability, and pure usage models transfer too much risk to the buyer.
Version four: the hybrid that held (November 2025 - present)
The current model combines a platform fee (predictable base cost that satisfies procurement) with usage-based expansion (pay more as you use more, without seat limits). The platform fee is $1,200 per month. Usage above the included threshold bills at a declining rate per unit. Customers get budget predictability and value alignment. Stackline gets expansion revenue that grows with usage.
"Each pricing version failed in a way that taught us something we could not have learned by surveying customers or analyzing competitors," Webb said. "The per-seat model taught us adoption mattered most. The flat tiers taught us value alignment could not be ignored. The pure usage model taught us buyers need predictability. The fourth version only works because the first three failed specifically enough to be useful."