Ryan Lunka

ToolJet now integrates with Salesforce! This means our users can directly tap into Salesforce without complicated setups. Here’s why this integration will make a difference: 1. Quick data access – Connect your Salesforce account and instantly pull the data you need into your internal tools. No more jumping through hoops. 2. Custom insights at your fingertips – Build dashboards that pull live data from Salesforce, giving your team the exact insights they need. 3. Bring it all together – Easily combine Salesforce data with other tools you’re already using on ToolJet to build even more robust workflows and apps. This integration is all about making life easier for teams who want fast, flexible, and powerful internal apps. #lowcode #salesforce #opensource

48

In the latest iDialogue Flow CPQ+AI release, transactions are divided into guided chat prompts and Auto-Launched flows. This is the traditional Model-View-Controller (MVC) development pattern many developers are familiar with, where the “View” is implemented as a GPT AI Agent and the Controller is an auto-launched flow that handles validation and record INSERT. This division of responsibility aligns well with the job functions of Business Analyst (BA) and Salesforce Developer; where the BA defines product bundles and add-ons using natural language expressions that are passed to Flows for more deterministic validation and record handling. This implementation is far faster because the BA's requirements and specifications are immediately executable "code" that offers real-time feedback.

9

2 Comments

Quick video on how you can approach enrich(ed) contact and account data in your #CRM (#Salesforce in this one) Enjoy the day!

14

1 Comment

Salesforce acquiring Own Company for $1.9B was NOT a big move. It's a highly conservative acquisition. And the move was about purchasing revenue 👇 In general, Salesforce acquisitions fall into 1 of 2 categories: • Acquisitions for Innovation • Acquisitions for Revenue Acquisitions for innovation would include Slack or Mulesoft. • Yes, they add some revenue as well but that's not the purpose. • The goal is ADDITIVE value to the core product suite. • It brings IP into the fold that would be hard or impossible to develop in-house. • And this IP makes existing products MORE valuable to customers. The most recent example of an acquisition for revenue is Spiff. • Newly acquired IP doesn't make existing Salesforce products better. • The goal is simply to boost top-line revenue. • Both in ARR from acquired co and future upsell of a complementary product. When "they acquire a company for revenue", it's like you spending on paid ads. Remember the scale at which Salesforce operates. You spend $1,500 to acquire a single, $5,000 ARR customer. Salesforce spends $1.9B to acquire 6,000 customers. I believe Own Company falls squarely into Category 2. Why? 1) Salesforce already owned a huge chunk of the company. Potentially 20%-25% after investing in Series C, D, and E Rounds. So, subtract $380m from the acquisition price. 2) The vast majority of Own Company customers are Salesforce customers. This alone shows the product doesn't expand on what Salesforce can offer. It's a nice add-on to existing customers - again, it's all about the upsell now. Now, I'm not saying this isn't a good acquisition by Salesforce. But it's more conservative than the $1.9B price would imply. Sure, there is potential upside. Own is a provider of data backup & recovery systems. Any product aiding in data quality will benefit from AI tailwinds. The move doesn't help Salesforce remain competitive, though. And those are the moves Salesforce needs to be making now. It's a smart acquisition. A highly safe acquisition. But this does not signal that Salesforce is BACK in the acquisition game. We will need to wait a bit longer for that to become a reality. I believe we'll see it in the next 12-24 months - but this ain't it. __ #Salesforce #SaaS #Data

88

27 Comments

"But our products are too complex for CPQ." I hear this all the time. Truth bomb: Complex products NEED CPQ. Let me share a quick win: A manufacturing client had 10,000+ product variations. Their sales cycle? 3 months on average. We implemented Salesforce CPQ with custom configuration rules. Boom! Sales cycle dropped to 6 weeks. Why? Because CPQ: 1. Eliminates configuration errors 2. Automates pricing calculations 3. Generates professional quotes in minutes Result: More deals, faster close rates. Pro tip: Start small. Pick your most popular product line and build from there. What's holding you back from implementing CPQ? #SalesTransformation #CPQSuccess #salesforce #salesforcecpq

