Latest / Inside Commerce: Ecommerce Strategy, CX and Technology Podcast / EP201: How Salesforce Commerce Customers Should Approach A SiteGenesis Migration, With Liam Downes & Shivko Rusev from Tryzens
Transcript
- 0:02Thanks for listening to the Replay from podcast sponsored by
- 0:05Crown Peak and Elastic Power from Hosted by me, James Get and
- 0:07Paul Rogers. We've felt a lot of time and
- 0:09effort into bringing interesting guests and great useful content
- 0:12all for free. Help us keep it that way.
- 0:14Let other people know about the podcast so we can get some new
- 0:16listeners. Refer us to your friends, repost
- 0:20our LinkedIn and and Twitter post.
- 0:22That really does help amplify reach and the best thing you can
- 0:25do is give us a rating of wherever you are listening or
- 0:28watching today. So let me introduce our episode
- 0:30and our guests and then we'll crack on.
- 0:31So the topic today is how Salesforce commerce customers
- 0:36should approach and can approach migration from site genesis to
- 0:40more modern versions of Salesforce.
- 0:42And who better to talk to than one of the leading global Si's
- 0:45Trojans? I've had a lot of fun over the
- 0:48years working on various projects and they've got a
- 0:51massive amount of experience and they're not just experiencing
- 0:53sales for as well. So they do build another
- 0:55platform. So they've got experiencing
- 0:57migrations from other platforms to Salesforce and also from
- 1:00Salesforce older versions to the newer format.
- 1:03So first of all, let's introduce Schiff Garusseff who's the SVP
- 1:07for the Salesforce practice based over a Bulgaria, I
- 1:09believe. Good.
- 1:11Well, it's just 10. Good afternoon.
- 1:13How are you doing, Sir? I'm doing well, James.
- 1:18Pleasure to be with you and Paul today.
- 1:21Really appreciate you joining us.
- 1:23Do you want to give people a little bit of an introduction to
- 1:26who you are and what you do at Trizents?
- 1:30Of course. So as I mentioned, I'm Senior
- 1:34Vice President of the Salesforce practice at Trizents, so I'm
- 1:37responsible for the technical delivery of our Salesforce
- 1:40projects across the globe. And I'm also leading some of the
- 1:44strategic investments in the Salesforce ecosystem Trizons is
- 1:50doing. So all of the accelerators that
- 1:53we've built and the quick starts throughout the years together
- 1:57with our partners at Salesforce, excellent.
- 2:00Thanks. And also and welcome to Liam
- 2:02Downs, who's the Director of Strategy is Success and also
- 2:06backgrounds working in retail e-commerce with brands like The
- 2:09Body Shop, who I would imagine quite a few people have come
- 2:12across in shopping. So hi Liam, how are you?
- 2:14Do you want to give a bit of an intro to yourself and your role?
- 2:16And maybe give the people who haven't worked with Trizens for
- 2:19a bit of a flavor for where Trizens fits and what your
- 2:22expertise is? Yep.
- 2:25Thanks, James. Yeah.
- 2:27So I'm giving it a little bit of a a headline intro to me there.
- 2:31So I've been with Trizons for three years now.
- 2:34And so I look after all of our in life customer strategy and
- 2:39success. I've got getting on for now kind
- 2:43of 17 years worth of experience working within digital in in the
- 2:47retail space on the other side of the fence.
- 2:51So having worked with many agencies like Trizons in the
- 2:54past and. I guess my, my sweet spot is
- 2:57really around digital transformation and supporting no
- 3:01more traditional and startup brands in terms of navigating
- 3:05their their digital journey. And and then with a bigger focus
- 3:09on internationalization as well and more recently Triesens for
- 3:14anyone that that that doesn't know us or hasn't heard of heard
- 3:17of us in the past. So we're an international
- 3:20digital agency and we were born out of being at, you know, an
- 3:24SI. And so for anyone who's been in
- 3:26the industry for a while will recognize that term, but we
- 3:30really are a technology agnostic digital agency where we're
- 3:35supporting customers in making the right technology choices
- 3:41from an end to end perspective and generating best in class
- 3:46customer experiences. And So what what does that mean
- 3:49in practice? You know we are supporting our
- 3:52our clients in making the right. Technology decisions and at
- 3:57whatever level that might be, you know, full programs of work
- 4:00around digital transformations down to smaller and technology
- 4:04choices, but also working with them and this is probably the
- 4:08more important pieces, is focusing on customer and what
- 4:12customer experience needs to be expectations, How do you meet
- 4:16them? Because technology, at the end
- 4:17of the day, is a facilitation, a method for us to be able to
- 4:22deliver. A best in class customer
- 4:24experience. So it's supporting our customers
- 4:26and bringing back to that that question I guess in terms of
- 4:32what does a best in class customer experience look like
- 4:35and how do we bring in a technology architecture and
- 4:39experience to deliver that. As I mentioned, we're a global
- 4:43agency, so we have multiple and. Delivery centers, we have
- 4:48headquarters in the UK and Australia, so we're able to and
- 4:52America now. So we have a big focus in the
- 4:54States and so we're able to really scale our partners and
- 5:00clients and across the globe no matter where they are.
- 5:05Great. So I'll ask the first question
- 5:08and just to set the thing a little bit for listeners that
- 5:10maybe. Is kind of well versed in
- 5:13Salesforce and the kind of ecosystem.
- 5:17Can you just give us a bit of an overview on what site Genesis is
- 5:20and kind of why Salesforce have kind of moved away from it and
- 5:24introduced additional options? Yeah, thanks Paul.
- 5:29So Site is actually the reference code application built
- 5:34by a company called Demander in the past which was acquired by
- 5:38Salesforce back in 2016. So this code architecture has
- 5:44actually gone through several iterations.
- 5:46So the original version of side genesis was based on so-called
- 5:51pipelines which are still popular across the Salesforce
- 5:57community which is kind of a mixture of UML based diagrams
- 6:02and server side JavaScript. Code which are being parsed by
- 6:06Arena Engine and transformed into a JavaScript code which is
- 6:09running on the application servers, so the cloud
- 6:12infrastructure, Salesforce. So this is the legacy kind of
- 6:16version of the code architecture.
- 6:19And then we have CYT Genesis which was introduced in 2016 and
- 6:28obviously there is. To newer versions.
- 6:31So SFRA is most probably one of the most popular one which was
- 6:36introduced in 2018. So the Storefront reference code
- 6:39architecture which introduced a lot of improvements around
- 6:44mobile first experience, performance, extendability and
- 6:49so on and so forth. And of course the latest 1, the
- 6:53composable storefront architecture, which we're going
- 6:56to cover most probably a little bit more details further down
- 6:58the conversation. Great.
- 7:02And then so the next question. So I guess I've had a number of
- 7:07clients that have been on Salesforce where they've been on
- 7:10site genesis and they've been kind of pushed towards.
- 7:13Either SFRA or the composable route, which I think makes
- 7:17complete sense if you want to get the most out of the
- 7:19platform. And James and I work on someone
- 7:22at the moment who run site Genesis.
- 7:24And I guess one of the things that I don't think is
- 7:29necessarily clear around Salesforce is the pros and cons
- 7:34of actually staying on site Genesis.
- 7:36So in terms of kind of like you know, new functionality within
- 7:40Salesforce and stuff like that like.
- 7:44Obviously that might be a pro for investing in the move away
- 7:48from CYT Genesis, but what's your view on as an SI partner on
- 7:53how people should be thinking in this scenario?
- 7:56Is there a route forward with cygenesis and what are the pros
- 7:59and cons of actually staying on it for a period of time pre
- 8:03having the budget available? Yeah, of course.
- 8:07So side joins, this is definitely a legacy code
- 8:12architecture now within the sales force world.
- 8:14So there are no new releases. I think 2021 most probably or
- 8:222022 most probably must have been the last release, which
- 8:25doesn't necessarily mean that. You're not getting any of the
- 8:29new features, so obviously there are seamless platform upgrades
- 8:34and you get all the latest features which are available in
- 8:38the Salesforce Commerce engine. Most probably for some of the
- 8:42front end features that Salesforce are introducing to
- 8:46SFRA, you would need to do a bit of work in terms of customizing
- 8:50your your front end. So for for customers there will
- 8:55be an additional work to actually benefit from.
- 8:58Everything that is being released within SFRA world for
- 9:01example is the thing on side Gen. is still a good option for
- 9:08customers. So I think so yes, because you
- 9:11can still do pretty much everything on on side gem, so
- 9:17customers can continue to improve their performance,
- 9:22continue to improve their customer stress and so on and so
- 9:24forth. So if they have reached to the
- 9:26point of. Being limited by what they can
- 9:30do with the code architecture and the improvement that they
- 9:33can make out, the agility that they have with this particular
- 9:38version of the architecture, then they definitely need to
- 9:40consider moving on to either SFR or Composable.
- 9:45Crown Peak enabling organizations to build
- 9:47meaningful digital experiences for everyone, everywhere.
- 9:51Engage your customers with our content management system.
- 9:54Reach your entire audience with our digital accessibility and
- 9:58quality tools, and grow your brand with our product discovery
- 10:02solution. Find out more at crownpeak.com.
- 10:06Did that answer the question? Yeah, absolutely.
- 10:09From my perspective, yeah, I think that's a good kind of
- 10:12overview leading into some of the next questions.
- 10:15I mean I think pulse part is something that I missed to chat
- 10:17is what we usually advise our clients is to try to sweat the
- 10:23asset as much as possible or as to try to get the most of side
- 10:27Jen before they consider migrating to the New York color
- 10:30picture. And I think what we, what I'd
- 10:35add into that is that I think this is where the role of the
- 10:39the good partner comes into play in a lot of the discussions that
- 10:43we have. With our clients and there are a
- 10:46lot of discussions going on at is very point around site
- 10:50genesis and what is the you know should should we stay, should we
- 10:53move you know what the options ahead of us.
- 10:57And I think a good partner will always help you navigate that,
- 11:00but help you understand where the benefits are and you know,
- 11:05at what point do the minimal gains that you're able to
- 11:09achieve with the technology become.
- 11:13I guess I'm viable from a commercial perspective and it
- 11:17requires you to make that jump in technology choices.
- 11:23Yeah, I think it's good advice to give people is is don't jump
- 11:26and invest in a big project until you fundamentally need to
- 11:29and plan for that carefully because it is, it is a lot of
- 11:32effort and often people don't sweat the assets they've
- 11:35invested in enough before they make a leap.
- 11:38Leads me on to to to to a related question is we we all
- 11:42know the markets evolving in terms of of technology, the the,
- 11:46the tech stacks that people use in the greater need for that
- 11:49interoperability and the ability to isolate and retire far more
- 11:53easy than used to be the legacy monolith space which where it
- 11:56would be, yeah a couple of years before you could properly retire
- 12:00a system and plug other stuff it and obviously sales forces made
- 12:03some of these moves with SFRA with its move into composable
- 12:08and some that make retailers review and decide where they're
- 12:11going. Love to hear from your
- 12:13perspective, working with a lot of different businesses and
- 12:16different platforms, what type or size of business is best
- 12:19suited to those modern sales force solutions and why?
- 12:22And where do you think that sweet spot is?
- 12:30Right. So what type of businesses from
- 12:34my perspective I would say that any.
- 12:37Business could actually get on board onto Salesforce Commerce
- 12:41because it's most probably the best solution on the market.
- 12:47And of course, maybe this more and less digitally mature
- 12:53businesses will struggle to manage the platform, but still
- 12:58they're a lot of tools that are actually easy to use within the
- 13:04platform and. Even for those type of
- 13:07customers, it will be easier, not easier, but easy to
- 13:12understand how to work with the platform.
- 13:14So I would say that it's suitable for smaller businesses
- 13:18as well. But certainly what we see in the
- 13:20market is that those businesses usually prefer other platforms
- 13:25like Shopify or Bitcoin, but we do have some.
- 13:31Accelerators built for, for those type of customers, we have
- 13:34managed services options to actually help them run their
- 13:38business and operate on, on the platform which makes Salesforce
- 13:41suitable for for them as well. Of course we we see more midsize
- 13:48like and upper midsize lower enterprise customers go on to
- 13:53Salesforce as well as large enterprises.
- 13:56So actually that's that's where Salesforce.
- 13:59Constraint is in those kind of two segments of the market.
- 14:06So yeah, I think that will be my take on this then.
- 14:09Do you wanna jump in? Yeah, I think what I'd add to
- 14:12that is that and again a frequent conversation is not
- 14:19necessarily size of business which dictates kind of that
- 14:23technology decision. I think it's what are your.
- 14:29Objectives and goals as as as a business and what how is your
- 14:34business structured and I'll I'll go into a bit more detail
- 14:38in that because it it really did to Salesforce really comes into
- 14:43its own and has a sweet spot where we have clients that have
- 14:48aspirations to grow on a global level and because the the
- 14:53technology enables that really easily and and that is really a
- 14:57sweet spot so. When we're having conversations
- 15:00with with new clients and existing clients on on these
- 15:03technology decisions, if if there is a priority list and
- 15:08priority high up on that list is internationalization and
- 15:13internationalization at pace with the capacity to really
- 15:17scale and and have the I guess the configurability and
- 15:24functionality to scale the business equally across each
- 15:27market globally. That's where Salesforce's sweet
- 15:30spot is it. It really is because we know
- 15:34that we're able to build a build a reference architecture within
- 15:37Salesforce that enables that global rollout for our clients
- 15:41and that's where we see the benefit and growth trajectory
- 15:47enabled by Salesforce for, for, for clients.
- 15:50I would say there the other technologies in the market are
- 15:53catching up for sure, but the gap is still there and.
- 15:58It's yeah that that's the sweet spot for me is you know if I
- 16:02have a business that really wants to scale globally and and
- 16:07I've got a you know a three-year plan in place or a five year
- 16:09plan in place to be able to do that.
- 16:12And I have no complex, certainly if I have a complex business
- 16:18structure with you know, various different entities spread across
- 16:21the globe, you know Salesforce does that easily, it just does
- 16:26it. Elastic Path is on a mission to
- 16:28break through the barriers that prevent commerce leaders from
- 16:31delivering extraordinary shopping experiences.
- 16:34Both business and tech teams are able to innovate on their own
- 16:37terms, fully embrace composability, and in turn,
- 16:41never compromise on what's possible.
- 16:44Learn more at www.elasticpath.com.
- 16:49Yeah, I I can answer that point about having the reference
- 16:52architecture there to enable like that consistent way of
- 16:54going. I I think I'll challenge on the
- 16:56speed and say that there are platforms that are false
- 16:59speedier to launch internationally, but you have to
- 17:01take compromise with it. And I think this the the hearing
- 17:05lies where what what size and and structure of business and
- 17:08how complex is it and what appetite do you have for those
- 17:11compromises and therefore having to plug in more additional
- 17:14things to to resolve them versus having the capability in the
- 17:17platform. It's always interesting why
- 17:19there's no such thing as a perfect platform.
- 17:22But one thing I'd love to, I'd love to dive into more about the
- 17:26composable stuff actually because yeah everyone's everyone
- 17:30talks about composable and I think a lot of time composable
- 17:33doesn't land with business teams because it just sounds very
- 17:35nebulous even though actually it's a strategic way of thinking
- 17:38rather than an architectural solution and and it's about
- 17:40giving flexibility and sometimes I think that the message doesn't
- 17:44land. So what I'd love to for you guys
- 17:46as having a lot of knowledge and expertise around the Salesforce
- 17:49ecosystem is drilling into that where they're going with their
- 17:53composable approach. Can you summarize the people
- 17:55who've come from that more legacy view of what was demand
- 17:58where then cite Genesis on Salesforce?
- 18:01What how does the composable bit fundamentally differ to that,
- 18:04and what are the implications to an e-commerce team?
- 18:12Right. So in in terms of the
- 18:15differences, so obviously the composable storefront solution
- 18:20is fundamentally different because it's a different
- 18:23architecture. So headless slash composable
- 18:27architecture. So headless architecture means
- 18:31that the front end is decoupled from the back end usually, and
- 18:35composable means that more of the components that we usually
- 18:38see. Kind of plug them into
- 18:40Ecommansion or further decoupled so you have multiple services
- 18:44which are connected to the front end through APIs.
- 18:48So that's the fundamental difference.
- 18:50So in SFRA or side Gen. you have everything kind of stitched
- 18:55together in one of the architectures.
- 18:57So the front end is titled to the back end, which drives its
- 19:02own complexity. Obviously when you're doing
- 19:05changes to the back end or to the front end, you have to
- 19:07deploy the code together. Which means that everything
- 19:10needs to be planned very well upfront to ensure that there are
- 19:16no disruptions to business processes.
- 19:18Within Composable, it's obviously very different.
- 19:21So you can have deployments across the front end, across the
- 19:25back end, which enables customers to innovate faster and
- 19:30on the front end and build personalized customer
- 19:32experiences easier. So we are our customers who have
- 19:37migrated onto Composable. Have actually gone from the
- 19:41client every couple of weeks to the point every day, which is a
- 19:45huge benefit because it's speed up the innovation and mostly
- 19:51they can migrate from working for primarily with a partner
- 19:58like Treasons or external agencies into building their
- 20:03own. In house development teams to
- 20:06enable this relation to happen in house to enable the brand to
- 20:10control this customer experience and I think there was a bit
- 20:16more. So can you repeat the second
- 20:20part of the question? Yeah, that's really interesting.
- 20:22Actually I've got a sub question related to that because one of
- 20:25the one of the not criticism, one of the issues people have
- 20:29faced in the past on legacy version sales forces.
- 20:32It does require more QA release work because of the way it's
- 20:36it's architected, so you tend to spend a bit more time getting
- 20:39those releases out. It is this in in in this
- 20:42commercial place. I'm assuming then that actually
- 20:44from a developer point of view, there's less work on the
- 20:47releases and it's a speedier process to get code committed
- 20:50and out. Is that, is that a fair
- 20:52assumption? Absolutely.
- 20:57Of course you still have those quality gates in place, but
- 21:03everything happens a lot, all quicker because you can actually
- 21:07focus your attention on small pieces of functionality and just
- 21:14kind of introduce more pieces of functionality quicker.
- 21:18So that this is the bit that actually reduces the time spent
- 21:21on testing. So it's not a huge release where
- 21:24you need to test 1015 features at once, which should then
- 21:30introduce regression issues and so on and so forth.
- 21:33Of course, we encourage our customers to focus on automating
- 21:37the whole process through unit testing, through automated
- 21:41functional testing, which are being executed across the
- 21:44different instances just to make sure that quality is intact.
- 21:53Great. And I guess the big elephant in
- 21:56the room around site Genesis is the cost of my grating.
- 22:04So we've had I think James and I have both worked with self lost
- 22:08brands in the past that have been quoted kind of you know
- 22:10between half a million and 1.5 million before you even start
- 22:14them thinking about new features.
- 22:16And I think you guys obviously work Magenta and Adobe in the
- 22:19past and have seen. Of what happened with the M1 and
- 22:22two migrations and I think you know we've seen you're like
- 22:26Salesforce has definitely seen a lot of brands kind of move away
- 22:30due to the cost essentially being directly comparable to a
- 22:33re platforming project or even sometimes higher.
- 22:36And what makes this migration so expensive and so complex?
- 22:41Like, yeah, what is it that is essentially being done when
- 22:44you're migrating to an SFRA or going down the composable route,
- 22:52right. So if we start with side, Jan to
- 22:57SFRA, so and the cost that you have heard is not unusual,
- 23:03especially if we're talking about starting everything from
- 23:07from scratch and fully migrating onto a new color architecture,
- 23:12which most customers prefer because they usually try to
- 23:17leave the technical depth that's been piling up throughout the
- 23:20years behind. So they want to start from the
- 23:23kind of black piece of paper and then start building up
- 23:27everything on the solid foundation.
- 23:29So that's that's where the higher cost comes in.
- 23:33So it's pretty much starting everything from from scratch,
- 23:36right. So it's pretty much moving on to
- 23:40a new platform. And to be fair, we usually apply
- 23:45for that approach because there is a different path.
- 23:49Also, so you can do a gradual migration from Sidegen and SFRA
- 23:53because obviously both code architectures can run
- 23:56simultaneously in the cloud. But this sometimes is a bit
- 24:01challenging because obviously there is a fundamental
- 24:06difference between the code architectures.
- 24:08Some developers are pretty used to work with Sidegen, others
- 24:11with SFRA. So just running those two code
- 24:14architectures at once could be challenging, could lead to some
- 24:17unpredicted kind of behaviors on the storefront, issues that are
- 24:21difficult to pinpoint and so on and so forth.
- 24:23So we we usually advise customers to go down that road.
- 24:26But of course if cost is the inside and factor, which in most
- 24:30cases it is right there, there is a path to gradual migration
- 24:36from side Gen. to SFR. If we're talking about
- 24:39composable, I think most probably that the majority of
- 24:47the budget gets into the fact that a lot of things are done
- 24:51differently between the model and the composable architecture.
- 24:56And there is a bit of investment from customers that has to be
- 25:03focused on making sure that everything works as it used for
- 25:07before in the model architecture.
- 25:09Obviously there are some differences around how we match
- 25:14SEO metadata and URLs and side preferences found like API keys
- 25:22and so on and so forth. So this is where we come in and
- 25:26our accelerators that we've built for our customers to just
- 25:29speed up the process and reduce the cost for our customers who
- 25:33are migrating into Composable. Great.
- 25:39And then Liam, I guess this one might be just one for you to
- 25:42answer. So if you're a brand and you've
- 25:46obviously worked in house for retailers and brands and past
- 25:50and you're on site Genesis and you're starting to look at your
- 25:53next move, what how do you think, what do you think the
- 25:57wrong approach is obviously is a considerable investment like
- 26:00what do you think the right kind of first steps are?
- 26:03Yeah. Yeah.
- 26:04I just, I guess just to add on to the point that Jivcos just
- 26:08made. I think the one thing and that
- 26:10I'd add into the the approach of composable storefront certainly
- 26:14detaching the front end anyway as as a whole is that it's
- 26:19become a lot more accessible and and less cost prohibitive.
- 26:23And so one of the things that we're certainly starting to talk
- 26:26to clients about now, which plays into into your second
- 26:29question is that. The business case is a much
- 26:33easier one for us to, I guess, validate with a proof of value
- 26:38because of the hybrid deployment process that we can go through.
- 26:42So we're able to build a business case around one or a
- 26:49few pages across the site or particular sites.
- 26:53So if I take the example of 1 particular client we've just
- 26:58been launching composable storefront with.
- 27:01We started off by saying let's let's create a proof of value
- 27:05for the US and which is much more accessible from a from a
- 27:11cost perspective. And we're not going to go into a
- 27:14big four week platform project and we'll we'll test it on on a
- 27:22smaller smaller base than going out to our entire, our entire
- 27:30site. And by doing that, we're able to
- 27:33get in quickly. We're able to get in a much
- 27:35lower price base and we were then able to prove that business
- 27:41was able to see Okay. This is actually going to
- 27:43provide value and these are the KPIs that I'm able to impact and
- 27:48we're seeing commercial and value out the back of it, which
- 27:52then opened the door for us to be able to move the project
- 27:55across across the rest of the architecture.
- 28:00I think to tackle your your question kind of head on, if I'm
- 28:05if I'm sat on the client side today and I'm you know I'm a
- 28:08site genesis customer, it really comes back to you know what are
- 28:12my objectives and what are my objectives as a business and
- 28:17what is my current status with site genesis.
- 28:20Do I feel, you know, going back to the original points we're
- 28:23making, am I getting the most out of the platform as it
- 28:26currently stands and do I have? No, the the operational and team
- 28:34in place on on my side to be able to deliver it right because
- 28:39I mean in the scenario moving from site GEM to SFRA, having
- 28:44SFRA as a technology does not make my business perform any
- 28:48better. But let's let's be clear about
- 28:51that. It it can enable my business to
- 28:54perform better, but just by switching it on does not.
- 28:58Just do that, it's not a flick of a switch.
- 29:00So do I have the operational capabilities to make use of all
- 29:04of the functionality and configurations and trade it hard
- 29:09to be able to just squeeze the value out of it.
- 29:12And for the business case that it's going to take to go through
- 29:15a REPLAT for me exercised to go through that because I think
- 29:21that's the key for me is how am I going to produce value.
- 29:25Out of any new types of technology, you know if you're
- 29:30putting a gun to my head, I would certainly be looking to go
- 29:33down a composable route because of that point around it being
- 29:37more accessible. And I think you know had we been
- 29:40having this conversation four or five years ago around you know
- 29:43as a business, if I'm a mid to mid sized business, do I want to
- 29:47go down at composable headless route, It would have been much
- 29:51less accessible, it would have been.
- 29:54And more expensive to achieve. I think that the implications
- 29:58that it would have on my business and my team and all
- 30:01costs to actually operate it, the complexities would have been
- 30:04much higher. Whereas now that you know the
- 30:08level of entry is is is much lower and I think the the Kpi's
- 30:13that most customers are looking for in terms of around front end
- 30:17performance and the ability to influence and impact the
- 30:21customer experience. At greater velocity and
- 30:28frequency is greater than going down a Nessa for a route as an
- 30:32example. And so yes, it is kind of a long
- 30:36way of saying if I'm sat as a client today on site Genesis and
- 30:40I feel that I am at a point where I can no longer take that
- 30:44technology forward, I would certainly be looking at going
- 30:47down the composable storefront ring.
- 30:51It's, it's a noise, Yeah, family job in here.
- 30:55Yeah. Sorry, James, I was going to say
- 30:59like so going down the composable path is important if
- 31:05you're looking to just optimize the way you create those
- 31:11personalized customer experiences and obviously
- 31:14innovate faster. Whether you whether you want to
- 31:20take a ball some platform components and and plug in some
- 31:23external systems into into your architecture or do something
- 31:29else that doesn't really require for for you as a business to to
- 31:33go down the composable Rd. because you can do that with
- 31:36side units. So for example if you want to
- 31:39plug in a headless search provider or headless CMS
- 31:41provider doesn't necessarily mean that you you need to go
- 31:44down the composable path. So it it as As for Leon's point,
- 31:48the most sort of most important consideration is what are the
- 31:52business priorities, right? And the business leaders who are
- 31:56driving digital transformations within the organizations need to
- 32:00define their priorities first, and then tie the right
- 32:03technology to the to the priorities.
- 32:07Yeah, that's really nice points. I love the fact that you focused
- 32:10on operational readiness because I think the change management
- 32:13piece is totally underestimated in a lot of projects by client
- 32:16teams of we've got great shiny new care.
- 32:19But what resource wise do we need to adapt to?
- 32:22What are the new processes that we should do to to work more
- 32:25effectively? What are the tool, what are the
- 32:28tool limits introducing where we might not have an expert in the
- 32:30business and we either need to get an Excel specialist or we've
- 32:33got to bring somebody in. So yeah, it's a really nice
- 32:35point because those decisions aren't isolated fundamentally
- 32:39they they've got to happen hand in hand.
- 32:42It leads me onto nicely onto the question around.
- 32:47So you've the e-mail that you said about Compose with you had
- 32:49to, you were forced to know you call us the last because that's
- 32:52more future proofing. I know that Tries has built a
- 32:54front end accelerator for for Salesforce composable solution.
- 32:59I think this would be really useful time to to talk people
- 33:01through what is your accelerator, what what does it
- 33:04do and what are the benefits for Salesforce customers, right.
- 33:13So yes, we we have our Trizons composable storefront
- 33:16accelerator and actually when Salesforce introduced this
- 33:21concept of composable storefront, we we started
- 33:25exploring it that that was I think back in 2021, most
- 33:29probably Q3 or Q4. And we identified quite a few
- 33:35gaps which were very obvious. But I think that the big one for
- 33:39us is the ability to manage content through the platform.
- 33:46So Salesforce is very popular for the content management
- 33:52capabilities which are built in within the platform.
- 33:54So the people who are within the Salesforce space all about pages
- 33:58are and all the content assets and slots and the content
- 34:01scheduling so on and so forth. So when Salesforce originally
- 34:05introduced their composable storefront, those capabilities
- 34:09were not kind of introduced to the decoupled front end.
- 34:13So we started speaking to our customers, we started speaking
- 34:16to prospects. So this was a big one for them
- 34:18and to be honest, some of them were kind of finding this a
- 34:23barrier to even think about headless, you know, so because
- 34:27usually in headless implementations you need to go
- 34:31and implement the headless CMS for example, which we all know
- 34:35that could be a costly exercise. So that's why in the first
- 34:41iteration of our composable storefront, we actually focus on
- 34:45covering this large gap for our customers.
- 34:49And what we managed to achieve is like we introduced all the
- 34:53capabilities that were available within the moment that
- 34:57architecture. So customers have all the pages
- 35:01are components that they're used to work with.
- 35:03They have the content scheduling, they have the
- 35:06personalization as well across the different pages, which was
- 35:10really important and actually help us gain more visibility and
- 35:15in the Salesforce space and be one of the very first Salesforce
- 35:19partners to to launch composable storefront.
- 35:24And we were actually introduced at Dreamforce 2022 as one of
- 35:29four launch partners for composable storefront and
- 35:33obviously we, we continue to invest in and iterate further
- 35:37with our accelerator. So in version two, we have
- 35:42actually focused on three key areas as well.
- 35:46So the first one is to implement the best in class UX for kind of
- 35:53standard integrations which normally all customers go
- 35:57through just to enable the quicker time to market.
- 36:00So functionalities like the cookie, constant messaging like
- 36:05the other research store locator, the Google Tech manager
- 36:07integration with J4 setup which proved to be quite challenging
- 36:12for some customers. And this all saves time and
- 36:16money for our customers and enable them to go faster and
- 36:18actually focus on the customer experience then the
- 36:22composability element as well. So we wanted to enable more
- 36:26chance going down the composable, but to actually have
- 36:30some of the components decoupled from the architecture or rated
- 36:33from the commerce engine. So like the search in March we
- 36:37partnered with Olgoda, so we do have Olgola integrated into our
- 36:42composable store accelerator. And then the third focus area
- 36:46was continuous integration and deployment back to our point
- 36:50around quality and setting a solid foundation for our
- 36:54customers to start innovate within our composable
- 36:57architecture. So we implemented A framework
- 37:00and we have around 80% coverage of unit tests and front and
- 37:06functional tests. So that we enable our customers
- 37:08to actually start from the solid foundation, make sure that
- 37:14quality remains intact. But if I have to summarize,
- 37:22because that's all of the information, we're primarily
- 37:25focused on covering the gaps and also enabling our customers to
- 37:30go to market quicker with a lower investment.
- 37:35Right. And that kind of leads on to the
- 37:37next question, which is quite, I guess a bit related to some of
- 37:41the comments you've made, Liam, around particularly like the
- 37:46headless side of things being more accessible and a bit more
- 37:50like kind of widely integrated. What do you see as the kind of?
- 37:57Operational, in fact going down the composable route in terms of
- 38:01kind of capabilities in house for a retailer or brand.
- 38:06So what kind of skills and resources do you think a
- 38:11retailer or a brand needs if they are to invest in kind of,
- 38:16you know, get the most out of the composable stack?
- 38:23Yeah, I mean I'll let jive code come on to some of the
- 38:26technical. Skill sets, but I think the the,
- 38:28the key one for us and again like this is a, it almost
- 38:33becomes an enabler I think in terms bringing it in because
- 38:36operationally you can still lean on a partner like us to provide
- 38:42the resources to be able to run it.
- 38:45But I think what it enables from a from a skill set, perspective
- 38:49and capability, what would then end up in making kind of.
- 38:54Key operational changes if you like on on the client side is
- 38:58that ability to to manage the front end on on on the client
- 39:05side and to to to greater effect and impact.
- 39:08So what we're definitely seeing is more clients moving to having
- 39:12kind of that front end React skill set internally and because
- 39:19it gives them the control over the CX element of the site and.
- 39:24And it becomes as you scale it becomes more cost effective.
- 39:29Certainly if you are running multiple, you know,
- 39:33personalization streams with multiple testing streams and
- 39:37you're wanting to make lots of change at a higher velocity, it
- 39:41makes sense to bring that resource in in house and have
- 39:47that skill set available to you. And that's certainly certainly
- 39:51where we're seeing the biggest operational changes where you
- 39:53know in the world of monolith we would you would need a sales
- 39:58force developer with with your SI and who would be managing
- 40:03that that workload in most cases and not in all cases but in most
- 40:08cases we're certainly seeing that shift out now where where
- 40:12clients are looking to bring that resource in house the for I
- 40:15guess from a from a technical. Operational side, there will be
- 40:19other bits, but certainly from my perspective that's the main
- 40:22shift that we're seeing across clients.
- 40:26Yeah. So from a technical point of
- 40:30view, as I mentioned and certainly the skills that are
- 40:35required are in the reactive space.
- 40:40So our customers are. I started looking for React
- 40:45developers to bring in house and back to my point are there like
- 40:48this enables them to change their relationship with the
- 40:52vendors. So obviously do more things in
- 40:54house and decrease kind of the dependency on the service
- 40:57integrator or the digital agency and like we see how those
- 41:04engagements change across our client base, so.
- 41:09People rely on us more for the Salesforce skills rather than
- 41:12the front end skills currently just because they can now
- 41:17acquire those skills and build a new house development team
- 41:21because the pool of developers is definitely larger.
- 41:24While the Salesforce skills are still required, those niche
- 41:28skills are usually followed across the partners and in terms
- 41:32of operational most for the. Our clients usually need are
- 41:40strong product owners or product managers who do understand how
- 41:46the architecture changes with composable and how the front end
- 41:51interacts with the back end and the APIs and all the changes
- 41:58that are happening across the text stack and the integrations
- 42:01because of the fact that you're migrating on the composable
- 42:04architecture. So that's really important
- 42:06because. They can actually make decisions
- 42:08and plan features and functionalities better because
- 42:11they actually understand what needs to come first from the
- 42:14back end and so that the front end could be built on a later
- 42:18stage and done by the house development team.
- 42:23In terms of for the support on monitoring and maintenance,
- 42:26things are changing as well, but that's where we usually step in
- 42:29to support our customers to ensure that they continue
- 42:32monitoring the performance of the front end and back end.
- 42:36As they used to previously Yeah I think that's that that's good
- 42:40point see I think is that that product owner role definitely
- 42:44needs to have the the understanding and experience of
- 42:48the of the new architecture and so that they're they're able to
- 42:56to support the strategic direction of of of the product
- 43:00and the and the architecture. I think that's that you know
- 43:02that's the key one because they they're going to be leading that
- 43:04road map and working with with a partner like us to to drive that
- 43:10and the you know the the architecture is quite different
- 43:15and the technology is different and the focus areas for them
- 43:17will be different. So having I guess the training
- 43:20in place to to either you know, either elevate existing teams to
- 43:24be able to take that on or to bring different resource in that
- 43:27has that skill set and capability is, is, is key.
- 43:32Cool. Actually that's been really
- 43:33useful. I've I've really enjoyed like
- 43:35listening to your perspective because obviously you work with
- 43:37a lot of different businesses who come at this with different
- 43:39perspectives and different business needs.
- 43:41So it's always interesting to the SI view there.
- 43:45There's a lot of people out there in the Salesforce world,
- 43:47Salesforce merchants at various stages of maturity or various
- 43:50stages of their project life cycles.
- 43:52If they want to reach out and probe on any of this or if
- 43:54they've got a potential project challenge they want to to throw
- 43:58at you, how do they reach out What we have a website you would
- 44:10be won't be sufficed to hear. So there is there are contact
- 44:13forms on the website that you can use or you can get in
- 44:17contact with either Jivco or myself by LinkedIn and will be
- 44:21able to support with any questions.
- 44:23And we have a sales team, so Paul Green in in the UK who will
- 44:27pick up any of those questions. But ultimately to to reach out
- 44:31in all of the normal channels and either by the by the website
- 44:34LinkedIn, we'll share all of our contact details with you guys.
- 44:40So if anyone wants to come direct to you, feel free to pass
- 44:43on our details and we're more than happy to have a
- 44:45conversation, coffee, lunch, dinner, beers and whatever is on
- 44:50the menu. So anyone that wants to kind of
- 44:53pick our brains. I said, yeah, I'd like all of
- 44:55those. That sounds good.
- 44:57Now that's good. It's going to say that we are
- 45:01available at a point in time so. We would love to have a chat
- 45:06only that's what is what it takes.
- 45:09So we we we're happy to consult people on their composable
- 45:13strategy and general strategy as well.
- 45:16And I'll see that we said at the start we're an international
- 45:20business. So anyone in the US that wants
- 45:22to kind of pick up with the US team or or anyone kind of in
- 45:27Australia who wants to pick up down there with with direct them
- 45:30in their direction? And anyone who's listening in on
- 45:34the landing page on the website, there will be links to both
- 45:37Schiffco and Liam's LinkedIn profile, so don't worry.
- 45:41Thanks everyone for listening. I hope you found it useful.
- 45:43Do pass it on to anyone else you know who's in the Salesforce
- 45:47community. Anyone else who's emerging using
- 45:48Salesforce will find this interesting and useful.
- 45:51And don't forget because it's that rating on Apple, Spotify,
- 45:53YouTube, or where else you might be listening.
- 45:55Take care everybody. See you all next week.
- 46:04More information on this topic Head over to Replatform dot FM
- 46:08for our audio podcasts to discuss a project.
- 46:10Or if you'd like to chat about any of the topics covered in
- 46:12this episode in more detail, please reach out to myself,
- 46:15James Gird, or my cohost Paul Rogers by LinkedIn and Twitter.
- 46:18Thanks again for listening and keep your ears peeled for the
- 46:20next episode.