WEBVTT

00:00:00.359 --> 00:00:03.080
Hey, I'm Jess Vosler, chief solutions officer here at Second Mile. I'm gonna take you through this case study.

00:00:03.299 --> 00:00:08.039
We identified that there was a lot of manual and duplicative, uh, processes going on, and we felt that with

00:00:08.039 --> 00:00:13.020
an integration between HubSpot, which they were using as their sales and client services tool, and Sage, their accounting

00:00:13.039 --> 00:00:17.700
platform and ERP, we felt that we could support them in decreasing the amount of manual hours that were being

00:00:17.739 --> 00:00:20.019
spent. And decrease the errors that were occurring because of

00:00:20.399 --> 00:00:23.719
duplicative, entry in two different platforms. Um, so we put together kind of, um,

00:00:24.019 --> 00:00:28.119
a chart here to show the client here are the manual processes that we propose replacing with this integration between

00:00:28.119 --> 00:00:32.299
the two platforms. Um, and so the main things that we were looking to replace here, um, were duplication

00:00:32.299 --> 00:00:37.239
of these efforts. So, um, we worked with them to, um, streamline the contract creation and signing process using the

00:00:37.239 --> 00:00:40.139
quotes tool, in HubSpot. And then, um, the goal was to kick over,

00:00:40.180 --> 00:00:41.040
um, a

00:00:41.399 --> 00:00:45.000
notification to the account team, um, that they needed to go in and prepare the invoice based upon that

00:00:45.059 --> 00:00:49.159
quote information that had been sent over to Sage. From there, um, we wanted to eliminate, um, the duplicative

00:00:49.180 --> 00:00:51.199
effort that was occurring, how executives needed to manually

00:00:51.199 --> 00:00:56.019
request invoices from the accounting team filling out a spreadsheet, and we wanted to, um, push that information over in

00:00:56.019 --> 00:00:59.979
a more streamlined fashion, and then push that information, once the invoice was ready, back into, um, HubSpot in a

00:01:00.040 --> 00:01:03.080
more, uh, streamlined fashion as well. Uh, from there, we also wanted to eliminate the need to

00:01:03.319 --> 00:01:07.939
create deals/programs, contacts and companies in both places, uh, and have HubSpot kind of be the original source of truth

00:01:07.939 --> 00:01:10.140
on that. But now the two were able to speak back and forth if accounting needed to make an update

00:01:10.339 --> 00:01:13.299
or if the account executive/BD team needed to make an update in HubSpot.

00:01:13.799 --> 00:01:17.199
We also wanted to make sure that there was an automated process for when, uh, invoices had updates. Account executives

00:01:17.199 --> 00:01:19.180
were really having a hard time understanding had their, uh, invoice

00:01:19.180 --> 00:01:22.979
been paid, was it overdue, et cetera, and so we worked through this integration to help set up, um,

00:01:23.080 --> 00:01:26.999
that information to be automatically pushed to HubSpot when an update occurs, and then also a internal notification email sent

00:01:27.000 --> 00:01:30.920
to the account executive assigned to the deal so that they could be up to date on what was occurring

00:01:30.920 --> 00:01:33.059
with their invoices and be able to communicate properly with their client point

00:01:33.059 --> 00:01:36.760
of contacts. Another huge component of this was the closing the book processes. So, what was happening prior to the

00:01:36.760 --> 00:01:38.320
integration was that the account,

00:01:38.659 --> 00:01:42.140
accounting team was having to go in and close the books, so add in the final revenue numbers per

00:01:42.199 --> 00:01:44.999
each program, add in the final expense numbers, which got them to their profit number.

00:01:45.159 --> 00:01:46.039
And then once that

00:01:46.039 --> 00:01:46.920
was all complete in Sage, they were

00:01:47.399 --> 00:01:51.039
just retyping that information into the CRM to close out the books in both places. So

00:01:51.059 --> 00:01:54.059
we wanted to eliminate that process and have, um, have it once the books were closed in Sage, that information

00:01:54.059 --> 00:01:57.339
would automatically push over, um, which was hugely important, and I'll show this in a minute, to the PnL reporting

00:01:57.339 --> 00:01:59.079
that the executive team, uh, pays very close attention

00:01:59.099 --> 00:02:00.999
to. Um, and then finally, this was a small component of it,

00:02:01.199 --> 00:02:06.839
um, but their former CRM, uh, test created a four-digit program ID, which was essentially like the record ID for

00:02:06.839 --> 00:02:10.258
a deal in HubSpot, but the number was too long, uh, in terms of the one that's automatically created

00:02:10.479 --> 00:02:16.679
in HubSpot, so they needed, um, a custom-coded workflow to create that unique four-digit, um, deal and program ID that

00:02:16.679 --> 00:02:19.899
would then be the unique identifier in the connector between, um, the programs in Sage. They needed to be a

00:02:19.919 --> 00:02:21.079
four-digit ID because, um,

00:02:21.559 --> 00:02:24.039
every single person who works on that program has to, like, manually type that in and log

00:02:24.059 --> 00:02:27.579
all their expenses to that specific number, so the longer, uh, deal ID that was created through HubSpot was not

00:02:27.599 --> 00:02:31.159
an option, uh, for their current processes. Thanks, Jess. Hi. I'm Sam Crockett, CTO here at Second Mile.

