Seamless End-To-End Integration of Your Donor Systems

How much time does your organization spend exporting, manipulating, and importing spreadsheets across your online giving platform, donor management system/CRM, and accounting application? Even worse, are you hand keying the data? Chances are these activities are hindering you from doing the work you were actually hired to do, or you’re working tireless hours and missing out on time with your family, friends, and other activities because you’re trying to get data across multiple systems.

In this session with Venn Technology’s Scott Hollrah, you will see the power of the possible – seamless integration across all aspects of your fundraising process, which will reduce the potential for error and free you to work on the things you’re best at.

Interested in learning more about how JMT can help you operate more efficiently?

Melissa Waters: Alright, welcome, everyone. My name is Melissa. I'm the manager of events and programs here at JMT consulting

We're an ERP financial solutions firm has that specifically works with nonprofits only. We've been in business for 30 years I need to update that slide.

And if you go to the next slide. For me, Scott, that'd be great to have a few housekeeping notes that I wanted to share

We are recording this webinar, we will share a copy of the slides and the recording with you, following the webinar.

If anytime you have a question during the program, please make sure to submit it in your Q AMP a box and we'll answer those at the end of the webinar.

And with that, I'm going to introduce Scott Hall from Ben technologies. He's our wonderful presenters family are happy to have them with that. Take it away scot

Scott Hollrah: Alright, good afternoon or good morning. For those of you on the West Coast. I am Scott Hollrah. I'm the founder and managing partner of Venn technology. I'll tell you about us here in just a second.

a quick rundown of what we're going to do tell you a little bit about then tell you a little bit about

The work that we do. And then we'll get into some best practices as it relates to building system integrations and

As we go through this presentation. We're going to talk a lot about specific applications, mainly because they're the applications that we work on day in and day out, but really when it comes to the best practice part

The, the conversation really applies to whatever systems, you might be working with a little bit about me. For those of you in the SEC. I'm a Texas Aggie

Over the years, I've worked with lots and lots of different technologies with a heavy emphasis on salesforce.com and sage intacct.

We've worked across all kinds of industry verticals, including a lot in the nonprofit space roughly half of our customers are in nonprofit.

And one of the things about our organization is that we really take a big picture approach to our integrations.

Often people will come to us and say, hey, can you help us get data from here to here.

And we'll talk about this again in a little bit, but it's important that you actually look at what happens before that initial point and what happens after that. Second point, there's so much more to consider. And that's really

How we operate, how we build out our integrations across systems. I am based just outside of Dallas, Texas, we opened an office this year and Washington DC and we are doing work all across the country.

Then we have something we call it our brand promise. And that's what you see on the screen. We create systems to free people to focus on what they're best at.

And for your entertainment. I won't play this. But if you go out to YouTube find ven technology, we made a fun little music video that kind of tells the story of the burnt-out controller CFO.

Development Officer. That's just struggling to get all this data back and forth and how we solve the problem. So it's a good laugh. Go, go check that out when you get a chance

As I mentioned, there are several applications that we're really focused on at Venn. We are a sage Intacct marketplace partner. And what that means is that we come alongside groups like JMT consulting and while they are focused on

Putting together the best possible intact implementation for you. We're there to help you take it a little bit further and connect that into other things take taking the value of that core platform and extending it out.

We have a couple of listings out on the intacct marketplace. One is for our Salesforce nonprofit integration for intact.

And the other is for a stripe integration. So people that are taking credit card payments that needed to flow directly into the accounting system.

We do a lot of that work and kind of a standardized manner, but at the end of the day, you see a whole bunch of icons, off, off to the right there. We help any people integrate anything with an API to sage intact.

The other aspect of our business is our Salesforce com practice. So we are a Salesforce partner.

And we do everything from implementing brand new ground-up systems. So for those of you on the call, who may be on something else that are thinking about Salesforce.

And we would be able to help you move off of Razor's Edge or whatever system you might be on

For those of you that may already be on Salesforce. My guess is, you're probably not getting the full potential out of it.

