Integrate to Accelerate: How GetBusy optimizes operations and grows worldwide sales with Celigo

Okay. Good morning, good afternoon, good evening to everyone, depending on where you are in the world. Welcome to this webinar, Integrate to Accelerate: How GetBusy optimises operations and grows worldwide sales with Celigo. A few housekeeping items before we start. First off, this session is being recorded and everyone will receive the recording of this presentation after we are done. We do want it to be an interactive presentation, so there will be room for a Q&A, either as we’re presenting or there will be time for questions at the end as well. But please submit those as you go within the GoToWebinar user interface. You can either use the chat function or the Q&A function, and we’ll be monitoring that throughout the event. And with us today– my name is Rico Andrade. I’m VP of marketing here at Celigo and I’m coming to you from Celigo World Headquarters in San Mateo, California. And very happy to be able to bring our good friends – longtime Celigo customers at GetBusy – Jason Ross, chief information officer, and Ben Oliver, the chief technology officer at GetBusy. So let’s go ahead and get started. So quick introduction before we hand it off to GetBusy, on Celigo. So for a lot of folks who have registered, Celigo has been a ubiquitous name for a long time. We’re an integration platform as a service. We have been around as a software company for over 10 years now with well over 5,000 customers, some very recognisable names such as the ones that you can see here. And we are very proud to say that we have been very well regarded. Last year we were nominated as G2 Best Software for 2021, which was a huge honour for us. And we’ve won several awards, including when you go into Gartner Peer Insights, you can see that we have a 4.9 rating, which is a incredible achievement for an iPass company. So to summarise what Celigo does, we essentially do three things. So as an iPass, the primary thing that we do is we integrate any business application or data to any other business application. So it’s a platform that makes it much easier for you to connect different systems that you might be using. And many companies use dozens of systems such as ERP, CRM, and other applications, and they need to communicate with each other. So it allows you to leverage the platform so you don’t have to use a lot of coding, APIs, massive projects to be able to connect those applications together. The second thing, which is a corollary of that, is we automate business processes end to end. So for example, some of the processes we’re going to talk about today are the quote-to-cash process, we’re going to talk about Customer 360. And by connecting these applications together, you can add transformations and orchestrations and other items that allow you to move the data in a certain way that automates those business processes throughout. And then the third item is that we essentially accelerate digital transformation efforts across the entire organisation. So for a lot of companies who are not just moving to the cloud but trying to understand how to best make use of the cloud in their operations, leveraging a platform in which you can automate and essentially insert these different applications together, really accelerate these efforts and helps companies like GetBusy move into best practices in a cloud-based world. So with that introduction of Celiga I’d love to hand it off now to Jason Ross, who’s going to tell us everything about GetBusy. So welcome aboard, Jason, and excited to hear from you. Thanks for having us, Rico. Hi, everyone. So today, we’re going to run through a couple of bits. The main thing we’re going to talk about is operationally, how we at GetBusy use Celigo and integrations to run our business. So which business is that? Well, we are a software company. I’m coming to you from the Cambridge offices in the UK. We’ve also got offices in Houston, Texas and Sydney, Australia. We’ve got around about 150 staff across those regions. And we’ve been doing business for a good 20 years now, mainly solving problems for professional service companies around document management and productivity. Our product suites include the likes of SmartVault, Virtual Cabinet, and GetBusy, which we’re going to talk to you about today. And recently, we’ve launched a GetBusy with NetSuite suite app, which you can see on the screen at the moment into the NetSuite ecosystem. So let’s talk about who we are and how we actually run our business. So the vast majority of our staff now are working in a hybrid manner. We were prepared for that because we did a digital transformation about three years ago. We moved from an in-house ERP system, all on-premise into best-of-breed cloud solutions. And what we did was we put three small operational teams on each region between one to three staff, depending upon the region. And they are used to perform that digital transformation, but also to look to continually improve it, maintain and support our internal operations around our software. The software that we do is a combination of SaaS applications for small businesses right away through to enterprise on-premise software, using a traditional quote to cash and large invoice processes in NetSuite right away through to simple small credit card payments for small transactions. So we have a wide variety of work that we do as a software business across the globe. Okay, so moving on for us now on to who we are as a business. Like every software company, we look to produce great software and help people do great work. But more importantly for us, it was about having standards by which others are judged. And what I mean by that is let’s give our staff tools and more importantly, a way of working that allows them to provide the best service they can to stand aside from the crowd, particularly for our enterprise business, where it’s a high touch model, there’s a longer sales cycle. We have an implementation process, much like implementing an ERP system. Implementing our document management systems can be a similar sort of process. So we wanted to make sure that we could offer the best service. So as a result, that’s why, as you saw from the last screen, we’ve chosen to go for some heavyweights in our tech stack. So moving on to our next slide, we will see our challenges as a business that we’ve used. In a minute, I’m going to get into the detail of what we’ve got and how we do it, but our challenges are around taking new products to market and trying to stay agile. Now, a lot of people say that they’re agile. I’m not talking about, for instance, Ben’s team on how they do development. We came from a small family business and as we have grown. We have done our best to maintain our values, and part of that is to keep in small agile teams where we try to keep our staff hierarchy low and we try to make sure that we are delivering as much sort of hand to hand stuff with our customers as possible. So we needed to make sure that we had a tech stack that supported that and more importantly, integrations allowed us to do that as well. So we chose to go for best of breed and as we go through, you’ll see exactly how we did that. So just pausing for a second, this slide explains how we choose technology. It’s not there to tell you our buying process because that’s not what this is about. But what’s really important is actually number six on here, what we do when we look at a part of our transformation improvements because we don’t call it sort of a full project anymore. We’re always looking at how we can integrate, what’s our next stage of integration and how do we make sure that the right data is in the right department at the right time for decisions to be made. A classic example of that is how does my account manager that looks after my 15-year-old customer and has been with us for that amount of time on a bespoke pricing model– how do they know how much they pay per user when someone calls them? Well, we feed that data from NetSuite into Salesforce and when we create a quote, it automatically inherits all that pricing history. So that’s an example of how we needed to have decent integration with those tools. Our preference operationally is that we buy, integrate, and customise within that small 1 to 3 user team of operations internally. So what Ben doesn’t want is anything internal depending on his sprint planning. He wants his developers and his team working on revenue-generating products, not me saying, “Actually we’ve changed our NetSuite requirement and what we now need to do is flow a different subsidiary name through from one product to another.” Yeah. “Sorry Mr And Mrs Customer, I can’t make a feature improvement for you today because I’m doing something for the ops and finance team.” Yeah. So often he wouldn’t be too impressed with me. So let’s go into the detail of what we’ve actually got at GetBusy. So we started this process with Salesforce as our only cloud system. That’s shared by number of our businesses and products that we have as a business and connected and built into that was DealHub, which we use as our CPQ system. So that CPQ system is used to generate quotes and our enterprise document management can come with five or six different modules that all have lots of requirements around them. So our DealHub system needed a lot of the logic that sat inside Salesforce and also ultimately would sit in our opportunities for our pipeline value. So the quote would drive the value of the pipeline which would calculate the ARR and MRR for our sales guys. And that worked relatively well until the problem of historic pricing or customer agreements and special pricing agreements and expiry dates come in. So we decided as we are publicly listed we needed to have a general ledger that consolidated our regions, our subsidiaries, and our product lines, and all of that good stuff. So we chose to use NetSuite to do that. And part of our NetSuite requirement is that we had to have a bridge between Salesforce and NetSuite and that’s how we first come across the Celigo. During that process, we selected Celigo to create if you like that bus between those two applications. We’re just going to pause for a second here because this is the most important on this entire deck for me because what it does is not only does it flow data from one place to another and keep, for argument’s sake, the customer master up to date. That’s not really where we get the most benefit from, by the way. Where we get the most benefit from is that before we used the Celigo integration, there was no home in Salesforce for our financial information. There was nowhere to put our pricing unless it was a custom field. So with the Celigo integration, not only did we end up having a connector that flowed the data from A to B, but what it also did was it gave us several different places actually where we could house financial data in Salesforce populated near real-time from NetSuite, so our sales team could see copies of invoices, copies of sales orders all from within Salesforce without the need to jump into NetSuite to do so in an environment that they’re used to working with all from their mobile app and also feeding directly into DealHub so that our pricing and our pipeline was accurate. All of that we were always able to do, but there was a lot of manual work and all of this was completely automated for us and our sales team, to be honest with you, they don’t know compared to what some other companies have to do. So with that, I mentioned that we use Best of Breed. Zendesk is a big part of our business. I mentioned that we want to provide the best support as a customer. We have several instances of Zendesk, not just one, many, for our different products and even use it internally for different functions. So from our perspective as a group, that was a really important tool for us. And we also then realised that looking at the Celigo marketplace and talking to Celigo that we could also send our data from NetSuite to Zendesk to make sure that Zendesk was also up to date when a customer was brought on board. So in quote to cash that Rico mentioned earlier, a customer exists in Salesforce, we win the opportunity as a new customer, we press the button, which is a Celigo integration button in Salesforce which creates a sales order in NetSuite. That feeds 360 back into Salesforce, so we know that’s happened. In NetSuite, the finance team approve the sales order and agree stage payments and all the good jazz that comes with that sales order and all the downstream invoicing, part payments, and all of that good stuff and all the dumbing off the back of it. But at the same time, when the customer’s created in NetSuite that customers then created in Zendesk with the contract header information that says we’re allowed to support them straight away. So the Zendesk system is kept up to date with all of the key information in the middle of that diagram. And for us, that was really, really useful because we were doing it all manually. Our team also get to– our support team, sorry, also get to see sales order details from that integration as well, which is great. So in summary, that’s where we landed and have been operating for a couple of years. We have scaled off of that tremendously throughout year on year growth through acquisitions, through new markets, new products, and that has seen us through quite a lot of turbulence and we’re really happy with it. The data that gets exchanged, in summary, is customer master data, vendor master data, and financials. When I’m saying financials, it’s everything from receipts to invoice and credit notes all back into the Salesforce system. So we really do provide a 360 view for our staff and that goes back to our company goals of being able to provide really good service customer rep’s on the phone. If you’re an account owner selling a new module or demonstrating, you’ve got all the information you need at your fingertips without having to go and log in to several other applications to get it. So fast-forwarding to sort of our modern era. We have our own product, GetBusy. We’ve developed a suite app to work with NetSuite following our establishment that there was a requirement for GetBusy to work really well with NetSuite, giving you greater control over your communication and teamwork. And that was great. But that arrow that goes from NetSuite to GetBusy was missing. We had no automation. So I spoke to Ben and said, Right, Ben, if we’re going to take this to market, this product, and we’re a customer ourselves, we are going to need to think about automation.” And so, as a challenge as a business, we needed to develop, buy, or do something to automate NetSuite to GetBusy. And at that point, I’m going to bring Ben in to help describe what we went through on that process. Yeah. Thanks, Jason. The existence of Celigo is like a dream come true. So GetBusy’s essentially a next-generation product of what we’ve been doing for the last couple of decades. Solving similar problems just in a more sort of cutting edge way– in a way that’s built for the technological world and the business world as it is today and is heading into the future. So having Bill as a team– and Jason’s been directly involved. Historically, hundreds of integrations with different applications, each of which has its own nuances and differences, the prospect of sort of recreating all of that around our GetBusy product was an ominous one, one I’d rather not have to go on building everything from scratch. So by the time we got to the stage where we’re looking at solving integration challenges through automation with our product, Jason and the team and the rest of the business had gone on this journey with Celigo– that it just became more evident as they were going on that journey that it was our future integration platform for the GetBusy product. And we were aware of iPaaS and tracking it. But it was only when we discovered Celigo with the breadth and depth– not only that they’ve got within the ecosystem in terms of connectors, but also the depth of the integration, and it being able to facilitate things like custom objects– because a lot of the integrations we’ve done historically are sort of surface level. So to tell you a little bit more about what we’ve done on that side– if you will forgive me, to give you some context. So by the time we get there, having a rough understanding of what the GetBusy product does and what challenges it’s helping people solve, we’ll then give you some context about how we’re using Celigo on the product side of the business as well. So, in summary, we talk about GetBusy as one place to organise, communicate, and store work. There’s a lot to unpack in that for another day, but the general gist is documents, tasks, communication, and relationships. We call that the who, what, how, and why of the work we do, but think File Cabinet but supercharge, think a better alternative to email and internal team chat tools, all organised under business-critical relationships. To give you a sense of what it looks like, the people, the organisations in GetBusy ultimately need to exist or come from the source of truth for these customer and vendor and partner relationships. The source of truth– that is NetSuite. Whether it’s affiliate, stockist, or whatever type of relationship, those need to manifest in GetBusy because those are the contexts in which we do our work, and each of those relationships has what we call this, quote-unquote, “magic” folder, which is a bit like a classic document folder. But rather than just files and documents, it has all this extra stuff going on. It has tasks, and it has communication. It has collaboration, and interaction history, both internal and external. It pulls it all together in one place that’s structured and ordered dynamically. The example we’re seeing here at the top is– that’s some accounting practice tags and classification. But ultimately, it’s customisable with the view that we’re trying to create this place where it’s really simple and easy to use in its premise. But it covers the whole spectrum of what’s happened, what’s happening, and what needs to happen to service relationships effectively. So on the document side, simple stuff like drag and drop, making it really easy. There’s document management capabilities, so there’s version control. There’s detailed classification. There’s a history of every interaction and context in which documents have existed, audit trails, etc. So think file cabinet, but supercharge because it’s got this layer on top of that, that focuses in on communication and not just the ability to communicate, but a framework that helps us internally and externally when dealing with customers, to communicate really effectively and really well so that we can rather boldly and brashly and maybe a bit altruistically, someone nauseatingly go, “Oh, we want to set the standards by which others are judged,” but within that comes down to communication in part and the service and the care we put behind how we communicate. So a real-time secure messaging experience, documents involved, push notifications, automatic reminders and prompts so that work can’t slip through the net. A large part of that is tasks. So tasks is this layer on top of communication where people are communicating, supported by documents to work together for a purpose, making people accountable for things and getting things done. That is just more often than not done in traditional tools like email and even team chat like Teams and Slack these days. Having things that are purpose-based and focused and ultimately flexible. So whether it’s drafting a presentation or approving a vendor bill or a Dunning query, scheduling a meeting or picking up and sorting out a sales order query. Doing that in an environment where there’s ultimate control, ultimate visibility across the team and in the context of those relationship records. There are different types of tasks, one of which is e-signing. So if we switch to a signature, we can see we get the ability to prepare documents for signing different types of signature, all of which are legally admissible. Bleeding-edge signing experience, as you’d expect from competitive products. And then the key point, I guess is on top of all of that, just to sum up, is GetBusy is being designed to work as well inside the team as outside the team. So we get branded email notifications going out, inviting people into the products, the signature or to upload documents directly onto their customer file as an example. And all of that’s branded and manifesting and reinforcing the brand of our customers and all sort of natively available for iOS and Android as well. Now we get to the Suite app, which is where we started our journey and taking that one place. Well, we’re not just one place. We’re one place for certain types of information in the context of ERP, in our case, next week. And if it’s going to be a source of truth, then we need to support and manifest that. So our Suite app embeds those magic folders within the NetSuite relationship records. And then at transaction level, whether it’s an order or a purchase or an invoice or a quote, it allows you to convert those transactions to documents for onward collaboration and action, both internally and externally in a secure means. The quote transaction is really good example where a lot of customers want to get that signed. So we have a button on a quote that says signed by GetBusy. I’m going to just stop you there, Ben. Those transactions that we get when we’re speaking to customers like Ben showing there. Those are great if you’re a service-based organisation that’s doing things with a mouse. Quotes normally have to come with a bespoke message like Ben showing on the screen here, but sales orders, invoices, and copies of documents, that’s where the automation requirement was coming in and we were missing something. It requires someone, a human to go into that screen and click the button. Whereas that’s the reason why we came up with this idea of trying to do automation is to serve our customers that had sort of 24/7 businesses probably fed through an e-commerce s platform usually with a Celigo connector from Shopify or from Daydot or something. Coming through means that both a customer comes on board for the first time on a Sunday evening when the warehouse come in on Monday morning, GetBusy has the copy of the sales order inside it for you to go and work on. And I think that’s– those screens there that Ben’s got there is what we look to try and automate as we get further down the story. Yeah. Thanks, Jason. And because GetBusy’s got all this stuff going on and they’re putting that front and centre within the NetSuite dashboard in the form of a port, that is important as well. So exactly as Jason was talking about, we knew from Daydot and have increasing feedback and demand for automation– I was going to say automisation then. Where that was going to come from, I don’t know. So in terms of record synchronisation, those relationships and getting those documents and that data into GetBusy so that it’s there and available for anyone either via NetSuite or independently via GetBusy using the mobile app on the go, and talking personally for me, I’m not a NetSuite user internally at GetBusy. So it’s great for me because I deal with a whole load of vendor relationships in terms of how we build our product. AWS is a primary example of getting to invoices, even contracts from a vendor perspective. I can go in and get to those and work on those and collaborate directly with vendors via GetBusy. Rather than having to ask the finance team to extract out the last six month’s worth of invoicing from a vendor, I can just go and get to those in GetBusy. So making sure that information was there and readily available for people was really important from an automation perspective. And having been through our Celigo experience as a customer, I’ve already said it was going to be a no-brainer for us. But that was reinforced from our suite app experience. Love NetSuite and its ecosystem, love the fact that it’s infinitely configurable. And as a new SDM partner and developer doing the suite app, we were opened up to this world that is enormous, all of these different tools and methodologies of doing things and different versions of things. Actually doing the right thing to an intricate degree of detail that customers need whilst maintaining quality and with relatively low effort and keeping it simple was going to be a tough job. So the suite app experience was just– again, Celigo was just there making it simple for us to deliver automation and in a scalable way as well, given its breadth and expanse as a platform with other tools that NetSuite customers use. And we’re a good example. And we didn’t have to wait months for it. Yes. Yeah. Not at all. Thanks for that. On top of that as well, I have to say that having worked on a lot of integrations and with a lot of partners historically, the team at Celigo and the calibre of people there that Jason had managed to experience in terms of our implementation just continued to flow through to the development team as well as we worked on our Celigo integration app. In summary, in terms of the nuts and bolts of our V1 integration app, we’ve got that relationship synchronisation going on. So it’s new entities are added and maintained in Celigo. They’re automatically there and available in GetBusy. And at the moment, automatic conversion of transactions to actionable documents within GetBusy, they’re going across as well. And that’s very much the start of the journey. For us, one of the things we are keen to extend to in the next version, just as an example, is the automated pushing out and creation of tasks off the back of workflows and processes with other systems as well. So excited about the next steps for that. But all around, yeah, it’s been an excellent experience on the product side. And I’m very pleased to be working with Celigo. And on that note, I think I’m handing back to you now, Jay. You can do. Yeah. I think without the Celigo integration, we would struggle in the markets I mentioned earlier, as particular retail. With the NetSuite retailers, having that constantly on– their sales orders being generated at all times a day, the automation was really important. We’ve already started working with other connectors in the ecosystem as we come across opportunities as a software company. We’re able to go into opportunities with confidence that we can integrate, not just in a sort of superficial way of the front end. We can do some decent high-level data integrations with the monitoring and the exception handling that Celigo comes with out of the box, which is what people need for confidence in an integration. I know internally the fact that we’ve got one person that is monitoring all of those integrations that you’ve seen and more is something we want our customers to be able to benefit from as well. We don’t want to add more work. And that’s the same on the product side as well. Building for the happy path and getting data to go from A to B is great. But then the exceptions monitoring, the reporting, the handling that all came as part of the platform there and ready to go. So on to our next one. What’s next for us? So summing it up for us, world domination. Obviously, they can get busy to the NetSuite world. It might not be the world. But we hope that particularly with our automation and our integration in place, that we’re going to have world domination. And from an internal perspective, our next project internally for that diagram I showed at the beginning, we have– I mentioned at the beginning we’re made up of several product lines as a business. We have a number of SaaS-billing engines that are– because remember our choice to not build billing engines but to buy them and integrate them. That also goes right the way through all of our products as well. So one of the projects we’ll be doing next with Celigo internally is taking those SaaS-billing engines, for example, Chargebee and looking to build the same level of integration that we have with our other tools such as Salesforce and Zendesk into our NetSuite system to give us even more visibility of our financials across the board in a real-time fashion rather than once a month having to extract the data out and dump it in just before we– so otherwise our NetSuite dashboards aren’t accurate. I think, Rico over to you for any Q&A at that point. We might have covered a fair bit there. But it’d be good to see if there’s any questions. Any questions? Great. I think you’re on mute, Rico. The most famous saying of the year. Oh no. Still no Rico. Have you got any questions for me, Jason? No I think I would have done this before. I’m so sorry. No, thank you so much. We do have questions that are coming in. Great. We appreciate it. So first question, please describe the extension of salesforce with Celigo for financial data visibility. Did Celigo enable this without salesforce customisation? How so? And just one thing before you start, it’s much more than an extension. It really is a complete quote-to-cash integration application that automates the whole process across– I mean, we’ve seen it all. There’s thousands of customers use it. So go ahead and please describe it there, Jason. Yeah. Good question. Whoever has asked it, feel free to reach out on LinkedIn, and I can give you a walkthrough of how it works because you kind of have to see it to appreciate it. But the answer to your question is, during the installation of the package in Salesforce, it creates custom objects for you and also puts them in those views of those objects of salesforce into your customer and/or opportunity records. But we then heavily customised that, but not the objects themselves, just the views within salesforce. So we don’t have any salesforce qualified developers here at all. We’re learning very much on the job as far as that’s concerned. But the Celigo tool itself gave a home called Financials where our invoices and sales orders went without us touching anything. The only customisation we did was what we showed to who, and under what security profile, and whether we show VIP data to non-VIP users. That’s it. And just maybe to elaborate a little bit more on this. So CRM and ERP are two of the most customisable solutions that any organisation– complex solutions that any organisation’s going to use. So there are so many different specific configurations. And the application was really built for that, understanding that there are going to be things that different companies are going to be needing to do. Much of that is done out of the box with the application. There are situations, though, that needs to be extended. And in which case, the beauty of it is it’s an iPaaS, and so you can get additional flows with the underlying platform, the integrator.io platform to do that level of customisation. So a really common example, for example, is salesforce not-for-profits. And so, whereas the out of the box application uses– it’s mainly a quote-to-cash process, the nonprofit customisation is specific towards donation-to-cash, which changes the nature slightly, but it still can be accommodated. So it’s built for quite a bit of flexibility there. We have more questions here. What type of operational team did you have to build and manage these integrations? Did you leverage partners or consultants? I’m trying to understand if I need to hire internally or externally to manage these projects? No. Celigo did the implementation for us as part of our NetSuite project when we went to NetSuite. We have both a sandbox and a live environment. So it’s almost two implementations, really. And following that implementation, we now have two Level 4 Celigo Masters in the team. And they look after and manage all of our connections, and monitor it, and make sure it’s all running true. It’s also worth pointing out, unlike any other integration, if something happens from a bad data perspective, it can also be reported in salesforce itself in an error text box. We show you that. Some customers, but we’ve shown that. So if the sales guys send us all that and it’s got some bad data in it. Their Celigo integration also has some rules in it to keep the data clean. That will also report back in Salesforce. So sometimes, from a support perspective, our sales guys will send a screenshot in opportunity or a link to the opportunity that hasn’t worked and we’ll go, “Well, that’s because you’ve not filled in X, Y and Z, which are somehow mandatory fields, but somehow, you’ve managed to cheat the system.” That, as an example, as well as having just one or two people monitoring it. And that’s what we use. Yeah. And that monitoring is an extension of somebody existing in the Ops team and somebody in the VIP team as well. So it’s sort of a small part of their overall responsibility. There’s also monitoring, but fixing stuff with integrations could be a nightmare because once you fix– once you find there’s a data issue between A and B, if you resolve the data issue, what you’re then going to do, because time has moved on, things have moved on. It’s near real-time. Well, with Celigo, we can just play the error back, make sure that goes through, and go, “Okay, fine, that’s gone through.” Double-check each system and then off we go. We haven’t got to worry about doing a load of data migration or transformation work manually in either system. Another question, and I think we’ll have a related answer, but did you consider just building the integrations with SuiteScript? That was a good question, Ben. We did. Having familiarised with our first encounter of SuiteScript was building the Suite app and looking at services like SuiteTalk, etc and various APIs available. We concluded that it would not only take a significantly larger upfront investment in terms of time, it would also require sort of expertise around NetSuite usage in the context of the Dev team. Even coming up with the exact requirements and all manifestations of, given how NetSuite can be customised itself. And then the ongoing maintenance and iteration of that as well. And going back to our sort of operational philosophy of buy and integrate versus built. There was just on no level other than, obviously, having ultimate control and responsibility. Did it end up being appealing to build it all ourself given the experience we’d had with Celigo and everything we’ve learned as a customer to that point in time? Hopefully, that answers your question. I think it does. So more questions here. GetBusy tool looks cool. What does it cost? I’ll take that one if you like. We’re very straightforward as far as our pricing is concerned. It’s priced on a per-user, per-year, or per-month basis. Just to give you an idea of pricing in a US dollar price, it’s $30 per user per month, billed annually or in pounds, it’s £23 per user per month, annually. And it includes all support and implementation. Excellent. Give me one more minute. Great value. It’s great value. Let’s see if there’s any other questions here. But if not, so you mentioned, how can people get a hold of you if they have any more questions? Yeah, I think one of my biggest bugbears as a CIO is not being able to talk to other people that are in the same situation and being able to share experiences, particularly around all of the information that I showed you of the Salesforce and Zendesk app. So I’m keen to help others that are in the same situation. So if anyone is, please feel free to– the best thing to do is to reach out informally on LinkedIn. You’ll find both Ben and I under GetBusy on LinkedIn, and just send us a message and we’ll jump on and see if we can help and share stuff. That’s predominantly what we want to be doing here. Wonderful. Okay. So I think that’s it then. Thank you so much, Ben and Jason, for joining us. Super informative. Please, anyone interested in learning more connect with any of us on LinkedIn, reach out and of course, you can always just go straight to our websites: celigo.com, getbusy.com, and start using the applications right away. But really appreciate the GetBusy team. You guys have been wonderful partners for a while and excited to see what you’ve launched and that we’re part of that journey. So thank you for joining us and we look forward to continue the conversation. Thanks for having us, Rico. Yeah, thank you, Rico. Thank you, everyone, for coming. Bye-bye, everyone.