Courtney Meddaugh

Join Snowflake at Collision to learn how the Snowflake’s single platform eliminates data silos and simplifies architectures, so you can get more value from your data. Come visit me at the Snowflake Booth next week!

3

Calling all Snowflake & Databricks customers. If you are not using Sigma Computing, your current BI tools do not empower your business stakeholders to write back to your warehouse in a meaningful way. True story. This means you are missing out on the ability to safely and securely perform some high-value, mission-critical workflows (i.e. scenario planning, P&L reconciliation, GTM forecasting, adding contextually rich data, feedback loop closure) without your data being moved out of your warehouse. This is a bit like building your dream home but then living in a tent in your neighbor's yard. Looking for an impactful way to spend that year-end use-it-or-lose-it budget? I would love the opportunity to prove what I'm claiming here. PM me to get started, we will happily guide you through an evaluation on your data. Legacy BI Tools cannot do what Sigma can do with Modern Cloud Data Warehouses. They were designed and developed to solve a different set of challenges, unfortunately not today's.

81

What will be the biggest AI investment areas for enterprises in 2025? How will leaders balance rapid AI adoption with governance? Read Databricks’ predictions for enterprise AI this year.

1

If you’re thinking about implementing Data Cloud any time in the future, or wondering what you can do now to prepare for it, you will get value from this session

19

Come See Yourself in the Data! If your analytics tools don't allow you to write back to the data warehouse they're only doing half the job. Come see Sigma Computing this week at Snowflake Summit #ScenarioModeling #GLreconciliation #TerritoryPlanning #FeedbackLoops #Summit24

6

Wondering how "Data Intelligence" enhances data governance, data engineering, data streaming, data warehousing and all your data user experiences? See you in Austin at the Databricks Data Intelligence Day this Wednesday August 21st - register here:

13

Snowflake should at least tell us what bugs they are fixing and what features they are working on in snowflake managed Polaris. It will helps us to prepare .. For example: add_files, register_table procedure are not working. I know snowflake team is working on it but no info to community. Some of these features essential to move on from PoC to prod. James Malone Snowflake

8

Metronome‎ accelerated its new Salesforce integration by 4 months with Census‎ Embedded 🚀 ‎ Companies like OpenAI, Databricks, and NVIDIA use Metronome to manage usage-based pricing models and track real-time usage data. Revenue teams need that data in Salesforce for quoting and 360° visibility. Census provided the most robust Salesforce integration for Metronome, achieving results like: 𝟏️⃣ ‎ 𝗣𝗿𝗼𝘃𝗶𝗱𝗶𝗻𝗴 𝗻𝗲𝘄 𝗦𝗮𝗹𝗲𝘀𝗳𝗼𝗿𝗰𝗲 𝗳𝗶𝗲𝗹𝗱𝘀 𝗮𝗻𝗱 𝗼𝗯𝗷𝗲𝗰𝘁𝘀 𝗶𝗻 𝗺𝗶𝗻𝘂𝘁𝗲𝘀 — Census Embedded makes it easy to sync data to new Salesforce objects, without days of development work. 𝟐️⃣ ‎ 𝗖𝗮𝗽𝗮𝗯𝗶𝗹𝗶𝘁𝗶𝗲𝘀 𝗶𝗻 𝘄𝗲𝗲𝗸𝘀, 𝗻𝗼𝘁 𝗺𝗼𝗻𝘁𝗵𝘀 — Census Embedded helped Metronome rebuild its Salesforce integration in 3 weeks, not 5 months. 𝟑️⃣  ‎𝗥𝗲𝗺𝗼𝘃𝗶𝗻𝗴 𝘀𝗶𝗻𝗴𝗹𝗲 𝗽𝗼𝗶𝗻𝘁𝘀 𝗼𝗳 𝗳𝗮𝗶𝗹𝘂𝗿𝗲 – Census Embedded saves the Metronome engineering team from maintaining in-house Salesforce expertise. Read the case study: https://lnkd.in/ged5DifS

18

So I've joked about it in the past, and it's not actually that funny anymore. Yet another release and no updates to CPQ. Salesforce your customers are paying a hefty premium for this product and to have no meaningful feature enhancements in over 2 years is absurd. I realize you're pushing everyone to Revenue Cloud, but a lot of us maintain orgs that are going to have CPQ for quite some time. Is the product team going to fill us in on the official demise, or are we going to continue to pull the wool over our eyes? #salesforce #salesforcecpq #cpq

120

22 Comments

Exciting usecases with Snowflake + Salesforce Data Cloud : Retailers can now combine Commerce and Service Cloud data from Salesforce with point-of-sale and supply chain data in Snowflake to help troubleshoot customer challenges and pinpoint manufacturing issues. With a comprehensive single source of truth that combines ERP data with customer data, retailers can also run targeted campaigns that feature discounts for surplus inventory. CPG customers have heavy advertising budgets but lack first-party data due to indirect contact with customers. CPG customers must rely on secure data collaboration methods that allow them to gather data which allows them to run more effective ads more confidently. By sharing Salesforce Marketing Cloud and Sales Cloud data from Salesforce to Snowflake, unifying those data sets with their own financial and sales data, CPG customers can then use a data clean room to share data with their retail partners without exposing PII, to gather a more refined view of their advertising and marketing performance. This allows them to adjust strategies and better allocate ad spend to maximize ROI. Finally, CPG customers can then share refined audiences back to Salesforce to execute consistent, cross-channel campaigns through the Salesforce Marketing Cloud.