And we will oftentimes come in and help organizations optimize that existing system and for others we act as kind of an outsourced administrator. So it may not make sense for you to have a full time Salesforce admin then technology can step in and kind of fill that role for you.

Everybody on the vnen technology team has one or more Salesforce certifications. This is just kind of a sampling of kind of the different area of expertise that we have

And you'll notice on the right of cold one out and that is the nonprofit cloud consultant

I mentioned earlier that nonprofit is half or more of all that we do and I'm very proud that one of the members on our team was actually one of the very first people in the world to obtain

The nonprofit cloud consultants. So we speak nonprofit. We know nonprofit and we understand the differences between how you operate and how

How the for profit world operates.

A little bit about our ethos, I, I grew up in the Salesforce world where they preached this message of clicks not code. We want to be able to configure things

As opposed to having to write custom code to to achieve the things that we want. And so we we really look at code as a last resort.

We want to be able to configure systems, as far as we can, without having to write that code. And we'll talk a little bit more about why here in a minute.

Already talked about the big picture approach and when that when we are in that mode, we've really got to look at all the different parts and pieces that are floating around.

And we can't, we can't try to fix things in silos or fix things in a vacuum. We've got to look at, you know, from end to end where the things really begin and where do things really end and and that's where, that's how we back into figuring out how to make the in between.

So before we dive into the the meat of this just kind of laid some groundwork. My hope is that at the end of the session you will come away with a better understanding of whether or not it makes sense to integrate your systems, sometimes it doesn't.

We're going to talk about several different ways to go about integrating systems and, you know, my hope is that you'll come away with a sense of which might be the best approach for you.

And then finally, what are some criteria that you really need to think through before you can take on that integration project.

Real quick, I don't know, Melissa. I don't know if we can do like a show of hands, but let me, let me just throw this out there.

Is anybody out there already using Salesforce. Is there a way to maybe chat that over

Melissa Waters: They can either chat or they can raise their hand.

Scott Hollrah: Okay, so there's a handful of you that are on Salesforce. So I suspect that

The rest of you are probably on Razor's Edge or something, something similar. I don't know if we're gonna be able to

Communicate this across very well. But a question that I would often ask in a an in person setting.

Was is, how well would you say your systems are integrated scale of one to 10 and more most often

You know, people raise their hand at five and six and maybe seven. But when we start getting up into the eights nines 10s. A lot of hands in the room, start going down and my, my guess is that, for those of you that don't have integrated systems, you've got a number of challenges.

And so I love this slide here today. We use tons and tons of different applications. Many of these names probably ring a bell. Many of you probably are using several of these and in in

These things should work together, we should be able to take that donation in our donor management system.

Or online giving platform have that flow into the donor management and on to finance and then, you know, tie it in with something like a collaboration tool like slack, you know, hey,

We just achieved this major donation. Let's get the word out to the whole company and get everybody really excited.

So there's all kinds of examples. Maybe you put on events and you use something like cvent or event bright, you should be able to take those registrations flow them again into that donor management.

And for those registration fees pass them on into accounting without a human having to touch anything.

I know this will come as no shock to you but manual processes are time consuming and their error prone

How many times have you had a corrupted macro, you know, spoil your Excel file. There's, there's just lots of different

Problems that come with these manual processes. And not only is it time consuming, not, not a, not a good use of resources.

But it also often handicaps you in terms of not having timely insight into important metrics about the organization.

How are we doing on a revenue. How are we doing on our expenses. And for those of you that may, you know, track a lot of operational metrics, not having that info across systems really leaves you really leaves you blind and may may hinder your decision making abilities.

Alright, so let's let's talk a little bit about different ways to integrate systems and the first. I even kind of alluded to it on the previous slide, is the classic export, import

Again, if we were in the same room, I'd have you all raise your hands. And I'm guessing that most, if not all of you have probably done an import probably your payroll data.

Sometime in the last couple of weeks and on the upside. Hey, it's, it's free. Right. And I usually do air quotes around free because obviously it's taking your time.

