# value-based pricing Published articles for value-based pricing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How we develop pricing and packaging at Fin DevFeed: [How we develop pricing and packaging at Fin]() Original publisher: [Read original article]() Author: Sophie Woods Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Intercom]() Topics: [AI Trends](), [To-Do]() Tags: [adoption](), [ai](), [business](), [customers](), [growth](), [pricing](), [pricing-model](), [product-design](), [value-based-pricing]() ### AI overview Intercom describes how its team develops pricing and packaging for Fin, its AI Agent. The process combines buyer research, willingness-to-pay studies, commercial modeling, and executive sign-off, with the pricing system reviewed as the product expands. ### Source excerpt At Fin, pricing and packaging must balance the needs and wants of our customers and our broader vision. Here's how we do it. ## Value-Based Pricing for SaaS: How to Price Based on Customer Value DevFeed: [Value-Based Pricing for SaaS: How to Price Based on Customer Value]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-03-24T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [API Monetization](), [API Business Models](), [Use Cases for Every Cloud Service Model]() Tags: [metric](), [pricing](), [research](), [saas](), [strategy](), [value-based-pricing]() ### AI overview Value-based SaaS pricing ties charges to customers' perceived return, time saved or outcomes rather than production costs or competitors' prices. Choose a simple value metric that scales with customer benefit, such as active users, contacts, transactions or compute; consumption metrics are easier to track but can penalize efficiency, while outcome metrics align incentives but may be difficult to measure and dispute. A hybrid of base subscription and usage overages offers recurring revenue with room to scale. The guide recommends segmenting customers, researching willingness to pay with a Van Westendorp survey (at least 50-100 target-customer responses), mapping metrics and features to tiers, then testing and reviewing prices every six months. For migration, it suggests launching new prices for new customers first and giving existing customers a 6-12 month grandfather period. Billing systems need to support subscriptions, usage and credits. The article's named company examples and claims are presented as illustrations, not independently substantiated evidence. ### Source excerpt Guide to implementing value-based pricing for SaaS. Learn how to find your value metric, research willingness to pay, and set prices customers accept. ## Value-Based Pricing and TDD DevFeed: [Value-Based Pricing and TDD]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2020-02-09T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Test-driven development](), [Functional programming](), [software-development](), [intrinsic motivation]() Tags: [algorithm](), [bias](), [business](), [business-context](), [consulting](), [counts](), [development](), [exploring](), [family](), [financial](), [fixed](), [functional-programming](), [idea](), [pricing](), [save](), [startup](), [tdd](), [time](), [value-based-pricing](), [work]() ### AI overview The author argues that both value-based pricing and TDD work best when outcomes are predictable, and that blanket rules overlook exploratory work. Value-based pricing can reward efficient delivery, but the author questions whether money is the only incentive and notes that fixed fees for unfamiliar consulting tasks require pricing in uncertainty. TDD worked well for a clearly specified round-robin algorithm, where expected behavior was known. During exploration, the author may not yet know what to test, and writing tests for code that may be discarded can slow discovery; waiting too long to test, however, can leave viable code harder to test. The author suggests a middle ground: stay conscious of testability while exploring, and sees functional programming as encouraging testable code. The broader caution is against the "Simplicity Bias" behind absolute claims such as "Only use TDD" or "Hourly Billing is Nuts." ### Source excerpt I first heard about value-based pricing from an accountant who was creating a startup based on the idea. He tells a story about consulting for a family who inherited an estate. Because of the accountant's extensive knowledge, he was able to give advice that saved the family a million or more. However, he only charged for his time, a couple of hours. To save that amount, the story goes, the family would have been happy to pay more, an amount based on the value of the work rather than the time it took.