Sept. 24, 2024

Episode 340: In the Dynamics Corner Chair: A Journey into the Cosmos

Cosmos is a fully cloud-based reporting and analytics platform designed for Microsoft Dynamics 365 Business Central. With Cosmos, you can make data-driven decisions at the speed of business. It is the only true cloud reporting and analytics solution for Business Central, built for accurate data, rapid insights, and everyday users.

In this episode, Anthony and Brian unveil the latest enhancements to the Cosmos solution, revolutionizing how businesses report with Microsoft Dynamics 365 Business Central. Listen as they discuss the powerful yet simple design, providing a comprehensive view of reporting and analysis. They also discuss the "BC Bash" event at the upcoming SummitNA Conference in October 2024.
Connect with Anthony Bonaduce on LinkedIn (https://www.linkedin.com/in/anthony-bonaduce-88211154/)
Connect with Brian Petersen on LinkedIn (https://www.linkedin.com/in/thebrianpetersen/)
Learn more about Cosmos (https://www.cosmosdatatech.com)

Send us a text

#MSDyn365BC #BusinessCentral #BC #DynamicsCorner

Follow Kris and Brad for more content:
https://matalino.io/bio
https://bprendergast.bio.link/

00:00 - Dynamics Corner

14:00 - Simplified Data Migration in Cosmos

24:38 - Simplified Quote Form Interaction & Implementation

35:02 - Business Central Deployment and Customization

40:36 - Simplicity and AI in Reporting

WEBVTT

00:00:00.740 --> 00:00:07.389
Welcome everyone to another episode of Dynamics Corner, the podcast where we dive deep into all things Microsoft Dynamics.

00:00:07.389 --> 00:00:19.152
Whether you're a seasoned expert or just starting your journey into the world of Dynamics 365, this is your place to gain insights, learn new tricks and understand what a good reporting and analytics tool should be.

00:00:19.152 --> 00:00:21.788
Simple, I'm your co-host, Chris.

00:00:23.080 --> 00:00:23.763
And this is Brad.

00:00:23.763 --> 00:00:26.972
This episode was recorded on September 6th 2024.

00:00:26.972 --> 00:00:29.484
Chris, chris, chris, simple.

00:00:29.484 --> 00:00:31.931
I like simple, me too.

00:00:31.931 --> 00:00:41.049
I like data and I like analysis and I like it to be simple and I also like big news.

00:00:41.049 --> 00:01:15.596
And with us today, we had the opportunity to speak with two longtime friends of the podcast, brian peterson and anthony bonaduce of cosmos, to learn all about cosmos and the new features that they've added to the product welcome welcome we do this.

00:01:15.635 --> 00:01:18.277
We do this routine before this whole thing starts.

00:01:18.277 --> 00:01:19.439
Okay, we do like that.

00:01:19.439 --> 00:01:25.069
You know, when you're uh, when you're a singer, right Like you got to go through that throat exercise.

00:01:31.500 --> 00:01:31.965
So it's just.

00:01:31.965 --> 00:01:37.471
I had a little funny throat exercise this afternoon and just sometimes we just come in and we want to do it.

00:01:39.760 --> 00:01:39.801
Mr.

00:01:39.822 --> 00:01:42.530
Bonaduce, did I say something that you didn't agree with?

00:01:42.879 --> 00:01:44.006
No, can you hear me, okay now.

00:01:44.819 --> 00:01:46.346
I can hear you perfectly fine.

00:01:46.667 --> 00:01:48.582
I did the test, I tested everything.

00:01:48.582 --> 00:01:50.870
Of course, it all worked, your mic's working.

00:01:50.870 --> 00:01:54.829
And then I of course had to go back to old, reliable, my little desktop speaker.

00:01:54.829 --> 00:01:55.432
So there we go.

00:01:56.219 --> 00:02:03.992
It's just like when you're doing a presentation you can spend a month preparing it, walk through it 300 times and then, the one time you have to go, do it live.

00:02:04.873 --> 00:02:05.974
Something always goes wrong.

00:02:05.974 --> 00:02:09.764
Something goes wrong.

00:02:09.764 --> 00:02:10.264
What's up, guys?

00:02:11.086 --> 00:02:12.889
Nothing, nothing Been looking forward to speaking with you.

00:02:12.889 --> 00:02:23.230
I haven't had the opportunity to speak with you on the podcast in a long time, so thank you for taking the time to speak with us this afternoon.

00:02:23.230 --> 00:02:26.680
I'm looking forward to hearing a lot of great things from the two of you.

00:02:26.680 --> 00:02:28.697
I've been seeing a lot of great things from the two of you.

00:02:28.697 --> 00:02:30.507
I've been seeing a lot of great things, and now to have the opportunity to discuss them with you is exciting.

00:02:30.507 --> 00:02:38.169
But before we jump into that and talk about all these great things, do you mind telling everyone a little bit about yourselves and Cosmos?

00:02:38.169 --> 00:02:40.187
We start with Mr Brian this time.

00:02:40.187 --> 00:02:41.545
I think we did you last time, anthony.

00:02:42.461 --> 00:02:54.211
So, brian Peterson, I'm the coo here at cosmos data technologies that's it that's it, anticlimactic I know exactly

00:02:54.812 --> 00:02:56.134
wait, do we need to like let's?

00:02:56.134 --> 00:03:00.670
Let's do the elevator pitch of who you are yeah, have anthony do that.

00:03:00.691 --> 00:03:01.331
That's his job.

00:03:01.331 --> 00:03:03.806
That's funny okay okay, mr.

00:03:04.247 --> 00:03:05.288
Mr bon sir.

00:03:05.849 --> 00:03:08.747
Yeah, I guess I'll start and Brian, you can, you know, take notes here.

00:03:08.747 --> 00:03:15.532
No, my name is Anthony Bonaduce, so I'm I kind of act as our CRO, but I'm one of the founders here at Cosmos.

00:03:15.532 --> 00:03:30.352
I've been in the Microsoft channel for I don't know, 13, 14 years, something like that, but primarily focused on all things reporting and analytics and those kind of hot button items, and so, yeah, it's a little bit about my background.

00:03:32.822 --> 00:03:44.122
Great and Chris informed me yesterday because we were talking about how long we've been in the space and we were talking with someone who's been in the space for 20 years and I've been in it for a lot longer than 20 years.

00:03:44.122 --> 00:03:53.811
You're supposed to say decades, so you've been in the space for 20 years and I've been in it for a lot longer than 20 years, you're supposed to say decades, yeah, so you've been in the channel for a decade and a half yeah, it's like, um, you know it's like when people have a baby and they're not sure.

00:03:54.282 --> 00:03:57.054
When you switch from like months, you know people are like yeah, they're.

00:03:57.054 --> 00:03:58.961
You know my daughter's 38 months.

00:03:58.961 --> 00:04:02.787
You know there's a cutoff somewhere in there but yeah, 164.

00:04:02.787 --> 00:04:03.127
Months.

00:04:03.687 --> 00:04:06.954
I felt like I had two decades before I went there, but I got it.

00:04:06.954 --> 00:04:10.949
Yeah, no, no Under two decades sounds better, right yeah.

00:04:10.990 --> 00:04:13.168
Exactly, oh, just under two decades.

00:04:13.168 --> 00:04:15.604
Yes, yeah, you can say a long time.

00:04:15.604 --> 00:04:17.740
That is a good point, though it's when do you transition?

00:04:17.740 --> 00:04:18.401
I like that.

00:04:18.401 --> 00:04:24.728
When do you transition from, like, having an 18 month old to a year and a half old, or 24 month old, or a two year old?

00:04:24.728 --> 00:04:25.988
Yeah, like when.

00:04:25.988 --> 00:04:29.812
When do you, uh, when do you cut over?

00:04:29.812 --> 00:04:31.254
Yeah, it's tough.

00:04:31.254 --> 00:04:33.935
You didn't know that we were going to talk about that today, did you?

00:04:34.637 --> 00:04:38.810
I mean it's an important topic so I'm sure the community's interested, so that's good.

00:04:38.839 --> 00:04:40.161
I think they're interested in one's take.

00:04:40.161 --> 00:04:41.524
We'll have to throw up a poll.

00:04:41.524 --> 00:04:55.779
One of these days we'll have to do a live podcast and we can throw up polls and everything, but no, thank you for joining us Now, cosmos what is Cosmos?

00:04:55.800 --> 00:04:56.221
What does Cosmos do?

00:04:56.221 --> 00:04:58.363
Yeah, I would let Brian go, but after that performance, I think I'll handle this one.

00:04:58.363 --> 00:05:00.086
So Cosmos, simply put.

00:05:00.086 --> 00:05:05.512
Yeah, I didn't know you were feeling short and sweet today, brian, but simply put, Cosmos is.

00:05:05.512 --> 00:05:06.935
You know the way I describe it to people.

00:05:06.935 --> 00:05:16.389
It's the first and only fully cloud-based reporting and analytics platform that's born in the cloud and then built specifically for Business Central Cloud.

00:05:16.389 --> 00:05:27.173
So, obviously, to answer your question in a succinct manner, brad, I mean it's reporting analytics for Business Central, but I think it's, you know, unique in that it really is kind of the first of its kind.

00:05:27.274 --> 00:05:47.252
There's been a lot of, as we know, household names for reporting and third-party solutions in the Microsoft space, but those were all designed for on-prem, they were built for nav or GP, and when you work in the cloud and you work with Business Central Cloud, it's a real delicate way you have to approach the reporting side to make sure things are performant and you're able to get all the data you need.

00:05:47.252 --> 00:05:50.603
And so you know, we saw that gap, as I mentioned.

00:05:50.603 --> 00:06:00.353
You know, brian and myself have been doing reporting analytics for I don't know 35 years combined or something like that 30, 35 years, over three decades.

00:06:00.353 --> 00:06:02.202
Over three decades, 35 months.

00:06:02.202 --> 00:06:08.391
But you know, we saw that gap in functionality and just thought you know what?

00:06:08.391 --> 00:06:11.254
Someone needs to do something about it, and we're probably the people to do it.

00:06:11.475 --> 00:06:14.624
So so you're born.

00:06:14.624 --> 00:06:18.451
Everyone merely adopted cloud.

00:06:18.451 --> 00:06:20.134
You were born in the cloud.

00:06:20.600 --> 00:06:21.701
Yes, just like Bane.

00:06:21.701 --> 00:06:23.786
I got where you're going with that, by the way.

00:06:23.786 --> 00:06:25.949
Yeah, so that's I mean.

00:06:25.949 --> 00:06:28.935
So that's kind of the gist of it, but obviously there's a whole lot more to it.

00:06:31.261 --> 00:06:54.187
No, it's great and I've seen some great things with Cosmos in the cloud reporting and we did have an opportunity to speak with you in a previous episode a little bit more in detail about that and I'd like to talk about how it works and repeat some of that, but I'm impatient, yeah, and I want to get down to the latest and greatest and what's new with Cosmos.

00:06:54.930 --> 00:06:55.230
Yeah.

00:06:55.230 --> 00:07:05.144
So I mean, if people saw our first episode I know you guys, and congratulations, by the way the podcast has blown up, it seems like and you've had some amazing, you know heavy hitters on here.

00:07:05.144 --> 00:07:10.084
A lot of people were, I like, like I said, I wasn't even sure if we were cool enough to be on the podcast anymore.

00:07:10.084 --> 00:07:11.848
So I'm honored to be here as part of this.

00:07:11.848 --> 00:07:17.108
But, um, yeah, I mean you guys had said, hey, when you have something you know interesting, let us know.

00:07:17.108 --> 00:07:18.060
We'd love to have you back.

00:07:18.060 --> 00:07:21.045
That was shocking, obviously, for you guys to invite us back.

00:07:21.567 --> 00:07:30.824
But what you know, what's exciting that we wanted to get on and obviously talk about is that there's been a huge need in general around reporting functionality, which is where Cosmos was born.

00:07:30.824 --> 00:07:39.651
And as the needs of the channel have matured and moved into a more modern approach to reporting, people need something to get holistic views of data.

00:07:39.651 --> 00:07:41.502
So Cosmos was born for BC.

00:07:41.502 --> 00:07:47.091
But then, you know, we started working with customers and obviously there were needs for third-party data sets.

00:07:47.091 --> 00:07:49.235
Right, we have historical data in NAV.

00:07:49.235 --> 00:07:54.992
We want to bring that along with us, or we have some data that lives in, you know, some payroll system or whatever.

00:07:55.012 --> 00:07:57.887
It is right, external data sets, and there's been a big demand.

00:07:57.887 --> 00:08:28.067
We've been pushing as quick as we could to release this, and so now Cosmos can accommodate those data sets as well alongside the customer's business central data, so they can truly have that holistic, comprehensive single data repository that harnesses and kind of mashes together all of their data across the organization and then obviously expose that comprehensive view into reports, excel-based reports, power BI dashboards, analytical views, whatever you want to do.

00:08:28.067 --> 00:08:30.988
And so that's the really, I think, exciting stuff.

00:08:30.988 --> 00:08:35.351
We announced that last week and it's been busy, we'll put it that way.

00:08:35.351 --> 00:08:38.610
So I know that's validated needs right there, I guess.

00:08:39.380 --> 00:08:40.787
There is a huge need for that.

00:08:40.787 --> 00:09:05.390
But before I get into it, I do want to say you both always have vip access to the podcast so you don't even have to wonder if you're cool enough your og you have that vip card until you don't yeah just remember that you have every card, but it can be revoked yes, no, see you again on monday, anytime you want to, you can just slide right in.

00:09:05.431 --> 00:09:07.073
We make time, just like we did today for you.

00:09:07.073 --> 00:09:08.743
Uh, it's, it's.

00:09:08.743 --> 00:09:13.389
Not many have that status, but the two of you do the.

00:09:13.389 --> 00:09:32.030
That is more significant than it may sound to someone that's listening, because reporting on business center, which is cloud-based application, is it's important and what you had put together is easy and it's almost turnkey right, so somebody can set it up and get it running in a short period of time.

00:09:32.030 --> 00:09:35.245
I won't say the statistics you may have some more information on that.

00:09:35.245 --> 00:09:49.215
But now to bring in other data sources to report alongside of that is significant because Business Central is a fully functional ERP software application that can satisfy a complete business right, all the areas for that business.

00:09:49.662 --> 00:10:03.186
But I work with many businesses that have other separate systems that perform another function or a need that has data and they often struggle with okay, how do we take this data and put this together so that you can report in one, as you had mentioned one place?

00:10:03.186 --> 00:10:14.889
So I think that is such a need for that I had a loss of words there within the space, so that somebody can report off many different systems.

00:10:14.889 --> 00:10:39.782
And, to your point, with space being I don't want to say it's a premium, but this space for Business Central or having data when you're doing a migration from one system to a new system or even an old version of Navision, nav whichever version you want to say, depending on how long you've been working with it to not have to worry about bringing that with you or bringing that forward, but still be able to look at that.

00:10:39.782 --> 00:10:41.323
Historical access is significant.

00:10:41.323 --> 00:10:57.809
Access is significant when doing this, with Cosmos being a cloud-based reporting engine I guess you could call it or reporting system, and now we're talking about bringing third-party data into it.

00:10:57.830 --> 00:10:58.693
Are there any limitations?

00:10:58.693 --> 00:11:01.722
Business Central is cloud-based, so you're pulling off a cloud-based repository.

00:11:01.722 --> 00:11:07.913
Are there any limitations to the data that can be read within Cosmos?

00:11:07.913 --> 00:11:10.548
If it's an on-premise system, do they have to move it to the cloud?

00:11:10.548 --> 00:11:15.672
Can they read it directly from their SQL service sitting in their back room somewhere, or how does that work?

00:11:16.539 --> 00:11:23.094
Yeah, I think, since Brian has been super talkative, I'm going to defer this to you, brian, so you can actually chime in on today's podcast.

00:11:23.500 --> 00:11:24.062
Yeah, of course.

00:11:24.062 --> 00:11:28.529
So there's a few different ways we can pull in data now you know one of them is Excel files.

00:11:28.529 --> 00:11:30.043
We have some folks that have used that.

00:11:30.043 --> 00:11:37.538
If it's not a ton of data and it's something that's static, right, we can just dump everything into Excel from wherever they want, ingest it into Cosmos.

00:11:37.538 --> 00:11:38.160
Nice and easy.

00:11:38.782 --> 00:11:46.293
For folks that have data in like a SQL database or something that's on-premise, all we would ask them to do is just shift it up to Azure SQL.

00:11:46.293 --> 00:11:47.375
That way we can pull it in.

00:11:47.375 --> 00:11:52.977
I mean, with Management Studio nowadays and SQL, you can do a few clicks and it'll just send all the data up.

00:11:52.977 --> 00:12:02.663
So it's not a big lift to do that, and once it's in Azure SQL, we can grab it and it's super fast for us to pull all the information in right.

00:12:02.663 --> 00:12:11.591
A lot of organizations nowadays have more advanced firewalls, so us trying to, you know, find a way to get through their firewall and access to their SQL server from outside.

00:12:11.591 --> 00:12:25.989
Most good IT folks are not going to want to allow that to begin with, and so having everything in Azure SQL makes it, puts it in the cloud and makes it nice and easy for us to get to and easy for the customers to maintain as well.

00:12:27.542 --> 00:12:38.083
So the customer would need someone who's looking to take advantage of this new functionality that's been introduced within Cosmos over the last week, which I can't say enough.

00:12:38.083 --> 00:12:41.466
It is a need for this and I'm happy to see that it's there.

00:12:41.466 --> 00:12:43.380
They would put it in Azure SQL.

00:12:43.380 --> 00:12:43.942
Now, on that Azure SQL.

00:12:43.942 --> 00:12:44.182
Is that?

00:12:44.182 --> 00:12:44.663
See that it's there.

00:12:44.663 --> 00:12:45.323
They would put it in Azure SQL.

00:12:45.323 --> 00:12:46.384
Now, on that Azure SQL.

00:12:46.384 --> 00:12:49.307
Is that something that would be their Azure SQL?

00:12:49.307 --> 00:12:51.331
Like how, again, where would they store that?

00:12:51.331 --> 00:12:52.812
Would they store that with Cosmos?

00:12:52.812 --> 00:12:55.495
Would they store that within their own Azure SQL server?

00:12:55.495 --> 00:12:55.676
That?

00:12:55.696 --> 00:12:57.337
would be within their own Azure SQL.

00:12:57.337 --> 00:12:58.019
Yeah, that's a great question.

00:12:58.038 --> 00:13:00.927
Within their own Azure SQL and then you can link the two together.

00:13:00.927 --> 00:13:10.083
Yep, I have some questions on the data construct or the data sets there.

00:13:10.083 --> 00:13:15.500
But is it intended or could it be someone who may have another system, that's another transactional system?

00:13:15.500 --> 00:13:23.187
Is it intended to be a static database or is it something that if they could update it regularly with transactional data, that that would work for them as well?

00:13:23.508 --> 00:13:23.727
Either.

00:13:23.727 --> 00:13:31.427
Or, as far as we're concerned, if it's static data, we have a little checkbox when they're setting up the configuration to connect to that Azure SQL database.

00:13:31.427 --> 00:13:37.885
It's just called static data and that means it'll pull it in once and then it doesn't need to pull it every single night, since the data is never changing.

00:13:37.885 --> 00:13:50.355
Otherwise, if it is something that's kind of, you know, replicated from a transactional system, then every time that we go and pull the data we'll just pull that fresh data from Azure SQL.

00:13:53.586 --> 00:13:54.750
So it's intended for either one.

00:13:54.750 --> 00:13:59.982
Okay, that's a wonderful feature to have With now.

00:13:59.982 --> 00:14:08.172
There being so, Business Central extensions aside, Business Central is a pretty standard data set.

00:14:08.172 --> 00:14:09.333
We know it's a known data set.

00:14:09.333 --> 00:14:28.836
Now you're talking about bringing in an additional third-party data set in essence for the sake of the conversation.

00:14:28.876 --> 00:14:30.820
How do they map or manage or tell Cosmos this is what the data is that I have?

00:14:30.820 --> 00:14:33.563
Yep, yeah, I'll speak to that a little bit, brian, then I'll let you fill in some of the color on that.

00:14:33.563 --> 00:14:46.533
But yeah, one of the really cool things about our engineering team is they have a lot of experience, a lot right, and so when they build things in the product, they build them with a future thinking view in mind.

00:14:46.533 --> 00:14:52.985
Like if we solve a problem that's immediate, they usually take the opportunity to say what else are we going to need to do?

00:14:52.985 --> 00:14:59.340
Are people going to want our, you know is going to be important down the road, and how can we put the foundation in to solve for that?

00:14:59.340 --> 00:15:02.205
And so this is a good example to your point, brad.

00:15:03.628 --> 00:15:10.385
So inside of Cosmos, basically from day one, there's been a cloud-based ETL platform.

00:15:10.385 --> 00:15:27.972
We call it the Cosmos Data Engine, and what it really is is a way to take data out of a system, whether it's business central or something else immediately see all those tables, all the fields, and then, basically in a point-click interface, be able to say hey, you know, we had our business central data over here.

00:15:27.972 --> 00:15:51.184
Now we have this new system and we just want to check the boxes for these 12 tables or these 20 tables that we want and then within those tables we have, you know, these specific fields that we want for reporting and basically those just get dropped into their existing data set, or a new data set can be created and then you just publish, literally click a publish button and the application actually writes everything behind the scenes.

00:15:51.184 --> 00:15:55.000
So it cleans the data, moves, it builds out all the procedures, everything.

00:15:55.000 --> 00:16:02.523
So you know the way I describe it is like it's a no code ETL platform on the back end and, brian, anything you'd add on that.

00:16:03.424 --> 00:16:04.788
Yeah, no, I mean, that's what I was going to say.

00:16:04.788 --> 00:16:10.339
There's a lot of tooling, for you know, if there are things that are different.

00:16:10.339 --> 00:16:18.448
Like we're working with a customer right now, they're bringing in some legacy data from their previous system, which wasn't nav, it wasn't anything in the dynamic space.

00:16:18.448 --> 00:16:22.523
And you know they said well, our GL account numbers are different though.

00:16:22.523 --> 00:16:28.955
So they already have a mapping file they put together as part of their migration to Business Central.

00:16:28.955 --> 00:16:32.000
But we can bring in their historical data.

00:16:32.000 --> 00:16:42.404
It's really easy for us to just use that mapping file and say, hey, it was this old GL account number in Traverse, which is the system they're using, and the new GL account is now.

00:16:42.404 --> 00:16:45.793
You know this is the one from Business Central, right?

00:16:45.793 --> 00:16:50.179
So by the time that it comes, you know Cosmos can handle all of that easily.

00:16:50.179 --> 00:16:55.613
So when it comes into Business Central, they have all of their old transactions but with their new BC account numbers.

00:16:55.613 --> 00:16:58.148
So everything's pretty seamless from a reporting perspective.

00:16:59.110 --> 00:17:08.961
Okay, so it's designed for quick user adoption, yeah Right, so does this also help?

00:17:08.961 --> 00:17:14.542
Now we're talking about moving legacy data to Cosmos.

00:17:14.542 --> 00:17:19.681
Have this been used for data migration as well, or is it?

00:17:19.681 --> 00:17:30.260
Oh okay, so can you give me an example of how that turned out for them, what the average time it took that client?

00:17:30.260 --> 00:17:47.296
Because that's something that we had a conversation recently, as of yesterday, about what are the different paths of data migration, what are the tools, and so there's so many different tools out there, so it is good to hear that you know Cosmos can do something like that.

00:17:48.739 --> 00:17:55.672
Yeah, yeah, brian, do you want to talk to like what you've seen hooking that up and how it gets married up and the level of complexity and kind of all that stuff?

00:17:56.394 --> 00:18:44.051
Yeah, exactly Well, and it's one of those things where I mean, as far as the data migration is concerned, we talk to, you know, we'll talk to customers that are in the process of moving from, say, like we talked to someone recently who's on an older on-prem NAV 2016 system, they're in the process of moving to Business Central and one of the concerns that they have is, well, what a lot of reports that you know that go back, you know, several years to do kind of year over year comparisons for, like you know, item sales by customer, things like that, and so you know, and they'd received a somewhat hefty estimate to move all of that transactional data directly into Business Central, and the thing is they don't even really care if it's in Business Central, they just want to report on right.

00:18:44.152 --> 00:19:16.362
So, as part of this, you know, moving all of this data into Cosmos, right, we can just easily get the information out of the old system, like I mentioned, either a direct connection to the SQL database we can do any of the data cleansing or mapping if needed and then, when they just run a report in Cosmos even though let's say that they just went live January 1st of this year they can run a year over year comparison of this, you know, this August versus last August, and everything just works.

00:19:16.362 --> 00:19:21.863
The users don't know, or, honestly, really even care, that the data is from the old system.

00:19:21.863 --> 00:19:24.719
They just want to know what were the numbers last year and what are the numbers this year.

00:19:24.719 --> 00:19:33.442
And are, you know, things up and down, up or down for this customer right and it's like, like, like I mentioned, it's a very, it's a very fast and easy process on our side.

00:19:33.442 --> 00:19:39.731
It's not a heavy, you know, it's not what I consider like a large services engagement or anything like that.

00:19:39.731 --> 00:19:44.443
Usually a couple hours and everything's done, imported and ready to go.

00:19:50.390 --> 00:19:53.057
Yeah, I think a lot of what we've been focusing on because, to your point, chris, like there are other solutions out there, right.

00:19:53.057 --> 00:19:57.374
So it has to not just do what those things do, it has to, like, provide more value, right.

00:19:57.374 --> 00:20:07.019
And where we've really been focusing on is just, you know, cutting costs and effort, reducing, like you know, the time it takes, all those questions you're probably asking about for that exact reason.

00:20:07.019 --> 00:20:16.625
But, like it's, it's the same thing with the data modeling, like to Brian's point, you can bring it into BC in theory, unless it's some insane volume of data, but you can bring it into BC.

00:20:16.625 --> 00:20:18.811
But it's going to have a hefty price tag.

00:20:18.852 --> 00:20:27.365
And I've talked to so many partners that are like we hate doing that, like it's the worst part of the deployments is dealing with the historical data migration, right.

00:20:27.450 --> 00:20:32.674
So you know, okay, let's make that easier, let's make that cheaper, let's make that faster, let's make it repeatable.

00:20:32.674 --> 00:20:52.337
And it's kind of the same idea on, like, the reporting side of the platform, right, like people can kind of get the data they want, they would want in the cosmos report currently, I suppose, not always, but, like you know, brian and I always talk about, like this one customer that we just always kind of felt horrible for and luckily we solved their problems.

00:20:52.337 --> 00:20:57.759
But like you know, they just wanted to get this one report and it just took them 47 steps.

00:20:57.759 --> 00:21:00.051
And when I say that like that's not an exaggeration.

00:21:00.051 --> 00:21:05.423
They had a word document, a Word document that every time they needed the report there was 47 steps.

00:21:05.423 --> 00:21:09.862
So it was like okay, export this, run it for these companies, export each one individually.

00:21:09.862 --> 00:21:14.060
Those go in a file, take that file, use the mapping file, reference all that.

00:21:14.060 --> 00:21:14.561
You know what I mean.

00:21:14.561 --> 00:21:15.846
Like so can you do it.

00:21:16.491 --> 00:21:17.496
Can it be done better?

00:21:18.632 --> 00:21:22.061
Like that's what we try and solve for here right at Cosmos.

00:21:25.029 --> 00:21:55.135
Yeah, I think people forget, when you're looking at some of those reporting tools or even in the process of implementing Business Central, is that the last thing you really care for is all the tedious work that you'd have to do just to bring historical data, be able to report on legacy information, and so it sounds like you've really built this amazing product that allows that to be easier, or make it easy, not only from a client's perspective, but also from a partner's perspective.

00:21:55.135 --> 00:22:09.064
Right, because sometimes you don't have the, maybe the skillset within your staff that can do all of that, and you got to figure it out when set within your staff that can do all of that, and you got to figure it out when, hey, I can just reach out to Anthony and Brian and say, hey, can you help us with this one?

00:22:09.746 --> 00:22:12.394
Yeah, it's important to remember.

00:22:12.394 --> 00:22:44.717
I think with this you hit on a couple of points, because bringing the data forward can be a costly event as part of an implementation, not only for the time it takes to take the data and put it into a specific box and try to map it and put it together or you can create an extension to store it and then you're still going to have to report on it but there's also a cost for the storage, for the business central access as well, which I think often gets overlooked, and a lot of times I hear the same questions we just want to bring it forward, we just need the information.

00:22:44.717 --> 00:22:45.080
So it's important.

00:22:45.080 --> 00:22:45.789
Yes, there are many tools available.

00:22:45.789 --> 00:22:48.839
I think there are many tools available for everything in this world.

00:22:48.839 --> 00:22:50.135
There's not only going to be one option.

00:22:50.135 --> 00:22:52.519
It's to make sure you have the option that's best for you.

00:22:53.289 --> 00:23:05.726
In a case like this, it's important for someone to say, hey, there are tools such as Cosmos or something where, okay, if you're just looking to report on the data, you don't have to have it within Business Central any longer.

00:23:05.726 --> 00:23:10.696
Now we can report on the data from a separate system that we can upload the information into.

00:23:10.696 --> 00:23:21.390
It will be your footprint and then we'll just map it, using the wonderful tools to put it together, to have one homogeneous view of your data and, like you had mentioned, brian, nobody will be the wiser of it.

00:23:21.390 --> 00:23:30.263
One homogeneous view of your data and, like you had mentioned, brian, nobody will be the wiser of it With the use of this and, I think, with Cosmos in general.

00:23:30.263 --> 00:23:33.849
So now you have the features and the functionality that you built into it.

00:23:34.852 --> 00:23:39.325
One question will be okay, it sounds great, it sounds wonderful, but how do I pay for it?

00:23:39.325 --> 00:23:40.069
How is it licensed?

00:23:40.069 --> 00:23:42.558
Is it licensed by the data volume?

00:23:42.558 --> 00:23:46.500
Is it licensed by the number of users licensed, by the number of tables licensed, by the number of reports?

00:23:46.500 --> 00:23:54.884
For this additional feature, what can a customer expect to have added to their implementation or their cost of the application?

00:23:55.630 --> 00:24:00.179
Yeah, like everything, we try to make it simple and you brought up a good point earlier, brad.

00:24:00.179 --> 00:24:02.289
Like benefits to partners and customers.

00:24:02.289 --> 00:24:04.858
We try to keep both of those in mind, right?

00:24:04.858 --> 00:24:09.932
So I can tell you, having worked on the partner side, there's nothing more obnoxious than when an ISV is.

00:24:09.932 --> 00:24:15.352
Pricing is like you need a secret decoder, ring Right, and there's like 200 line items and there's the if.

00:24:15.532 --> 00:24:19.122
If you check this, add this, like there's a connector charge.

00:24:19.122 --> 00:24:20.715
So we do it by data source.

00:24:20.715 --> 00:24:27.857
If they want to add another, you know they want a data source for their historical data they buy one connector.

00:24:27.857 --> 00:24:36.253
They don't have to pay for the Azure storage, they don't have to get a, you know, variable bill, it's just a flat price that gets added to their monthly or annual subscription.

00:24:36.253 --> 00:24:37.998
So we keep it very simple.

00:24:37.998 --> 00:24:48.715
I think even with these new features, there's a total of let's see one, two, I think four line items on the quote form that you can literally interact with.

00:24:48.715 --> 00:24:52.231
So the goal is to make it so that partners can easily understand it.

00:24:52.231 --> 00:24:56.532
Customers can look at it and not need a whole explanation or have to have a pricing call.

00:24:56.532 --> 00:25:02.936
They can look at this and say I need two of these users two of these users and I need an additional data source right, so it's very simple.

00:25:02.957 --> 00:25:04.741
These users two of these users and.

00:25:04.741 --> 00:25:06.928
I need an additional data source, right.

00:25:06.928 --> 00:25:07.430
So it's very simple.

00:25:07.430 --> 00:25:12.116
I laugh because all the stuff that you're talking about are challenges that many face.

00:25:12.116 --> 00:25:17.232
I've been in many conversations where, honestly, we were going through a quote and the customer said this is too complicated.

00:25:17.413 --> 00:25:18.194
I'm not interested.

00:25:18.556 --> 00:25:19.959
And they just drop it.

00:25:19.959 --> 00:25:32.040
So I laugh because I appreciate the simplicity, and often that gets overlooked as well is you have to keep it simple because, from an implementation or a customer point of view, sometimes they just want access to the data.

00:25:32.040 --> 00:25:33.635
How much is it going to cost me?

00:25:33.635 --> 00:25:37.721
I don't need you know, it's the whole Baskin-Robbins, you know.

00:25:37.721 --> 00:25:39.657
Experiment with the ice cream.

00:25:39.657 --> 00:25:49.951
So one data source charge and then again, if they bring it into the azure sql, then whatever cost would be for the azure data storage is uh, in addition to that as well correct.

00:25:50.113 --> 00:26:02.273
Yeah, if they want, if they're going to pull and like, if they're not doing static exports into excel or something and they want to have a dedicated azure sql, we would let their you know it team and their infrastructure team deal with with piece.

00:26:02.575 --> 00:26:04.597
Okay, great, great.

00:26:04.597 --> 00:26:06.780
That's exciting news.

00:26:06.780 --> 00:26:10.205
Now, is that something now to bringing it all the same.

00:26:10.205 --> 00:26:11.353
We talked about how it can be done.

00:26:11.353 --> 00:26:18.780
Is that something that a customer could do on their own, or would they need you to set all this up for initially, or a partner to do it?

00:26:20.009 --> 00:26:21.193
Yeah, I'll let you answer that.

00:26:21.213 --> 00:26:28.999
I mean, I know what I'd say, but yeah, I was going to say I mean, it's something that a customer or a partner could definitely do on their own.

00:26:28.999 --> 00:26:36.675
There's nothing with that where we, you know, we lock people out and like it's all stuff we have to do behind the scenes, it's all available right there in their Cosmos portal so they can do it as they see fit.

00:26:36.675 --> 00:26:46.026
We do see a lot of customers that are like you know what if people will just help them out a little bit or get the connection set up and, you know, show them how to pull in some of the tables and fields and stuff like that.

00:26:46.026 --> 00:26:47.872
But, um, I mean, it's all you know.

00:26:47.872 --> 00:27:04.585
The whole, the whole platform is meant to be um focused on business users, so it's not something where it's like you're telling an accountant like well, yeah, if you just write this sql statement to move the data over, like no one wants to do that, you check the boxes, you click, you click a button, cosmos handles the rest and it just moves everything over.

00:27:04.650 --> 00:27:08.196
Yeah that's the biggest thing there's no coding in the whole platform.

00:27:08.196 --> 00:27:09.392
You can't find it.

00:27:09.392 --> 00:27:10.114
It doesn't exist.

00:27:11.336 --> 00:27:11.958
No, that's good.

00:27:11.958 --> 00:27:17.695
Simple is good, and just because something's simple doesn't mean it's not effective.

00:27:17.695 --> 00:27:25.580
Sometimes, individuals put stuff together and they feel they need to make it complicated because that means it's something To me, it's something successful.

00:27:25.580 --> 00:27:27.223
I can just you know, it's like a light switch.

00:27:27.223 --> 00:27:28.435
I turn it on and turn it off.

00:27:28.435 --> 00:27:33.580
I really don't need to worry about the generation of the electricity or where it comes from or how to make a light bulb.

00:27:33.580 --> 00:27:39.994
I just turn the switch on and I get what I need, and I can move on With this.

00:27:39.994 --> 00:27:44.701
I always get a little excited, so I'm going to kind of jump a little bit and we'll transition there as I jump.

00:27:44.701 --> 00:27:51.134
If someone's interested in learning more about this, how can they see it or how can they experience it?

00:27:51.134 --> 00:27:55.303
Is there an online video, a demonstration, a trial version?

00:27:55.303 --> 00:27:57.474
Do you have webinars?

00:27:57.474 --> 00:27:59.760
How can someone learn more about this?

00:28:00.430 --> 00:28:05.962
Yeah, I mean all of the above and, as you guys know, we'll be at, you know, upcoming summit conference, right?

00:28:05.962 --> 00:28:10.436
So folks are attending that, but you know we're at all the major events so we're pretty easy to find.

00:28:10.436 --> 00:28:17.982
You know, obviously we do do webinars, we do record all this functionality and post videos about it on the website.

00:28:17.982 --> 00:28:20.258
We're really well known for our knowledge base.

00:28:20.258 --> 00:28:21.511
I'm sure you guys have seen that.

00:28:21.511 --> 00:28:27.231
But there's, you know, over 350 articles, right, about pretty much any piece of the product you'd want to know something about.

00:28:27.231 --> 00:28:44.944
They all have, you know, step-by-step walkthroughs and screenshots, video walkthroughs, and then, obviously, it's just like I made this announcement last week you can always just email us at hello at Cosmos data techcom, so we'll get back to you if you want to see it or talk about your specific organization and what the data sets are and how you want to integrate them.

00:28:45.911 --> 00:28:46.673
Who came up with that?

00:28:46.673 --> 00:28:47.737
I like that Hello.

00:28:48.298 --> 00:28:50.516
Yeah, it's funny, Brian came up with that one Apparently.

00:28:50.516 --> 00:28:52.315
It's a thing I was not privy to it.

00:28:53.451 --> 00:28:54.915
It is after I came up with it, Anthony.

00:28:55.336 --> 00:28:56.000
Well, it is now.

00:28:56.000 --> 00:29:07.182
But the famous Mike Lumo, who we all know in the channel he commented on the LinkedIn post immediately referencing.

00:29:07.182 --> 00:29:09.150
Adele and her song Hello, so that derailed the entire LinkedIn thread.

00:29:09.150 --> 00:29:12.378
So always appreciate Mike for that valuable input.

00:29:12.439 --> 00:29:12.961
That's excellent.

00:29:12.961 --> 00:29:25.876
I will say, the first thing that came to mind with me and Chris may appreciate it was when you get a new Mac, when you set up a new Mac or a new device or iPhone, ipad Mac says hello, yeah, and then you pick your language and you go through it.

00:29:26.391 --> 00:29:35.239
So you will be at Summit in October, and that's October 13th through the 17th, I believe, with the pre-conference workshops two days prior to.

00:29:35.239 --> 00:29:41.612
I would like to talk about your booth and all that you have, but I also heard there's something else going on.

00:29:41.612 --> 00:29:45.942
That's going to be like the first annual yeah.

00:29:45.982 --> 00:29:47.788
so you know, there's not enough parties.

00:29:47.788 --> 00:29:52.720
That was the feedback, you know, about all the microsoft events, right, there's just not enough stuff to do.

00:29:52.720 --> 00:30:08.881
And so, uh, no, uh, the lovely, wonderful shannon mullins actually reached out to us, uh I don't know, maybe four or five months ago, and said, hey, I've got this cool idea that I'm thinking about doing for Summit this year and that's having a true dedicated, you know, bc bash.

00:30:08.881 --> 00:30:17.336
So obviously, in years past there's been the PowerGP online party and Chris and the team at Ingevity, that kind of you know, are the title sponsor for that.

00:30:17.336 --> 00:30:26.644
Right, they've always been great about letting you know the NAV folks and BC folks and things attend that as well, but it always has been, you know, very GP focused, for obvious reasons, because that's what it's about.

00:30:26.644 --> 00:30:33.278
And so Shannon thought it'd be great to have more of a BC version and Chris over at Ingevity thought it was a great idea as well.

00:30:33.278 --> 00:30:35.557
So now we've kind of got a couple different events.

00:30:35.557 --> 00:30:45.643
You can obviously go to both, but you know, if you're focused on one or the other, it might make sense to network more with those specific folks that want to talk about that platform and things like that.

00:30:45.782 --> 00:30:47.845
So, uh, so, yeah, we're really excited.

00:30:47.845 --> 00:30:49.846
She asked if we wanted to sponsor and be a part of it.

00:30:49.846 --> 00:31:12.579
There's us and four or five other sponsors and, um, I believe the way it works is you need to come by one of the booths and basically register or get scanned, um, and then you can also find the registration link on social media and all that, and then, once you're there, you can get uh admitted at the door, um, if you're registered, and then we'll have some drink tickets at our booths as sponsors.

00:31:12.579 --> 00:31:24.839
So if people want to have, uh, some adult beverages, there are ways to get those for free, which are always good just show up and just say I know anthony yeah let me in listen.

00:31:24.859 --> 00:31:28.315
It'll probably kill me if that happens, but try it I tried.

00:31:28.655 --> 00:31:31.701
I tried and I even said do I really need to register?

00:31:31.701 --> 00:31:33.594
And everyone's like yes, you need to register.

00:31:33.594 --> 00:31:35.018
And I asked anthony.

00:31:35.018 --> 00:31:37.465
I said can I just have some drink coupons?

00:31:37.465 --> 00:31:39.594
He said no, you have to come by the booth and get some.

00:31:39.594 --> 00:31:44.523
So everybody seems to be following the rules on this one, which is good.

00:31:44.523 --> 00:31:45.365
I do.

00:31:45.365 --> 00:31:49.589
You know there's a little fun with that, with that little conversation.

00:31:49.589 --> 00:32:02.251
But anybody who is going to summit, I do promote stopping by the booth to take a look at the product and, while you're there, pick up a drink coupon for later to talk with you guys a little bit more about the product while you have a beverage in hand.

00:32:02.251 --> 00:32:09.800
If you don't have a beverage in hand at the booth, because sometimes the expo hours they do have a cocktail or two available, which is good.

00:32:09.861 --> 00:32:12.324
So can I reserve some of those drink coupons.

00:32:12.505 --> 00:32:13.244
I think you're you're.

00:32:13.244 --> 00:32:17.857
You're on the, you're on the VIP list as well, so we'll reciprocate VIP lists.

00:32:17.857 --> 00:32:21.999
You guys let us on the podcast list, you're on the drink ticket list, but yeah, and I haven't.

00:32:21.999 --> 00:32:23.500
I haven't been to the venue.

00:32:23.500 --> 00:32:26.383
Shannon and some other folks checked it out, said it was awesome.

00:32:26.383 --> 00:32:28.243
So I don't know if there's a back door.

00:32:28.243 --> 00:32:29.464
I don't know if I can get you guys in.

00:32:29.464 --> 00:32:30.726
You know around the back.

00:32:30.726 --> 00:32:34.494
We'll figure that out when we get there we'll have to do it, get it.

00:32:34.875 --> 00:32:39.392
So the bc bash that, uh, your partner sponsor is just for a bunch of business.

00:32:39.392 --> 00:32:43.898
Again, it's a business central focused uh guess celebration.

00:32:43.898 --> 00:32:47.404
That's part of the conference, because the conference covers several different tracks.

00:32:47.404 --> 00:32:54.364
It covers Power Platform, d365, finance and Operations Supply Chain, whatever they call it today.

00:32:54.364 --> 00:33:00.994
There is a GP contingent there as well, so there's a good, I think, five tracks there as well.

00:33:00.994 --> 00:33:20.121
So this is a good place to go where you're at an event that's focused on Business Central, if you're a Business Central partner or a Business Central user, so you can talk with people with similar interests and maybe learn a little bit more about the application, as well as the Cosmos reporting solution, again, and data analytics, which is good.

00:33:20.121 --> 00:33:21.022
Data analytics, which is good.

00:33:27.390 --> 00:33:30.713
And I'm trying to pull up real quick just to see to confirm the start time and the date, as I just moved this to another monitor.

00:33:30.713 --> 00:33:34.480
Um, so that is third.

00:33:34.480 --> 00:33:40.609
Uh, tuesday, october 15th, and it starts at 8 and goes to 11 30 central.

00:33:40.829 --> 00:33:49.555
So wait eight, so that's nine, so that's 2100 to 11 it's an hour behind you, man yes, minus one.

00:33:49.555 --> 00:33:50.596
That's past my bedtime.

00:33:50.596 --> 00:33:54.346
Yeah, I go to bed at 10, so I think I'll be there for about an hour there you go.

00:33:54.446 --> 00:33:54.855
That's plenty.

00:33:54.855 --> 00:33:55.499
Maybe that's all you need man.

00:33:55.499 --> 00:33:56.925
Maybe that's all you need man.

00:33:56.925 --> 00:33:57.849
Yeah, that's all you need.

00:33:59.878 --> 00:34:00.923
No, I'm looking forward to it.

00:34:00.923 --> 00:34:02.400
I did register.

00:34:02.400 --> 00:34:06.305
Hopefully I'm on the list, if you guys can look at the list and confirm it.

00:34:06.305 --> 00:34:07.471
Just don't delete me please.

00:34:07.491 --> 00:34:09.639
Yeah, I won't it should be a good event.

00:34:09.639 --> 00:34:18.480
I want to say they said as week ago there were over 200 people registered.

00:34:18.480 --> 00:34:21.786
We're not even at the conference yet, so I think this caps out at 750 people, but I would be shocked if we don't hit that.

00:34:21.806 --> 00:34:22.168
So seven.

00:34:22.168 --> 00:34:25.838
I was going to ask 750 people capacity.

00:34:25.838 --> 00:34:26.898
Where is this?

00:34:26.898 --> 00:34:31.965
That has to be a big place 1174 east commerce street.

00:34:33.206 --> 00:34:37.130
It's a secret yes, that place the 1902.

00:34:37.150 --> 00:34:42.320
The 1902 is the name of the venue yeah, I'll have to look that up and see.

00:34:42.320 --> 00:34:44.606
I did register and I I was, you know.

00:34:44.606 --> 00:34:47.963
I figured I'd get the date and the time when I was there it'd be like a speakeasy.

00:34:48.063 --> 00:34:50.880
You just like show up at this building and like I don't know what's in here.

00:34:50.900 --> 00:34:58.347
Let's go through it, yeah, just a random like barber shop or something you walk through the back yeah, we'll have to give chris a different address.

00:35:01.061 --> 00:35:01.702
Oh, that's funny.

00:35:01.702 --> 00:35:02.483
So.

00:35:02.483 --> 00:35:13.922
So with back to going back to cosmos, I'm thinking of these things and we're talking about the some of the other applications or other products, and just to throw it out there, have you ever considered doing it for d365?

00:35:13.922 --> 00:35:21.056
Uh, fno or what's the snsem that's now, I don't know fnsem yeah, you know we've talked about it.

00:35:21.197 --> 00:35:30.766
I think there's so much more that we want to do for bc, like there's so much untapped potential still and like I mean we had a call with a customer this morning about a couple items.

00:35:30.766 --> 00:35:40.402
They wanted to see what we're working on and like brian will just start talking right and it's like the amount of plans that him and the engineering team have put together around different functionality.

00:35:40.402 --> 00:35:51.661
I mean I'm going to let Brian talk more about that because he gets really mad if I say what the engineering team is planning that's not on our formal roadmap, because then everyone hears it and thinks it's going to be out next week.

00:35:51.661 --> 00:35:53.641
But we'll talk about that.

00:35:53.641 --> 00:36:01.342
But I mean, to your point, like there's a lot more we want to do for BC Cloud and for just the general SMB space.

00:36:01.603 --> 00:36:08.820
And then when you talk about FNSCM or you know, getting into the bigger, you know enterprise level customers like everything has to change right.

00:36:08.820 --> 00:36:15.219
Pricing has to change significantly, data volumes and the you know the way the platform handles the data has to change.

00:36:15.219 --> 00:36:21.155
Like there's just so much shakeup that we don't think it makes sense right now, I guess is the way to put it.

00:36:21.155 --> 00:36:23.061
But what would you say on that, brian?

00:36:24.182 --> 00:36:40.884
Yeah, no, and I think that you know, in my experience in working with more of the you know the FNSCM customers too like it ends up being a lot more about customization, which equates to services, than it does about the software, if that makes sense.

00:36:40.884 --> 00:36:44.420
Like everything that we've built so far is like quick, fast, easy deployments.

00:36:44.420 --> 00:36:46.826
Customers are up and running in 30 minutes.

00:36:46.826 --> 00:36:57.505
We have they have all of these prebuilt reports and you know, and in the VC space, I think that we, that we have a real sweet spot as far as that's concerned.

00:36:57.505 --> 00:37:03.380
Right, I mean so many I've heard it from partners too we go into an onboarding and they'll tell me afterwards.

00:37:03.742 --> 00:37:07.469
When you said 30 minutes, like I knew that that wasn't going to be a thing.

00:37:07.469 --> 00:37:19.018
Nothing, just it deploys in 30 minutes and afterwards we'll wrap up in 25, and they're like I don't know why, why more isvs don't follow your deployment model, even with our extension in bc.

00:37:19.018 --> 00:37:25.480
Like we go and we create, and you know there's an intro application that's used to facilitate data moving around, etc.

00:37:25.480 --> 00:37:25.740
Etc.

00:37:25.740 --> 00:37:32.351

Brian Petersen

Chief Operating Officer

Brian Petersen is a household name in the Microsoft Channel with over 15 years of experience in leading successful product and services teams. Prior to co-founding Cosmos Data Technologies, Brian was the Vice President of Product and Services at Jet Reports (now insightsoftware) and most recently served as a Vice President at Rand Group, overseeing and leading a successful professional services team dedicated to helping clients with their needs around reporting, analytics, and data management. Cosmos isn’t the first product that Brian has taken to market as he was also responsible for launching Jet Analytics back in 2007.
Those who know Brian recognize him for his diverse business skillset and his willingness to always step up and help his colleagues and customers. We’re pretty sure if you look up the definition of ‘going above and beyond’ there’s a picture of Brian. Brian earned his bachelor’s degree in Finance, Computer Science, and History from Linfield University.
His hobbies include camping, playing guitar, and spending time with his wife and kids.

Anthony Bonaduce

Chief Revenue Officer

Anthony Bonaduce is an experienced sales executive who is proud to have been a part of the Microsoft Channel for the better part of a decade. Prior to co-founding Cosmos Data Technologies, Anthony was the Vice President of Sales at Jet Reports (now insightsoftware) and most recently served as a Vice President at Rand Group, helping clients conduct their due diligence around leading reporting, analytics, and data management solutions.
Anthony has a passion for building relationships and fondly recalls growing Jet’s partner channel to new heights during his tenure. Needless to say, he’s excited to be back working with Microsoft partners once again.
Anthony is steadfast in his commitment to exceptional customer service and honest communication which he credits for the majority of his business success.
Anthony earned his bachelor’s degree in Business Administration with concentrations in Finance and Marketing, as well as a minor in Economics from the University of Oregon (GO DUCKS!). His hobbies include watching the Oregon Ducks, playing golf, and spending time with his family and friends.

Episode 340: In the Dynamics Corner Chair: A Journey into the Cosmos

Brian Petersen

Anthony Bonaduce

Listen On

Featured Episodes

Recent Episodes

Business Central Episodes

Microsoft Episodes

Partner Episodes

ISV Episodes

Other Episodes

Browse episodes by category

New to Dynamics Corner?

Episode 403: ⚠️ Mastering the Art of Podcasting and AI in the Workpla…

Episode 405: ⚒️ Balancing Functional and Technical Skills in Business…