But on the downside. It is time consuming. We deal with formatting issues we might have data transformations. You know, we export out of, out of this application.

And it formats, the date this way, but the system that's receiving the data, the date format in a different way. And so we've got to go through reformat

run some formulas do all kinds of different things to get it.

And with that, we can we can encounter errors, we can have duplication. We've got a client that we worked with several years ago, down in Austin, Texas.

Who wasn't quite ready to go fully automated and so we built them an export file out of Salesforce that they were then able to just go and import into sage intact.

Well, it didn't take but a week when we get a phone call saying, hey, remember we talked about that fully automated integration. Yeah. So, well, maybe, maybe it's time for us to revisit that.

What had happened was somebody had gone on vacation and not communicated the last date that they export the data and imported it and as a result they ended up duplicating all of the

Information that had been imported and then a whole lot more. And so the export, import. Sometimes it's the only option. And if that's the case that you've got to roll with it. But, but there may be better options as well.

So our next option is what I call packaged integrations.

Oftentimes software publishers have pre built ready to go.

I'm going to say plug and play type integrations with other systems. I'm sure at some point, we've all used one

And and on the plus side, they can be a lot quicker to implement and oftentimes you're going to get updates from the software publisher over time. And those updates usually include things

include additional features and functionality that add value to to that integration. But on the downside, just because there is a packaged integration option available.

It doesn't mean it's going to meet your use case and the other side of it is, and we see this a lot in the Salesforce world.

Packaged integrations may not play well with the way that you have set your systems up even if it meets the use case you may have customized your source systems in such a way that that package integration just won't work.

So, a quick little story here at venn technology we we use MailChimp for our email communications and we use Salesforce com as our CRM system.

And we wanted to drink our own champagne, so to speak, and have our systems integrated so that we didn't have to do that ongoing export, import and we got really excited when we found this pre built MailChimp integration.

However, our hearts kind of sunk a little bit when we really dug into it and realized, we've got some things in our Salesforce environment and the way that we

We Categorize our audiences and group people together that it just wasn't going to play with that packaged integration and so we had to go through an exercise to build something different that really matter.

And. And one of the things that I like to do when we're doing this kind of evaluation is we need to lay out our use case. And in this in this example.

This is a reflection of what a standard integration looks like for Salesforce com and sage intact.

For a lot of nonprofits. This just doesn't meet their needs. We're not dealing with sales orders and invoices, you know, perhaps, for, for those that are grant funded

You may deal with some of that but but for most organizations this workflow just doesn't make sense. And so it's really important for you lay out the applications.

Lay out the data that needs to get exchanged across the different objects and the systems and determine if that package option is actually going to meet your needs.

Alright, the next option is custom code. And I think that for so many of us when we think about an integration.

This is where our mind goes right we think about the developer. That's just, you know, coding away at the keyboard and for a lot of us.

Myself included. It's just a whole bunch of gobbledygook. I can't. I can't make any sense of it, but I'm glad those guys can on the plus side with the custom code option you can get exactly what you want.

If the API's for the different applications. Support the workflow, you're trying to achieve. You can get exactly what you want. But on the downside custom code is almost always the most expensive and the most time consuming option.

Additionally, with custom code. We don't get a lot of flexibility. And so let's say we go live with our integration and six months down the road.

We decided we need to change some field mappings. Well, we've got to go spin up the dev team dig through 10s, maybe hundreds of thousands of lines of code.

Find a couple of lines that pertain to that mapping make that update deploy it through three different environments to get it out into production. And so again, custom code, you can get exactly what you want, but it's going to come come at a cost.

All right, I'm kind of wanting things down on the the integration approaches.

The last one that we're going to talk about is middleware.

You may say what is middleware middleware software that sits in between other software applications and the handles all of the automation. It handles all of the transformation logic and gets it in with. Without without a lot of human intervention.

With middleware, much like custom code, we can get exactly what we want. So long as the API's are there to support it.

