I don't know why, but when you mentioned that my most nostalgic scent was in the social
my age, but I guess it's coming back.
So maybe it's not, is when you used to first open up a vinyl album, there was always a
specific smell that came from them.
So you'd pull the plastic off and you'd open it up and you'd go, I got a new album.
Kyle, what's a nostalgic scent for you?
Nostalgic scent?
Yeah.
Nintendo.
Oh wait, that's not a scent.
Yeah, yeah, yeah.
What is this?
What is it?
It smells like mold at this point because it's so old.
Dust?
What does dust smell like?
I like how we're getting such nice scents.
Can we smell plastic?
Can we smell dust?
When I play my old games, that's when I get dust.
Very dusty.
You know, I don't analyze, you know, just the nostalgic growing up stuff.
I think it's more of the, you know, mom making the cookies, you know, or sugary cereals,
other stuff that comes to mind, stuff like fruity pebbles and stuff like that is nostalgic.
You get fruity pebbles anymore?
Yeah.
Oh yeah.
You get fruity pebbles.
Yeah.
When stones are still a thing in the world?
Yeah.
Oh yeah.
Yeah, that's that.
That one survived with it.
Lucky charm's another good one.
Like I've listed off a lot of things that might be potentially be carcinogens.
This is great.
Most likely.
So Kelsey, what's a nostalgic scent for you?
That's such a tough question.
Right.
I think it's one thing if I'm not smelling it, like I feel like if you smell something,
then you're like, oh, that reminds me of that.
But I do agree with Kyle that I feel like food smells and I'm still remembering like
going to Disneyland as a child and the fact that they pump smells into Disney, which is
just super fascinating to look into all of that.
But we're like the smell of just like, oh, it smells kind of like sugar and things in
the air.
You're like, that's such a happy association that I'm like, I don't know if it makes sense
for my house to always smell like that.
I tend to use the volcano scent so that I smell like an anthropology store instead.
This is fine.
As we discovered in past episodes, I like shop too much.
So it all checks out.
But I agree.
And you know, like sugary goodness.
But what about you, Ariel?
I was trying to think of like a good one because I didn't want to say burning plastic or something.
But actually, like, you know, I'm thinking like manure.
That sounds weird.
But like when they spread manure in the fields, like I grew up near farms.
That's what I think of, you know, if that's something that I smell now, but that time
of year.
So I get that.
You have like it's like, it's a very strong smell too.
You're like, you can't ignore it.
You know what it is.
I like how we have vinyl kind of plastic dust with the end of cereal manure and then I'm
coming in with, oh, by the way, I like the smell of Disneyland.
Disneyland.
What a wild group.
Oh, man.
I don't know if I can assure one thing I can't stand the smell of.
Of course.
Casinos.
Yeah.
I've never been to casino.
Smoke.
Just think of it.
Oh.
Stale smoke.
That's what it smells like, stale smoke with a lot of spilled drinks.
It's nasty.
And then in Vegas, they tend to try to put this vanilla smell over the top as though
that's going to fix it.
It's disgusting.
You're really selling going to a casino for me.
I'm going, yeah.
Yeah.
No, thanks.
You got to go at least once.
There.
There's my pitch.
You got to go at least one.
I'll go and report back on the smell.
Yeah.
Yes.
Well, this conversation started because we were talking about our office and what scent
we would want to pump in like Disneyland.
So today on our Tech for Business podcast, we're talking about tech partners and why
you need one.
So Kelsey and myself are joined by Kyle, our president and CEO, Todd, our COO and CISO.
And before we kind of dive into why you need a tech partner.
I just want to kind of level set what do we mean by a tech partner?
What does that mean?
Because that's a big umbrella.
So Kyle and Todd, when I say tech partner, what comes to mind for you?
I can jump in real quick before Todd gets going here.
Why?
It's a, to me, it's an external third party group that has experienced their resources
to assist with skills you do not have in-house.
So that could be related to just computer deployment or server deployments or server
upgrades to physical security to cyber security to application development.
So there's a whole, there's a lot there and a lot of different category sides of it, but
it's really that external group where you reach out to to get additional expertise
you just don't have in-house.
Nothing alike in the plumber, electrician, other types of services you would bring in,
but obviously more slated towards business related services.
Yeah, I tend to agree.
I mean, when you first threw out the phrase, the first thing that popped into my head was
trusted partner.
It's that place where you would go to get additional knowledge.
But it could be something that is the break fix person too is I don't know how to break
fix this.
I mean, can I lean on somebody quickly or something that potentially is an added service,
if you will, if you have the ability to outsource a component of something you just simply can't
get to.
So that ad would be another thing that I would add to it.
Yeah, the other analogy that comes by is you're a CPA and I'm an accounting firm of
those things where you bring in that external expertise to assist with a knowledge side of
it where there's, there can be a lot of additional complexities.
So you hire a CPA firm to help.
The technology partner serves in a lot of those roles as well from a strategic guidance.
So obviously a lot change in technology rapidly, so it can be very difficult to keep up.
Yeah, for sure.
So we've touched on this topic before and I'll make sure to kind of link that in the
description, but I sort of wanted to go through when we're talking about businesses, I kind
of think about small, medium, large, and what a tech partner, why those may or may not need
a tech partner, what pros and cons come for each of those sizes.
So starting out with kind of the small business, I'm thinking like, when I think of small business,
I think of like mom and dad, there's like two to five employees, they probably got a
guy, they bob, who knows how to turn the computer on and off, like that's their level of IT.
Why would a company like that need a tech partner?
Well, you kind of got into it.
They got somebody that knows how to turn on and off, but all the rest of it, they don't
know how to do.
And this scales into the large side too.
It is kind of like into that, the technology change is so rapid that they're just, they
don't know what they don't know.
Is that kind of the simplest term side with it?
So by engaging and having a tech partner, the tech partner is constantly getting information
on industry changes, new technology shifts from key vendors and new solutions that potentially
could be introduced into their business side of it.
By having regular cadence and conversations and engagement tech partner, you're going
to get some insight as to how that technology can assist their business.
Because most likely they're not doing technology as their business, so they have, whether they're
repairing cars or they're an HVAC shop or whatever it may be, they got their knowledge
that they're delivering and the tech partner brings in the technology information to help
them.
Yeah, what I'd expand on there is very similar, but I would add that they do typically have
their hands full.
Those individuals typically are wearing all the hats, so it's not multiple hats where
you'll see in some business, they're wearing all of them.
And to your point, bringing in Bob, he's typically going to be a friend or somebody down the
street or a neighbor or somebody like that, and he may have some stuff in place, he may
not.
A great example is I was talking to a smaller org that we don't even actually do business
with, and they were kind of complaining about some things that were dealing with in this
particular case, it ended up being their internet connection, and they just had an old, I don't
really remember the vendor, I'll just say Comcast, and I'm not picking on Comcast, don't sue
me please.
But they had an old internet provider, had a very small bandwidth on it, and over the
years what just ended up happening is, and this is pretty typical, you get your technology
in place and it just sits there, there are ads, right?
There's changes, and the way a lot of those agreements are written is there is just this
natural progression, and they were paying a significant amount for what they had in place,
and I said have you ever considered looking at cable or if there's fiber optic in the
area and just did a quick search on my phone, looks like you've got three other vendors
you could look at, have you considered that, and it took a multi-hundred dollar bill down
to 50 bucks by switching to a new vendor.
Now you don't always get the lock into that price for a significant amount of time, but
just as a simple, what can a tech provider do for you is a simple question like that
can save you hundreds of dollars per month, but to Kyle's point too, it can help you with
stepping up your business as well.
So I think on the small business end, it seems like, yeah, they definitely need to help,
but one of the hurdles that they're running into is financing.
If I just have Bob, and Bob's who I got and I can afford, I mean, how does that conversation
with a tech partner go when you say, I got five employees, I don't know if a tech partner
is right for me?
Well, I usually like to lead into those again to get to that.
It's not what it costs, it's what it's worth.
And I think you have to take a step back and separate those two, because to Todd's example
he just gave, again, you may be getting free or very low cost services from somebody that's
got technical aptitude and just moonlighting or something on the side, but they're missing
the objective of the speed of the internet and those overall cost of those things, how
that's affecting the productivity of the business.
You're losing dollars every single day because you didn't, you know, it just brings somebody
in that's just got a little more insight as to how to improve the productivity of your
workers and then all of a sudden, boom, you know, in the smaller you are, the more almost
immediate that can be.
So when you're wearing a lot of hats, you're trying to service your customers.
I mean, that can be a real killer, you know, just trying to get something done is taking
so long or you're troubleshooting your Wi-Fi continuously and or, you know, God forbid
you get, you know, a cybersecurity incident or those things, how impactful those can be.
So, you know, there's it's worth it just to do it and get it done right and bring the
right person in will pay dividends in the long run.
Yeah, one of the things I like to lean on is return on investment and that's what Kyle
is really saying.
It is not something that all small businesses are looking at consistently, especially when
it comes to technology.
They're not looking at it saying, well, if I spend this, I get this in return.
But that's exactly what Kyle highlighted, right?
A great example would be this business thought they could get away with an iPad as their main
computing tool set or they're using a Chromebook.
And then the reality is, is they're trying to build quotes or they're trying to process
the cash, whatever, transaction and it's being slow or you guys have probably all experienced
it, right?
You go in and they're like, oh, the computer is causing me problems.
How many times have we got to check out?
And that's the comment you get.
Oh, the computer is causing me problems.
What is that costing you?
Do you have a line of people out the door that can't check out because you're having issues
with it?
So if you invested on a really nice PC and let's just say that you're, I was going with
the iPad example, you spent a couple hundred bucks on an iPad, but if you had a thousand
dollar device, would that have increased it?
Would you be able to check out more people?
Would you give a better experience to your customers?
What is that worth?
That was exactly Kyle's phrasing, right?
Those are the things that aren't always considered because it's technology.
You're not great at it.
What you're great at is counting, whatever it is.
And so you don't always think about those kinds of things, but the partner can kind
of come in and quickly highlight those.
They can look at things very easily and say, you're internet slow.
You're spending too much on your phone system.
Your phone system barely works.
Whatever the case may be, you can start to quickly look at those things and identify
areas where you can get quick, fast impact, reduce costs, get better deliverables, et cetera.
And that's where those partners typically come in and really have a big bang for the
bug.
Yeah.
The ROI is the right message side of it.
Let's just do an inventory and just understand that.
I mean, it's true pretty much all businesses, the labor is the most expensive cost to every
business that's out there.
And even if you're a business of one or you're a business of a thousand, it's always your
time or all your people's time that add up.
And it doesn't take much.
And it multiplies.
So a thousand people being affected by an internet outage or slow internet really gets
to be a big ROI quickly.
But again, likewise, when you're a small business and it's just you or a couple of people, again,
you're still feeling a significant impact because you don't have that much extra time
to give.
And wherever you're spending your time, if you're troubleshooting your technology or
you got a slow computer, the computer you bought off eBay because you wanted to only
spend a few dollars is ultimately costing you a multiple more in your productivity loss
than if you just going out and bought a brand new current model is typically what probably
should have been done.
In most cases, come in there because you hear horror stories.
We walk into it all the time that they went by the cost matter factor.
They had a technology.
Somebody was advocating to cost alone and says, no, we just want to buy something cheap.
We don't have a lot of money.
You know what I say?
I want to buy something cheap.
And it's like, well, the people using it aren't cheap.
So why are you giving them the cheap tools?
Those are always the things that always just we want them to just take a step back and
say, this is ultimately costing you a lot more than you think.
Yeah.
I think a lot of these things, as we sort of move up on the tier to maybe like a medium
size business, which is at least our kind of bread and butter, but you know, what are
the differences in pros and cons when it comes to working with a tech partner with a medium
business?
I sort of think about it as they probably have a team.
Maybe some of their employees are a little bit more tech savvy.
So what does it look like for them to have a tech partner?
Yeah.
With the medium size organizations, it's usually is getting them focused on the business applications
and the business, how they use technology specifically within their business and trusting
the partner to do the general IT support needs sides around the patching, the asset inventory,
you know, up, down, monitoring, all those types of things that are, you know, just very
general support, but to have one person or a couple of people internally do that really
takes away, again, doesn't necessarily move the company forward on how technology is servicing
them and or their customer sides with it.
So strategically engaging those as well as having that partner available for knowledge
supplement, supplementation when you need it.
So when you have a project, when you need to do a new initiative, are you going to go
through an acquisition or whatever it may be, you can, you know, engage that partner,
bring in the additional help when you need it, and then have them pull back when you're
back to normal operational and support more side of it.
So it's, it's, we see organizations that tend to, you know, feel like their on site IT
needs to know everything about everything and they need to, you know, do it and carry
that full burden side of that really is just not realistic in this day and age.
You just can't do it, you know, that it's too big of a too big of a roadmap to try to
cover it all.
It's a lot of ground and mistakes are going to be made and there's going to be things
that just don't happen.
And that leads to other more business impacting outages things, you know, can be as far as
it is a really bad cybersecurity incident because they didn't have time to pay attention
to patching or deploy the right security tools or the knowledge to know what security tools
they should use to, you know, just, you know, misconfigured firewalls or things that were
left undone, you know, poor password management accounts that weren't deactivated.
I mean, there's just numerous things that happen when it's just on one person.
It's not that they didn't have the knowledge of skills, just their spread to thin.
And then ultimately they're not focused on where, you know, as a technology partner,
we don't know that businesses generally, you know, certainly as well as they do in their
customer side, but we know general IT very, very well.
And we can do that extremely well.
And that's true of most tech partners.
They can come in, they can do that incredibly well and provide that augmentation services
to really allow that person then to make sure that their sales team, their manufacturing,
whatever it may be, that the technology is getting handled correctly for what they need.
Todd, anything you want to add on that?
What am I going to say after all that?
No, I agree a lot of it.
I was trying to figure out where I was going to come in next and kind of fill in, but you
covered a ton of ground and it makes a lot of sense.
You will see in some medium-sized businesses where IT reports to somebody who may not be
very technical.
So we will run into that too.
And so Kyle touched on that already, is do you need that additional expertise?
And I think it makes sense to kind of highlight that in the senses, even when they do have
technical expertise, those people are very spread thin, very, very often, and it is very
hard for a technical person to know everything.
So cybersecurity was a great example.
Cybersecurity guys are very, very specialized.
They just are because there's so much to it.
It's a very broad topic and there's a lot to know in it.
And those individuals are very expensive.
So when you're looking at medium-sized businesses, they typically don't have the expertise in
every vertical.
So that's one of the reasons why they'll typically look for a tech partner.
And then the other part that Kyle mentioned and I wanted to highlight it is, I always
try to explain it to leadership in the sense of when a partner comes in and they bring
in automation or they're bringing in the stuff that you can easily automate, you're freeing
up your team to do the highly strategic work.
It's the stuff that drives the business further instead of just doing, like Kyle mentioned,
the patching, the updating, the reboots, the password changes, etc.
Those things you can really streamline and you can use tech partners to help you get
those things done.
And then you can actually start focusing on the things that matter.
A line of business app that you're not getting the right reporting out of or tuning up your
SQL server or whatever the case may be, you can focus on the things that truly matter
and less of the day-to-day things.
We've run into many cases where, you know, when you talk about the tool sets that a tech
partner brings in that is that automation Todd's talking about for how you manage your desktops
and monitor your servers and you can be telling those system sides of it why you can go out
and deploy these internally again and bring these even in as an internal application.
Again, that requires now focus inside of there and now automatic.
So it's usually I've had these conversation sites to say, you know, we have multiple
full-time employees that just manage those platforms.
So for you to take your internal resources and now say you're going to devote a high
percent of your time to manage the management platform itself, just as something they don't
think about.
They think it's all I'll do this capital acquisition or pay this monthly fee for this piece of software
and it's just going to do all this work for me and then I don't have to pay this technology
partner.
That's only the acquisition costs.
The management cost is where, you know, the rubber hits the road and it's where most of
the time gets spent.
And again, it's that other ROI component.
There's a large cost side to it because many times to come in and customers have invested
in the past into these platforms and they are collecting, you know, technology dust.
They are not used.
They're not used correctly or they basically were abandoned because they just gave up as
it's just too much for them and they just lost the priority for it.
So it was shiny for a while.
They tried it and just forgot about it.
So again, that was just money probably not well spent.
It's just that it happens far too often.
Cybersecurity falls into the same category too.
Or you would deploy the tool that's up.
It's running.
I don't need to pay attention to it.
And that does tail really well into the cybersecurity point I was going to make is you bring in a
tool set whether it's endpoint detection response or something else that's potentially
more robust and those things create a lot of additional information that you need to
sort through to be completely blunt about it.
And it does take a lot of time and attention to go through all of it.
And a lot of companies will kind of go out.
It's really not that big of a deal.
My team's got it.
We really don't get that many alerts.
But if you look in the cybersecurity world, all those alerts do matter and you will find
that as people do that and they focus heavily on it, there's a ton of burnout that goes
with it.
So conceptually what you'd be looking at as a tech partner in that situation is you're
for all intents and purposes, you're outsourcing that burnout to somebody else.
You don't have to worry about your one guy that you lean on for everything day in and
day out getting burned out and going, I've had enough.
I'm out.
So that would be another good reason as well.
And if they're looking at cybersecurity tools, who's looking at the backup tool?
Who's looking at the monitoring tool?
Who's looking at, who's taking care of the user requests for the applications?
Who's handling the upgrade?
I mean, again, you can start to put together real quickly how it just gets underserved.
Some area gets ignored.
There's only multitasking is a myth.
You can't multitask.
They're only looking at one thing.
They're task switching.
So they're going to look at one thing and the other stuff's going to get ignored until
they do the attention and it's just going to go around.
But something is not getting handled right.
So it makes a lot of sense to strategically outsource what makes sense.
You know, it gets back to getting everything organized, know what you got, automate what
you can and then outsource what makes sense.
That's the best way to approach.
Bob's a busy guy in case anybody wants to know.
Yeah, Bob is busy.
Bob's busy.
Still have some burnout.
He's going.
Well, as our business kind of grows, maybe Bob now has a full, robust IT department.
He's got some security guys.
I mean, we're talking like large companies.
Would a tech partner in that circumstance even be worth it?
You know, if they've got a full team, if they've got, you know, their different departments,
what does a tech partner look like for them?
Those are typically very strategic side with it.
So it's usually a lot of project related services sides of it.
They tend to, you know, our large groups, again, as you mentioned, have teams so they
have knowledge that get trained, you know, in many ways.
So the daily maintenance side of it, they do have people that they have the full-time
employees done the management systems, those things typically side of it.
But when they're ready for upgrades, again, they're managing that already.
When they need an upgrade, they don't have the extra time or bandwidth to do that and
still do their, their main job.
So bringing in the technology partner help augment, handle the project, transition back
to operations, customer takes over the operation size, if they move on.
So it tends to be very, very project focused and very strategic as to how we get engaged.
Yeah.
And I think those larger companies typically know what they're needing additional help
with because there's a lot of different things that come out there.
So if you're in a large company and you have compliance, there's always a need for a third
party validation.
So you could potentially looking at it as a partner that comes in completely independent
from you that's coming in and validating.
And as Kyle mentioned, there's all kinds of projects.
It could be switching, it could be firewall, it could be cybersecurity remediation.
There's a lot of stuff that does take additional resources.
And as we mentioned, and this is true across all sizes of businesses and most business leaders
already know this, but you have limited resources and ultimately your IT guy can be, or gal,
can be full 100% all the time and it then becomes what is the priority where our tech
partner potentially comes in and helps make a boon is you've got the ability to kind of
toggle an on off switch of how much you want to ramp up to something.
I've got a very specific project I want to get in before the summer is over.
Schools would be a great example.
I'm going to quick toggle up.
I'm going to outsource this piece and then I'm going to pull it back down and I'm going
to be able to control my costs.
So it becomes a very easy variable expense for them to manage.
I can budget for it.
I can plan for it.
I can use it and then I'm going to take it away or it can be something that's very supplemental.
So you got that very specific technology need that you need.
Again going back to the example that I meant mentioned with the security alerts is it's
a lot of information.
And if you could potentially outsource that at a reasonable cost that might be desirable.
So those are some good options that would potentially be out there as well.
Yeah.
And there's that knowledge augmentation.
They may recognize for example that they want to do a zero trust deployment.
They want to do some zero trust platform deployment but they don't have the experience yet.
They may have done some initial training side of it but they don't feel like they're ready
for implementation because they've just never done it before.
So again bringing the technology partner let them do the assistance or do the initial deployment
of it and allow them to shadow through that deployment and then be ready to take over
the operations after some handoff and training and then have that tech partner kind of be
the point of escalation when they feel like okay I'm something not familiar with I'll
engage this tech partner and see if they have some familiarity.
So there's some escalation of troubleshooting those things that occurs in those sites.
So very augmentative.
Yeah.
One last thing that I'd throw on that just to kind of highlight it is because your tech
partners tend to be across industry, healthcare, finance, manufacturing, etc.
They tend to see everything.
So they're much more likely to have that additional expertise that Kyle is referring to.
So when you get stuck it's certainly possible and most companies have felt this before.
It's even when the small company you reach out and say, hey Bob I don't know how to do
this Bob has at least a thought of what to go on because he's got a lot more experience
in that technical area than a lot of other organizations.
So the tech partners do have that wide breath that does give them those additional insights
and they work with a ton of vendors.
So when people are looking for what's the right tool, how do I know what's a good fit
your partners typically can do it.
Most of them aren't just schlepping skews.
Some may be but most of them aren't I was going to bash a very large one that I'll leave
it alone but that is their job that is their business model and they will have the ability
to say hey we looked at X, Y and Z and the reason why we picked Y is because of all of
this information they can help you through that process as well.
Yeah.
I feel like-
Yeah and the tech partner can have access to some additional levels of technical support
to that the customer may not be able to get to because of certain certification levels
or partner level size of those we can leverage access to a higher level of support which
again is another reason to potentially engage them on the troll between process or escalation
process because they may be a lot quicker than the direct vendor support is the way
a lot of times they get structured.
It certainly depends on the product and other sides but in many cases that seems to be the
model that is leveraged is have your staff certified, months are certified, if you're
certified partner side of it you go to this direct to this tier support you don't go to
the first tier and wait and then troubleshoot side of it the partners typically skip those
first initial tiers and get right to more knowledge related experts which expedites
the troubleshooting process.
So I wouldn't be doing my due diligence if I didn't ask is there ever a time when a tech
partner is not right and then I'll kind of open it up for closing thoughts.
No.
And that's the end of our presentation.
Again that's pretty broad it really depends it certainly really depends.
The one thing that comes to mind directly area on that side of it again is with very
verticalized applications when you go much you know that are you know part of the line
of business application for example whatever you know your ERP system is and how are you
using ERP to service your customer side of those.
Again very that's very specialized and not that there aren't again consultants that can
probably come in and drive into that.
If we're talking more general technology partners what we're kind of been speaking of here typically
not your not your group you know for CIT for example when people have using Salesforce
or they're using Microsoft CRM that's not us you know we were more the technology plumbers
is kind of get into making sure that the speeds the feeds the users accessibility their devices
are secure and performances there and have accessibility to get to Salesforce but once
they log into Salesforce we don't know you know and that's so usually once it gets deep
into those things that's another consultant or something better served you know by a champion
in the business themselves.
Yeah my feedback was going to be when you have the expertise is when you wouldn't need
the partner but you wouldn't even be looking in those situations.
The one that I do want to caution on though would be when you don't have the money which
would be probably a natural thought for most people but I think the having the real good
conversation about what is it the worth and what is the ROI that probably is a different
conversation than what your first reaction is I don't have the money for that.
It would be worth the conversation to figure out whether it would be worth spending some
additional dollars or reallocating them if that makes more sense.
Yeah just better planning in that case you know whether you don't have it now but plan
for it ahead of time so you can allocate it will pay dividends just like you're essentially
savings for the right full deployment so save save up to do it right you'll actually be
probably much happier with the results long term than than cutting corners.
Yeah so my closing thoughts are in most cases a tech partner makes sense they can help you
strategically and kind of tailing off the last thing that Kyle said is that budget cycle
is important if you're thinking it is something that you need to be considering if you've
put the time and energy into planning for it you can typically figure out how to pay
for it Ava it's next year or you've built a plan to say how do I put this in in phases
zero trust was one of the things that Kyle mentioned earlier that's not a I put in a
tool that works it's a process you need to plan and you need to work on it it takes time
but if you build the plan you build the budget you can get there from here.
Yeah yeah planning is key on it you know and the last thing I was going to say is you know
when you engage in the technology part of there's many things they'll offer just you
know the advice just from the initial engagement side of it so you know if you're not sure
if you haven't you know start a conversation that's typically you know no obligation it's
not costing anything to just have a conversation and see if there's an alignment and there's
a value side of it there's you know I know for us the initial conversation you go out
there and talk and do that discovery and even like Todd was mentioning on the internet side
of it that that that's just you know typically falls under a sales engagement that's just
an introductory you know side to see if there's an alignment that's cost of your little bit
of your time but that discovery could give you some better insight as to is it the right
technology partner for me and is there potential you know ROI that I can see come out of that
that's that's just an investment a little bit in your time you know so you don't really
have to go deep into your in your budget to worry about that just set aside some time.
I love it that was all very informative I love we touched on more than IT you know it's
strategic it's planning it's budget there's so much more that goes into having a tech
partner and it costs nothing to look it costs you know a conversation is often free so thank
you Kyle and Todd for joining us today if you enjoyed this podcast please like subscribe
if you have a question or a topic or you enjoyed this more you know strategic and business conversation
please let us know reach out to us at info at cit-net.com or head out to our website
cit-net.com slash podcast and we'll be back next week with an all new episode.