3

Our new CPQ Health Check provides insight into system health, guidance on tackling pain points & ways to optimize CPQ https://bit.ly/3SBT90J CPQ Health Check deliverables include: Current state review Feature utilization assessment Health score Maturity benchmarking Remediation guidance for top pain points Recommended next steps to optimize CPQ for your business Suggested KPIs and measurables #salesforcecpq #revenuecloud

3

We've run highly successful agent design sprints that have found use cases by looking at automations and NCLC Apps in use in an organisation. By defining the underlying workflow, and then redefining them as agents. NCLC AI Agent building tools and teams using a strategic method like agent design sprints is a powerful combination.

3

Are you ready for Salesforce Prompt Engineering? 🏎️ Can you make AI dance to your tunes? 🕺🏼 See what you can do. AGENDA ⬇️ 1. Introduction: AI in Salesforce 2. Prompt Engineering Fundamentals: Lifecycle, Few Shot Learning 3. Advanced Techniques: Scoring-Based & Coaching Prompts, Humanizing AI-Generated Emails 4. Tips & Tricks: Recency Bias, JSON Prompts, HTML Generation 5. Enhancing Effectiveness: Dynamic Locale, RAG (Retrieval-Augmented Generation), File Analysis 6. Grounding Rules: Data Privacy and Security, Ethical Considerations, and Salesforce-Specific Guidelines 7. Q&A Today at 2PM CST. Sign up here https://lnkd.in/g3VBPHDv Event sponsored by GPTfy #promptengineering #salesforce #gptfy #aicloud #genai #salescloud #servicecloud

11

The future of NRR: Will CCOs become the new CROs? (...a 7-figure ARR CCO asked me) A CCO recently asked me, "I've seen CCOs reporting to CROs these days and CCOs becoming CROs. What do you think the future holds? Is this going to be a trend to stay?" It's a fascinating question. Here's what I'm seeing: Companies are laser-focused on improving NRR. But who's directly responsible for it? Marketing, support, CS, AMs, strategic account sales...everyone influences NRR, yet no single executive owns it. That's changing. CCOs are emerging as the "Chief NRR Officers." Why? Because the CCO's ultimate goal aligns perfectly with growing NRR. CCOs are under immense pressure to drive new revenue. However, acquiring new customers is far more expensive than retaining and expanding existing accounts. Putting CCOs in charge of NRR makes strategic sense. But there's another strong candidate for owning NRR: The COO. Retention is a team sport. Every customer touchpoint impacts churn, including product, pricing, sales, onboarding, and support. The COO oversees all these critical functions. They're ideally positioned to drive NRR improvements. Mark my words: Having a dedicated NRR executive will soon become the norm. Will it be CCOs or COOs leading the charge? Only time will tell. I break down the full future of NRR in this video:

9

5 Comments

The Death of the Subscription model .... There are clear benefits from taking a hybrid subscription and usage approach in which customers leverage aspects of both pricing approaches. There were several Salesforce acquisitions in the past decade that came into the Ohana with a consumption model, but SaaS wasn't ready for a shift from the reliability of of the subscription. On average, the cost of ownership flips within four or five years and businesses eventually end up paying more for subscription-licensed software. This, and a marketplace play, is how Black Swans take flight nowadays.

18

6 Comments

I'm looking for CPQ success stories! If you don't have one yet, perhaps consider our Health Check offering. We specialize in CPQ remediations and have quite a few success stories to share. CPQ can be tricky so if yours gets a gold star, do share. I'm sure others would appreciate any tips or best practices. #happytohelp #cloudgiants

26

3 Comments

Ever had someone go rogue and update the connector of a Salesforce integration without telling you? 😱 It can create a flood of new data to start syncing, causing existing fields to get updated, and even trigger unintended workflows to fire. With Sonar Pulse, you'll never be caught off guard again. We send real-time notifications when unexpected field mapping changes to your integrations could put the integrity of your Salesforce at risk. Check it out here 👉  https://lnkd.in/gu6QHGiw #RevOps #SalesforceIntegrations #IntegrationMonitoring #EventMonitoring