36

1 Comment

Dynamic visual showcasing the power of PLATFORMS! This exemplifies why customers invest in comprehensive data solutions like Snowflake Data Cloud. A single platform unlocks diverse possibilities: advanced data warehousing, seamless collaboration, AI integration, and scalable application development. #DataPlatforms #SNOWFLAKE

2

This is a great session to learn about to build End to End Data Pipelines using Snowflake's advanced feature set. Definitely worth attending to help automate data pipelines. https://lnkd.in/gpzbUZ2z ❄️ #snowflake #data #automation ❄️

9

Ian Whitestone at SELECT has scooped us again! If you read Snowflake release notes as avidly as Ian does, you may have noticed we recently announced the general availability of two account usage views: > The TABLE_DML_HISTORY view can be used to determine the magnitude and effects of the DML operations performed on a table. > The TABLE_PRUNING_HISTORY view can be used to determine the efficiency of pruning for all tables, and to understand how a table’s default (natural) ordering of data affects pruning. Check out a great example of how to use this view here: https://lnkd.in/gWPdD4gK #datacloud #dataengineering #datawarehousing #businessintelligence #analytics cc: Tim Sander

68

I've long struggled with calling saying something has "Good" or "Bad" Developer Experience (DX) because it's extremely binary and doesn't really help product teams improve their DX. For that reason when I started the Developer Advocacy program at Twilio and began to work with product teams on improving their DX we ended up creating the "DX Spectrum" framework that is helping product teams evaluate their DX better and helps to answer the question "How do we create a magical developer experience?" https://lnkd.in/ggMmCx_e

49

3 Comments

Partners & Developers, Do check out this webinar on Data cloud 2GP packaging and scratch orgs ! Use the benefits of 2GP to create your Data Cloud apps. #salesforce #datacloud #isv #appexchange #salesforcepartners

14

The Databricks product team conducted a research survey with over 70 users to learn more about the Assistant's impact on productivity. Check out the survey results and see how you can use Databricks Assistant to increase yours. #DatabricksAssistant

13

In Spring 2024, monthly churn for Copilot CRM hit 11%  At that rate, 90% of customers would be gone before the year's end. Our codebase contained 285 documented bugs. The database was fragile, inconsistent, and often experienced outages during peak hours. I had hardly slept for almost four days. It was excruciating... Not because we were losing members. Not because people were cursing at me online or threatening legal action. It was painful because the members were my friends, franchisees, and closest supporters. Everything broke. Emails got hacked, texting stopped, jobs disappeared, invoices gone.  Every time we fixed a bug, three others popped up. Regression after regression. The codebase was melting under the pressure of massive user growth. IT WAS HELL! A few months before, everything was gravy. We had tripled users for two straight months. We got to break-even without investors. Q1 2024 was on track to be profitable. We had delivered 15+ massive features in 2023. Everything was going great. So fast forward to present day.  We have reduced the reported bug count by almost 80% (we aren’t done yet!) We have had stagnant growth for most of 2024. Churn is still high at 4% monthly. Our expenses have more than tripled, and they have room to run as we continue to hire more team members. In the meantime, I bought out my co-founder to ensure I would take the financial hit required to get us back on track. We aren't out of the woods yet.   Credit is due. 1.) Most important. The users that stuck with us from the beginning. The company would have failed if everyone had left. They had every right to. I will not forget this. We have 1-2 more months to clean up the mess I created, but you have my word; I will make it up to you. 2.) The team. I am not going to mention names. They know who they are. They were unwavering in their support for me and the vision of Copilot. People have worked and continue to work around the clock. I messed up big time trying to hire engineers as a non-technical founder. I had to make difficult decisions to cut staff and rebuild from the ground up. This caused intense pain. Thank you to each person who contributed to this effort! 3.) Josh Kahle deserves a special rose. I needed to attract the best talent in the industry to turn the company around. Why would ANY great engineer step into this mess??! For some reason, Josh believed in me. He had the tech skills, experience, and connections we needed. He caught my vision for home services, software, and robotics. He cosigned on the vision of Copilot and put his reputation at stake. This gave us credibility to attract the top engineers, designers, and team members. So why am I writing all this? Where is the feel-good ending? It’s not here yet. But it's coming... If you want me to make BTS posts like this in the future, let me know in the comments. I hope it helps someone. Quitting is not an option.

16

3 Comments

I've noticed a disturbing trend in the Salesforce ecosystem: Salesforce employees being antagonistic with customers. A tale as old as time is that when you're "on top," you will have dissenters. These dissenters fall into two camps: 1️⃣ Folks who don't like your product 2️⃣ Folks who like your product and want to make it better For the sake of this post, we'll put 1️⃣ aside since the antagonism is pointed more towards 2️⃣ . Rather than listening to the content and intent of this group, this group of Salesforce employees is on a mission it seems to disprove. And at the same time, they are missing the point. Customers are experiencing core issues. Customers that are spending A LOT of money on a product with issues. These customers use their voices to educate others, initiate discussion, and suggest a better path forward. Instead, we see ad hominem attacks towards these posters through a quest for silence. If you're building a product, you don't have all the answers, listen to your customers (actively), and open a dialogue rather than seeking to shut them down. #salesforce #businessystems #product * LinkedIn posts aren't the best for nuance. This is not targeted towards _all_ SF employees, but rather the subset doing this. And yes, there is a bit of confirmation bias due to the algorithms. But it is a trend, nonetheless.

43

18 Comments