We also get extensive ability into multiple systems. I'll talk more about that in a minute.

Middleware is typically going to be faster than custom code, but not quite as fast as those package options.

And we're going to get flexibility and error handling and so the greatest integration, the world, by the way, you're going to have errors at some point something is not going to make it across, for one reason or another.

And with middleware options you get some great retry mechanisms to to address the errors.

On the downside, these, these middleware options, you're still having to build something. It's not that packaged integration.

And so we're a publisher of a software application that has an integration may enhance that we're not getting that kind of benefit, we would have to go build those enhancements on our own, and you are going to have some ongoing investment in that middleware tool.

And so one of the things that we we like to do our ethos, again, is that we want to evaluate the package options. First, and if the package option isn't going to meet our needs. We look at middleware second and custom code again is kind of that last resort.

Let's talk about some integration examples, some different fun projects that we worked on. Here's an example of an integration that actually is using several different kinds of integrations. We've got some

Packaged integrations. We've got middleware.

tying a whole bunch of different things together and the other great thing about this integration I referenced that that middleware is extensible and and I'll talk through that here as we look at this diagram.

Excuse me one second.

So this is an organization that came to a several years ago with a rapidly growing nonprofit.

In December of 2016 they basically broke the internet, they receive more online donations than

They had ever. And it literally cratered their QuickBooks system and their legacy donor management system and so

These, these guys were really crafty. You'll notice we've got PayPal. We've got authorize net. We've got stripe.

They've found a way that if you're willing to give them money, they got it, they've got a way to collect it and so they actually had some developers on staff that built some some custom code type integrations into their Salesforce environment.

They leverage some pre-packaged integrations to do things like gift acknowledgement letters. Again, that's, that's that pre built one where the publisher has provided all the hooks and maintains that and then we came in.

And took their e commerce store they sell goods that are made by refugees around the world.

Through through a Shopify site. We're taking those routing them through this middleware passing them into the donor management system.

And then recording the financial transaction over in intact and then we've built several different integrations and flack for notifications about big orders.

About error handling error notifications that they can go retry things. And so this is where that middleware that extensive ability, really, really shines.

Here's another one where, again, we've got a combination of some pre built and some

Middleware based integrations. This is an international faith based missions organization that uses an online giving platform called pure charity.

And pure charity had built an integration directly into Salesforce to record donations and through that integration. We're seamlessly pushing those gifts and the and the donors into the CRM system in real time.

And what was really neat about this pure charity system is that it also had an operations component and so

People would would work with this organization to go on mission trips around the world. And as part of that they had to provide all kinds of documentation.

immunization records agreed to certain, you know, to a code of conduct and unfortunately, that was not available in their standard integration and so

What we did was we built a file based integration against sometimes that that Excel is the only way to get it.

What we did was we built a process by which they could save that Excel file and either Google Drive or Dropbox.

And the middle where watch for that pick that information up and wrote it into into the CRM and that was their kind of central point

To view all of their activity, whether it was donors or that operational activity or people are going on these trips and then of course we would sink those financial transactions over into the accounting system.

Alright so this all sounds great. Scott, you know, we want to we want to get going. We want our systems integrated and you know what, what do we need to do next.

Well, the first thing is we've got to begin with the end in mind.

We will get calls from people on a regular basis and they'll say, Hey Scott, we've got the system. And we've got that system.

And we want to integrate them and we say, great, what do you, what do you want that integration to do

And they say we want to integrate these systems and we say, well, that's great, understand that but but what specifically does that integration need to do

And so in order to really be successful with your integration, you need to be able to clearly articulate that with with as much specific specificity as possible.

What that needs to do. So here's some examples when properly integrated our systems will sync all of our customer data across systems so that we can see full order, and payment history and each application.

Or perhaps a much more nonprofit from the example when our systems are properly integrated that we provide access to summarize journal entries for all donations on a daily basis. So you've really got to narrow down what parts of these systems. Do we need to get talking to

All right, here's an excellent process.