00:02:31.159 --> 00:02:34.019
In this video, I'll walk you through the technical aspects of the integration we built for Leo's team to connect

00:02:34.019 --> 00:02:35.079
the HubSpot portal to Sage, Intacct.

00:02:35.619 --> 00:02:38.079
So overall, take a look at the diagram here, this is simply what

00:02:38.079 --> 00:02:41.339
we built. On the left side, we have HubSpot. On the right side, we have Sage Intacct, and in the

00:02:41.339 --> 00:02:45.379
middle, we have, um, a Node.js service that's hosted securely on Heroku that's handling all the information that's passing back

00:02:45.379 --> 00:02:47.199
and forth. One of the key reasons we needed this Heroku,

00:02:47.299 --> 00:02:49.099
uh, middleware solution is HubSpot's using

00:02:49.259 --> 00:02:53.839
a API, um, and Sage Intacct is using an XML-based API. So it's, uh, a bit more data, a bit

00:02:53.839 --> 00:02:55.079
more complex to connect to, so our

00:02:55.699 --> 00:02:58.059
Heroku middleware solution here helps connect the dots between the systems to keep everything nicely in

00:02:58.079 --> 00:03:02.039
sync. So at a high level, on the HubSpot side, we have the deals API, which financial dates directly

00:03:02.099 --> 00:03:06.639
into deals, contacts and companies, APIs utilized to keep company information consistent. We're utilizing the files and notes API to

00:03:06.659 --> 00:03:10.039
attach invoices from Sage right onto the deal in HubSpot, and that includes updating that invoice, um, as

00:03:10.039 --> 00:03:12.999
it changes from open to partially paid, um, to fully paid to overdue depending on the state

00:03:13.079 --> 00:03:17.459
that all gets pushed over. Um, and then HubDB is being utilized to manage Leo's employee-to-owner mappings, um, that are

00:03:17.479 --> 00:03:19.059
in Sage, and make sure that gets mapped properly onto

00:03:19.059 --> 00:03:23.059
deals. Then on the Sage side, um, we're using a lot of XML functions within their API, um, specifically

00:03:23.099 --> 00:03:27.119
for creating and updating customers and projects, retrieving those invoice PDFs quickly and pushing them over to HubSpot,

00:03:27.239 --> 00:03:30.699
and then performing nightly employee data syncs, uh, between Sage and HubSpot, which is what we have here in the

00:03:30.699 --> 00:03:34.179
HubDB table as well as, uh, deals. So you can see for each of these we have the API endpoints

00:03:34.319 --> 00:03:36.939
with a method and a purpose, um, for each of those in HubSpot. And then similarly, we have it over

00:03:36.939 --> 00:03:40.199
here for Sage Intacct, um, with those XML functions that are being utilized and the purpose below. The technical aspects

00:03:40.219 --> 00:03:43.999
of the integration. Uh, just to take us home, I wanted to go over the integration business outcomes that we

00:03:44.019 --> 00:03:48.019
achieved. So, uh, first up was, um, we saved a ton of manual labor time,

00:03:48.599 --> 00:03:53.279
roughly about 36,000 in OPEX savings based upon the 240 hours of manual labor that we eliminated. We

00:03:53.299 --> 00:03:57.319
also were able to provide that real time PnL dashboard in HubSpot, which allows leadership to view the profitability

00:03:57.319 --> 00:03:59.999
within minutes of the books being closed in Sage versus days and weeks as it had been in

00:04:00.019 --> 00:04:04.939
the past. There also has been faster cashflow, so invoices generated and sent, um, in a more automated fashion, has

00:04:04.959 --> 00:04:08.319
cut out that ping-pong back and forth between accounting and account executives, um, and really has allowed,

00:04:08.379 --> 00:04:12.019
uh, the payment cycle to be accelerated, which is a huge win, uh, for the top and bottom

00:04:12.059 --> 00:04:14.999
line. Um, error-free data handoff, one source of truth has removed

00:04:15.019 --> 00:04:20.099
that m- manual key, uh, mistakes and rekey mistakes that could be occurring, um, so really helping to clear up

00:04:20.219 --> 00:04:20.319
that

00:04:20.358 --> 00:04:24.579
data handoff. Also, we were able to retire their financial spreadsheets that they were utilizing to request invoices and also

00:04:24.659 --> 00:04:25.239
to maintain

00:04:25.239 --> 00:04:28.819
some of the reporting. An initiative that we didn't really realize was gonna be a great business outcome was they

00:04:28.859 --> 00:04:31.999
are able to have tighter Sage security at a lower license cost, so they, because they were able to remove

00:04:31.999 --> 00:04:36.019
some users from the Sage side based upon this integration. And generally, um, we found great feedback and happier teams,

00:04:36.019 --> 00:04:38.079
the account executives are able to focus more on their client

00:04:38.559 --> 00:04:43.359
relationship, um, p- person, other role, while the acc- accounting and finance team are able to focus on strategic analysis,

00:04:43.519 --> 00:04:47.279
um, and not that copy-paste work. So overall, the integration, uh, really met those business inc- outcomes

00:04:47.299 --> 00:04:48.259
that we were hoping to achieve.

00:04:48.839 --> 00:04:49.199
Thank you.