Activity
Mon
Wed
Fri
Sun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

PricingSaaS

1.1k members • Free

2 contributions to PricingSaaS
Implementing complex pricing structure
Hi guys, I read Ulrich's book as I have an enterprise focused collaboration solution (AI) being developed. I think it makes sense for us to price for usage, infra and some services. I have a good contract lawyer who can draft pretty much any legal agreement but a question lingers: how do you guys do it operationally? (what tech stack do you use from "quote to cash" to implement complex pricing structure? Any stack that would scale from startup to more mature state?). On a separate but related topic : what license server/engine would you recommend for an AWS BYOL approach? Thank you!
1 like • Dec '24
Hey Alex, this is a really important question and one that most companies answer with homegrown systems. This often leads to reinventing the wheel, driving up engineering costs, and constraining business agility. We've written in depth about how to implement & operate pricing from a systems & architecture perspective. https://schematichq.com/blog/how-to-operate-pricing-and-packaging I've also curated 10 of the best articles I've come across related to the question you're asking here: https://www.linkedin.com/posts/fynn-glover-b0410015_10-useful-actionable-reads-for-product-activity-7260732669955555328-20Ac?utm_source=share&utm_medium=member_desktop What's key is that you decouple pricing & billing from application code, so you can remove engineering from having to support future changes, and empower the business to iterate as your product & market evolve. To do this, would encourage you to make entitlement management a first-class citizen in whatever path you go down. You could build or outsource an entitlements system. If you outsource, here are a few vendors to evaluate: - if your company is quite large (e.g. $100M ARR+), you might look at license management providers like Thales, Revenara, Nalpeiron, Stigg, etc. - if your company is a startup, you might look at my company Schematic (https://schematichq.com/) - some companies try to solve this through their billing provider (e.g. chargebee, stripe, etc), but they still have to build logic between their application and the downstream billing tools, which usually means engineering is always critical path in pricing changes/initiatives. Hope this is helpful, and happy to connect on this anytime, as it's an important question.
How to price AI in SaaS
I'm writing a guest chapter on AI pricing for another authors upcoming book. So I'm thinking about this a lot lately, and wanted to give you a sneak-preview of a linkedin post that will come out later next week. - I've done maybe 10 pricing projects involving significant AI functionality this year. Here is how I think about it. AI should be considered a 2-layer stack: 1️⃣ The AI compute 'fuel' (i.e. token pricing at OpenAI) 2️⃣ The AI solution (i.e. the value you add on top of AI) The dilemma with AI pricing is that currently: ◾ Fuel is expensive - at least way more so than traditional SaaS. ◾ Solutions are immature and early stage, not yet adding a lot of value. So any AI pricing model needs to both work today AND tomorrow. AI PRICING TODAY: 🔹 Charges usage-based on fuel consumption to ensure costs are covered, as usage patterns of customers is often unpredictable. 🔹 Is mostly focused on low barriers to entry to get users onboarded in order to develop the solution layer and get data on behaviour and cost patterns. 👉 This is unsustainable as fuel costs will drop and 2025 customer will refuse to pay a price-per-token (or token equivalent) that is based on 2024 token costs. This is especially true for enterprise. AI PRICING TOMORROW: 🔹 Charges based on the outcome created by the solution layer and just factors in fuel costs in the use case. 🔹 Protects against cost-downside of over-usage with 'fair usage limits'. HOW I SOLVE FOR THE TODAY-TOMORROW PROBLEM IN AI PRICING 🔸 Focus on speed: just get usage and adoption as fast as possible. You likely have a core non-AI product that monetizes just fine. Consider AI a 'development budget' and focus on profitability later. 🔸 Tell customers you are BOTH charging for fuel and for a solution outcome. Educate them. But keep it 90% fuel and 10% solution early on. 🔸 Over time: shift $$ from fuel to solution pricing. Cut Fuel pricing aggressively, even anticipating future cost reductions. Consider solution pricing separately and from a value perspective.
2 likes • Oct '24
This is a super interesting topic. I interviewed the founder/ceo of an AI company yesterday who an interesting take on this subject. Summarizing in case useful: 1. he doesn't believe that value-based pricing will work for the AI companies as many people have argued  2. he thinks most AI companies — assuming they're application layer —  should price based off seats and maybe have a little usage on top of the seat Why does he believe this? I need to go back and listen and better synthesize, but the gist is: 1. costs of fuel are coming way down fast 2. its buy vs. build, so enterprises can build their own application layers or outsource 3. there's a ton of change management to adopt application layer 4. consumer LLMs anchor prices for application-layer startups.  Curious people's thoughts?
1-2 of 2
Fynn Glover
1
1point to level up
@fynn-glover-7113
co-ofunder & ceo of Schematic

Active 503d ago
Joined Aug 26, 2024
Powered by