And again, I wish that we were all in the same room together because I'd love to see you know see hands going up and down. How well are your processes defined is his routine in agreement as to what the process is where things begin and

We frequently after we've kind of laid the groundwork of this is specifically what we're trying to accomplish with the integration, we'll, we'll start off

Our projects with a with a workshop requirements gathering workshop

And we'll go around the room and we'll ask, you know, how do you do this. And the first person will raise their hand. And I said, Well, we do it like this.

And then the person sitting next to them goes, No, no, I don't know what you're thinking. We do it like this and and there's that third person that goes, You're both wrong. No, no, we do it like this.

So we got to make sure that everybody is on the same page that the computers only do what they're told. And if we got people thinking that they need to do different things.

That the system just isn't going to work. So you got to get everybody on the same page. And part of that is determining when and how your integration should run

Oftentimes, our integrations are built whether some kind of trigger that hey we we received the new donation and in real time. Let's go. Push that donation over into the general ledger.

Other times, there needs to be some kind of a human review. It's a button press or maybe somebody in operations or accounting needs to review an entire batch before it gets pushed over

And then the. The other type that we see is we schedule things every night at midnight go grab this data and move it from here to there. So make sure everybody's on the same team with

With with your process.

Alright, this one, this is a big one. I have a feeling that there were a lot of size as they as the the slide came up. What is the quality of your data.

We've all heard the expression garbage in, garbage out and and oftentimes that that phrase that's been around forever is is used in the context of report.

And that's absolutely true for reporting if we put bad data in, we can't expect to get good reports out and the same as as true, if not more true with our integrations.

If we have bad data in our source system, we're going to now have bad data in our target system and that that can be a big, big problem. So before you start taking on an integration project.

Check to make sure that you d duplicated your data set and validate the the accuracy of the data and then fill in the missing pieces.

We've probably all got, you know, all kinds of different fields on on our in our donor management systems, make sure that those critical values are populated, otherwise you're going to now have have a mess going

Downstream and to other systems.

The other part of this is making sure that you have consistent identifiers record IDs across different systems and in a minute. I'm going to show you an example of where that really comes into play.

And with that we will go ahead and hop into a quick live demo. So I'm going to exit presentation.

Let me switch tabs here and I am going to log into this online fundraising tool called raise donors, we do not sell raised owners, but we do a lot of partnering with them on on projects. And if you're looking for a new online giving platform. This is a fantastic one to check out

So we're going to come into this tool we're going to build a new online gift page.

And

Just give it something to get started. And we'll go ahead and publish this page.

I mentioned a minute ago that it's important to have common IDs across systems.

One of the things that happened when I when I added this new online fundraising page is that we immediately and seamlessly created a new campaign over in our donor management system. In this case it's Salesforce. COM. And so now, whenever we

Whenever we receive donations through that online giving page the integration is going to tie it to this campaign, these, these are in sync. In other words,

And even more importantly we've gone all the way downstream into our into our accounting system. And we've created what what's known as intact as a project. And so if we come in here.

We will see that that project got created so so the action of creating that fundraising page created a campaign and then created a new project in our accounting system.

And this again speaks to that extensive ability of middleware where one action in one system to trigger off a whole bunch of other things.

Let's go back to our donation system and we'll pull up the fundraising page. We're, we're in test mode. No money is actually moving around here, but we've got somebody that's going to make a generous $250 donation.

And that'll get submitted.

And again, our system hands free right now is is seeing that this donation was received in the donor management system.

And now to keep the data clean over in the CRM system it is looking for an existing donor it's checking various aspects of the donor information that we got on the donor management system.

Looking for for existing donors that meet that criteria and if it doesn't find it if it doesn't find a match. It's going to go ahead and create a new donors. So here, we're still on our campaign or fundraiser. And we can see that we've received a donation for $250 from the Ramirez household

And

It has also synced over to the accounting system. So if we hop back over into intact go into our general ledger.

