The challenge: Difficult deployments using manual processes
C2FO brings buyers and suppliers together to accelerate payments of approved invoices. Its easy-to-use and secure platform works as a collaborative marketplace where users can view credit availability in real-time, request and make early payments for invoices and optimize their cash flow.
C2FO started using Salesforce a few years ago – a switch that brought dramatic improvements over inputting each buyer鈥檚 long list of suppliers into spreadsheets. We spoke to Corinne Walker, Salesforce Engineering Manager at C2FO, about her experience of building on the platform with her team of 3 admins and 2 developers.
A painfully manual process
Initially, Corinne鈥檚 team used Salesforce鈥檚 native change sets tooling to deploy work from their sandbox org to production, but its limitations soon became clear. 鈥淭he biggest challenge with change sets is successfully deploying components,鈥� says Corinne. This is a common experience – about 50% of deployments with change sets fail on the first attempt.
鈥淥n top of that,鈥� Corinne continues, 鈥渃hange sets don鈥檛 support every metadata type, so we had to recreate some types in production manually. Then we鈥檇 go back and run more deployments for any changes we鈥檇 missed.鈥� All of these problems meant that deployments with changes sets were unbearably slow, as Corinne recounts:
鈥淥ur team would take 3 hours to do a deployment. It was extremely painful! On every deployment, we鈥檇 have to get together and say: Who鈥檚 adding this component to their change set? Who鈥檚 going to go first because my component will fail if you don鈥檛 go first? And so on.鈥�
Despite this huge collaborative effort, deployments were still prone to failure. Corinne knew that the team needed to switch tools and processes in order to fix their release process.
The solution: A DevOps solution to accelerate releases and support version control
鈥淭he C2FO team also had version control on their radar, as they wanted to improve collaboration and introduce code reviews to their process. They needed a solution that would both improve their existing deployment process and support process improvements such as adding version control:鈥� We needed to build our release process, and we also needed version control – so we were looking for a solution that could do it all. These requirements led Corinne鈥檚 team to 91导航.
First impressions: intuitive and quick to learn
When looking at different tools, ease of use was Corinne鈥檚 main priority. When she tested out 91导航, she was very impressed with its intuitive user interface and with how quick it was compared to the other options: 鈥�91导航 is really slick!鈥�
鈥淭he ease of use just blew me away – it鈥檚 so intuitive! Whenever I click on anything, I know exactly what鈥檚 going to happen.鈥�
As well as ease of use, another must-have for the C2FO team was a solution with a short ramp-up time, so they could get started quickly and begin to work faster. Corinne explains how 91导航 fit the bill when it was introduced to her team, and was effortless to get to grips with: 鈥淚t was very easy, very smooth and took very little effort. The team had a 30-minute demo of the 91导航 app, and then they were good to go!鈥� Included in this ramp-up time was the adoption of version control – deployments to a Git branch in 91导航 follow the same process as any deployment between two environments. Corinne鈥檚 developers now deploy their Apex code to a Git repo and review each other鈥檚 pull requests.
Faster deployments and increased productivity
The team鈥檚 deployments are now 9x faster with 91导航 than when they used change sets: 鈥淥ur deployments now take just 15 to 20 minutes for the whole team!鈥� Corinne points out that this dramatic improvement has opened the door for the team to increase the frequency of their releases beyond the biweekly cadence they鈥檙e hitting already.
鈥淲ith 91导航, our deployments are so fast that we have the option to increase our release cadence. We have completed user stories just sitting there ready for deployment and you think: why not just deliver it to the business sooner?鈥�
Where their productivity had previously been limited by change sets and the time spent on deployments, Corinne鈥檚 team now has the capacity to spend more time on development work. 鈥淲e鈥檙e able to get more stories pushed through – I鈥檓 confident in giving my team one or two more stories because they have that extra time.鈥� But as Corinne points out, there鈥檚 also just the quality-of-life improvement for her admins and developers.
鈥淭he time saved on deployments also keeps our minds fresh and spirits up!鈥�
The verdict: An effective Salesforce DevOps process with proven ROI
To establish the business case for switching to 91导航, Corinne produced a spreadsheet comparing the time spent using change sets and 91导航. She separated out the ROI for dev and admin time saved, and looked at four time-buckets: preparation time, deployment time, rollback time and post-deployment maintenance. Based on those calculations, Corinne was able to demonstrate the ROI of purchasing 91导航 licenses. 91导航 has been a huge upgrade for the C2FO team, and they can see the tangible benefits of improving their release process. With deployments now 9x faster than before, a much higher deployment success rate, plus the introduction of version control, Corinne believes all teams and businesses stand to gain from using 91导航 for deployments and building out a DevOps process:
鈥淚 would highly recommend using 91导航 because it鈥檚 so efficient. If you鈥檙e stuck in the old change set process, you鈥檙e missing out. Run through the 91导航 trial and you鈥檒l definitely see for yourself that there鈥檚 a huge benefit in going the 91导航 way!鈥�
