21–30 of 59 posts
Price will go up from $50 to $100 per seat. Now can only have 8 seats instead of 40 seats and only 1 project instead of unlimited projects.
In a recession you learn who your true strategic partners are. It is fair enough that prices need to be increased in line with cost, however, a 100% increase with one month notice is #@#**. In our case it would be a 600% increase as this forces us onto the enterprise plan. Budgets for 2023 have already been agreed this late in the year, so this is a hard sell to the C suite. Our conclusion is that we can't rely on DB…
In a recession you learn who your true strategic partners are. It is fair enough that prices need to be increased in line with cost, however, a 100% increase with one month notice is #@#**. In our case it would be a 600% increase as this forces us onto the enterprise plan. Budgets for 2023 have already been agreed this late in the year, so this is a hard sell to the C suite. Our conclusion is that we can't rely on DB…
The new metrics feature is tied to DBT cloud - probably because that is the only way they could get bigger users to get value from their hosted product and not just DIY it. (offering a largely propitiatory feature). However, I don't know what the uptake of the metrics feature is - it seems half baked to me.
In a recession you learn who your true strategic partners are. It is fair enough that prices need to be increased in line with cost, however, a 100% increase with one month notice is #@#**. In our case it would be a 600% increase as this forces us onto the enterprise plan. Budgets for 2023 have already been agreed this late in the year, so this is a hard sell to the C suite. Our conclusion is that we can't rely on DB…
What is their cloud offering if it’s just sql templating? Why would anyone pay for that?
There is cloud IDE, which is just ok in my opinion. I'd rather use a local editor, but might be a value add for some.
The cloud plans also has metadata features and APIs, which could be worth it for some use cases.
The most interesting thing tied to the cloud is the new metrics feature, but I don't really like how it's done (metrics are defined as sql fragments in YAML). Really using metrics depends on proprietary parts that dbt cloud only has, so if you are using this, you'll probably be paying for the cloud.
[1] https://docs.getdbt.com/docs/use-dbt-semantic-layer/dbt-sema...
In a recession you learn who your true strategic partners are. It is fair enough that prices need to be increased in line with cost, however, a 100% increase with one month notice is #@#**. In our case it would be a 600% increase as this forces us onto the enterprise plan. Budgets for 2023 have already been agreed this late in the year, so this is a hard sell to the C suite. Our conclusion is that we can't rely on DB…
Quoted post unavailable.
- Grandfather in old users for as long as you can. Forever if it's feasible. More than likely future customer revenue >>> current customer revenue so it's not worth burning goodwill. Don't go past this point unless you have a really good reason.
- If you absolutely need to increase prices for current customers, the warning should be long (6mo+). If people want to leave, they shouldn't feel rushed, and they should have time to put migrating off on their roadmap. More time also helps goodwill.
- Give several automatic extensions of ~1 month after initial deadline. No matter how many times you email, some people won't read them. This has a few benefits. 1) extensions help pick up some users who would have churned. They might miss deadline 1, but you can pick up an extra 10-15% on an extension. 2) It give you something to point to when the price increase hits and they contact support ("we told you 4 times, and extended it twice already"). It's not perfect, but it helps. Be sure to send an automatic email when you extend. 3) People will leave it to the last minute, and migrating off might take longer than planned. Blanket extensions reduce the number of panicked manual extensions, and lower manual support load.
- Be willing to give a manual extensions of a fixed time for those who raise a stink to support. Messaging can be "we'll give you a 4th extension of 3 months, but this is really the last one". Let the support team grant these without any approval to lower management overhead. It makes most people happy, but more importantly, it spreads out the anger over a longer time.
Ultimately, the steps above will slightly increase uptake, but dramatically reduce the chance of ending up on the front page of hacker news. The latter is more important, it's burning chances with future customers.
Mailchimp's Mandrill is still the worst case I've ever seen. Cheap to host product, increased prices dramatically, with minimal warning, no opt in, and unsympathetic tone from C-suite. People don't forget when companies act like this. Also: don't use Mailchimp.
I was not disappointed: “Updating dbt Cloud pricing to support long-term community growth” - though I reckon they could have gotten “journey” in there as well.