We can see that donation from the Ramirez household. And what I love about this. It happened without a human having to do anything. All we did was created our online fundraising page. And the next thing you know all of this data was propagated across our central and critical applications.

So that concludes the whoops.

That concludes the demo. Let's open the floor up for questions.

Melissa Waters: Awesome. Thanks Scott. We do have a few questions for you. Sorry I tickle in my throat.

So first is

Does this pertain to Abila MIP or community brands at my peak. Can you work with them, or is it just, are you just intacct focused

Scott Hollrah: That is an excellent question. We, we have in the past with building integrations with MIP and

Their, their architecture is a little bit different than some and really the the export, import is is really the only option that we've found for for working with MIP.

Good, good question.

Melissa Waters: And the next question, can you integrate razor's edge with Sage intacct.

Scott Hollrah: The answer is yes. There are some some details that need to be worked out need to know a little bit more about which version of razors edge on I believe you need to be on the next tee version, but as razor's edge can be integrated with Sage intacct.

Melissa Waters: Wonderful. And how long does an integration project to take to complete

Scott Hollrah: You know, it varies as you might expect, depending on the number of systems that we're tying together the complexity that we are having to build into these integrations, but in general.

Most of our projects run about 90 days it's not said that I can't take a little bit less than. That's not to say that they don't take longer, but 90 days is a pretty good average

Melissa Waters: Yeah. Here's another question for you regarding Salesforce is there, the ability to batch transactions through an integration as we do not want the individual transactions and intact.

Scott Hollrah:Yes, that is an excellent question and I have a feeling that the way that we present this integration and the demo may throw you off a little bit. We don't want to wait until midnight. We don't want to keep you on the webinar all day.

So for for demo purposes we built that integration as a real time so that you can see the data flowing across all three very, very quickly.

99% of the time when we build a GL integration into intacct. It is done in batch and there's a whole bunch of different ways that we built those we've got a client who

They tend to have to make a lot of adjustments somebody makes a donation and they

They get a call, they call up the organization, say, hey, I meant to give it to this but I gave it to the general fund. Can we can we move

And in Salesforce. It's very easy to just go in and edit the record. But if we've already synced it to accounting

It's, it's not quite. It's not quite the same. We've got to get into reversals and so forth. And you're never going to

You're always going to have some kind of adjustments to deal with. And we've got ways of doing that. But what this one organization did was they actually waited a whole week and

You know, some might say we needed it more frequently. We can do whatever interval interval, but they wanted to give it a week before they sink things over just to make sure that they had accounted for any adjustments that might pop up shortly after somebody made

Some excellent question.

Melissa Waters: Here we've got another question that just came in for you. Is there a best time and the fiscal year to implement says eg to Q build three Q run parallel for Q Final Cut over

Scott Hollrah: You know,

There really is no magic answer. We certainly have a lot of clients that try to that want to tie their the launch of their integration to the start of the fiscal year or the start of a quarter.

I think that what it really comes down to is how bad is the pain that you're experiencing in the organization. And can you wait until then to resolve it or

Is it just going to hurt too much.

In the interim, I don't have a I don't have like a specific magical answer for you. I think it really just depends on on what kind of

What kind of struggles, you're having in your organization.

Melissa Waters: So she follows that by saying pros and cons of two stages one convert to intact and then second year do integration with sales force versus doing and one project.

Scott Hollrah: So we have had clients that have done both we've had clients that implement intact first

We've had clients that have implemented intact first and then implemented Salesforce and then gration we've had it go the other way. And we've also had organizations that did them at the same time.

If you do them at the same time, you need to make sure that you've really got the the bandwidth and the ability to absorb that much change at one time.

How can you afford to have your focus divided among you know multiple, multiple projects? And if that's the case. Yeah, full, full speed ahead but

You know, there's a lot of people that also choose to do the crawl walk and run phased approach.

And and in some ways that can even be advantageous. You know, sometimes you have to live with a system for a little while to figure out how exactly you want them to be integrated

And by doing things manually for a little bit. It gives you some perspective on on how you want that integration to actually run

So there's there's definitely no magic answer. It can be done both ways. But a lot of it just has to do a lot of it's going to come down to how much time can you afford to give to multiple projects at once.

Melissa Waters: Yeah, she thought that by saying they have Salesforce already, but it's not fully mature.

Scott Hollrah: Gotcha.

It is important that you've got things pretty well settled out again, you know, going back to the conversation toward the beginning about process.

You need to make sure that you've got your processes buttoned up and and I may be over reading into it. But if things are not very mature. That tells me that processes may still be in development. So I'd want that to settle out before before starting the integration project.

Melissa Waters: Another question came in I. How can I register for this certification course and how long will it take

Scott Hollrah: I'm guessing that's in reference to the Salesforce nonprofit certification exam.

Salesforce has changed how they do their certifications, I believe that if you go out to trailhead that salesforce.com you'll be able to find information on

All kinds of certifications and as far as how long it will take. I mean, the exam itself you the exams range and the time that you're allotted between probably 45 minutes in a couple of hours. But, you know, really, it's kind of kind of up to you.

And and Salesforce with their certification exams, they, they do not make them easy. I used to say they are not Mickey Mouse exams, they really, really test your knowledge and so you definitely have to go into those exams being very prepared.

Melissa Waters: Right. And here comes another question for you. Scott, how long does it take to convert from Razor's Edge to Salesforce.

Scott Hollrah: That's it all depends. I would say, thinking about the the conversions that we've done

Theyre probably three to five months if we're just moving the donor data from Razor's Edge to Salesforce.

You know, could probably be done and 90 ish days.

We did a project recently for adoptions organization. We worked on it with the with the folks at JM T consulting

And they were thinking really really big picture and they see saw that the full value of what Salesforce could bring. It's not just the Stoner system.

It's this platform that we can leverage for all kinds of things. And so

In addition to getting them off of razor's edge for the donor management and moving that into Salesforce. We built a portal or a community where

Families who are looking to adopt could go set up this profile start their, their online fundraising. See what the donors were were

Providing for them and their families and and and even had a mechanism by which, when a family needed to receive funds to pay for things. There was a way for them to request.

funds through this community and integrated with intact. So it depends on how far you want to take it. I would say minimum 90 days.

Melissa Waters: Gotcha. Next one, and

Make sure I can ask this, right.

How to think about then versus JMT, which one win.

Scott Hollrah: So it's not an either or it's it's a both end or might be one. Now one later we we're not competitive with JMT. JMT is not competitive to us.

We can't do what we do without them. And our goal is to come along and together between then and JMT create that successful and seamless end to end system we're complimentary not competitive.

Melissa Waters: Perfect answer. I like it.

Alright so far. These are all of our questions. So I'm gonna leave it open for just a second, see if anybody else has any questions.

And while we're waiting, I'll take this minute to to say Scott's presentation got you thinking about your back office, the systems you leverage and how, you know, things can work better together.

We want to know that both Venn and JMT can help you streamline those processes.

We'd love to have a conversation with all of you and learn more about your nonprofit and how we can help.

And today we're doing something fun that as an added bonus for the first five people that sign up to chat with us and we'll send you a Starbucks gift card.

And the way you can do that is going to JM T consulting com backslash book, but we will also have a team that will follow up with you.

And can also put you in touch with Scott for anything as well.

So I don't see any other questions coming in. So Scott, I'm gonna wrap it up. I'll let you say any final remarks and then I'll take it from there.

Scott Hollrah: Well, thank you so much for for hosting me and allowing me to present. I hope this added value.

As as Melissa said, You'll, you'll get a copy of the slides. But if if you're eager to talk if you got some questions.

Head out to Venn technology com and connect with us out there and we'll, we'll get you squared away. Thanks so much, everybody.

Melissa Waters: Thank you everyone for joining us and Scott. Thank you as always for your time today and I hope everyone has a wonderful day.

powered by
CATEGORIES: Product Demo