12

Watch this podcast between Ben McCarthy (Salesforce Ben) and Marc Benioff on the latest "hard pivot" Salesforce is making to Agentic AI with Agentforce. If you want to find out how this can be implemented in your Salesforce Org today, DM me. "Don't DIY your AI" - Marc Benioff #salesforce #agentforce

12

3 Comments

So many #Startups book office hours with Kevin Maney and I because they are struggling with their #CategoryDesign strategy. 7 times out of 10 they are stuck on a category name. And we tell them to forget the name, focus on their category point of view first. Once you understand the problem you solve, the ramifications of not solving it, and the outcomes of solving it...then the name becomes obvious! Wait for the drop the mic moment! If you're ready for the name...here are some tips:

7

2 Comments

Everything You Want to Know About the November 2024 🟠Boomi Integration and Automation Platform Release🚀 This 📰article recaps the #Boomi Platform November 2024 release and highlights recently delivered product features. For a full list of what’s included in the release, see the detailed release notes: https://lnkd.in/eNmZpQUZ 📝Let’s take a look at the highlights in this release: https://lnkd.in/eqQ6-VDp

3

The extreme arrogance of the #NDIABoard. No business case. But as the #EY report hints at, the total cost of this defective #Salesforce #PACE system could be in the **HUNDREDS OF MILLIONS** of dollars. AND, the #Salesforce deal ends NEXT YEAR. In my recent submission on the #NDISBill, I examined the unknown and uncapped costs of the #PACE system - and challenged the current #NDIA leadership narrative on “the business case”.👇👇👇 https://lnkd.in/dDekWjrG “From the NDIA responses to questions from the Joint Committee of Public Accounts and Audit Inquiry into Procurement at Services Australia and the NDIA. PACE Costs and Business Case… "The business case for PACE estimated a 10% reduction in cost-to-serve, or a reduction of 1.8M hours from the time it takes staff to interact with the former CRM. These savings are being reinvested in increased participant contact. That is, PACE reduces the amount of time that staff and partners spend interacting with the CRM, meaning they have more time to spend working directly with NDIS participants.” ➡️ Something doesn’t add up - a big problem for an “actuarial business”. Was there NOT a business case, as stated by the #EY report. Or WAS there a business case, as claimed by the #NDIA in evidence to questions from the Committee. Both answers cannot be true. Over to the #ANAO to investigate further in their audit on the #NDIABoard. On behalf of folks pursuing this story for years - through various Parliamentary inquiries, administrative processes and forums - with respect, #BillShorten is not the hero. The #FOI requesters are the heroes. Well told InnovationAus.com More to come. #RoboNDIS #ClassAction #RoyalCommission Mark Sweeney Mark Toomey Tony Ridley, MSc CSyP FSyI SRMCP Karen Kline Paul Flintoft Graham Taylor Samantha Connor Tara Hannon Renee F. Muriel Cummins Georgia van Toorn Peter Gregory Shirley Humphris Vinod Ralh Jordon Steele-John David Pocock Rick Morton https://lnkd.in/didGb3nj

19

5 Comments

18% of developers struggle with building integrations with other platforms according to a recent survey by SF Ben. So I spent 20 hours building a Jira ➡️ Salesforce integration. This is a great demo repo that showcases how to use: ❎ Named Credentials ❎ Third-party callouts ❎ VF to run apex code ❎ Async apex to sync data on an interval ❎ LWC from an action to capture user input ❎ Unlocked Packages to distribute the code You can view the repo on how I performed each of these tasks. #salesforce #salesforcedeveloper #salesforceintegration

228

9 Comments

There is a better way to do 'Approval Workflows' & avoid the disconnect of siloed communications. Watch these CPQ Pro Tips from Ryan, our Partner at Thriviti (great series!) DealHub.io CPQ! #Salesforce #ApprovalWorkflows #GuidedSelling More in the series here > https://lnkd.in/dkjFsdK9

289

28 Comments