00:00:03.379 --> 00:00:04.469 A really close attention.
00:00:04.479 --> 00:00:06.664 I think it'll be really interesting, good high level
00:00:06.664 --> 00:00:07.159 information.
00:00:08.329 --> 00:00:12.511 Then we're gonna go into updates from some of the respective
00:00:12.511 --> 00:00:14.019 areas within the team.
00:00:14.509 --> 00:00:17.259 We just, we don't have time to cover everything today.
00:00:17.269 --> 00:00:21.315 So you won't hear from every single department in, in every
00:00:21.315 --> 00:00:22.259 area of focus.
00:00:22.269 --> 00:00:26.390 So I do expect as we continue the firesides that you'll get
00:00:26.390 --> 00:00:30.373 coverage of other areas that we don't hit on today in the
00:00:30.373 --> 00:00:31.609 upcoming fireside.
00:00:31.619 --> 00:00:36.189 So anyway, with that in mind, we can go ahead and get started.
00:00:36.779 --> 00:00:39.606 I did share the link into the chat, so you're welcome to
00:00:39.606 --> 00:00:41.639 follow along visually if you would like.
00:00:42.529 --> 00:00:46.514 And just to get things started and let me show my screen and my
00:00:46.514 --> 00:00:47.199 camera too.
00:00:47.209 --> 00:00:49.829 Here just one moment while I get that going.
00:00:51.859 --> 00:00:52.539 All right.
00:00:55.229 --> 00:00:57.019 So can you see my screen?
00:00:57.099 --> 00:01:00.569 You should see Steve Jobs looking lovingly at you if so.
00:01:02.959 --> 00:01:03.279 We do.
00:01:03.569 --> 00:01:04.209 Indeed.
00:01:04.089 --> 00:01:05.149 OK, awesome.
00:01:05.159 --> 00:01:07.399 Awesome, excellent.
00:01:05.259 --> 00:01:05.589 Yes, Sir.
00:01:07.949 --> 00:01:09.869 And let's see if this camera is gonna work too.
00:01:11.199 --> 00:01:12.429 And you guys see my camera?
00:01:12.439 --> 00:01:16.489 OK, looks like it's showing up OK. Awesome.
00:01:14.449 --> 00:01:14.609 Yep.
00:01:15.129 --> 00:01:15.319 Yep.
00:01:15.259 --> 00:01:15.559 Oh yeah.
00:01:18.309 --> 00:01:18.739 Yeah.
00:01:18.749 --> 00:01:21.981 So you know, I like to start these out with just kind of
00:01:21.981 --> 00:01:25.497 talking about the high level vision and the overall, you know
00:01:25.497 --> 00:01:28.559 kind of like reason why we're doing what we're doing.
00:01:30.359 --> 00:01:34.616 So obviously, if you're really excited or passionate about what
00:01:34.616 --> 00:01:38.674 you're focusing on, it just kind of comes naturally to to do
00:01:38.674 --> 00:01:39.539 great things.
00:01:40.329 --> 00:01:44.176 And one of the things that I can say about our products is our
00:01:44.176 --> 00:01:47.413 products really do make a difference for individuals
00:01:47.413 --> 00:01:47.779 lives.
00:01:47.989 --> 00:01:52.327 And you know, we've talked about this before, but some of the
00:01:52.327 --> 00:01:56.316 products literally directly impact umm care outcomes for
00:01:56.316 --> 00:02:00.094 individuals who are going through some pretty intense
00:02:00.094 --> 00:02:04.502 situations medically or you know it just dramatically improves
00:02:04.502 --> 00:02:08.840 their you know their experience when they're working at their
00:02:08.840 --> 00:02:12.129 job or they're delivering for their customers.
00:02:12.439 --> 00:02:15.926 And although that's not necessarily life changing at the
00:02:15.926 --> 00:02:19.720 moment, it it really does make a big impact on people's lives
00:02:19.720 --> 00:02:23.268 whenever we make things more efficient, reduce stress and
00:02:23.268 --> 00:02:27.123 allow them to kind of, you know, improve how they're executing
00:02:27.123 --> 00:02:28.469 within their business.
00:02:29.599 --> 00:02:34.464 And so, umm, I just asked you to think about as we, you know, go
00:02:34.464 --> 00:02:39.329 into the next year and as we go into 2024, you know, what is it?
00:02:39.579 --> 00:02:43.093 What is it about the products and what we're doing that you
00:02:43.093 --> 00:02:46.256 can get yourself really passionate about and that you
00:02:46.256 --> 00:02:49.828 can really engage with and you know one of the things that I
00:02:49.828 --> 00:02:53.518 always like to look at is not just the, you know, not just the
00:02:53.518 --> 00:02:57.149 the business itself, but also the people within the business.
00:02:57.639 --> 00:03:01.252 So we have a lot of, you know, incredible team members on our
00:03:01.252 --> 00:03:04.633 team and we're all really seeking to grow in some form or
00:03:04.633 --> 00:03:05.099 fashion.
00:03:05.529 --> 00:03:08.903 So there's a huge opportunity to be very passionate and engaged
00:03:08.903 --> 00:03:12.119 around helping each other to grow and get to the next level.
00:03:12.869 --> 00:03:17.162 So I think they're this is a multifaceted thing with being
00:03:17.162 --> 00:03:21.819 able to engage and really, you know, press and pour it on going
00:03:21.819 --> 00:03:26.548 into 2024 and in a similar vein, you know, how are you promoting
00:03:26.548 --> 00:03:31.060 yourself and growing yourself and holding yourself to a level
00:03:31.060 --> 00:03:35.789 of accountability and standards that you can achieve within your
00:03:35.789 --> 00:03:40.519 career and how can we help each other to get to that next level?
00:03:40.529 --> 00:03:44.122 So these are questions that I would love for you to be sort of
00:03:44.122 --> 00:03:47.659 asking yourself and thinking about as we talk today and as we
00:03:47.659 --> 00:03:49.199 go through different areas.
00:03:49.469 --> 00:03:53.319 And I would encourage you to take notes and and sort of, you
00:03:53.319 --> 00:03:57.359 know, either make comments or, you know, take notes for offline
00:03:57.359 --> 00:04:01.019 discussion about how you might want to be engaged and and
00:04:01.019 --> 00:04:03.039 really pressing going into 2024.
00:04:03.819 --> 00:04:04.099 Umm.
00:04:04.199 --> 00:04:07.974 With that said, you know one of the most powerful things about
00:04:07.974 --> 00:04:11.929 our business model is that we're really focused on niche markets.
00:04:12.859 --> 00:04:16.141 One of the things that I like to talk about is this kind of, you
00:04:16.141 --> 00:04:18.969 know, red ocean that typically occurs within marketing.
00:04:19.339 --> 00:04:22.697 And so you can see you've got a blue ocean on the left and a red
00:04:22.697 --> 00:04:25.693 ocean on the right, and the red ocean really represents a
00:04:25.693 --> 00:04:26.829 generic product offer.
00:04:27.239 --> 00:04:30.838 And what we've done and we we certainly didn't do this right
00:04:30.838 --> 00:04:34.378 out of the gate, but what we figured out is that by niching
00:04:34.378 --> 00:04:37.800 down and really focusing on these specific product offers
00:04:37.800 --> 00:04:40.809 that we have and this doesn't include all of them.
00:04:40.819 --> 00:04:43.869 But this is, you know, substantially representative.
00:04:44.259 --> 00:04:48.588 It puts us into a position where we're sort of fishing in a blue
00:04:48.588 --> 00:04:51.319 ocean, so the guy with a 
on the left.
00:04:52.029 --> 00:04:55.665 Umm guy, gal and and the basically like from my
00:04:55.665 --> 00:05:00.588 perspective, fundamentally this is what we've done over the last
00:05:00.588 --> 00:05:05.057 I would say two to four years depending on the part of the
00:05:05.057 --> 00:05:05.739 business.
00:05:06.689 --> 00:05:10.256 So fundamentally, this has been something that has helped the
00:05:10.256 --> 00:05:13.421 business to perform at an extremely high level and and
00:05:13.421 --> 00:05:17.161 actually go from about 3,000,000 a year in top line revenue to 6
00:05:17.161 --> 00:05:20.556 million a year in top line revenue over about a three year
00:05:20.556 --> 00:05:20.959 period.
00:05:21.849 --> 00:05:22.309 Umm.
00:05:22.689 --> 00:05:26.644 And just to kind of visualize that, let me go to uh, there's
00:05:26.644 --> 00:05:30.599 just a ton of information on here, so bear with me as I jump
00:05:30.599 --> 00:05:34.619 around, but this is a really nice view of the last few years.
00:05:35.069 --> 00:05:38.795 And so you can see that we basically you know we we went
00:05:38.795 --> 00:05:42.978 from around 3 million in revenue to 6 million during the course
00:05:42.978 --> 00:05:43.959 of this period.
00:05:43.969 --> 00:05:48.618 Here I would really describe this year as stabilizing the
00:05:48.618 --> 00:05:49.339 business.
00:05:49.729 --> 00:05:53.872 You can see that we on the left of each of these, I'm
00:05:53.872 --> 00:05:58.858 representing expenses as yellow and then profit as green and any
00:05:58.858 --> 00:06:00.469 kind of loss as read.
00:06:00.759 --> 00:06:04.834 And so you can see the, you know the 2022 was not the best year
00:06:04.834 --> 00:06:08.462 as far as from accounting perspective, but we made a lot
00:06:08.462 --> 00:06:11.009 of major investments into our products.
00:06:11.259 --> 00:06:15.252 And so now this year we've been able to really accumulate that
00:06:15.252 --> 00:06:19.182 into, you know, a profitable operation, especially the second
00:06:19.182 --> 00:06:20.259 half of the year.
00:06:21.239 --> 00:06:25.970 And I'll talk about that in more detail as we go, but this is the
00:06:25.970 --> 00:06:30.414 projection for next year and I'll show you a breakdown of why
00:06:30.414 --> 00:06:35.002 I think this is potentially, you know, something we can achieve
00:06:35.002 --> 00:06:36.149 to get from 6.1.
00:06:36.799 --> 00:06:40.658 We're expecting to close out somewhere between 6.1 and 6.2
00:06:40.658 --> 00:06:44.714 million, and it really depends on how things go by the end of
00:06:44.714 --> 00:06:48.769 next week, because there's still a lot coming in as we speak.
00:06:48.779 --> 00:06:52.843 So, but somewhere between 6.1 and 6.2 million to go from that
00:06:52.843 --> 00:06:55.269 to 8,000,000 is a pretty major jump.
00:06:55.279 --> 00:06:57.972 So I'm going to show you, you know, what the thought process
00:06:57.972 --> 00:06:58.369 is there.
00:07:00.569 --> 00:07:05.127 And so ultimately, you know, taking this vision of being able
00:07:05.127 --> 00:07:09.244 to deliver for niche markets that we're focusing on and
00:07:09.244 --> 00:07:13.655 really owning that market by being the best in that market,
00:07:13.655 --> 00:07:17.919 it it's easy to talk about, but it's not very easy to do.
00:07:18.349 --> 00:07:22.262 Maybe it's simple, but not easy and so that's kind of the next
00:07:22.262 --> 00:07:26.175 topic here is to just reinforce this idea of execution and you
00:07:26.175 --> 00:07:28.659 can see the quote from Steve Jobs here.
00:07:28.669 --> 00:07:33.183 I think is a great quote and fundamentally we have to really
00:07:33.183 --> 00:07:37.549 just take our vision and break it into granular specifics.
00:07:37.559 --> 00:07:41.031 And I'm going to show you and a lot of this is just reinforcing
00:07:41.031 --> 00:07:44.502 areas that you're already well aware of, just to make sure that
00:07:44.502 --> 00:07:47.974 we're talking about, you know, keeping the main thing, the main
00:07:47.974 --> 00:07:51.229 thing right, and keeping the main fundamentals on our mind.
00:07:51.879 --> 00:07:54.069 But we have to take the plan.
00:07:54.459 --> 00:07:58.643 Break it into, you know, detailed goals and objectives
00:07:58.643 --> 00:08:02.599 and then actually execute on those and then review.
00:08:02.679 --> 00:08:06.501 And so that's what I'm going to talk about next is basically
00:08:06.501 --> 00:08:10.322 what is our execution been like over the last several months
00:08:10.322 --> 00:08:14.081 since you've seen an update where we at is an overall group
00:08:14.081 --> 00:08:17.401 because I know a lot of team members know about your
00:08:17.401 --> 00:08:20.910 independent, you know sort of focus area, but it's hard
00:08:20.910 --> 00:08:24.982 especially being remote to get a great sense of how everything's
00:08:24.982 --> 00:08:25.859 going overall.
00:08:25.869 --> 00:08:29.284 So I want to walk you through that next, umm, first of all,
00:08:29.284 --> 00:08:31.219 just say this is really exciting.
00:08:31.229 --> 00:08:32.659 There's some nice progression.
00:08:33.149 --> 00:08:33.479 Uh.
00:08:33.489 --> 00:08:37.852 From a marketing perspective, from results vantage point with
00:08:37.852 --> 00:08:42.427 getting our products represented as products and our niche focus
00:08:42.427 --> 00:08:42.849 areas.
00:08:42.859 --> 00:08:45.929 So this is one of our pages on our site.
00:08:45.939 --> 00:08:48.119 You can go to this now if you want to check it out live.
00:08:49.209 --> 00:08:53.240 It's it's probably slightly different looking than this, but
00:08:53.240 --> 00:08:57.337 this is a you know, sort of a picture of some of the products
00:08:57.337 --> 00:08:58.659 that we're offering.
00:08:58.949 --> 00:09:01.739 And I think the work on the site has been incredible.
00:09:02.469 --> 00:09:07.163 You know, really over the last six months it it's really had a
00:09:07.163 --> 00:09:11.856 very positive uptick and major positive impact on the business
00:09:11.856 --> 00:09:12.229 here.
00:09:12.239 --> 00:09:15.329 You can see data, so I'm not just using words.
00:09:15.479 --> 00:09:17.729 You can see data on our site performance.
00:09:18.379 --> 00:09:20.589 This is a six month view.
00:09:20.739 --> 00:09:24.144 Going back to this summer, looking at organic traffic for
00:09:24.144 --> 00:09:27.725 the website and you can see this is a really good, you know,
00:09:27.725 --> 00:09:31.306 trend up into the right and and this is just what we've been
00:09:31.306 --> 00:09:34.829 experiencing really consistently within our marketing team.
00:09:35.059 --> 00:09:35.429 Yeah.
00:09:35.439 --> 00:09:39.860 Go Alex and Autumn and Steve and Phil and there's a lot of
00:09:39.860 --> 00:09:44.355 contribution will and Ron are doing a lot with the new site
00:09:44.355 --> 00:09:45.479 and collateral.
00:09:45.489 --> 00:09:46.699 So, good job, everyone.
00:09:47.609 --> 00:09:47.899 Yeah.
00:09:47.909 --> 00:09:51.497 And ultimately, we're expecting to, you know, have the
00:09:51.497 --> 00:09:53.519 opportunity to do more of this.
00:09:54.049 --> 00:09:57.942 And really, the thing that I want you to take away from the
00:09:57.942 --> 00:10:01.836 marketing is that we're focusing in on niche areas with our
00:10:01.836 --> 00:10:05.600 products and this really makes us valuable to those niche
00:10:05.600 --> 00:10:05.989 areas.
00:10:06.459 --> 00:10:10.865 We can be the best within the particular niches, and again
00:10:10.865 --> 00:10:15.047 whenever I'm, you know, referring to niche focus areas,
00:10:15.047 --> 00:10:19.155 I'm talking about, you know marketplace, HIPAA auction
00:10:19.155 --> 00:10:23.412 integrated ecommerce with specific Erps, payment hub and
00:10:23.412 --> 00:10:24.009 connect.
00:10:24.119 --> 00:10:28.579 And so, umm, my son is crying in the background.
00:10:28.589 --> 00:10:31.829 Ohh so I've it's so so sad.
00:10:32.459 --> 00:10:37.078 Hopefully he's OK, but yeah, basically one of the one of the
00:10:37.078 --> 00:10:41.999 challenges within this business is the growth that we're working
00:10:41.999 --> 00:10:46.845 in the growth model that we're working in is a bootstrap growth
00:10:46.845 --> 00:10:47.299 model.
00:10:47.679 --> 00:10:51.772 And so I just want to show you and I'll kind of start back
00:10:51.772 --> 00:10:52.119 here.
00:10:52.559 --> 00:10:53.049 Umm.
00:10:53.599 --> 00:10:57.665 Basically, the mechanics of this focusing on these particular
00:10:57.665 --> 00:11:01.797 products, it's very challenging to get everything right all at
00:11:01.797 --> 00:11:06.059 once and take on a bunch of new customers and do a great job and
00:11:06.059 --> 00:11:10.191 and you know how everything go perfectly when you don't have a
00:11:10.191 --> 00:11:11.109 lot of buffer.
00:11:11.579 --> 00:11:13.889 And so that's really been the name of the game.
00:11:13.899 --> 00:11:17.178 For clarity, the entire time we've operated, we've been
00:11:17.178 --> 00:11:19.169 operating as a bootstrap company.
00:11:19.789 --> 00:11:23.827 This fundamentally puts a lot of pressure on key roles within the
00:11:23.827 --> 00:11:27.620 business and overall it puts a lot of pressure on the team on
00:11:27.620 --> 00:11:31.352 you, on everyone you know on this call and it it changes the
00:11:31.352 --> 00:11:32.759 dynamic of the company.
00:11:33.719 --> 00:11:38.020 Umm, the positive from this and and you know there are positives
00:11:38.020 --> 00:11:42.256 and negatives from this approach is that we have control of the
00:11:42.256 --> 00:11:43.579 business as a group.
00:11:44.499 --> 00:11:48.367 So there isn't going to be an external, you know, venture
00:11:48.367 --> 00:11:52.569 Capital Group or private equity group that's going to sell the
00:11:52.569 --> 00:11:56.703 business out from underneath us or make a really poor choice,
00:11:56.703 --> 00:12:00.771 you know with how to operate the business, we get to own and
00:12:00.771 --> 00:12:03.239 execute on these decisions together.
00:12:04.089 --> 00:12:08.651 Umm so as we build momentum, we're going to be positioned to
00:12:08.651 --> 00:12:13.362 make all of the generally the most optimal decisions and be in
00:12:13.362 --> 00:12:17.849 a position to benefit from it the most financially as well.
00:12:18.719 --> 00:12:22.759 It's just intense getting that sort of inertia going.
00:12:23.309 --> 00:12:26.386 And what I think you'll see is that from what we've
00:12:26.386 --> 00:12:30.231 accomplished and what we've been through really over the last 12
00:12:30.231 --> 00:12:33.781 months, the company is in a position now, uh to really take
00:12:33.781 --> 00:12:37.036 advantage of that position of ownership and not having
00:12:37.036 --> 00:12:38.929 external liability, if you will.
00:12:39.889 --> 00:12:41.529 And so now I just.
00:12:43.829 --> 00:12:44.589 Side buddy.
00:12:47.999 --> 00:12:49.739 Ohh her little on.
00:12:51.559 --> 00:12:53.189 On the pink swing.
00:12:53.199 --> 00:12:54.039 I'm sorry, buddy.
00:12:55.489 --> 00:12:56.619 Hmm, I hope you feel better.
00:12:56.629 --> 00:12:57.519 Daddy's in a meeting.
00:12:57.529 --> 00:12:58.639 Do you want to say hi to everyone?
00:12:59.589 --> 00:13:00.539 Can you say hi?
00:13:00.909 --> 00:13:04.044 Ohh I'm sure for those of you that have kiddos home from
00:13:04.044 --> 00:13:06.189 Christmas break, you know the feeling.
00:13:07.729 --> 00:13:11.875 Umm but yeah, basically in summary, why don't you go
00:13:11.875 --> 00:13:13.439 downstairs to Mommy?
00:13:13.449 --> 00:13:15.119 OK buddy, I'll see you in a little bit.
00:13:15.169 --> 00:13:15.679 I love you.
00:13:16.049 --> 00:13:16.759 I hope you feel better.
00:13:18.829 --> 00:13:23.883 Umm, one of the things that I'll say here is, umm, the business
00:13:23.883 --> 00:13:27.199 has really experienced a lot of overhead.
00:13:27.609 --> 00:13:30.828 That's been really challenging and you can see that if you if
00:13:30.828 --> 00:13:33.840 you basically take a look at where we've been, uh, from a
00:13:33.840 --> 00:13:37.007 financial perspective and I'll try to make this pretty quick
00:13:37.007 --> 00:13:39.759 for you, I don't want to get too mired in the weeds.
00:13:40.539 --> 00:13:45.025 Umm, we track all of our revenue in an Excel file in addition to
00:13:45.025 --> 00:13:47.579 our CRM and our accounting software.
00:13:48.219 --> 00:13:51.694 The Excel file is really helpful because we can see really high
00:13:51.694 --> 00:13:54.789 level where we're at in any given time without having to
00:13:54.789 --> 00:13:57.069 get, you know, into the details too much.
00:13:57.959 --> 00:14:01.508 So you can see if you look at this, basically our average
00:14:01.508 --> 00:14:05.240 revenue, the second half of this year has been substantially
00:14:05.240 --> 00:14:07.749 higher than the first half of this year.
00:14:08.299 --> 00:14:12.317 And there's an ebb and flow to the revenue and that's just a
00:14:12.317 --> 00:14:14.359 reality of this business model.
00:14:14.989 --> 00:14:17.758 But generally, the average revenue in the first half of the
00:14:17.758 --> 00:14:20.619 year was substantially less than the second half of the year.
00:14:20.929 --> 00:14:25.046 So the key takeaway here is really simply that top line
00:14:25.046 --> 00:14:29.825 revenue second half of the year, big top line revenue first half
00:14:29.825 --> 00:14:31.589 of the year, not as big.
00:14:31.699 --> 00:14:35.376 And I know that's really simple, but I I want you to sort of take
00:14:35.376 --> 00:14:36.769 that key thought process.
00:14:37.869 --> 00:14:42.899 In fact, our average revenue over the last you know basically
00:14:42.899 --> 00:14:47.685 six months of the last of the you know, yeah, the last six
00:14:47.685 --> 00:14:52.390 months including this month UMM, is expected to be around
00:14:52.390 --> 00:14:53.039 550,000.
00:14:53.049 --> 00:14:54.709 Again, we still have to close this month out.
00:14:55.439 --> 00:14:59.442 Umm, our overhead has gone substantially down from where it
00:14:59.442 --> 00:15:03.779 was earlier in the year and it's now sitting at about $509,000 a
00:15:03.779 --> 00:15:04.179 month.
00:15:05.039 --> 00:15:09.305 So if you just kind of do the quick math 550 -, 509, that's
00:15:09.305 --> 00:15:11.509 about a $40,000 a month profit.
00:15:12.889 --> 00:15:15.652 Now the interesting thing about our business, and I promise I'll
00:15:15.652 --> 00:15:18.161 try to keep this part quick, but I'm trying to give you an
00:15:18.161 --> 00:15:20.329 overview of the fundamentals of the business here.
00:15:21.179 --> 00:15:25.563 Umm, the fundamentals just very, very high level are that we're
00:15:25.563 --> 00:15:28.988 expecting certain general numbers from a billable
00:15:28.988 --> 00:15:32.139 perspective and then a licensing perspective.
00:15:32.709 --> 00:15:37.238 So anywhere from 10 to 15% of our top line revenue is coming
00:15:37.238 --> 00:15:39.169 from license revenue, umm.
00:15:39.179 --> 00:15:44.181 And then we also have services revenue as I'm showing here now,
00:15:44.181 --> 00:15:48.870 our average hourly rate is really somewhere between 175 and
00:15:48.870 --> 00:15:50.589 185 an hour right now.
00:15:50.959 --> 00:15:55.002 And so with our current team and with our current allocation,
00:15:55.002 --> 00:15:59.111 this is gonna change per month based on holidays and paid time
00:15:59.111 --> 00:16:01.589 off and number of days in that month.
00:16:01.599 --> 00:16:05.908 But it's gonna average around 600,000 a month in revenue that
00:16:05.908 --> 00:16:07.229 we can achieve now.
00:16:07.239 --> 00:16:11.281 We've been tracking this very closely and what you'll see, let
00:16:11.281 --> 00:16:12.949 me get to the report here.
00:16:13.899 --> 00:16:18.027 What you will see is that we're actually we're doing a great job
00:16:18.027 --> 00:16:22.154 and this is where reflection on the operations team, the project
00:16:22.154 --> 00:16:25.647 management team and the development team in particular
00:16:25.647 --> 00:16:27.679 with really nailing our numbers.
00:16:27.689 --> 00:16:31.249 So this is a report that shows November.
00:16:31.319 --> 00:16:35.289 So this is just one month, but the most recent month you can
00:16:35.289 --> 00:16:38.739 see that and and by the way, there's a link to this.
00:16:38.809 --> 00:16:39.819 It's hard to see.
00:16:39.829 --> 00:16:43.431 I know I've made the font really small, but take a look at this
00:16:43.431 --> 00:16:44.219 if you'd like.
00:16:44.229 --> 00:16:45.799 Everyone should have access.
00:16:45.859 --> 00:16:49.922 I would love it if you would click on it and just make sure
00:16:49.922 --> 00:16:53.646 you can see this report yourself, but you can see this
00:16:53.646 --> 00:16:57.911 for any given time period and it accounts for PTO and holidays
00:16:57.911 --> 00:17:01.635 and it looks at what the expected billable is per team
00:17:01.635 --> 00:17:04.479 member that's doing client billable work.
00:17:04.689 --> 00:17:09.014 And anyway, Long story short, we've got about a 94% attainment
00:17:09.014 --> 00:17:12.789 in November of our objectives and this is pretty good.
00:17:12.879 --> 00:17:16.960 So it's it's not perfect, but if you kind of take that and
00:17:16.960 --> 00:17:21.456 measure that against what I was showing you earlier with what is
00:17:21.456 --> 00:17:22.079 possible.
00:17:23.039 --> 00:17:24.119 So let me go back to that.
00:17:27.039 --> 00:17:31.363 You can see that we're expecting to be at about 3600 client
00:17:31.363 --> 00:17:33.669 billable on average in November.
00:17:33.679 --> 00:17:36.861 Because of the holiday was a little bit lower of a month in
00:17:36.861 --> 00:17:37.179 total.
00:17:37.619 --> 00:17:39.039 And so we're very close to this.
00:17:39.049 --> 00:17:43.041 We're not ******* it perfectly, but if you also add in license
00:17:43.041 --> 00:17:46.969 and SAS revenue, which I'll talk about here in just a minute,
00:17:46.969 --> 00:17:50.834 we're really are at a position where we can be hitting about
00:17:50.834 --> 00:17:53.369 600,000 a month really going into 2024.
00:17:53.579 --> 00:17:56.379 And then incrementally raise that number as we progress
00:17:56.379 --> 00:17:57.379 throughout the year.
00:17:58.179 --> 00:17:58.499 Umm.
00:17:58.519 --> 00:18:02.244 So if you look at our projections for next year and
00:18:02.244 --> 00:18:06.183 I'll just kind of briefly go into those now, there's a
00:18:06.183 --> 00:18:10.552 section called financial and C Labs that's short for Clarity
00:18:10.552 --> 00:18:13.919 Labs and I'll, I'll just, I'll spell that out.
00:18:14.689 --> 00:18:18.919 Umm, so this is basically our objectives for those.
00:18:20.309 --> 00:18:25.204 You can see that basically the target for January of 2024 is
00:18:25.204 --> 00:18:30.259 600,000 gross revenue and about 10,000 a month in SAS revenue,
00:18:30.259 --> 00:18:33.629 which we already are achieving right now.
00:18:33.869 --> 00:18:35.999 And I won't go into a ton of detail.
00:18:36.009 --> 00:18:41.117 I'll just show you the here's here are all the accounts and
00:18:41.117 --> 00:18:46.481 the the monthly amount and the you know the total value, total
00:18:46.481 --> 00:18:51.249 contract value of these SAS payments is about $219,000.
00:18:51.489 --> 00:18:54.975 So we have about $10,000 a month that's currently coming in and
00:18:54.975 --> 00:18:57.209 recurring SAS revenue, which is awesome.
00:18:57.989 --> 00:19:00.814 And you can see, uh, we also have about 5000 a month in
00:19:00.814 --> 00:19:02.579 payments revenue that's coming in.
00:19:03.419 --> 00:19:07.302 And so the plan is to just increase these incrementally
00:19:07.302 --> 00:19:08.689 throughout the year.
00:19:09.219 --> 00:19:12.947 Now by doing that, and if you recall, I I mentioned the
00:19:12.947 --> 00:19:16.409 overhead of 509,000, I just rounded that up to 510.
00:19:17.159 --> 00:19:21.617 Umm, it actually, our overhead goes down in April to about
00:19:21.617 --> 00:19:26.075 450,000 and so you kind of do the math and you get to this
00:19:26.075 --> 00:19:30.609 profit number that's in the middle and and so we're looking
00:19:30.609 --> 00:19:35.218 at about 100 to, you know even more in profit as we progress
00:19:35.218 --> 00:19:36.729 throughout the year.
00:19:37.469 --> 00:19:41.709 Now, believe me when I tell you that this is really exciting to
00:19:41.709 --> 00:19:42.239 look at.
00:19:42.249 --> 00:19:45.416 And think about what the reality tends to be is something more
00:19:45.416 --> 00:19:47.879 like this is kind of like a roller coaster ride.
00:19:49.419 --> 00:19:53.173 Umm, but you know you're not gonna achieve a goal unless you
00:19:53.173 --> 00:19:54.589 set it and focus on it.
00:19:54.599 --> 00:19:55.149 Right.
00:19:55.399 --> 00:19:59.089 And so this is what the goal is going into next year.
00:20:00.369 --> 00:20:04.097 And one of the really awesome outputs from this that I really
00:20:04.097 --> 00:20:07.705 wanna make sure you catch and you understand is that at the
00:20:07.705 --> 00:20:11.073 last event we announced that we're going to be creating
00:20:11.073 --> 00:20:13.839 something we're referring to as clarity labs.
00:20:14.309 --> 00:20:18.362 And I think a lot of folks will agree that it's absolutely
00:20:18.362 --> 00:20:22.141 critical that we invest into our products and into our
00:20:22.141 --> 00:20:26.125 development team so that we can do our R&D and really
00:20:26.125 --> 00:20:30.178 improve our products and do the obvious things that you're
00:20:30.178 --> 00:20:33.751 seeing as you're working on projects that there are
00:20:33.751 --> 00:20:38.010 challenges or issues with on a particular part of the code or
00:20:38.010 --> 00:20:41.239 project type or integration, et cetera, right.
00:20:41.849 --> 00:20:45.015 It's absolutely critical that we have this reinvestment back into
00:20:45.015 --> 00:20:45.639 the business.
00:20:46.429 --> 00:20:48.519 Eric's gonna talk about this in more detail.
00:20:48.599 --> 00:20:50.399 I just want you to see the high level.
00:20:50.409 --> 00:20:54.478 This is something that's baked into the plan starting in
00:20:54.478 --> 00:20:56.619 January to allocate resources.
00:20:56.629 --> 00:21:00.253 And so we've got the dollar amount and then we have the
00:21:00.253 --> 00:21:03.359 number of hours per month baked into this plan.
00:21:03.569 --> 00:21:06.650 And so the really cool thing about this is as our profit goes
00:21:06.650 --> 00:21:08.539 up, this number goes up dramatically.
00:21:08.969 --> 00:21:13.681 And so, for anyone who's really been seeing their, you know, the
00:21:13.681 --> 00:21:17.886 projects that you've been working on challenges, which is
00:21:17.886 --> 00:21:22.526 basic parts of the code and and really just generally our offer
00:21:22.526 --> 00:21:23.469 that we have.
00:21:23.579 --> 00:21:26.848 And this is really meant to dramatically improve our offer
00:21:26.848 --> 00:21:30.449 in the market and the value that we're bringing for each client.
00:21:30.799 --> 00:21:34.094 So as a really exciting opportunity, it's also a very
00:21:34.094 --> 00:21:37.938 exciting opportunity for team members who are helping to drive
00:21:37.938 --> 00:21:41.599 these areas of research and development, because you'll get
00:21:41.599 --> 00:21:44.711 to spearhead big chunks of software development or
00:21:44.711 --> 00:21:48.128 improvement to our documentation and client expectation
00:21:48.128 --> 00:21:49.409 management, etcetera.
00:21:49.879 --> 00:21:52.609 So let me just stop and see if anyone has any questions.
00:21:52.919 --> 00:21:56.694 I'm gonna leave it there on the just sort of general financial
00:21:56.694 --> 00:22:00.170 update and then I'm gonna go ahead and talk about project
00:22:00.170 --> 00:22:01.249 deliverables next.
00:22:01.479 --> 00:22:05.595 And I want to invite any of the leadership team members to sort
00:22:05.595 --> 00:22:09.004 of chime in on topics I've covered or on the project
00:22:09.004 --> 00:22:10.869 deliverables as I go into it.
00:22:10.879 --> 00:22:13.475 But any questions or comments before I move on to the next
00:22:13.475 --> 00:22:13.739 topic?
00:22:16.419 --> 00:22:21.391 Feel free and you can raise your hand, or you can just pipe in
00:22:21.391 --> 00:22:22.969 whatever works best.
00:22:22.979 --> 00:22:23.349 Feel free.
00:22:27.409 --> 00:22:30.415 And if I don't hear any questions, I'll just go ahead
00:22:30.415 --> 00:22:31.139 and continue.
00:22:31.869 --> 00:22:35.061 Basically, the next thing that I want to hit on and I'll just
00:22:35.061 --> 00:22:38.459 take a couple of minutes to talk about this is what I would refer
00:22:38.459 --> 00:22:39.849 to as project deliverables.
00:22:40.759 --> 00:22:45.156 Umm, one of the challenges that I think everyone faces at
00:22:45.156 --> 00:22:49.629 clarity is that we generally know what to do, but we don't
00:22:49.629 --> 00:22:54.101 necessarily have enough time to do it all and there can be
00:22:54.101 --> 00:22:58.650 spikes as we know of major amounts of work that needs to be
00:22:58.650 --> 00:22:59.029 done.
00:22:59.499 --> 00:23:03.327 And one of the challenges in general with operating business
00:23:03.327 --> 00:23:06.779 is that fundamentally it's hard to transfer knowledge,
00:23:06.779 --> 00:23:07.909 especially remote.
00:23:08.519 --> 00:23:12.219 It's mechanically challenging to transfer knowledge and so we
00:23:12.219 --> 00:23:14.069 really need to have a playbook.
00:23:14.079 --> 00:23:17.880 We need to have a way as a group, that we can make sure
00:23:17.880 --> 00:23:21.273 that we're executing consistently for clients and
00:23:21.273 --> 00:23:25.413 this really helps us with a playbook and reviewing the plays
00:23:25.413 --> 00:23:29.621 like actually watching how the plays went and then, you know,
00:23:29.621 --> 00:23:34.032 actually conducting analysis and discussion and review about how
00:23:34.032 --> 00:23:38.036 each of these projects go and each of the deliverables are
00:23:38.036 --> 00:23:42.380 executed on it will help us to dramatically improve how quickly
00:23:42.380 --> 00:23:46.452 we're sharing information and targeting what information to
00:23:46.452 --> 00:23:46.859 share.
00:23:47.859 --> 00:23:51.948 And fundamentally, I think one of the challenges that we have
00:23:51.948 --> 00:23:55.509 at clarity, which is an opportunity is our client sat
00:23:55.509 --> 00:23:57.949 and making our client sat go way up.
00:23:58.389 --> 00:24:02.807 I I think that will continue to drive our team morale and our
00:24:02.807 --> 00:24:07.154 you know, just our overall sense of having actual value that
00:24:07.154 --> 00:24:09.149 we're delivering to clients.
00:24:09.369 --> 00:24:12.829 It's really predicated on client satisfaction, right?
00:24:13.439 --> 00:24:17.569 And so the project deliverables are really founded in that
00:24:17.569 --> 00:24:21.769 thought of how can we ensure that clients get an incredible
00:24:21.769 --> 00:24:25.829 delivery that's going to provide them with what they were
00:24:25.829 --> 00:24:27.159 expecting up front.
00:24:28.059 --> 00:24:32.119 Now, without going into a lot of detail on these, there's a link
00:24:32.119 --> 00:24:36.242 that has, uh, granular detail in nuclino that you can take a look
00:24:36.242 --> 00:24:36.429 at.
00:24:36.599 --> 00:24:40.757 We're gonna be continuing to talk about these, but it really
00:24:40.757 --> 00:24:44.029 boils down to taking three phases of a project.
00:24:44.119 --> 00:24:49.263 One is onboarding and discovery, the next is the per Sprint
00:24:49.263 --> 00:24:49.949 cadence.
00:24:49.959 --> 00:24:54.003 So development implementation and then you know basically prep
00:24:54.003 --> 00:24:58.111 for and go live and included in the go live is this idea of you
00:24:58.111 --> 00:25:02.155 know basically transitioning the project to an ongoing support
00:25:02.155 --> 00:25:02.669 project.
00:25:03.549 --> 00:25:06.623 And so how are we making sure that this goes really, really
00:25:06.623 --> 00:25:06.879 well?
00:25:07.289 --> 00:25:11.653 Now I think a lot of folks will know that, you know, we're doing
00:25:11.653 --> 00:25:15.412 a lot more with demos on projects you may be working on
00:25:15.412 --> 00:25:17.359 demos right now or next week.
00:25:18.089 --> 00:25:23.039 We're really pressing to get demos for active projects now.
00:25:23.049 --> 00:25:26.580 We can't do this level of delivery for every single client
00:25:26.580 --> 00:25:27.059 project.
00:25:27.349 --> 00:25:31.069 It doesn't logically make sense to do everything on this list
00:25:31.069 --> 00:25:34.789 for every client project, but for projects that have a lot of
00:25:34.789 --> 00:25:38.509 activity, it makes sense to go through an audit and make sure
00:25:38.509 --> 00:25:42.349 that these basics are at a very high level of delivery and that
00:25:42.349 --> 00:25:44.269 we're rigorously reviewing that.
00:25:44.559 --> 00:25:48.925 So we actually put together in the CRM fields to be able to
00:25:48.925 --> 00:25:53.365 track this and per project go in and verify that each of the
00:25:53.365 --> 00:25:55.839 phases has these items completed.
00:25:56.699 --> 00:26:00.934 And So what I would say to this is just generally speaking, I
00:26:00.934 --> 00:26:05.305 want to encourage you to, as we go through and execute on these
00:26:05.305 --> 00:26:09.540 project deliverables, share your feedback and thoughts on you
00:26:09.540 --> 00:26:13.502 know how effective these are areas that we can refine and
00:26:13.502 --> 00:26:17.122 tune these the intent is for each of these to have a
00:26:17.122 --> 00:26:21.152 checklist so that each of these areas that we're executing
00:26:21.152 --> 00:26:24.499 against has detailed steps that we can complete.
00:26:25.409 --> 00:26:28.955 And I'm sure you would probably agree if you work in connect
00:26:28.955 --> 00:26:31.919 versus Seth, it's not gonna be the same checklist.
00:26:32.189 --> 00:26:36.156 It needs to be reflective or respective to that particular
00:26:36.156 --> 00:26:38.039 niche focus area or product.
00:26:38.809 --> 00:26:42.722 So anyway, that is the project deliverables and I just want to
00:26:42.722 --> 00:26:46.262 make sure you have a heads up about what it is, what the
00:26:46.262 --> 00:26:49.553 intent is behind doing these check-ins so that we're
00:26:49.553 --> 00:26:53.466 essentially operating against a playbook together that each of
00:26:53.466 --> 00:26:57.441 us on the team can work against and that we have the ability to
00:26:57.441 --> 00:26:58.559 conduct reporting.
00:26:59.589 --> 00:27:03.168 And then review together as a team so we can make sure that
00:27:03.168 --> 00:27:06.210 each client has a great experience and that really
00:27:06.210 --> 00:27:09.908 drives everything within the business as long as clients have
00:27:09.908 --> 00:27:13.665 a great experience, then we're going to be able to continue to
00:27:13.665 --> 00:27:14.739 fuel this machine.
00:27:15.149 --> 00:27:18.972 And really, I I'll just wrap up my comments, which is kind of
00:27:18.972 --> 00:27:22.857 talking about what I talk about a lot in some of the different
00:27:22.857 --> 00:27:26.866 events where you know, different team members are working within
00:27:26.866 --> 00:27:28.839 different areas of the business.
00:27:28.849 --> 00:27:32.632 And I like to relate it to different course types where you
00:27:32.632 --> 00:27:36.668 have a maybe a muddy course for a part of the group and maybe a
00:27:36.668 --> 00:27:39.379 paved course for another part of the team.
00:27:39.969 --> 00:27:44.230 But it's really curvy and then just a very flat course that's
00:27:44.230 --> 00:27:48.079 smooth and very technical for another part of the team.
00:27:48.089 --> 00:27:51.394 And I think if you just kind of, you know don't take that analogy
00:27:51.394 --> 00:27:54.249 too far, but just think about your area of the business.
00:27:54.259 --> 00:27:55.049 You would probably agree.
00:27:55.989 --> 00:27:59.286 Everybody has very different roles that we all have the same
00:27:59.286 --> 00:28:02.583 principles that we've got to adhere to so we can deliver for
00:28:02.583 --> 00:28:06.096 these clients and fundamental to everything that we're all doing
00:28:06.096 --> 00:28:08.799 is we wanna win the race, we wanna be successful.
00:28:09.069 --> 00:28:12.935 And for clarity, for us overall that means executing really well
00:28:12.935 --> 00:28:13.649 for clients.
00:28:14.159 --> 00:28:16.399 And so that's the intent behind the project deliverables.
00:28:17.039 --> 00:28:20.229 Umm, let me see if you want to.
00:28:20.299 --> 00:28:23.130 If you wanna talk about any of those, if anyone has any
00:28:23.130 --> 00:28:26.112 comments and then really the next part of this discussion,
00:28:26.112 --> 00:28:28.589 the fireside is gonna be a lot more interactive.
00:28:28.779 --> 00:28:32.104 Basically, the plan is to just go through and have different
00:28:32.104 --> 00:28:35.047 team members, different leaders from within different
00:28:35.047 --> 00:28:38.208 representative areas of the business, provide updates and
00:28:38.208 --> 00:28:41.315 just have some high level overview of what's going on in
00:28:41.315 --> 00:28:41.969 those areas.
00:28:42.439 --> 00:28:46.480 And just to kind of cue that up, my plan would be fulfill if
00:28:46.480 --> 00:28:50.389 you're comfortable going ahead next for you to start next.
00:28:50.519 --> 00:28:55.540 And then Eric, on the product side of things, Brendan Lyon on
00:28:55.540 --> 00:29:00.884 Phoenix, JLR on connect and then Brent provided a video that I'll
00:29:00.884 --> 00:29:02.909 be sharing as well on AI.
00:29:03.199 --> 00:29:07.009 But any comments or questions on project deliverables?
00:29:07.019 --> 00:29:07.349 Feel free.
00:29:08.899 --> 00:29:10.279 I added a comment, Chris.
00:29:10.289 --> 00:29:13.114 We were missing the client enablement and then you asked me
00:29:13.114 --> 00:29:14.009 before the meeting.
00:29:13.219 --> 00:29:14.039 Oh, thanks. Awesome.
00:29:14.119 --> 00:29:17.656 I didn't hear during the agenda you asked me to talk about the
00:29:17.656 --> 00:29:20.519 PFD's and the phases document, but you didn't, so.
00:29:19.219 --> 00:29:20.969 Yeah, if you would, that would be great.
00:29:20.979 --> 00:29:21.659 Yeah, please.
00:29:22.489 --> 00:29:23.459 And here's this.
00:29:23.529 --> 00:29:26.049 Here's this one if you want to talk about that.
00:29:27.339 --> 00:29:28.549 Ohh, wanna talk about it now?
00:29:28.559 --> 00:29:33.755 OK, one of the things that we're trying to do is give the PM's
00:29:33.755 --> 00:29:37.219 and the business analyst for the clients.
00:29:37.229 --> 00:29:40.509 When we get into discovery a little better expectation
00:29:40.509 --> 00:29:44.207 setting and we're gonna do this and we're moving this up into
00:29:44.207 --> 00:29:47.726 sales as well about this is strictly about the development
00:29:47.726 --> 00:29:48.919 life cycle planning.
00:29:48.929 --> 00:29:54.339 So how are their items within the discovery?
00:29:54.449 --> 00:29:57.645 How do they fall under a stratification of low, medium
00:29:57.645 --> 00:29:58.459 and high risk?
00:29:58.669 --> 00:30:01.609 So the term we're going to use is variability, right?
00:30:01.619 --> 00:30:05.127 So we can go into these guys as you get into discovery and they
00:30:05.127 --> 00:30:08.580 can have an expectation that of the 12 things that we're going
00:30:08.580 --> 00:30:11.869 to do on this project for those fall under low variability.
00:30:11.879 --> 00:30:14.729 So they'll be part of the early development.
00:30:14.739 --> 00:30:17.386 There'll be very little risk involved, very little
00:30:17.386 --> 00:30:18.009 variability.
00:30:18.139 --> 00:30:21.488 There will be some medium items that will happen during the next
00:30:21.488 --> 00:30:24.527 phase and then the high risk items or the high variability
00:30:24.527 --> 00:30:27.618 items may require additional discovery and they have a high
00:30:27.618 --> 00:30:30.349 likelihood of posing some variability or risk to the
00:30:30.349 --> 00:30:31.379 budget and timeline.
00:30:31.389 --> 00:30:33.249 So this document maps it out.
00:30:33.349 --> 00:30:37.203 It articulates which items would fall under that low, medium and
00:30:37.203 --> 00:30:37.499 high.
00:30:37.599 --> 00:30:41.232 So we're going to in the sales cycle provide access to this
00:30:41.232 --> 00:30:44.803 document and allude to the document as we talk about going
00:30:44.803 --> 00:30:48.618 through discovery, we're going to add to the project estimates
00:30:48.618 --> 00:30:52.190 we're going to qualify all of the individual line items as
00:30:52.190 --> 00:30:55.641 low, medium and high and then that way when you get into
00:30:55.641 --> 00:30:59.212 discovery and we go do the estimates and things change, it
00:30:59.212 --> 00:30:59.939 can go well.
00:30:59.949 --> 00:31:02.802 It's because these 5 high variability items, as we've done
00:31:02.802 --> 00:31:05.559 the discovery for him, they were highly variable, right?
00:31:05.569 --> 00:31:08.345 It's going to be something that's the expectations already
00:31:08.345 --> 00:31:08.769 been set.
00:31:08.779 --> 00:31:11.623 It's going to be very clear, Chris, you want to add to that
00:31:11.623 --> 00:31:12.239 articulation.
00:31:12.249 --> 00:31:17.759 This document is in the collateral worksheet.
00:31:18.389 --> 00:31:19.839 I moved it up this morning.
00:31:18.799 --> 00:31:20.509 Which I put a link to here.
00:31:20.989 --> 00:31:24.229 Yeah, I moved it up to row 23. Yeah.
00:31:21.139 --> 00:31:22.989 Again, it's a really small link.
00:31:22.999 --> 00:31:27.509 So yeah, go ahead, man. Sorry.
00:31:28.109 --> 00:31:31.829 Yeah, I moved it up to row 23 right below the PFSRD.
00:31:31.839 --> 00:31:35.509 Links to all the PDF SDS which are not only here in the
00:31:35.509 --> 00:31:39.311 collateral worksheet, they are also in the help center as
00:31:39.311 --> 00:31:43.375 they're being published, they're being moved to each of their
00:31:43.375 --> 00:31:44.489 respective pages.
00:31:44.739 --> 00:31:47.718 So when we do the client enablement training, the piece
00:31:47.718 --> 00:31:50.909 that I was just saying that was missing from the phase one.
00:31:51.099 --> 00:31:53.901 When I do that training, the very first thing I'm going to
00:31:51.609 --> 00:31:51.919 Umm.
00:31:53.901 --> 00:31:56.846 tell them as soon as Eric's team gets the base install up and
00:31:56.846 --> 00:31:59.886 running, I'm going to take him to the help center and I'm going
00:31:59.886 --> 00:32:02.831 to show them, by the way, here's your document that shows you
00:32:02.831 --> 00:32:05.871 everything that's off the shelf O the scope creep that you guys
00:32:05.871 --> 00:32:08.721 are talking about, PIP and all the stuff that we're dealing
00:32:08.721 --> 00:32:08.959 with.
00:32:08.969 --> 00:32:12.165 With, we're hoping to deal with that because the very first
00:32:12.165 --> 00:32:15.414 meeting I have with them when we do the client enablement is
00:32:15.414 --> 00:32:16.639 here's the Help center.
00:32:16.809 --> 00:32:17.879 Here's all the FAQ's.
00:32:17.889 --> 00:32:20.589 AQ's the training videos and everything, and oh by the way,
00:32:20.589 --> 00:32:23.379 here is a feature document of every single thing that you get
00:32:23.379 --> 00:32:24.819 off the shelf with your license.
00:32:24.829 --> 00:32:29.378 Your license so they can go back and read through that and have a
00:32:29.378 --> 00:32:32.549 very clean list of all the features they get.
00:32:32.719 --> 00:32:36.131 Anything outside of that they should know they're gonna be
00:32:36.131 --> 00:32:36.999 charged for so.
00:32:39.089 --> 00:32:39.349 Yeah.
00:32:39.359 --> 00:32:43.529 And if you want to if if you click on the link that's here
00:32:43.529 --> 00:32:45.579 for the collateral worksheet.
00:32:46.029 --> 00:32:48.239 This is a really important worksheet.
00:32:48.249 --> 00:32:52.568 It's it's just a Google Sheets and it's just absolutely
00:32:52.568 --> 00:32:53.879 critical content.
00:32:54.289 --> 00:32:58.243 You can see that here is what Ron's talking about with the
00:32:58.243 --> 00:33:01.863 PFS's, and so you can access those and see what we're
00:33:01.863 --> 00:33:02.399 sending.
00:33:02.409 --> 00:33:05.144 And this is something that the clients agreeing to
00:33:05.144 --> 00:33:08.522 contractually that this is what they're getting within each of
00:33:08.522 --> 00:33:09.809 the respective products.
00:33:10.279 --> 00:33:12.009 So it's within their contract.
00:33:12.019 --> 00:33:14.838 So if you're saying, you know what is included in our
00:33:14.838 --> 00:33:16.299 products, here's the answer.
00:33:16.779 --> 00:33:18.935 And back to you, Ron, if you wanted to comment on that
00:33:18.935 --> 00:33:19.249 anymore.
00:33:19.829 --> 00:33:23.202 Yeah, there are also available in the help Center so they can
00:33:23.202 --> 00:33:24.399 go to the help center.
00:33:23.399 --> 00:33:23.759 Umm.
00:33:24.409 --> 00:33:27.658 So you guys can go to the help center too if you don't remember
00:33:27.658 --> 00:33:28.419 or have access.
00:33:28.429 --> 00:33:31.946 If anybody wants access to the collateral worksheet, obviously,
00:33:31.946 --> 00:33:34.639 please send me your Gmail or your email account.
00:33:34.649 --> 00:33:36.389 I'm happy to add access to it.
00:33:36.399 --> 00:33:39.867 So you can have it, but if you go to the help center and click
00:33:39.867 --> 00:33:43.281 on it, there's a thing called feature documentation and it is
00:33:43.281 --> 00:33:46.859 the very first thing in the help center on each of the products.
00:33:46.989 --> 00:33:48.299 So they've got it.
00:33:48.309 --> 00:33:50.764 There's no way they can say I don't have access to that
00:33:50.764 --> 00:33:51.159 document.
00:33:52.129 --> 00:33:55.983 So Chris will go here and then go ahead and click on payment
00:33:55.983 --> 00:33:59.710 hub just for now and then if you look, Scroll down feature
00:33:59.710 --> 00:34:03.501 documentation and we've called it the feature spec and they
00:34:03.501 --> 00:34:07.418 click on that feature spec and up pops this document and this
00:34:07.418 --> 00:34:09.629 is what do you get out of the box.
00:34:09.639 --> 00:34:13.388 The very first page right and it talks and just literally walks
00:34:13.388 --> 00:34:16.903 them through everything that they should expect from an off
00:34:16.903 --> 00:34:17.489 the shelf.
00:34:17.499 --> 00:34:21.336 And we have these already done and posted for payment Hub
00:34:21.336 --> 00:34:23.189 CONNECT and HIPAA ecommerce.
00:34:24.219 --> 00:34:27.089 Chris and I have actually finished the final four.
00:34:27.769 --> 00:34:28.339 What did we do?
00:34:28.349 --> 00:34:33.099 We did Seth and auction hip is there auction?
00:34:29.589 --> 00:34:30.119 HIPAA.
00:34:30.409 --> 00:34:31.729 Ohh no I guess yeah.
00:34:33.929 --> 00:34:36.219 I think Kyle is still working on marketplace.
00:34:36.229 --> 00:34:37.919 So Chris and I haven't finalized that.
00:34:37.929 --> 00:34:41.595 The other two, we're just waiting for feedback and then
00:34:41.595 --> 00:34:45.915 those will be posted if somebody needs CEF or auction sooner, let
00:34:45.915 --> 00:34:46.439 me know.
00:34:46.449 --> 00:34:49.680 We'll PDF it will give it to you for use single use, but we're
00:34:49.680 --> 00:34:50.859 just waiting for final.
00:34:50.869 --> 00:34:54.127 But Chris and I've actually done the final audits of auction and
00:34:54.127 --> 00:34:54.779 Seth as well.
00:34:55.049 --> 00:34:57.459 Those can be posted as soon as I get feedback.
00:34:58.949 --> 00:34:59.449 Awesome.
00:34:59.589 --> 00:34:59.939 OK.
00:34:59.949 --> 00:35:00.479 Thanks, Ron.
00:35:00.489 --> 00:35:04.188 That was really helpful if anyone else has any comments,
00:35:04.188 --> 00:35:08.212 feel free to post them into the chat and just we'll just keep
00:35:08.212 --> 00:35:10.159 keep the the party going here.
00:35:11.009 --> 00:35:14.928 And with that in mind, I'll send it over to you, Sir Ganoe, if
00:35:14.928 --> 00:35:17.789 you're ready to go unintentional rhyme there.
00:35:18.909 --> 00:35:20.139 Yeah, baby.
00:35:24.189 --> 00:35:26.539 Of course, of course.
00:35:26.889 --> 00:35:34.359 So let me just pop up, talk about some marketing goodness.
00:35:34.369 --> 00:35:39.454 I know everybody's so jazzed to hear about that was joke anyway,
00:35:39.449 --> 00:35:40.429 I'm just hear about it.
00:35:39.454 --> 00:35:39.689 so.
00:35:40.059 --> 00:35:41.999 Boo marketing, yeah.
00:35:41.279 --> 00:35:42.039 Well, I know you are.
00:35:43.589 --> 00:35:44.059 Woo.
00:35:43.929 --> 00:35:44.589 So yeah.
00:35:44.649 --> 00:35:47.249 No, we'll get into some marketing stuff is actually
00:35:47.249 --> 00:35:49.049 pretty pretty neat things going on.
00:35:49.059 --> 00:35:51.891 I'm gonna focus on just kind of a a few things that are that are
00:35:51.891 --> 00:35:53.459 happening that are pretty exciting.
00:35:53.469 --> 00:35:57.969 But I do just wanna start by saying happy holidays to
00:35:57.969 --> 00:35:58.719 everyone.
00:35:59.509 --> 00:36:03.059 I really hope you have a wonderful break.
00:36:03.389 --> 00:36:08.298 I know we're headed into a very deserved break for everyone and
00:36:08.298 --> 00:36:11.979 you know, as as a team that runs lean and mean.
00:36:11.989 --> 00:36:14.336 I know everybody's putting their heart and soul in this business
00:36:14.336 --> 00:36:14.769 and it just.
00:36:15.759 --> 00:36:19.021 I just wanna say how much I appreciate it and definitely
00:36:19.021 --> 00:36:22.169 seeing if that's of it, that dedication this year that
00:36:22.169 --> 00:36:24.229 everybody's put into this business.
00:36:24.239 --> 00:36:27.849 So I'm very excited to see what we're gonna do in 2024.
00:36:28.459 --> 00:36:32.419 And with that said, let's get into some marketing so.
00:36:34.579 --> 00:36:39.559 One of the you know, just there's some things going on
00:36:39.559 --> 00:36:45.173 that's kind of interesting that is fundamentally changing the
00:36:45.173 --> 00:36:50.515 lifeblood of our business, which is our website and Google
00:36:50.515 --> 00:36:51.149 search.
00:36:51.949 --> 00:36:52.469 Umm.
00:36:52.479 --> 00:36:58.537 I'm not sure if everybody's aware, but our business truly
00:36:58.537 --> 00:37:00.939 runs because of Google.
00:37:01.609 --> 00:37:04.519 So we rely on it heavily.
00:37:05.029 --> 00:37:10.266 Most of our leads come in that way and so organic search is
00:37:10.266 --> 00:37:14.369 really predominantly what drives our business.
00:37:14.559 --> 00:37:18.570 And there's some key things that are changing right now with
00:37:18.570 --> 00:37:18.899 that.
00:37:18.909 --> 00:37:22.890 And so I just thought we'd kind of talk to that and where we set
00:37:22.890 --> 00:37:26.565 in some of you might already know this is going on and have
00:37:26.565 --> 00:37:30.424 questions like Phil, what are you doing and your team to to to
00:37:30.424 --> 00:37:31.649 go after this stuff.
00:37:31.659 --> 00:37:32.459 So let's talk about that.
00:37:33.319 --> 00:37:37.482 Umm, one of the big changes that's happening right now I've,
00:37:37.482 --> 00:37:41.849 which probably a lot of you know about, but you know, Google is
00:37:41.849 --> 00:37:46.012 changing how they display their results and there's now what
00:37:46.012 --> 00:37:50.311 they're calling their the Google search generative experience,
00:37:50.311 --> 00:37:54.406 which is their new AI powered search experience that places
00:37:54.406 --> 00:37:58.296 like, you know, helpful information when you do a Google
00:37:58.296 --> 00:38:02.663 search, right and it's right on the top areas got a pretty good
00:38:02.663 --> 00:38:06.690 size real estate that that that's gonna be on the top fold
00:38:06.690 --> 00:38:10.989 of the page and this is really continuing to expand with them.
00:38:11.169 --> 00:38:15.382 It's going to become more predominant, certainly over the
00:38:15.382 --> 00:38:19.959 next year and this will change some things in the game of SEO.
00:38:19.969 --> 00:38:25.402 It's really going to be a big change and as you can imagine,
00:38:25.402 --> 00:38:31.102 being served up information to respond to your searches in that
00:38:31.102 --> 00:38:36.623 top real estate through the AI response is is really going to
00:38:36.623 --> 00:38:41.700 start to make just, you know, really the top few trusted
00:38:41.700 --> 00:38:46.509 results for that search to be used for that response.
00:38:46.749 --> 00:38:52.055 And so what's gonna end up happening is, umm, you know, how
00:38:52.055 --> 00:38:55.239 are you going to compete with that?
00:38:55.629 --> 00:38:59.222 And so one of the big things of course is going to be the
00:38:59.222 --> 00:39:00.399 quality of content.
00:39:00.749 --> 00:39:06.180 So you know a big thing that's been happening since AI started
00:39:06.180 --> 00:39:11.524 coming onto the scene is lots of people that are just writing
00:39:11.524 --> 00:39:17.213 poorly made AI articles and just spraying them out for speed sake
00:39:17.213 --> 00:39:17.989 and ease.
00:39:18.649 --> 00:39:22.258 Uhm, to try to get, you know, topical authority, which is of
00:39:22.258 --> 00:39:25.985 course very important to Google, that you are a trusted source
00:39:25.985 --> 00:39:29.239 and that you know that topic and have authority on it.
00:39:30.149 --> 00:39:34.968 So for us, what we're trying to do is continue to make sure that
00:39:34.968 --> 00:39:39.490 we're going to have that content and that quality of content
00:39:39.490 --> 00:39:44.012 which our team works very hard to do and we're going to make
00:39:44.012 --> 00:39:48.089 sure that we have to be a trusted source on the topic.
00:39:48.679 --> 00:39:52.788 And if possible, you really wanna have it kind of in a niche
00:39:52.788 --> 00:39:55.549 and that's really going to be important.
00:39:55.999 --> 00:39:59.766 Well, luckily, clarity owns several niches, and so our
00:39:59.766 --> 00:40:03.944 marketing team does already produce high quality content and
00:40:03.944 --> 00:40:07.985 it has allowed us to gain topical authority with Google on
00:40:07.985 --> 00:40:09.629 several of these niches.
00:40:09.639 --> 00:40:12.629 So that is a very good thing for us.
00:40:12.689 --> 00:40:15.859 Another piece of it is the core web vitals.
00:40:15.869 --> 00:40:20.254 They're making a big change there where they're going to
00:40:20.254 --> 00:40:24.870 start going away from what they call F ID, which is a first
00:40:24.870 --> 00:40:29.178 input delay and over to interaction and X paint iimp as
00:40:29.178 --> 00:40:31.409 their core web vitals metric.
00:40:31.859 --> 00:40:36.407 Really, the difference there is that fid only measures the
00:40:36.407 --> 00:40:41.032 initial processing delay on a page where I amp measures the
00:40:41.032 --> 00:40:45.041 full amount of time between a user input and the UI
00:40:45.041 --> 00:40:45.889 responding.
00:40:46.099 --> 00:40:51.178 So that is meaning where fid only say as is going to count
00:40:51.178 --> 00:40:54.449 the first user interaction on a page.
00:40:54.719 --> 00:40:58.892 The IMP is generally gonna measure the worst input delay on
00:40:58.892 --> 00:41:02.579 a page the entire time you're you're going about it.
00:41:02.589 --> 00:41:06.769 So this means that we're gonna have to be running a streamline
00:41:06.769 --> 00:41:10.816 code deploying a newly designed website that's utilizing the
00:41:10.816 --> 00:41:14.797 latest technology and making sure we're optimized as we can
00:41:14.797 --> 00:41:16.389 possibly be in our site.
00:41:16.399 --> 00:41:20.441 Pages are gonna have to be responsive and provide visual
00:41:20.441 --> 00:41:24.909 feedback really quickly after a user performs an action and so
00:41:24.909 --> 00:41:29.377 well it just so happens we are in the middle of a redesign and
00:41:29.377 --> 00:41:33.704 we are going to be doing just that as part of that redesign,
00:41:33.704 --> 00:41:38.101 we will also be deploying our own CMS, which Chris decided he
00:41:38.101 --> 00:41:42.498 wanted to move away from like a third party CMS that tends to
00:41:42.498 --> 00:41:46.966 have commonly a lot of bloat in it and that's not good for you
00:41:46.966 --> 00:41:50.299 know, obviously page speed and responsiveness.
00:41:50.609 --> 00:41:56.696 So we are and this is going to be with a great amount of help
00:41:56.696 --> 00:42:03.175 from marketing and in particular the development of this is is uh
00:42:03.175 --> 00:42:08.869 is really being built out by my boy Alex for a lot of it.
00:42:08.979 --> 00:42:12.329 So appreciate you, Alex, and everything that you do in there.
00:42:12.379 --> 00:42:15.893 Autumn is also jumping in and helping you know the hate to
00:42:15.893 --> 00:42:19.645 like the UI wise to make sure that we're putting the best foot
00:42:19.645 --> 00:42:20.479 forward there.
00:42:21.499 --> 00:42:27.397 Uh for the marketing team, so to just continue on with that, that
00:42:27.397 --> 00:42:33.207 you know the the thing with the new CMS is you know we're really
00:42:33.207 --> 00:42:35.709 trying to improve that page.
00:42:35.719 --> 00:42:39.971 Let's be the responsiveness and just overall optimization there
00:42:39.971 --> 00:42:43.825 and then on the just the side benefit is going to be that
00:42:43.825 --> 00:42:47.679 since we can make the CMS do what we want to do in the UI
00:42:47.679 --> 00:42:52.064 will perform our marketing team, being able to deploy new content
00:42:52.064 --> 00:42:56.250 could be more streamlined, which DNN that we previously had or
00:42:56.250 --> 00:42:59.970 using right now not the most user friendly thing in the
00:42:59.970 --> 00:43:00.369 world.
00:43:00.379 --> 00:43:03.689 So and it does have some kind of issues, you gotta work around.
00:43:03.699 --> 00:43:05.809 It's naturally so.
00:43:05.819 --> 00:43:09.682 It hasn't been great, so this is going to be very good for us and
00:43:09.682 --> 00:43:12.199 something that we're going to be changing.
00:43:13.549 --> 00:43:19.021 Obviously one of the things that's happening with, you know,
00:43:19.021 --> 00:43:24.673 changes that we're seeing here is another area which they call
00:43:24.673 --> 00:43:30.504 8 and it stands for experience, expertise, authoritativeness and
00:43:30.504 --> 00:43:31.939 trustworthiness.
00:43:32.309 --> 00:43:36.321 When is what Google does to evaluate the quality of our
00:43:36.321 --> 00:43:36.679 site?
00:43:37.389 --> 00:43:40.839 The good thing about this is we're completely redesigning.
00:43:41.009 --> 00:43:41.599 We're gonna.
00:43:41.609 --> 00:43:47.212 We're going to bring in just a polished branding to the site
00:43:47.212 --> 00:43:47.579 now.
00:43:47.589 --> 00:43:51.269 That's really just going to be great cohesive.
00:43:51.339 --> 00:43:54.195 It's not like you're gonna go to one section or another section,
00:43:54.195 --> 00:43:55.469 and it's like changes on you.
00:43:55.479 --> 00:43:59.282 So you know the experience a little different, which is kind
00:43:59.282 --> 00:44:00.529 of what we have now.
00:44:00.579 --> 00:44:05.401 We have done a lot of updates in the marketing team and Alex
00:44:05.401 --> 00:44:10.145 really have done a great job of bringing the site just more
00:44:10.145 --> 00:44:12.279 polished and more polished.
00:44:12.289 --> 00:44:17.699 But moving into this new design, we're going to definitely see
00:44:17.699 --> 00:44:23.024 some some good stuff there, and that is going to help us with
00:44:23.024 --> 00:44:27.919 the eat that Google ranks and is really been showing us.
00:44:27.929 --> 00:44:32.546 Love, you know, for for what they when they've done there in
00:44:32.546 --> 00:44:35.649 the changes that we'll see in that area.
00:44:36.059 --> 00:44:40.359 But other than that we I just kind of wanted to give you guys
00:44:40.359 --> 00:44:44.382 a sneak peek at some of the branding that's happening and
00:44:44.382 --> 00:44:47.989 show you guys a little about what's going on there.
00:44:48.229 --> 00:44:52.119 But here on the left side you can see this is 1.
00:44:52.129 --> 00:44:57.614 This is basically the top fold of the home page and you can see
00:44:57.614 --> 00:45:00.099 kind of the difference there.
00:45:00.379 --> 00:45:05.169 Umm, again it's more polished this.
00:45:05.179 --> 00:45:09.466 This kind of Polish is what's going to be seeing now across
00:45:09.466 --> 00:45:10.109 the site.
00:45:10.279 --> 00:45:14.109 And the nice thing is, it's also going to have, you know, all the
00:45:14.109 --> 00:45:17.650 pages like right here where you're seeing the, you know, the
00:45:17.650 --> 00:45:19.449 B to B to C payment processing.
00:45:19.519 --> 00:45:23.083 These are all gonna have really polished landing pages and
00:45:23.083 --> 00:45:25.379 experiences that are all cohesive in.
00:45:25.389 --> 00:45:29.894 They're just all gonna to nicely work with each other, so it's
00:45:29.894 --> 00:45:32.039 really going to be impressive.
00:45:32.549 --> 00:45:33.959 What will be seen there?
00:45:34.969 --> 00:45:39.399 Another thing that we're really upgrading is the the menu.
00:45:39.799 --> 00:45:44.101 So as you can see with the new menu here on the left and the
00:45:44.101 --> 00:45:48.050 old menu here on the right, I don't think I have to say
00:45:48.050 --> 00:45:49.249 anything on that.
00:45:49.339 --> 00:45:53.413 And I will tell you the the the menus on the right actually have
00:45:53.413 --> 00:45:57.049 been improved through the marketing team and Alex's work.
00:45:57.059 --> 00:46:02.276 So it's, but what we're getting ready to move to is going to be
00:46:02.276 --> 00:46:07.168 very nice, not only for the Polish level, but just the user
00:46:07.168 --> 00:46:11.651 experience in general and being able to quickly access
00:46:11.651 --> 00:46:16.135 information that's just very simple to do is obviously
00:46:16.135 --> 00:46:18.499 another a great part of this.
00:46:18.509 --> 00:46:19.219 What we're seeing here?
00:46:21.209 --> 00:46:23.349 You know you can see just kind of some other sections.
00:46:23.359 --> 00:46:27.737 Here's a change, the new one being on the left again, old one
00:46:27.737 --> 00:46:29.079 being on the right.
00:46:29.599 --> 00:46:33.053 You can see kind of the Polish that we're adding in there,
00:46:33.053 --> 00:46:36.684 making it a little easier to, you know, do some filtering and
00:46:36.684 --> 00:46:37.679 things like that.
00:46:38.089 --> 00:46:39.879 So this is really nice.
00:46:40.689 --> 00:46:45.219 Here's just say one of the other product pages.
00:46:45.449 --> 00:46:49.733 What we call a commonly championed pages, and this you
00:46:49.733 --> 00:46:54.563 can see from the left the new design and on the right the old
00:46:54.563 --> 00:46:58.769 design definitely is going to be a bit more polished.
00:46:59.689 --> 00:47:00.279 Umm.
00:47:00.829 --> 00:47:05.996 In, in really loving what's going to be happening there.
00:47:05.996 --> 00:47:06.359 But.
00:47:08.859 --> 00:47:15.237 The just to kind of wrap up on on this part of it, you know,
00:47:15.237 --> 00:47:20.778 being that we're going to be bringing in like a very
00:47:20.778 --> 00:47:27.574 optimized site and which Google is about to make a big update to
00:47:27.574 --> 00:47:28.829 the metrics.
00:47:29.039 --> 00:47:32.867 If you're not on board and you're not running your site
00:47:32.867 --> 00:47:36.079 efficiently, ah, that's going to be a problem.
00:47:36.339 --> 00:47:38.229 And you're gonna you're gonna get.
00:47:38.439 --> 00:47:42.865 You're gonna see it in the rankings, so we're going to look
00:47:42.865 --> 00:47:47.069 to deploy this, which they're going to be changing their
00:47:47.069 --> 00:47:48.839 matrix in March of 2024.
00:47:49.649 --> 00:47:56.059 So we're going to be dropping this new site optimized site.
00:47:56.219 --> 00:47:59.428 We're gonna most certainly be seeing some very good
00:47:59.428 --> 00:48:01.279 responsiveness and site speed.
00:48:01.689 --> 00:48:06.162 We're going to have a better user experience with the site
00:48:06.162 --> 00:48:10.560 and and just really just improved UX and I'm very excited
00:48:10.560 --> 00:48:13.289 about what we're going to do there.
00:48:13.679 --> 00:48:17.965 And then as far as just being able to continue and just some
00:48:17.965 --> 00:48:22.180 of the work autumn, did some some work on some of our pages
00:48:22.180 --> 00:48:25.904 where she went in and specifically optimized some of
00:48:25.904 --> 00:48:29.909 our top pages that get hit and so she, you know, kind of
00:48:29.909 --> 00:48:34.265 cleaned it up, took some of the bloat out and really got that
00:48:34.265 --> 00:48:38.621 performing better, those pages performing better when she did
00:48:38.621 --> 00:48:40.729 that, they shot up in ranking.
00:48:41.109 --> 00:48:44.784 So if you could only imagine what the whole doing that to the
00:48:44.784 --> 00:48:48.341 entire site is going to do for us, not to mention we're not
00:48:48.341 --> 00:48:51.602 even talking about the conversions that could possibly
00:48:51.602 --> 00:48:55.455 see an increase just because of the better you access that we're
00:48:55.455 --> 00:48:56.759 going to have on this.
00:48:56.949 --> 00:49:01.284 It's pretty exciting and if you can see what we've done this
00:49:01.284 --> 00:49:05.762 year, we've more than tripled our traffic on the site from the
00:49:05.762 --> 00:49:06.899 from a year ago.
00:49:07.129 --> 00:49:10.247 And so it's, you can see Google's already loving what
00:49:10.247 --> 00:49:13.539 we're doing and the marketing team is doing a great job.
00:49:13.579 --> 00:49:15.199 There's a lot of goodness going on.
00:49:15.329 --> 00:49:20.165 I'm very excited for what can happen now and we actually
00:49:20.165 --> 00:49:24.578 deploy this new website and really have this better
00:49:24.578 --> 00:49:26.699 experience for the users.
00:49:26.709 --> 00:49:29.639 So anyway, that's what I have there.
00:49:32.809 --> 00:49:33.569 Any questions?
00:49:33.189 --> 00:49:33.499 Ask.
00:49:40.739 --> 00:49:42.069 Yeah, I put you all to sleep.
00:49:42.079 --> 00:49:42.439 I'm sorry.
00:49:44.779 --> 00:49:46.989 Yeah, it's it's hard not to fall asleep with.
00:49:46.999 --> 00:49:49.339 Uh, tripling the site traffic in the air.
00:49:49.379 --> 00:49:50.359 Good job, guys.
00:49:50.439 --> 00:49:51.109 That's exciting.
00:49:52.329 --> 00:49:55.359 Yeah, kudos, Phil, and to the marketing team.
00:49:52.929 --> 00:49:53.059 OK.
00:49:55.369 --> 00:49:56.959 Overall, great job everyone.
00:49:57.069 --> 00:50:00.717 And yeah, I I think you know this is kind of plays into the
00:50:00.717 --> 00:50:04.365 talk that Eric's gonna give around the products with taking
00:50:04.365 --> 00:50:07.892 this marketing momentum and really making sure that we're
00:50:07.892 --> 00:50:09.959 executing on it with the product.
00:50:09.969 --> 00:50:12.943 So if you're a ready, Sir weathers, we'll turn it over to
00:50:12.943 --> 00:50:13.969 you to take it away.
00:50:16.309 --> 00:50:17.299 Yeah, sounds good.
00:50:17.849 --> 00:50:19.349 Let me see here real quick.
00:50:20.489 --> 00:50:21.419 We just a second.
00:50:21.929 --> 00:50:22.379 Sorry I'm.
00:50:23.109 --> 00:50:23.399 Yeah.
00:50:23.409 --> 00:50:23.879 Take your time.
00:50:25.249 --> 00:50:25.519 Umm.
00:50:25.529 --> 00:50:29.918 And just while Eric's getting the screen pulled up there, you
00:50:29.918 --> 00:50:34.236 know, one of the things that we're looking to do is take the
00:50:34.236 --> 00:50:38.342 same architecture approach that we've had with our client
00:50:38.342 --> 00:50:42.164 projects and apply that to clarity labs and basically
00:50:42.164 --> 00:50:45.279 allocate the resources with detailed plans.
00:50:45.739 --> 00:50:47.409 Umm, so OK, I see your screen.
00:50:47.419 --> 00:50:48.279 Over to you, Sir weathers.
00:50:48.169 --> 00:50:48.579 Cool.
00:50:48.729 --> 00:50:49.009 Yeah.
00:50:49.019 --> 00:50:52.881 So some of the the first part of this visuals ultimately gonna be
00:50:52.881 --> 00:50:56.685 kind of going through the, umm, the screens that I shared at the
00:50:56.685 --> 00:50:57.329 last event.
00:50:57.339 --> 00:51:00.174 I know not everyone was at that event, so some of those will be
00:51:00.174 --> 00:51:02.389 for the first time, but kind of a recap of those.
00:51:02.399 --> 00:51:05.428 We've done a lot that we're kind of on the road map, what we've
00:51:05.428 --> 00:51:08.221 done in the past two months is kind of been incredible and
00:51:08.221 --> 00:51:10.919 we'll kind of talk about how that happened and what not.
00:51:10.929 --> 00:51:14.527 So the first of all kind of the high level pieces that we've
00:51:14.527 --> 00:51:18.301 been kind of pushing towards our obviously the React admin kind
00:51:18.301 --> 00:51:21.899 of goes in line with the store dot store slash doctor admin.
00:51:22.509 --> 00:51:25.289 Umm, we've been working on that with ever.
00:51:25.209 --> 00:51:28.588 Hey, sorry I was in my presentation when you guys were
00:51:28.588 --> 00:51:29.079 calling.
00:51:29.089 --> 00:51:29.589 What's going on?
00:51:31.529 --> 00:51:32.139 So what you.
00:51:34.139 --> 00:51:34.919 I got him.
00:51:35.509 --> 00:51:40.599 So we've been working on that with ever Valhalla and I believe
00:51:37.739 --> 00:51:37.929 Thanks.
00:51:40.599 --> 00:51:41.649 one one more.
00:51:41.659 --> 00:51:43.804 But ultimately, James has been doing a lot of work to bring
00:51:43.804 --> 00:51:44.269 that back in.
00:51:44.359 --> 00:51:47.738 There were a handful of people that started doing a lot of work
00:51:47.738 --> 00:51:49.269 on that and know Jesse David.
00:51:49.899 --> 00:51:52.789 Michael, I apologize if I left anyone out.
00:51:52.799 --> 00:51:54.539 Please, please post them in the chat.
00:51:54.719 --> 00:51:56.349 That was kind of hammering on that.
00:51:56.359 --> 00:51:59.829 It's starting to look fantastic and there's a lot there.
00:51:59.919 --> 00:52:04.224 Our goal is to kind of get that react admin up into basically
00:52:04.224 --> 00:52:06.029 remove what we're calling.
00:52:06.039 --> 00:52:11.115 What I'm kind of calling legacy and which is the injs admin
00:52:11.115 --> 00:52:16.107 potentially with the first set of projects that will be on
00:52:16.107 --> 00:52:16.699 2024.2.
00:52:16.929 --> 00:52:21.558 With that release, we will phase out use of injs similar to what
00:52:21.558 --> 00:52:24.549 we did when we brought in the storefront.
00:52:24.559 --> 00:52:24.829 React.
00:52:25.799 --> 00:52:27.649 Uh, where we just said, OK, we're gonna do it.
00:52:27.659 --> 00:52:28.329 And here we go.
00:52:29.199 --> 00:52:31.743 So there's there's quite a bit of feature parity that we need
00:52:31.743 --> 00:52:34.204 to pull over into that, but there's a lot of momentum on it
00:52:34.204 --> 00:52:36.789 with the client projects that we're working on and making sure
00:52:36.789 --> 00:52:37.979 that's coming back into core.
00:52:37.989 --> 00:52:40.556 There's a lot of logistics around there, so appreciate
00:52:40.556 --> 00:52:43.449 everybody who's been working on that, the seller marketplace.
00:52:43.639 --> 00:52:46.439 We have a lot of the auction marketplace brought in.
00:52:46.579 --> 00:52:50.121 Jewel was a obviously big for that and preciate your body
00:52:50.121 --> 00:52:51.159 working on Jewel?
00:52:52.419 --> 00:52:56.793 There are tickets to bring a lot of that work back into core for
00:52:56.793 --> 00:53:00.293 fixes from the seller marketplace, so that's really
00:53:00.293 --> 00:53:00.629 good.
00:53:00.639 --> 00:53:02.149 I'll kind of go into a couple more of those.
00:53:02.159 --> 00:53:06.077 Here, as these feature slides, the HIPAA feature set, there's
00:53:06.077 --> 00:53:09.679 so much work going in there with scheduling lab results.
00:53:10.279 --> 00:53:13.252 Uhm, I know I'm missing missing a couple other big ones
00:53:13.252 --> 00:53:15.429 prescriptions that we're working on for.
00:53:15.509 --> 00:53:19.429 Umm for core as well as that will go into the client base.
00:53:19.439 --> 00:53:23.153 So a lot of HIPAA feature sets there starting to get built out,
00:53:23.153 --> 00:53:26.983 both in tandem with the with the project as well as core and then
00:53:26.983 --> 00:53:30.059 just general ecommerce updates and things like that.
00:53:30.169 --> 00:53:32.999 So we'll kind of go into a couple slides here.
00:53:33.569 --> 00:53:36.139 So the HIPAA feature set, these are still some of these things
00:53:36.139 --> 00:53:37.199 are still on the road map.
00:53:37.209 --> 00:53:40.907 Telehealth still on the road map and I'll show the show the core
00:53:40.907 --> 00:53:44.548 backlog BRD here shortly just to kind of show just a high level
00:53:44.548 --> 00:53:45.629 of what's in there.
00:53:47.259 --> 00:53:50.394 Prescription management that is getting built out, I believe for
00:53:50.394 --> 00:53:52.709 AUI, obviously that's a slightly older version.
00:53:52.719 --> 00:53:55.959 So we'll have a little bit more work to merge that back into
00:53:55.959 --> 00:53:58.933 core once it comes in, but prescription management will
00:53:58.933 --> 00:54:01.589 ultimately be worked on across a couple projects.
00:54:01.599 --> 00:54:05.199 I know one of them say UI Valhalla, New Hope et cetera.
00:54:05.209 --> 00:54:06.489 So we'll work on there.
00:54:06.499 --> 00:54:07.849 Same with the pharmacy integration.
00:54:07.859 --> 00:54:11.716 Obviously with Valhalla doing some doing some integration with
00:54:11.716 --> 00:54:15.328 them and then the pharmacist management, now that one is a
00:54:15.328 --> 00:54:18.634 little more, we're kind of accomplishing the pharmacy
00:54:18.634 --> 00:54:22.368 things through more CSRS rather than a true pharmacist being
00:54:22.368 --> 00:54:25.919 able to log in and manage their their umm, prescriptions.
00:54:25.929 --> 00:54:29.622 So uh, that's still on the still in the backlog, but UM medical
00:54:29.622 --> 00:54:32.969 intake forms, I know several people have worked on those.
00:54:32.979 --> 00:54:36.209 Jesse did a handful of the work along the questionnaire and
00:54:36.209 --> 00:54:39.654 being able to put that into the cart, we've worked on that with
00:54:39.654 --> 00:54:40.139 New Hope.
00:54:40.149 --> 00:54:44.336 I believe Valhalla also has some medical intake forms, so that's
00:54:44.336 --> 00:54:47.749 great work there that came originally from some RX I
00:54:47.749 --> 00:54:50.519 believe RX1 questionnaire back in the day.
00:54:50.529 --> 00:54:53.579 So great work there, Doctor Dashboard.
00:54:53.589 --> 00:54:57.013 So again, coming going back to the React admin, we do have I
00:54:57.013 --> 00:55:00.548 think New Hope is using doctors in the storefront to review as
00:55:00.548 --> 00:55:00.829 well.
00:55:00.839 --> 00:55:04.050 So there's some kind of two places where those may happen,
00:55:04.050 --> 00:55:07.425 depending on the use case and then esign is also still in the
00:55:07.425 --> 00:55:08.949 backlog auction feature set.
00:55:09.159 --> 00:55:13.896 So we do have the out of the some more simple out of box
00:55:13.896 --> 00:55:19.049 bidding in the on the road map we've defined what the current
00:55:19.049 --> 00:55:21.709 out of box bidding is for jewel.
00:55:21.879 --> 00:55:24.139 And I believe that that got streamlined a little bit.
00:55:24.149 --> 00:55:24.699 There were some.
00:55:24.709 --> 00:55:27.628 There were some issues, some bug fixes as far as reserve pricing
00:55:27.628 --> 00:55:29.559 and things like that, that that got fixed.
00:55:29.569 --> 00:55:30.459 So that's great.
00:55:31.159 --> 00:55:32.209 I'm sorry.
00:55:32.219 --> 00:55:32.939 Close my door real quick.
00:55:37.819 --> 00:55:39.319 Marketplace seller auction management.
00:55:39.329 --> 00:55:42.614 Again, most of this stuff is going to be pretty, pretty well
00:55:42.614 --> 00:55:45.845 fixed on Joule as they've gone live and it all looks pretty
00:55:45.845 --> 00:55:46.599 good in there.
00:55:46.609 --> 00:55:49.086 So that's going to come back into core from Jewel and
00:55:49.086 --> 00:55:51.379 obviously we'll continue to make updates to that.
00:55:52.449 --> 00:55:53.099 Uh, lot.
00:55:53.109 --> 00:55:54.339 Closed options?
00:55:54.429 --> 00:55:55.679 UMI believe again.
00:55:55.689 --> 00:55:58.352 Same thing which you'll where we've, we've, you know,
00:55:58.352 --> 00:56:01.213 potentially added, you know shipping after the fact based
00:56:01.213 --> 00:56:04.074 off of the designation by the seller of what the shipping
00:56:04.074 --> 00:56:05.159 options are et cetera.
00:56:05.169 --> 00:56:08.762 So, and then a lot catalog card updates and I have I have a
00:56:08.762 --> 00:56:10.379 screen that will show that.
00:56:10.389 --> 00:56:11.489 So we'll kind of get into that.
00:56:11.679 --> 00:56:14.029 There's just a high level of the images there.
00:56:16.159 --> 00:56:18.612 Some of these are now these are from the HIPAA deck that will
00:56:18.612 --> 00:56:18.889 design.
00:56:19.099 --> 00:56:21.903 Obviously, as we brought them into core and then into the the
00:56:21.903 --> 00:56:24.436 project that they're actually going into, they may have
00:56:24.436 --> 00:56:27.286 changed differently to styling may not be perfect, but you can
00:56:27.286 --> 00:56:30.135 kind of see a high level of of what those kind of are supposed
00:56:30.135 --> 00:56:32.849 to be looking like and and the different features in there.
00:56:35.189 --> 00:56:36.679 Same thing with the auction feature set.
00:56:36.689 --> 00:56:39.959 So here we've kind of have a an auction.
00:56:39.969 --> 00:56:43.315 What I've kind of coined an auction action widget here with
00:56:43.315 --> 00:56:46.159 the current bid and the buy now and the place bid.
00:56:46.169 --> 00:56:51.669 You can see the reserve not met and it's not on here.
00:56:51.979 --> 00:56:53.269 But you've I'm sure you've seen it.
00:56:53.279 --> 00:56:56.286 If you've seen Jewel, where we have a very, very in your face,
00:56:56.286 --> 00:56:59.150 this lot is closed banner that kind of hides all of that to
00:56:59.150 --> 00:57:00.009 make it an active.
00:57:00.019 --> 00:57:04.225 So it's very up front as far as what what's in the auction or
00:57:04.225 --> 00:57:06.599 whether or not it's active or not.
00:57:08.219 --> 00:57:08.509 Uh.
00:57:08.519 --> 00:57:09.529 Going to seller marketplace.
00:57:09.539 --> 00:57:10.989 Same thing with Jewel here.
00:57:11.109 --> 00:57:13.989 Umm, I know that that form was improved over time.
00:57:14.329 --> 00:57:16.886 Uh, there's still a lot of iterations that we have in the
00:57:16.886 --> 00:57:19.619 backlog that will want to do for it, but there's a lot of the
00:57:19.619 --> 00:57:22.352 seller marketplace stuff brought forward from 10 when ten was
00:57:22.352 --> 00:57:22.969 working on it.
00:57:22.979 --> 00:57:26.610 And then obviously in July and then just high level on the
00:57:26.610 --> 00:57:30.550 React Admin, I know a lot more has gone into this, some of this
00:57:30.550 --> 00:57:30.919 stuff.
00:57:30.929 --> 00:57:35.063 Does some of this stuff is kind of ever specific, obviously, but
00:57:35.063 --> 00:57:38.879 it obviously looks with the reporting and things like that.
00:57:38.889 --> 00:57:41.889 And I know, David, I believe has done quite a bit of build out of
00:57:41.889 --> 00:57:44.572 the reports and ever and those are starting to look really
00:57:44.572 --> 00:57:44.799 good.
00:57:44.809 --> 00:57:48.432 So I'm excited for the React admin as it continues to move
00:57:48.432 --> 00:57:50.889 forward and then some quick notes here.
00:57:50.899 --> 00:57:54.951 So this is kind of what Chris was alluding to earlier and how
00:57:54.951 --> 00:57:59.133 we're actually building out core because obviously when we when
00:57:59.133 --> 00:58:03.119 we build for a client project, we get paid for the for those
00:58:03.119 --> 00:58:03.969 hours, right?
00:58:03.979 --> 00:58:07.106 So on the core core platform, you know that that has to come
00:58:07.106 --> 00:58:10.131 from somewhere since we, you know, we we bootstrapped this
00:58:10.131 --> 00:58:12.489 business that you know we have to pay for it.
00:58:12.499 --> 00:58:16.533 So a lot of that we're we're kind of doing in collaboration
00:58:16.533 --> 00:58:16.869 with.
00:58:16.879 --> 00:58:19.976 So, for example, we're subsidizing some base level
00:58:19.976 --> 00:58:23.984 features for core, building them in core because we needed, we'll
00:58:23.984 --> 00:58:26.959 need to build them with into the client as well.
00:58:26.969 --> 00:58:30.024 And depending on the client and what their expectations were,
00:58:30.024 --> 00:58:33.029 sometimes they will foot the bill for that because they were
00:58:33.029 --> 00:58:34.359 expecting it to be net new.
00:58:34.369 --> 00:58:37.897 Sometimes we will, and sometimes it's about a 5050 or somewhere
00:58:37.897 --> 00:58:38.999 anywhere in between.
00:58:39.169 --> 00:58:42.573 As far as building up that core feature and then they have
00:58:42.573 --> 00:58:46.150 customizations on top of that, lab results is a great one for
00:58:46.150 --> 00:58:46.439 that.
00:58:46.449 --> 00:58:50.057 For lab works, Jesse and Brendan just got finished doing the
00:58:50.057 --> 00:58:51.299 development for that.
00:58:51.309 --> 00:58:53.209 Justin did a great job in the architecture for it.
00:58:54.039 --> 00:58:55.129 Umm scheduling.
00:58:55.899 --> 00:58:58.855 I know that that one has gone into a couple projects and and I
00:58:58.855 --> 00:59:01.669 appreciate everybody who was working on getting that passed
00:59:01.669 --> 00:59:04.109 around between core and all the different projects.
00:59:04.439 --> 00:59:07.368 We have some tickets in to bring all of those fixes back in, so
00:59:07.368 --> 00:59:10.068 whoever that gets assigned to, I appreciate you doing that
00:59:10.068 --> 00:59:13.043 because that's going to be it's going to be an interesting merge
00:59:13.043 --> 00:59:13.729 back into core.
00:59:13.829 --> 00:59:16.152 And then obviously the seller marketplace talked about that a
00:59:16.152 --> 00:59:16.639 handful time.
00:59:16.649 --> 00:59:20.100 So those are some of the examples, ones that are coming
00:59:20.100 --> 00:59:23.613 up in the future that I know we're talking about are the
00:59:23.613 --> 00:59:25.339 variant and add on products.
00:59:25.749 --> 00:59:28.349 Umm, that were originally done for rydel.
00:59:29.599 --> 00:59:32.938 We're looking at generalizing those simplifying, basically
00:59:32.938 --> 00:59:35.089 learning from how we did it in rydel.
00:59:35.099 --> 00:59:36.389 How do we want to do it in core?
00:59:36.399 --> 00:59:38.929 So that's going to be exciting to bring that in, make that
00:59:38.929 --> 00:59:39.529 fully dynamic.
00:59:39.539 --> 00:59:44.417 Just fully data driven so that we don't have to build out
00:59:44.417 --> 00:59:46.099 custom UIS for that.
00:59:46.109 --> 00:59:46.809 I'm sure we will.
00:59:46.819 --> 00:59:50.591 For other clients, they're gonna want something different, but
00:59:50.591 --> 00:59:54.303 we'll be able to do that again out of box for the variant and
00:59:54.303 --> 00:59:56.339 add on architecture for products.
00:59:56.349 --> 00:59:57.059 So that's good.
00:59:57.069 --> 00:59:58.949 We'll then we'll kind of see that in the backlog as well.
00:59:59.789 --> 01:00:03.582 And then one of the things Chris was talking about is the clarity
01:00:03.582 --> 01:00:07.375 labs, two of the ones that Chris show off to remind me if there's
01:00:07.375 --> 01:00:10.881 another one that I'm missing that I know are happening are a
01:00:10.881 --> 01:00:14.444 Phoenix meeting that happens on Tuesdays, I believe to really
01:00:14.444 --> 01:00:15.479 build out Phoenix.
01:00:15.489 --> 01:00:19.073 I know that the main goal, and I apologize if somebody was going
01:00:19.073 --> 01:00:22.326 to do a presentation on this, but I know the main goal for
01:00:22.326 --> 01:00:25.799 Phoenix is to actually get our marketing site moved over to to
01:00:25.799 --> 01:00:27.839 living on Phoenix by end of January.
01:00:27.849 --> 01:00:30.875 I know that kind of aligns with what Phil was talking about with
01:00:30.875 --> 01:00:33.669 some of the Google changes, so that's gonna be really cool.
01:00:33.679 --> 01:00:36.046 I know Chris has done a lot to get his hands in there and make
01:00:36.046 --> 01:00:37.549 sure that that's going to move forward.
01:00:37.559 --> 01:00:38.489 So that's exciting.
01:00:38.729 --> 01:00:42.637 And then obviously, AI, we've been talking about doing AI for
01:00:42.637 --> 01:00:43.709 core for a while.
01:00:44.159 --> 01:00:47.376 There's a lot of cool projects that we were talking with
01:00:47.376 --> 01:00:50.875 potential clients about doing different levels of AI, whether
01:00:50.875 --> 01:00:53.189 it be content generation, whether it be.
01:00:53.469 --> 01:00:57.668 I know that for for desk we're doing what phone interactions
01:00:57.668 --> 01:01:01.109 and and basically a call center type interaction.
01:01:02.319 --> 01:01:05.255 We talked with the client very recently that wanted it to do
01:01:05.255 --> 01:01:07.998 like facial recognition for security software and things
01:01:07.998 --> 01:01:08.479 like that.
01:01:08.489 --> 01:01:11.833 So a lot of cool things happening on the AI front for
01:01:11.833 --> 01:01:14.929 core, and I believe that one meets on Wednesdays.
01:01:16.749 --> 01:01:18.479 So that's a that's exciting there.
01:01:18.989 --> 01:01:21.719 Obviously we're going to in the future make that part of, you
01:01:21.719 --> 01:01:24.273 know, potentially everyday schedules and whatnot and that
01:01:24.273 --> 01:01:26.299 kind of goes into the funded through profits.
01:01:26.309 --> 01:01:31.819 So these numbers are are where we're pushing for these numbers.
01:01:32.029 --> 01:01:34.039 I don't think we're fully there in terms of.
01:01:34.049 --> 01:01:35.639 This is exactly where we're strict.
01:01:35.649 --> 01:01:39.540 We're restricting it down specifically to this, but 50% of
01:01:39.540 --> 01:01:43.498 our SAS profit is expected to go towards umm towards either
01:01:43.498 --> 01:01:47.389 clarity Labs or core features or whatever that looks like.
01:01:47.479 --> 01:01:50.592 And then 15% of the services profit and again that's that
01:01:50.592 --> 01:01:52.149 profit number on top of that.
01:01:52.159 --> 01:01:55.476 So I think Chris gave numbers earlier on what those are
01:01:55.476 --> 01:01:56.779 supposed to look like.
01:01:56.789 --> 01:01:59.808 So you can do the math of what that would take to to get those
01:01:59.808 --> 01:02:00.239 hours in.
01:02:00.249 --> 01:02:03.484 So our main push and our main goal here is to really drive
01:02:03.484 --> 01:02:06.884 more and more hours into the clarity product so that you know
01:02:06.884 --> 01:02:08.419 it's really an upward cycle.
01:02:08.429 --> 01:02:10.989 So that sales is more confident in saying here's our product.
01:02:10.999 --> 01:02:14.457 Here's what you get out of box and the customizations can be
01:02:14.457 --> 01:02:18.029 few and far between in terms of the small fixes to what should
01:02:18.029 --> 01:02:19.219 be in a core product.
01:02:19.369 --> 01:02:22.279 And then it's just purely business logic on top of that.
01:02:22.289 --> 01:02:25.398 So as we continue to build our product and continue to generate
01:02:25.398 --> 01:02:28.263 those license sales, we'll continue to build more and more
01:02:28.263 --> 01:02:30.449 and more and ultimately take over the world.
01:02:31.909 --> 01:02:35.576 So I'll I'll pivot one last thing here before I before I hop
01:02:35.576 --> 01:02:37.319 off is I'll show you the BRD.
01:02:38.719 --> 01:02:41.741 Umm, so we're building out this core backlog BRD and you can see
01:02:41.741 --> 01:02:43.369 here we go to the Navigation Pane.
01:02:43.379 --> 01:02:45.429 We have different kind of levels of.
01:02:46.049 --> 01:02:46.729 I don't know if I can.
01:02:48.599 --> 01:02:49.369 Mass closed.
01:02:49.379 --> 01:02:53.259 These will go this route, so we have some things in basically
01:02:53.259 --> 01:02:57.013 needs prioritization, so a handful of topics that when they
01:02:57.013 --> 01:03:00.830 get brought up or I hear about them in a meeting or they you
01:03:00.830 --> 01:03:04.523 know somebody they they get relayed to me, then I'll throw
01:03:04.523 --> 01:03:08.527 them in here and it may be that you know there's just a couple,
01:03:08.527 --> 01:03:12.345 a couple bullet points about hey, we should do this and then
01:03:12.345 --> 01:03:13.909 we'll dive into it later.
01:03:14.739 --> 01:03:18.211 There is kind of a voting system that goes on for 1/4 of what we
01:03:18.211 --> 01:03:21.309 should go ahead and start putting architecture time into.
01:03:21.799 --> 01:03:24.613 Obviously some of that is still client driven as we've seen lab
01:03:24.613 --> 01:03:27.207 results may not have been something that we worked on this
01:03:27.207 --> 01:03:27.559 quarter.
01:03:27.569 --> 01:03:29.711 But because lab works came in and they needed it, we pushed
01:03:29.711 --> 01:03:31.889 that to the front so that we can go ahead and get that done.
01:03:32.329 --> 01:03:34.349 So there's various levels in there.
01:03:34.559 --> 01:03:37.579 We definitely want everyone's input in terms of, hey, I'm
01:03:37.579 --> 01:03:39.349 seeing this on a lot of projects.
01:03:39.359 --> 01:03:40.059 Can we have some help?
01:03:41.609 --> 01:03:44.727 We have some documentation I believe in nuclino of how how
01:03:44.727 --> 01:03:46.999 you can get that or information forwarded.
01:03:47.069 --> 01:03:50.416 Obviously feel free to ping me anytime you have something we
01:03:50.416 --> 01:03:51.459 can put it in here.
01:03:51.469 --> 01:03:54.294 May need to get back to you at some point, so feel free to
01:03:54.294 --> 01:03:57.263 throw it in here or to throw it at me and I'll get it in here
01:03:57.263 --> 01:03:58.029 and we'll start.
01:03:58.039 --> 01:04:00.459 We'll start looking through and prioritizing.
01:04:02.979 --> 01:04:05.129 But that that's about it for me, Chris.
01:04:05.139 --> 01:04:06.899 Unless you have anything that you'd like for me to cover.
01:04:08.889 --> 01:04:09.819 Thank you, Sir weathers.
01:04:09.829 --> 01:04:11.229 Yeah, I think that was awesome.
01:04:11.279 --> 01:04:14.961 And yeah, I I know one of the things that if we have time to
01:04:14.961 --> 01:04:17.919 talk about today might be interesting for folks.
01:04:18.009 --> 01:04:22.158 And I'm just this is totally ad hoc, so I understand if they
01:04:22.158 --> 01:04:26.172 this would be not a lot of detail, but there are some team
01:04:26.172 --> 01:04:30.389 members that are working on, you know, some of the areas that
01:04:30.389 --> 01:04:34.675 are, I would call clarity labs and just kind of a precursor to
01:04:34.675 --> 01:04:34.879 it.
01:04:35.849 --> 01:04:40.389 So if you do want to chime in, I would say some of the selenium
01:04:40.389 --> 01:04:44.859 work that's going on, as well as some of the unit testing work
01:04:44.859 --> 01:04:47.909 with Apollo and those types of activities.
01:04:47.919 --> 01:04:51.715 If you guys wanted to kind of dust it off and get it ready,
01:04:51.715 --> 01:04:55.069 I'll circle back just so you can show that off once.
01:04:55.219 --> 01:04:59.541 Once we get done talking with BL here and thank you again, Sir
01:04:59.541 --> 01:05:03.726 weathers and just around clarity labs, of course, Phoenix is
01:05:03.726 --> 01:05:07.636 really a key part of the big investment areas that we're
01:05:07.636 --> 01:05:11.890 going to be pouring into this year and we're planning on some
01:05:11.890 --> 01:05:13.879 major milestones for Phoenix.
01:05:13.889 --> 01:05:15.879 And I'll let you talk to that, Sir Lyon.
01:05:16.849 --> 01:05:20.241 I also just wanted to note I don't know that everyone saw it
01:05:17.189 --> 01:05:17.349 Yep.
01:05:20.241 --> 01:05:23.299 in the camera, but I did drink an honorary V8 earlier.
01:05:23.989 --> 01:05:28.364 So anyway, with with V8 and Phoenix and mind over to use or
01:05:28.364 --> 01:05:28.729 Lyon.
01:05:30.239 --> 01:05:30.909 Alright.
01:05:31.149 --> 01:05:32.739 Uh, well, welcome.
01:05:33.829 --> 01:05:37.124 At some point I'm gonna have to put together an estimated number
01:05:35.059 --> 01:05:35.199 Hello.
01:05:37.124 --> 01:05:39.709 of V gates consumed in the development of Phoenix.
01:05:40.079 --> 01:05:45.267 Let's I can figure out what our what, our miles per gallon is,
01:05:40.579 --> 01:05:42.789 Yes, that sounds awesome.
01:05:43.559 --> 01:05:46.689 A good website stat, yeah.
01:05:45.267 --> 01:05:45.679 yeah.
01:05:47.599 --> 01:05:52.441 But yeah, so let me take a very quick moment to, uh, go over
01:05:52.441 --> 01:05:56.409 Phoenix and where we're at right now, what we're.
01:05:58.209 --> 01:06:01.549 What we're working on next and what we've been working on
01:06:01.549 --> 01:06:02.759 recently, umm and uh.
01:06:02.919 --> 01:06:06.349 So yeah, also just felt like I had to include.
01:06:06.359 --> 01:06:09.691 Does anybody else mixed up the oh and the E sometimes that's
01:06:09.089 --> 01:06:09.339 Yes.
01:06:09.691 --> 01:06:12.913 it's finally getting better for me, but it's still happens
01:06:12.913 --> 01:06:13.459 sometimes.
01:06:14.949 --> 01:06:19.255 So anyhow, moving on, so first up, just a very quick refresher
01:06:19.255 --> 01:06:21.169 on what Phoenix actually is.
01:06:21.749 --> 01:06:26.432 It's a modular development framework that we're building on
01:06:26.432 --> 01:06:28.539 net seven soon to be net 8.
01:06:28.919 --> 01:06:29.449 Umm.
01:06:30.199 --> 01:06:33.289 And it's it's built with the.
01:06:33.379 --> 01:06:37.795 The primary goal of being easy to build in for all the
01:06:37.795 --> 01:06:42.452 different pieces of the code to to behave in predictable,
01:06:42.452 --> 01:06:47.270 extensible, and easy ways to work with, and we're trying to
01:06:47.270 --> 01:06:51.445 kind of meet that goal without sacrificing too much
01:06:51.445 --> 01:06:52.409 performance.
01:06:53.399 --> 01:06:57.663 I'll talk a little bit about that in a moment, but yeah,
01:06:57.663 --> 01:07:02.300 primary goal is basically to serve the needs that clarity has
01:07:02.300 --> 01:07:06.714 and play to the strengths of our development team and also
01:07:06.714 --> 01:07:11.426 getting us on to a more modern, uh, a more modern set of tools
01:07:11.426 --> 01:07:14.119 and software development practices.
01:07:14.679 --> 01:07:18.657 And the reason that we're going this direction, obviously
01:07:18.657 --> 01:07:22.429 building a platform that will help us scale a lot more
01:07:22.429 --> 01:07:26.613 effectively and that's both in terms of scaling as a company
01:07:26.613 --> 01:07:28.739 and being able to deliver more.
01:07:28.749 --> 01:07:32.805 And also on a technical level, literally scaling like an
01:07:32.805 --> 01:07:33.659 application.
01:07:36.419 --> 01:07:39.844 The way that it's built is is sort of focused around more
01:07:39.844 --> 01:07:43.210 modern tech stacks, like being able to containerize more
01:07:43.210 --> 01:07:46.872 efficiently and effectively and with less sort of boilerplate
01:07:46.872 --> 01:07:49.529 work to do there and all that kind of stuff.
01:07:50.429 --> 01:07:53.299 Another major focus is on eliminating technical debt.
01:07:53.579 --> 01:07:56.400 Umm, we have a lot of dependencies and versions of
01:07:56.400 --> 01:07:59.497 things that there's so many newer versions that are out
01:07:59.497 --> 01:07:59.829 there.
01:08:01.409 --> 01:08:06.060 And the those newer versions can open up a lot of awesome doors
01:08:06.060 --> 01:08:06.859 for us, UM.
01:08:06.949 --> 01:08:10.986 And so this is basically just a really cool way for us to, you
01:08:10.986 --> 01:08:14.830 know, ten birds, one stone basically, of of upgrading a ton
01:08:14.830 --> 01:08:18.739 of dependencies, getting a ton of awesome new functionality.
01:08:18.749 --> 01:08:23.556 And then also providing a more robust foundation for all that
01:08:23.556 --> 01:08:28.208 stuff to live on and all that funnels down into simplifying
01:08:28.208 --> 01:08:32.239 our day-to-day development practices, which in turn
01:08:32.239 --> 01:08:36.348 improves efficiency and generally just makes it more
01:08:36.348 --> 01:08:38.209 fun, a more fun process.
01:08:39.039 --> 01:08:44.519 So very very quick refresh on on what it is and why.
01:08:44.579 --> 01:08:47.657 And I know I have a little more time than I thought I was going
01:08:47.657 --> 01:08:48.379 to, so I might.
01:08:48.429 --> 01:08:53.931 I might go into more detail on that in a moment, but Next up is
01:08:53.931 --> 01:08:55.049 where we are.
01:08:55.419 --> 01:08:58.288 So this is just sort of what we've been working on over the
01:08:58.288 --> 01:09:01.109 last probably a few months since I last talked about this.
01:09:01.739 --> 01:09:06.348 So there's been lots of progress on core functionality and some
01:09:06.348 --> 01:09:08.869 some pretty cool upcoming plugins.
01:09:09.779 --> 01:09:13.057 So we have the plugin functionality has been really
01:09:13.057 --> 01:09:16.209 ironed out and improved over the last few months.
01:09:17.039 --> 01:09:21.774 Austin uh made a comment and I don't know if he even intended
01:09:21.774 --> 01:09:25.898 for it to to be as a a transformative, I guess to the
01:09:25.898 --> 01:09:29.259 way that I was looking at things as it was.
01:09:29.539 --> 01:09:31.889 But he just sort of made a comment about like, oh, what if
01:09:31.889 --> 01:09:34.119 we structured something like this instead of like this?
01:09:34.529 --> 01:09:37.963 And so that made me sort of go back and rethink how the plugins
01:09:37.963 --> 01:09:38.339 worked.
01:09:38.349 --> 01:09:40.639 And I'm super happy with how it came out.
01:09:40.789 --> 01:09:43.109 So thank you for that.
01:09:43.519 --> 01:09:44.249 Yeah. Yeah, awesome.
01:09:44.259 --> 01:09:44.649 Good job.
01:09:45.529 --> 01:09:48.559 But uh, so we've made a lot of really awesome progress there.
01:09:48.989 --> 01:09:54.618 I built a very cool, flexible, updating and basically just crud
01:09:54.618 --> 01:09:59.279 API and the system that's based on the new importer.
01:09:59.289 --> 01:10:04.302 For that I built on current CEF and it you it's based on quite a
01:10:04.302 --> 01:10:09.238 bit of back and forth with lots of different connect developers
01:10:09.238 --> 01:10:10.549 on some of their.
01:10:10.849 --> 01:10:14.432 Some of the pain points and frustrations of working with
01:10:14.432 --> 01:10:18.330 various APIs and what we can do to make that better still got
01:10:18.330 --> 01:10:19.839 some work it could have.
01:10:20.029 --> 01:10:23.210 It's not perfect right now, but it's a really awesome foundation
01:10:23.210 --> 01:10:25.069 for something and it's stupidly fast.
01:10:26.289 --> 01:10:26.939 Umm.
01:10:27.419 --> 01:10:30.549 Also, Chris has been working on bringing a lot of these teams
01:10:30.549 --> 01:10:31.659 functionality in that.
01:10:31.869 --> 01:10:34.549 Umm, I think Ron mentioned earlier.
01:10:34.559 --> 01:10:35.919 Maybe that was Philip.
01:10:36.109 --> 01:10:40.279 I think Philip mentioned earlier and that's the that is the
01:10:40.279 --> 01:10:41.739 functionality of the.
01:10:43.429 --> 01:10:47.787 In House CMS, so it it's basically getting us to where we
01:10:47.787 --> 01:10:52.295 sort of control the entire pipeline from start to finish in
01:10:52.295 --> 01:10:57.254 terms of how our website gets to this to persons computer instead
01:10:57.254 --> 01:11:01.988 of having to go through a CMS that does whatever it decides it
01:11:01.988 --> 01:11:05.369 wants to do and gives us no control over it.
01:11:06.159 --> 01:11:07.809 So I was taking control of the whole thing.
01:11:08.559 --> 01:11:11.956 Obviously means there's a little bit more work for us to do on
01:11:11.956 --> 01:11:15.246 that on on the upfront side of things, but once that work is
01:11:15.246 --> 01:11:18.266 done, the performance and the customization that we can
01:11:18.266 --> 01:11:20.639 squeeze out of it is pretty much unmatched.
01:11:21.579 --> 01:11:22.209 Umm.
01:11:22.259 --> 01:11:27.757 And again, a lot of that is built around UM being is easy as
01:11:27.757 --> 01:11:28.929 possible too.
01:11:28.979 --> 01:11:31.569 So very cool stuff there.
01:11:32.299 --> 01:11:34.879 We've also started on some front end development.
01:11:35.669 --> 01:11:36.179 Uh.
01:11:36.189 --> 01:11:39.452 Really starting to get a good idea of what the front end
01:11:39.452 --> 01:11:42.943 architecture is going to look like, which will also help lay
01:11:42.943 --> 01:11:46.378 out the what the day to day development process looks like,
01:11:46.378 --> 01:11:47.809 forefront and developers.
01:11:49.959 --> 01:11:52.865 This one still a lot in flux, so I'm looking forward to getting
01:11:52.865 --> 01:11:54.909 some of the front end team involved in this.
01:11:55.719 --> 01:11:59.366 So as we start bringing in the the the bulk of the CMS stuff
01:11:59.366 --> 01:12:01.519 and really starting to see it work.
01:12:03.159 --> 01:12:04.759 But with that said.
01:12:06.859 --> 01:12:07.739 Here's what's next.
01:12:08.489 --> 01:12:12.139 Umm, the uh.
01:12:12.149 --> 01:12:15.889 The immediate term sort of Q 12024 is.
01:12:18.129 --> 01:12:19.199 Namely or.
01:12:19.209 --> 01:12:23.444 Primarily, I guess, solidifying Phoenix's development cycle by
01:12:23.444 --> 01:12:27.276 continuing to bring into CMS functionality continuing to
01:12:27.276 --> 01:12:31.645 harden our core platform and the different pieces of it that are
01:12:31.645 --> 01:12:35.948 that are interconnecting now and that includes bringing in more
01:12:35.948 --> 01:12:39.645 developers which will necessitate having us solidified
01:12:39.645 --> 01:12:43.477 development cycle umm and the sort of the the goal we're
01:12:43.477 --> 01:12:47.174 cutting our teeth with on that is the CMS system we're
01:12:47.174 --> 01:12:47.779 building.
01:12:49.249 --> 01:12:53.097 And so the goal will be that as we're building the CMS system,
01:12:53.097 --> 01:12:56.762 it's going to require us to go and sort of harden different
01:12:56.762 --> 01:13:00.122 pieces of the code base and start to mature it and and
01:13:00.122 --> 01:13:01.099 solidify things.
01:13:01.409 --> 01:13:05.970 And the goal which I think Phil said is that the end of January
01:13:05.970 --> 01:13:10.175 to be running the clarity site off of Phoenix with our own
01:13:10.175 --> 01:13:10.959 custom CMS.
01:13:11.839 --> 01:13:13.299 Uh, which is really cool.
01:13:14.339 --> 01:13:18.519 Umm so that that I think is a is an awesome proof of concept of
01:13:18.519 --> 01:13:22.373 the architecture and everything and sort of shows that the
01:13:22.373 --> 01:13:26.554 concept is working and the idea is strong and now we're getting
01:13:26.554 --> 01:13:30.538 to a point where we can really build on it, which is awesome
01:13:30.538 --> 01:13:34.457 longer term through quarter the first quarter of 2024 we're
01:13:34.457 --> 01:13:38.246 looking to continue developing on the payment and invoice
01:13:38.246 --> 01:13:38.899 workflows.
01:13:40.999 --> 01:13:45.009 With the intent of rolling out pay hub projects on Phoenix
01:13:45.009 --> 01:13:49.086 toward the end of the first quarter and that's a really big
01:13:49.086 --> 01:13:53.436 part for those of you that are working on any pay hub projects,
01:13:53.436 --> 01:13:57.378 you know that pay up in current stuff is still on the old
01:13:57.378 --> 01:13:58.669 angular storefront.
01:13:58.679 --> 01:13:59.239 We haven't had.
01:13:59.449 --> 01:14:03.400 We haven't had the opportunity to bring it on to react yet and
01:14:03.400 --> 01:14:07.351 so this is sort of a two birds, one stone thing of modernizing
01:14:07.351 --> 01:14:10.863 it and also it sort of leading the charge on on initial
01:14:10.863 --> 01:14:12.619 ecommerce stuff for Phoenix.
01:14:12.869 --> 01:14:13.919 So very cool there.
01:14:16.159 --> 01:14:20.314 And that'll give us an opportunity to put together our
01:14:20.314 --> 01:14:25.225 payment processing and all that stuff and learn from some of our
01:14:25.225 --> 01:14:29.304 uh, learn from some of our challenges and and uh pain
01:14:29.304 --> 01:14:34.139 points we've had over the last, uh, ten years as a company, so.
01:14:36.409 --> 01:14:40.516 On that note, uh yeah, on that note, before I go on, umm, I
01:14:36.579 --> 01:14:37.239 Bless you.
01:14:37.719 --> 01:14:38.249 Bless you.
01:14:40.516 --> 01:14:44.896 mentioned I mentioned this every time I talk about Phoenix, but
01:14:44.896 --> 01:14:49.072 I'm gonna say it again anyway for anybody who might not have
01:14:49.072 --> 01:14:51.399 been there for those discussions.
01:14:52.159 --> 01:14:52.759 Umm.
01:14:53.319 --> 01:14:56.308 And this will this will primarily be geared at at
01:14:56.308 --> 01:14:59.596 development team members, but project managers, sales,
01:14:59.596 --> 01:15:01.689 everybody has relevant input here.
01:15:01.839 --> 01:15:06.551 If there's something that sucks, I would love to hear it,
01:15:06.551 --> 01:15:11.589 especially especially if it's something that's been tough for
01:15:11.589 --> 01:15:15.489 a long time or it's something that you're like.
01:15:15.499 --> 01:15:16.129 I know we.
01:15:16.139 --> 01:15:18.409 I know a better way to do this and we're just not doing it.
01:15:20.149 --> 01:15:24.924 I by all means tell me I don't it it doesn't hurt my feelings
01:15:24.924 --> 01:15:27.619 any, even if it's something I did.
01:15:29.249 --> 01:15:29.809 I would.
01:15:29.819 --> 01:15:31.269 I would rather just make it better.
01:15:31.459 --> 01:15:34.984 So, uh, if you do think of anything or know of anything,
01:15:34.984 --> 01:15:38.819 there's quite a few people that do a really good job of this.
01:15:40.889 --> 01:15:45.482 So thank you to those people who anytime, anytime, something
01:15:45.482 --> 01:15:46.009 smells.
01:15:46.839 --> 01:15:47.889 Uh. They?
01:15:47.899 --> 01:15:51.747 They asked me or they'll they'll bring it up and and, you know,
01:15:51.747 --> 01:15:52.889 put me on the spot.
01:15:52.899 --> 01:15:54.209 So appreciated.
01:15:55.059 --> 01:15:57.279 But uh, Daniel.
01:15:57.289 --> 01:16:01.453 The story the story with emails is is a complicated story, but
01:16:01.453 --> 01:16:05.617 we have a really cool plan for emails that if I have some time
01:16:05.617 --> 01:16:07.269 here in a minute, I will.
01:16:07.469 --> 01:16:08.369 I will talk about it.
01:16:10.329 --> 01:16:13.639 So anyway, so yeah, please tell me if things are bad.
01:16:14.569 --> 01:16:18.559 That's the best way to fix them is to know, and sometimes.
01:16:19.009 --> 01:16:21.935 Sometimes you go a little bit nose blind to certain things you
01:16:21.935 --> 01:16:23.329 don't smell the smell anymore.
01:16:25.259 --> 01:16:28.677 You've been around it for so long, but if especially like to
01:16:28.677 --> 01:16:32.096 hear from new people because they don't have the perspective
01:16:32.096 --> 01:16:35.458 of of having been in the code base for a long, so that that
01:16:35.458 --> 01:16:38.708 may mean that sometimes what they call out is just that's
01:16:38.708 --> 01:16:39.549 just how it is.
01:16:39.559 --> 01:16:41.868 But there are times where new people be like, hey, this kind
01:16:41.868 --> 01:16:42.209 of sucks.
01:16:42.219 --> 01:16:42.999 You're like, you know what?
01:16:43.009 --> 01:16:48.349 You're right, it does so by all means, all opinions are valid.
01:16:48.979 --> 01:16:49.459 Umm.
01:16:49.679 --> 01:16:54.584 So anyway, for moving past first quarter of 2024, we're going to
01:16:54.584 --> 01:16:59.338 continue focusing on bringing over some core set features like
01:16:59.338 --> 01:17:03.714 check out and registration discounts and just sort of the
01:17:03.714 --> 01:17:07.789 kind of bread and butter stuff that we have in stuff.
01:17:07.799 --> 01:17:10.569 We're just gonna work on bringing that in and defining
01:17:10.569 --> 01:17:13.691 what that process of pulling functionality from current stuff
01:17:13.691 --> 01:17:14.799 to Phoenix looks like.
01:17:16.429 --> 01:17:19.540 I'll be looking to find more ways to engage the development
01:17:19.540 --> 01:17:19.799 team.
01:17:19.909 --> 01:17:23.509 Uh in Phoenix's development, and Chris and I've talked about,
01:17:23.509 --> 01:17:27.108 like somebody mentioned earlier, we have a working session on
01:17:27.108 --> 01:17:27.979 Tuesday nights.
01:17:28.329 --> 01:17:32.152 That is presently just me and Chris, but we've talked about
01:17:32.152 --> 01:17:35.975 allowing or bringing in other people on that and or finding
01:17:35.975 --> 01:17:39.543 some time thoughts during business hours as time allows
01:17:39.543 --> 01:17:41.709 for us to press on it as a group.
01:17:43.029 --> 01:17:44.179 So I really do.
01:17:44.239 --> 01:17:46.249 I really do want to encourage people to get involved.
01:17:46.969 --> 01:17:48.459 Umm it's.
01:17:48.569 --> 01:17:52.876 It is a very fun project to work on and I I would I would love to
01:17:52.876 --> 01:17:56.856 get more hands on it and more opinions so but along with all
01:17:56.856 --> 01:18:00.772 that we'll work on documenting things, hardening the course
01:18:00.772 --> 01:18:04.752 systems more and just getting it to a point where it's super
01:18:04.752 --> 01:18:05.209 robust.
01:18:05.219 --> 01:18:10.748 Super easy to roll out and the process for developing and
01:18:10.748 --> 01:18:13.799 deploying it is well understood.
01:18:14.589 --> 01:18:19.584 So and with that, I want to really quickly give a thanks to
01:18:19.584 --> 01:18:21.249 a handful of people.
01:18:22.019 --> 01:18:26.111 So obviously, thanks to Chris for getting directly involved,
01:18:26.111 --> 01:18:30.471 that's motivated me a ton to get more, get back into it more and
01:18:30.471 --> 01:18:33.959 it's been our working sessions have been enjoyable.
01:18:35.189 --> 01:18:36.879 So thank you for that.
01:18:37.309 --> 01:18:41.360 And then of course, John Lee, our the original discussions we
01:18:41.360 --> 01:18:45.411 had at like 10:00 o'clock on a Saturday night a year ago or a
01:18:45.411 --> 01:18:49.593 year and a half ago where we we formulated the, the the Scratch
01:18:47.579 --> 01:18:48.119 That's awesome.
01:18:49.593 --> 01:18:53.578 code that became pipelines and then talked about a bunch of,
01:18:53.578 --> 01:18:55.669 yeah, when we called it, Jarvis.
01:18:55.679 --> 01:18:55.879 Yeah.
01:18:56.749 --> 01:19:00.991 Uh, those that discussion and the the discussions that stemmed
01:19:00.991 --> 01:19:05.233 from that are still the the core architecture of of Phoenix to
01:19:05.233 --> 01:19:05.839 this day.
01:19:05.849 --> 01:19:07.359 So, umm.
01:19:08.309 --> 01:19:09.299 Pretty awesome.
01:19:10.249 --> 01:19:13.489 Thank you for the inspiration and and great ideas.
01:19:15.229 --> 01:19:18.198 And then, Austin, that idea I mentioned earlier about
01:19:18.198 --> 01:19:21.716 splitting plugins in a different way, it it seriously made like
01:19:21.716 --> 01:19:25.180 1000 things kind of fall into place in my brain when I started
01:19:25.180 --> 01:19:26.499 writing the code for it.
01:19:26.509 --> 01:19:28.149 So that's really awesome idea.
01:19:29.739 --> 01:19:33.865 And for anyone curious, the idea effectively was instead of
01:19:33.865 --> 01:19:38.198 having and ecommerce plugin that includes products and catalog
01:19:38.198 --> 01:19:42.599 and invoices and etcetera, and instead having a products plugin
01:19:42.599 --> 01:19:46.932 and an invoice is plug in that sort of defined their processes
01:19:46.932 --> 01:19:50.920 and schema together so that uh for example your ecommerce
01:19:50.920 --> 01:19:54.978 plugin would need products and catalog and checkout and et
01:19:54.978 --> 01:19:55.459 cetera.
01:19:55.709 --> 01:19:59.405 But your and it might also need invoices, but your pay hub one
01:19:59.405 --> 01:20:01.399 just needs invoices and payments.
01:20:01.409 --> 01:20:05.086 It's to sort of modules of code, so rather than sort of splitting
01:20:05.086 --> 01:20:08.540 things at a horizontal level of, here's all the functionality
01:20:08.540 --> 01:20:11.159 included in ecommerce, we split it vertically.
01:20:11.169 --> 01:20:15.341 If here's everything related to products from the database level
01:20:15.341 --> 01:20:18.229 up to the service level, the API email, umm.
01:20:18.699 --> 01:20:22.306 And so that's it's just a really cool way of breaking things
01:20:22.306 --> 01:20:26.150 apart that allows us to assemble different niches with different
01:20:26.150 --> 01:20:28.929 pieces of code that we know work individually.
01:20:29.809 --> 01:20:30.349 Umm.
01:20:31.029 --> 01:20:35.009 And so that was a really cool a really cool idea that.
01:20:36.939 --> 01:20:39.749 That, yeah, worked out really well.
01:20:40.119 --> 01:20:43.907 And then, of course, to leadership in general for
01:20:43.907 --> 01:20:46.029 letting me explore the idea.
01:20:46.509 --> 01:20:50.438 And I jokingly said sorry for always talking about it, because
01:20:50.438 --> 01:20:52.309 as we all know, I'm not sorry.
01:20:52.319 --> 01:20:53.579 And I will continue to talk.
01:20:55.519 --> 01:20:56.199 That's awesome.
01:20:55.709 --> 01:20:58.719 And also to lots of lots of other people.
01:20:56.449 --> 01:20:56.809 Love it.
01:20:58.789 --> 01:20:59.319 Uh.
01:20:59.329 --> 01:21:05.295 Tons of people have have either directly or indirectly helped
01:21:05.295 --> 01:21:09.529 with things on Phoenix and just in general.
01:21:10.789 --> 01:21:14.623 So if I didn't specifically name somebody know that it's not
01:21:14.623 --> 01:21:18.268 because I forgot you, it's because this the I didn't have
01:21:18.268 --> 01:21:20.279 that much room on the slide, so.
01:21:23.229 --> 01:21:24.219 Uh, yeah.
01:21:24.269 --> 01:21:29.424 So uh, I'll quickly look at the chat there, potentially helpful
01:21:29.424 --> 01:21:33.049 topics, videos ramp up and how to access it.
01:21:33.059 --> 01:21:33.299 Yeah.
01:21:33.309 --> 01:21:36.763 So I've done some trainings with the dev team on how to get
01:21:36.763 --> 01:21:40.332 access to the repo if you need any help with that, definitely
01:21:40.332 --> 01:21:43.901 shoot me a message and at some point I'll I'll write up a new
01:21:43.901 --> 01:21:47.586 clean no page that details it, but all of the development teams
01:21:47.586 --> 01:21:50.579 should have access to the Phoenix project on Azure.
01:21:51.679 --> 01:21:52.279 Umm.
01:21:53.229 --> 01:21:57.254 And from there I do need to write up the readme on how to do
01:21:57.254 --> 01:22:01.279 the setup properly, but it's like a just a few step process.
01:22:01.289 --> 01:22:02.109 Very straightforward.
01:22:02.939 --> 01:22:03.539 Umm.
01:22:04.249 --> 01:22:08.111 And in terms of Chris asked what core topics could folks be
01:22:08.111 --> 01:22:11.522 reading up on or brushing up on so they can be ideal
01:22:11.522 --> 01:22:12.359 contributors.
01:22:12.619 --> 01:22:14.139 Couple of really big ones.
01:22:14.749 --> 01:22:17.209 Number one is just ASP .net core in general.
01:22:17.799 --> 01:22:23.401 Umm, the that is the the much of Phoenix is just tooling and and
01:22:23.401 --> 01:22:27.969 custom like bits of middleware built on top of that.
01:22:28.199 --> 01:22:31.789 So being familiar with how that works and how dependency
01:22:31.789 --> 01:22:35.630 injection works and some of the intricacies there would be a
01:22:35.630 --> 01:22:36.449 massive help.
01:22:37.259 --> 01:22:39.029 Umm, I mentioned earlier.
01:22:39.039 --> 01:22:40.269 It's currently on .net 7.
01:22:40.279 --> 01:22:44.310 We're gonna be upgrading the .net 8 pretty soon, so any of
01:22:44.310 --> 01:22:48.409 the modern documentation is good in terms of the front end.
01:22:48.479 --> 01:22:51.222 We're still playing around with next JS, that's we're pretty
01:22:51.222 --> 01:22:53.919 much settled that that is going to be the framework for the
01:22:53.919 --> 01:22:54.369 front end.
01:22:55.179 --> 01:22:58.117 So for those of you that are react developers writing the
01:22:58.117 --> 01:23:00.549 React Code is going to be very familiar to you.
01:23:00.559 --> 01:23:04.700 It's the same as normal react, but next does have some really
01:23:04.700 --> 01:23:08.508 neat additional features on the server side that you can
01:23:08.508 --> 01:23:09.109 research.
01:23:09.119 --> 01:23:11.259 Their documentation has also top notch.
01:23:12.909 --> 01:23:17.332 So if you have any, uh, any ideas or things like that, feel
01:23:17.332 --> 01:23:22.049 free to kind of cross reference their documentation and and see
01:23:22.049 --> 01:23:24.629 what you can see, what you can do.
01:23:25.639 --> 01:23:27.669 Umm. Uh.
01:23:27.829 --> 01:23:29.529 Then Daniel will have a second.
01:23:29.539 --> 01:23:30.759 I'll jump back to emails.
01:23:30.829 --> 01:23:35.224 UM, we're uh this summer, actually hoping to get into core
01:23:35.224 --> 01:23:39.470 stuff as well current CEF, but we're hoping to write a a
01:23:39.470 --> 01:23:44.088 alternative way of setting up emails where there's a a header
01:23:44.088 --> 01:23:48.259 and footer that you can kind of customize in the admin.
01:23:48.269 --> 01:23:51.873 Do like a WYSIWYG editor and then the body of each email
01:23:51.873 --> 01:23:55.414 template is just sort of sandwiched between that header
01:23:55.414 --> 01:23:59.271 and footer because 99% of the time clients don't really need
01:23:59.271 --> 01:24:02.369 to customize the body of like an order template.
01:24:02.379 --> 01:24:04.650 They might change like a couple of pieces of text here, and
01:24:04.650 --> 01:24:06.769 there's, like your order has been received or whatever.
01:24:07.439 --> 01:24:10.648 Umm, but generally the order grid that shows the line item
01:24:10.648 --> 01:24:13.748 things, they're not changing that per SE, they just want
01:24:13.748 --> 01:24:17.228 their logo and some details in the correct phone number and all
01:24:17.228 --> 01:24:20.709 that stuff in the footer and a lot of the tedium we have now in
01:24:20.709 --> 01:24:24.026 terms of customizing those is that we have to touch the full
01:24:24.026 --> 01:24:27.289 template and it's a physical file, so modifications require
01:24:27.289 --> 01:24:30.389 code change and redeployment and all that kind of stuff.
01:24:30.459 --> 01:24:32.974 That kind of circumvented that problem by making it something
01:24:32.974 --> 01:24:34.719 that's a lot more settings or data driven.
01:24:36.329 --> 01:24:39.893 And also separates the most commonly customized from the
01:24:39.893 --> 01:24:41.519 least commonly customized.
01:24:41.609 --> 01:24:46.239 So that's the plan for email templates in Phoenix.
01:24:46.249 --> 01:24:49.784 And I know that at some point we hope to get that into current
01:24:49.784 --> 01:24:50.569 stuff as well.
01:24:51.399 --> 01:24:52.269 Uh, but.
01:24:53.279 --> 01:24:55.323 Yeah, I'll add that it's actually went through
01:24:55.323 --> 01:24:55.889 architecture.
01:24:55.899 --> 01:24:59.366 I believe last Sprint for that, so we'll be getting that in in a
01:24:59.366 --> 01:25:02.459 in an upcoming Sprint to to bring into core current core.
01:25:02.019 --> 01:25:02.629 Ice.
01:25:03.499 --> 01:25:03.709 Add.
01:25:03.609 --> 01:25:05.129 Sweet, good job.
01:25:03.719 --> 01:25:04.259 It's awesome.
01:25:05.339 --> 01:25:07.769 Umm yeah? Umm.
01:25:09.839 --> 01:25:10.919 I guess that's all I have.
01:25:13.009 --> 01:25:19.281 If anybody has any questions umm, then yeah, feel free to
01:25:14.529 --> 01:25:15.099 That's awesome.
01:25:19.281 --> 01:25:21.119 feel free to ask.
01:25:21.129 --> 01:25:27.307 I I as as everyone knows I'm I'm happy to talk about it and and
01:25:27.307 --> 01:25:28.369 show stuff.
01:25:28.379 --> 01:25:30.159 So anytime.
01:25:29.969 --> 01:25:30.939 Thank you, Sir Lyon.
01:25:31.089 --> 01:25:31.979 Good job.
01:25:32.289 --> 01:25:36.757 How we're excited about Phoenix, however, is spelled and yeah,
01:25:36.757 --> 01:25:37.679 happy Friday.
01:25:37.809 --> 01:25:42.481 And Speaking of exciting things that we're working on, certain
01:25:42.481 --> 01:25:47.228 rows is doing some really great work with just generally making
01:25:47.228 --> 01:25:50.639 sure that we manage expectations really well.
01:25:50.649 --> 01:25:55.244 I think if you talk to any of the project managers, you know
01:25:55.244 --> 01:25:59.688 you can probably summarize a lot of the opportunity and or
01:25:59.688 --> 01:26:04.659 challenge that clients deal with with a single word expectations.
01:26:05.369 --> 01:26:09.733 And one of the challenging parts of our business, one of our
01:26:09.733 --> 01:26:13.883 challenging niche offers is integrations because managing
01:26:13.883 --> 01:26:18.319 expectations for clients in that arena is really challenging.
01:26:18.589 --> 01:26:22.340 There are a lot of sort of natural assumptions that clients
01:26:22.340 --> 01:26:26.153 will make and you know, although we understand that we wanna
01:26:26.153 --> 01:26:29.779 really work to continue to improve our execution and just
01:26:29.779 --> 01:26:33.718 consistently as a group operate from the same playbook so that
01:26:33.718 --> 01:26:37.344 we can deliver against their expectations and really do a
01:26:37.344 --> 01:26:37.969 great job.
01:26:38.199 --> 01:26:42.574 So Jeremy provided a training for the Connect team either last
01:26:42.574 --> 01:26:45.629 week or the week before and it was awesome.
01:26:45.769 --> 01:26:50.184 And so I just asked him to share some of the Nuggets, some of the
01:26:50.184 --> 01:26:53.529 sort of, you know, core ideas from that training.
01:26:53.909 --> 01:26:57.172 And then I also would love it if you wanted to share updates in
01:26:57.172 --> 01:26:58.549 general on connect as well.
01:26:58.559 --> 01:26:59.039 So la rose.
01:26:59.219 --> 01:27:01.759 So anyway, with that over to you, good Sir.
01:27:01.769 --> 01:27:02.969 If you're ready to take it away.
01:27:03.709 --> 01:27:04.509 Yeah, that's fantastic.
01:27:04.519 --> 01:27:05.079 Thanks, Chris.
01:27:05.829 --> 01:27:06.269 My pleasure.
01:27:05.869 --> 01:27:08.924 Yeah, I like Chris said, you know, 2023 has been a
01:27:08.924 --> 01:27:11.439 transformational year for connect for us.
01:27:11.709 --> 01:27:16.439 It's been a lot of work, a huge kudos the entire team.
01:27:16.449 --> 01:27:18.739 It's no small undertaking to modify.
01:27:18.909 --> 01:27:22.099 We changed not only the core of CONNECT to update it, but
01:27:22.099 --> 01:27:25.289 tediously going through one of the connectors to position
01:27:25.289 --> 01:27:28.699 ourselves as knowledgeable and have an actual product that we
01:27:28.699 --> 01:27:29.799 can sell to clients.
01:27:30.609 --> 01:27:33.229 The primary folks that we've been really drilling in on has
01:27:33.229 --> 01:27:35.543 been improving client satisfaction and improving how
01:27:35.543 --> 01:27:36.809 these projects go as a whole.
01:27:37.729 --> 01:27:41.768 And that's kind of my focus is in my opinion, if we can get
01:27:41.768 --> 01:27:46.009 these three pillars down, then our clients, they're just gonna
01:27:46.009 --> 01:27:49.779 think we're the greatest development team in the world.
01:27:49.789 --> 01:27:52.460 And I've I've started to hear that now from our partners to
01:27:52.460 --> 01:27:54.998 say, you know, we've tried lots of different integration
01:27:54.998 --> 01:27:55.399 partners.
01:27:55.469 --> 01:27:56.639 It didn't go well.
01:27:57.429 --> 01:28:00.274 We're really looking for someone that can be an expert in these
01:28:00.274 --> 01:28:02.985 systems and truly has something that is as a value for these
01:28:02.985 --> 01:28:04.319 clients and we can deliver on.
01:28:04.329 --> 01:28:08.253 So you know, the whole year has been focused around making sure
01:28:08.253 --> 01:28:11.686 does the connector work, is it documented, is it a good
01:28:11.686 --> 01:28:13.219 experience to develop in?
01:28:13.309 --> 01:28:14.959 Can we deliver these projects quickly?
01:28:15.149 --> 01:28:18.282 In my eyes, if we can deliver for these clients, you know
01:28:18.282 --> 01:28:19.849 that's what they want, right?
01:28:19.859 --> 01:28:21.169 They just want their data to move across.
01:28:21.179 --> 01:28:22.549 They want to know that it's gonna be there.
01:28:22.559 --> 01:28:27.116 They want to know the project to get done on time, so that boils
01:28:27.116 --> 01:28:28.939 down to these three areas.
01:28:28.949 --> 01:28:29.879 The discovery process?
01:28:30.519 --> 01:28:33.854 Uh, the development process and actually having a product that
01:28:33.854 --> 01:28:34.489 we can sell.
01:28:35.039 --> 01:28:38.422 So that's we've been focused on making sure that the discovery
01:28:38.422 --> 01:28:41.429 process goes better and is a cleaner operation overall.
01:28:41.439 --> 01:28:43.549 So kudos to Shelton.
01:28:43.559 --> 01:28:45.429 He and I've been working pretty closely together lately.
01:28:46.099 --> 01:28:48.894 The new discovery process for these integration projects is
01:28:48.894 --> 01:28:51.689 going to be taking the client, having them walk us through.
01:28:51.699 --> 01:28:56.517 This is blinding umm, having them walk us through what they
01:28:56.517 --> 01:28:56.919 have.
01:28:56.929 --> 01:28:57.899 That's OK.
01:28:59.519 --> 01:29:02.184 Walk through what they have in their ERP system and then taking
01:29:02.184 --> 01:29:04.349 comments and coming away with workflows from there.
01:29:04.439 --> 01:29:07.895 So if you zoom in here before we used to try to take these notes
01:29:07.895 --> 01:29:11.245 and just take jot them down on the calls with the client while
01:29:11.245 --> 01:29:14.382 they are sharing their screen and we would record them and
01:29:14.382 --> 01:29:16.509 we'd have to go back to the recordings.
01:29:16.519 --> 01:29:18.399 And sometimes would happen, and sometimes it wouldn't.
01:29:18.439 --> 01:29:21.674 The better way that I've found now has been Shelton and I
01:29:21.674 --> 01:29:24.910 together on the calls going through Shelton's leading the
01:29:24.910 --> 01:29:28.089 conversation as far as like what overall workflows have.
01:29:28.099 --> 01:29:31.277 They said they wanted to have and then bring me or some other
01:29:31.277 --> 01:29:34.404 system expert in to say, OK, cool, let's get a screenshot of
01:29:34.404 --> 01:29:37.275 your system and let's start thinking about what are all
01:29:37.275 --> 01:29:39.479 these fields and what does that relate to?
01:29:39.489 --> 01:29:42.559 And walk us through how this is gonna work.
01:29:42.929 --> 01:29:46.599 The idea behind this would be getting a lot of those pain
01:29:46.599 --> 01:29:50.269 points out of the way first, where we have these queries,
01:29:50.269 --> 01:29:53.939 we'll have this information available and really taking a
01:29:53.939 --> 01:29:57.609 deep dive into what is it that you're trying to automate,
01:29:57.609 --> 01:29:57.989 right?
01:29:57.999 --> 01:30:01.220 What is your manual process that you're looking to have automated
01:30:01.220 --> 01:30:04.246 here, and how can we, as connect developers, create a reality
01:30:04.246 --> 01:30:06.881 where programmatically that works and that's been the
01:30:06.881 --> 01:30:09.761 biggest change has been, you know, the client before would
01:30:09.761 --> 01:30:12.787 come in and say, you know, I want this thing to work this way
01:30:12.787 --> 01:30:15.861 and I want the sales order to appear over there and I want the
01:30:15.861 --> 01:30:17.179 customers to be over there.
01:30:17.229 --> 01:30:20.224 But what we found is they don't actually want all of the orders
01:30:20.224 --> 01:30:21.019 to be over there.
01:30:21.029 --> 01:30:23.199 They don't actually want all of the customers to be over there.
01:30:23.209 --> 01:30:26.585 What they want is they want automated workflows, So what
01:30:26.585 --> 01:30:30.197 we've tried to do is say hey, on this call on this discovery
01:30:30.197 --> 01:30:32.329 call, walk me through your process.
01:30:32.719 --> 01:30:35.829 Walk me through your workflows and let's let's identify.
01:30:35.879 --> 01:30:37.289 OK, so the order gets created over here.
01:30:37.299 --> 01:30:40.679 What happens then and come up with these architecture pieces
01:30:40.679 --> 01:30:43.449 right out of the box right on the call with them?
01:30:43.579 --> 01:30:47.386 So in this particular project on PIP, we talked about pricing and
01:30:47.386 --> 01:30:48.309 it was OK, cool.
01:30:48.399 --> 01:30:50.675 Walk me through how you would come up with a price for one of
01:30:50.675 --> 01:30:51.629 your products on the call.
01:30:51.799 --> 01:30:53.509 So then we were able to come up with this architecture.
01:30:54.379 --> 01:30:58.312 This seems like a lot of work, but this entire section of of
01:30:58.312 --> 01:31:02.567 the Connect sync almost the high level architecture is just about
01:31:02.567 --> 01:31:02.889 done.
01:31:03.259 --> 01:31:06.229 Was created in two hours, so there were some to DOS.
01:31:06.239 --> 01:31:08.980 There were some questions that we needed to know that Shelton
01:31:08.980 --> 01:31:11.722 and I were able to identify, but this is 2 hours of work, one
01:31:11.722 --> 01:31:14.419 hour with the client walking through their system and asking
01:31:14.419 --> 01:31:17.161 questions, and then one hour of going back through afterwards
01:31:17.161 --> 01:31:19.991 and reviewing the recording and reviewing what Shelton had come
01:31:19.991 --> 01:31:22.820 away with on previous calls to say, OK, cool, what workflows do
01:31:22.820 --> 01:31:23.749 we want to have here?
01:31:24.459 --> 01:31:28.151 So this combined with the push to documenting our connectors
01:31:28.151 --> 01:31:30.814 and having better notes in general has been
01:31:30.814 --> 01:31:32.569 transformational for connect.
01:31:32.659 --> 01:31:35.915 So if you haven't seen the new documentation that we have all
01:31:35.915 --> 01:31:39.118 of our connectors or by the end of the year or by the end of
01:31:39.118 --> 01:31:42.163 early quarter one, we'll be documented to where we have a
01:31:42.163 --> 01:31:45.209 principle PDF that we can give to the client to say cool.
01:31:45.399 --> 01:31:47.949 Here's how to set up Kinect for you, right?
01:31:47.959 --> 01:31:49.749 And we can just print this off as a PDF.
01:31:49.799 --> 01:31:52.201 Give it to the client and say this is how you set us up on
01:31:52.201 --> 01:31:52.689 your system.
01:31:52.739 --> 01:31:56.280 Or if you don't know how, now the next developer is able to go
01:31:56.280 --> 01:31:58.079 through and know how to do that.
01:31:58.089 --> 01:32:01.894 So we have not only the connector access, but how to
01:32:01.894 --> 01:32:02.899 create things.
01:32:03.389 --> 01:32:05.489 Huge kudos to gym for going through and doing these.
01:32:05.499 --> 01:32:08.678 This is tedious work and he just crushed it to go through and say
01:32:08.678 --> 01:32:08.919 cool.
01:32:08.929 --> 01:32:10.349 This is how you create a customer in the system.
01:32:10.359 --> 01:32:11.169 This is how you do this.
01:32:11.179 --> 01:32:12.819 This is how you do this thing.
01:32:12.829 --> 01:32:16.877 So all of the customizations that but yeah, yeah, it's a lot
01:32:13.089 --> 01:32:16.757 I just want to say here here that is a lot of work and is so
01:32:16.757 --> 01:32:17.599 key kudos gym.
01:32:16.877 --> 01:32:21.059 of work and I think one of the cool things is like having, you
01:32:17.969 --> 01:32:18.349 Thank you.
01:32:21.059 --> 01:32:25.306 know, these sample Jason files to be able to say, look, this is
01:32:25.306 --> 01:32:29.089 what this looks like from the system, this test product.
01:32:29.099 --> 01:32:31.762 So this is what we're expecting to see when a product is created
01:32:31.762 --> 01:32:34.302 and we could pull a product back from an API compared against
01:32:34.302 --> 01:32:36.269 this and say hey, that is not what we expected.
01:32:36.279 --> 01:32:37.209 You have some custom fields.
01:32:37.219 --> 01:32:38.509 You have something going on in there.
01:32:38.559 --> 01:32:41.329 Let's take a look a little bit deeper and adjust our estimates,
01:32:41.329 --> 01:32:41.589 right.
01:32:41.599 --> 01:32:42.949 And that's the biggest thing.
01:32:42.959 --> 01:32:45.823 Like Chris is saying about having client expectations
01:32:45.823 --> 01:32:49.059 manage right from the jump right from the very get go, we're
01:32:49.059 --> 01:32:51.976 focused on managing those expectations and setting the
01:32:51.976 --> 01:32:55.265 tone for our clients and what that means is more coordination
01:32:55.265 --> 01:32:58.660 between the Connect development team, myself and the sales team
01:32:58.660 --> 01:33:01.577 to be able to say on these initial estimates, you know
01:33:01.577 --> 01:33:04.919 we're going through, if you're doing addresses, do you want to
01:33:04.919 --> 01:33:07.359 differentiate, if you do, yes, that's a risk.
01:33:07.369 --> 01:33:10.967 Magento doesn't know how to do that having these type of things
01:33:10.967 --> 01:33:14.677 documented before we go into the client projects I think has been
01:33:14.677 --> 01:33:18.275 a massive improvement to where we're not going in blind or with
01:33:18.275 --> 01:33:19.849 a ton of assumptions to say.
01:33:20.059 --> 01:33:20.709 Ohh yeah cool.
01:33:20.719 --> 01:33:21.139 No problem.
01:33:21.149 --> 01:33:24.230 We can do pricing or yeah, we can push payments into a Magento
01:33:24.230 --> 01:33:27.165 and it's like now we have the ability to say wait a minute,
01:33:27.165 --> 01:33:30.050 this is all we can have out of the box or this is all that
01:33:30.050 --> 01:33:32.838 system supports even because I know as project managers,
01:33:32.838 --> 01:33:35.968 developers we've all gotten into projects and we'll get halfway
01:33:35.968 --> 01:33:39.049 into it and they say wait, wait, wait, wait, we can't do that.
01:33:39.159 --> 01:33:40.869 And then you have to go back and go.
01:33:40.879 --> 01:33:43.850 How did we go nine months in this project and not know that
01:33:43.850 --> 01:33:46.870 that's what we're really looking to solve here with having a
01:33:46.870 --> 01:33:48.999 better discovery and architecture process.
01:33:49.229 --> 01:33:53.439 So with that thinking about how does a developer work?
01:33:53.449 --> 01:33:56.599 Where do they work and how do they go through and do things?
01:33:56.809 --> 01:33:59.920 I've been focused on trying to get to where we have better
01:33:59.920 --> 01:34:02.925 documentation and snippets and everything that will help
01:34:02.925 --> 01:34:04.559 developers create these things.
01:34:04.689 --> 01:34:08.239 So for us we have our repo that has all of our notes in there.
01:34:08.329 --> 01:34:12.393 We have a ton of documentation snippets and this is all aimed
01:34:12.393 --> 01:34:16.589 at trying to make sure the team can go faster, so meeting notes
01:34:16.589 --> 01:34:17.769 are in here scope.
01:34:17.779 --> 01:34:20.944 Docs are in here, so if you've never seen how these work, I can
01:34:20.944 --> 01:34:22.329 create a new file scope Doc.
01:34:22.339 --> 01:34:22.809 I have this.
01:34:24.029 --> 01:34:28.276 I can name my my project, go through tab through this and now
01:34:28.276 --> 01:34:32.454 I have a scope doc that that better tracks how we work right
01:34:32.454 --> 01:34:36.700 and giving the developers the ability to write their own user
01:34:36.700 --> 01:34:40.399 stories and letting the system expert come into this.
01:34:40.529 --> 01:34:43.500 If we've done our job on the discovery and architecture
01:34:43.500 --> 01:34:46.630 process to accurately capture client requirements, then we
01:34:46.630 --> 01:34:49.814 don't need to get really into the weeds on how to build the
01:34:49.814 --> 01:34:53.209 thing, because that's up to the expert of the system to decide.
01:34:53.219 --> 01:34:55.059 That's why we pay the developers the big bucks, right?
01:34:55.069 --> 01:34:56.759 Like, that's what we have them for.
01:34:56.769 --> 01:34:58.469 Their experts in that system, that realm.
01:34:59.399 --> 01:35:02.409 So for us on the connect side, because there are so many
01:35:02.409 --> 01:35:05.260 systems, no one person can establish themselves as an
01:35:05.260 --> 01:35:06.369 expert on everything.
01:35:06.379 --> 01:35:10.189 So having this to where Scarlett or Jr or somebody could come in
01:35:10.189 --> 01:35:14.058 here, if it's Epicor Eagle, then Scarlett and come in here, she's
01:35:14.058 --> 01:35:15.289 gonna write this out.
01:35:15.299 --> 01:35:17.529 How she should do it and it's ready to go.
01:35:17.539 --> 01:35:20.071 So what that would look like on a finished one, this is what the
01:35:20.071 --> 01:35:21.629 information that developers should get.
01:35:21.739 --> 01:35:22.489 What should it do?
01:35:22.499 --> 01:35:25.349 What's the acceptance criteria and how does this look?
01:35:25.359 --> 01:35:26.629 Has really been my focus.
01:35:26.639 --> 01:35:32.254 Is creating a better process for the Connect team, so surrounding
01:35:32.254 --> 01:35:32.679 that?
01:35:32.729 --> 01:35:34.179 Like I said, is all the tooling right?
01:35:34.189 --> 01:35:36.964 So we have the the snippets to be able to create the scope
01:35:36.964 --> 01:35:37.199 docs.
01:35:37.469 --> 01:35:41.798 We also have streamlined the setup process for connect, so
01:35:41.798 --> 01:35:42.679 kudos to JL.
01:35:42.709 --> 01:35:45.350 What that would look like is we'd come here, we have a blank
01:35:45.350 --> 01:35:46.649 project, we would go, Maestro.
01:35:47.949 --> 01:35:50.359 We'll see if this autocompletes new project.
01:35:50.409 --> 01:35:51.739 New fireside.
01:35:51.909 --> 01:35:53.219 I'm gonna bring in CEF develop.
01:35:53.229 --> 01:35:54.419 I'm gonna bring in Syspro develop.
01:35:54.429 --> 01:35:55.839 I'm gonna use the templates branch.
01:35:55.949 --> 01:35:57.339 I'm gonna call it fireside.
01:35:57.569 --> 01:35:58.939 So my son is gonna come in here.
01:35:59.009 --> 01:36:00.699 It's gonna create all the connectors.
01:36:00.709 --> 01:36:02.119 It's gonna clone down core.
01:36:02.209 --> 01:36:03.759 It's gonna build them all together in a solution.
01:36:03.769 --> 01:36:06.247 It's going to set up an external key database and we're going to
01:36:06.247 --> 01:36:06.819 be ready to go.
01:36:06.829 --> 01:36:08.339 So now I can come in and see D fireside.
01:36:11.719 --> 01:36:11.959 Oops.
01:36:15.649 --> 01:36:16.279 Come in.
01:36:16.389 --> 01:36:19.059 Bring up my File Explorer, bring that over.
01:36:21.309 --> 01:36:25.131 From another monitor, open this in connect and now I have a
01:36:25.131 --> 01:36:28.698 working solution out of the box stood up that has those
01:36:28.698 --> 01:36:29.399 connectors.
01:36:31.299 --> 01:36:35.207 What those connectors are has been optimized over the last
01:36:35.207 --> 01:36:39.182 year to be able to stand up a basic sync very, very quickly
01:36:39.182 --> 01:36:40.639 and that's been focus.
01:36:40.649 --> 01:36:42.649 #2 is improving the development experience.
01:36:42.699 --> 01:36:44.789 Before we had to write these connectors by hand.
01:36:44.799 --> 01:36:45.969 It was kind of a pain.
01:36:46.199 --> 01:36:48.749 Now we have documentation that comes out of the box here.
01:36:49.219 --> 01:36:52.762 The connectors themselves have been tediously gone through so
01:36:52.762 --> 01:36:55.677 that they're not supporting specific entities, but
01:36:55.677 --> 01:36:57.849 genericized across the entire system.
01:36:58.099 --> 01:37:01.094 So if you've ever wondered why the estimates for creating a
01:37:01.094 --> 01:37:03.989 base connector have gone up and creating the common model
01:37:03.989 --> 01:37:06.984 mappings have gone up, it's because we're not just creating
01:37:06.984 --> 01:37:10.079 a sales order entity, creating a product entity, we're taking
01:37:10.079 --> 01:37:13.323 that connector, reading through all of its documentation, trying
01:37:13.323 --> 01:37:15.869 to understand that system as best we can, and then
01:37:15.869 --> 01:37:18.864 architecting a solution that could not only cover more than
01:37:18.864 --> 01:37:21.559 just those base entities, but be expanded on quickly.
01:37:22.399 --> 01:37:25.254 And that's that's the bigger piece is it's not the base
01:37:25.254 --> 01:37:27.956 entities that usually cause problems on these client
01:37:27.956 --> 01:37:30.709 projects, it's more the customizations aren't getting
01:37:30.709 --> 01:37:33.972 done fast enough or it's a new aspect of that connector that we
01:37:33.972 --> 01:37:35.349 haven't worked with before.
01:37:35.359 --> 01:37:38.881 So having a base architecture that works to expand quickly has
01:37:38.881 --> 01:37:39.999 really helped a ton.
01:37:40.939 --> 01:37:43.429 So what that means is all of these connectors have.
01:37:43.479 --> 01:37:46.864 If you read these base methods here, just standard search,
01:37:46.864 --> 01:37:50.019 async list, async, create, update, upsert, push all of
01:37:50.019 --> 01:37:53.461 these different methods that just take in generics to where
01:37:53.461 --> 01:37:56.789 it wouldn't matter as long as we've built these properly.
01:37:56.939 --> 01:38:00.508 What entity you're passing in this is going to cover all of
01:38:00.508 --> 01:38:02.769 those scenarios, so it's not perfect.
01:38:02.779 --> 01:38:06.414 There's some systems that just are hard to genericize, but Ben,
01:38:06.414 --> 01:38:09.708 like Scarlett, has done a fantastic job of building these
01:38:09.708 --> 01:38:13.002 systems out to where this satellites for these these hard
01:38:13.002 --> 01:38:16.239 systems like Sage, they cover the breadth of the system.
01:38:16.389 --> 01:38:19.513 So it's not just we support products out of the box and it's
01:38:19.513 --> 01:38:20.179 only pushing.
01:38:20.329 --> 01:38:24.753 We're trying to genericize these across the board, so that's been
01:38:24.753 --> 01:38:27.099 like I said, another massive push.
01:38:27.149 --> 01:38:30.568 What that means is if we can develop customizations quickly,
01:38:30.568 --> 01:38:34.042 what we ought to be able to do is deploy those customizations
01:38:34.042 --> 01:38:34.939 quickly as well.
01:38:35.399 --> 01:38:39.268 So what that would look like is we would go through and say OK
01:38:39.268 --> 01:38:43.077 deploy, but Ash, now I have my deployment script and I'll say
01:38:43.077 --> 01:38:45.779 OK, I made a change to this client project.
01:38:45.789 --> 01:38:46.959 I wanna push this to stage.
01:38:47.149 --> 01:38:49.139 We can just tell it it's going to the stage box.
01:38:49.409 --> 01:38:53.315 This is going to build zip, deploy, restart, connect so that
01:38:53.315 --> 01:38:56.709 this is running on the client system just like that.
01:38:56.789 --> 01:39:00.631 So deployment now, as long as it's clarity hosted, I broke it,
01:39:00.631 --> 01:39:04.106 but as long as it's clarity hosted would be a very, very
01:39:04.106 --> 01:39:04.899 fast process.
01:39:05.319 --> 01:39:09.279 So if I unbreak this and we redeploy.
01:39:11.799 --> 01:39:14.628 We should be able to see this go up to the client box and then
01:39:14.628 --> 01:39:17.322 the connect instance that's running would automatically get
01:39:17.322 --> 01:39:18.849 restarted and we'd be good to go.
01:39:19.019 --> 01:39:23.281 So now you see it's shipping and this takes just a small amount
01:39:23.281 --> 01:39:25.279 of time and we're ready to go.
01:39:25.319 --> 01:39:30.411 Connect is redeployed, so we are unzipping it over on the other
01:39:30.411 --> 01:39:30.809 side.
01:39:30.879 --> 01:39:32.709 It's now running inside the host three container.
01:39:32.819 --> 01:39:35.330 We could see it running over there and we could navigate to
01:39:35.330 --> 01:39:37.800 Bishop two stage connect or whatever and see their new and
01:39:37.800 --> 01:39:38.679 updated code running.
01:39:40.629 --> 01:39:43.499 Along with that, we've completed the upgrade to net eight.
01:39:43.509 --> 01:39:46.122 So we're running the latest and greatest all of the connectors
01:39:46.122 --> 01:39:46.869 have been updated.
01:39:46.879 --> 01:39:49.349 Thank you JL for doing a huge huge favor.
01:39:49.359 --> 01:39:52.207 I think Jim will forever thank you for updating the GP
01:39:52.207 --> 01:39:54.019 connector so that it supports net.
01:39:54.029 --> 01:39:57.621 It's been one of our biggest pain points, but I believe all
01:39:57.621 --> 01:40:01.272 the connectors now are now on the latest NET Framework, so a
01:40:01.272 --> 01:40:02.589 big improvement there.
01:40:03.489 --> 01:40:04.159 You're here.
01:40:03.879 --> 01:40:06.609 Oh yeah, yeah.
01:40:04.229 --> 01:40:04.799 Good job guys.
01:40:06.819 --> 01:40:10.176 So then along with that, all of that to say what we're trying to
01:40:10.176 --> 01:40:13.429 do is get to where we have truly out of the box functionality.
01:40:13.819 --> 01:40:17.251 So for our clients, what they care about is what does it do
01:40:17.251 --> 01:40:18.109 out of the box?
01:40:18.499 --> 01:40:21.867 So what we are doing now is taking what we've gained in
01:40:21.867 --> 01:40:25.656 knowledge and architecture on these projects and extrapolating
01:40:25.656 --> 01:40:26.679 it out so to say.
01:40:26.779 --> 01:40:29.249 Here's what we can do with a new project.
01:40:29.309 --> 01:40:31.614 So because we're working with these different partners,
01:40:31.614 --> 01:40:34.043 they're bringing us some of these similar deals in all the
01:40:34.043 --> 01:40:34.249 time.
01:40:34.419 --> 01:40:37.499 So Interpayments is looking at a lot of P21 to pay hub deals.
01:40:37.859 --> 01:40:41.889 So what we need to be able to do is say 4 P 21 to pay hub.
01:40:42.119 --> 01:40:45.083 We are going to build these opinionated workflows with the
01:40:45.083 --> 01:40:48.097 customization points clearly defined to be able to say to a
01:40:48.097 --> 01:40:48.449 client.
01:40:48.539 --> 01:40:53.136 Here's the documentation that you get when you buy our P21 to
01:40:53.136 --> 01:40:54.619 pay hub integration.
01:40:54.799 --> 01:40:57.956 Here's what it does out of the box, and here's the areas that
01:40:57.956 --> 01:41:00.858 you can customize in how so this is going to be the next
01:41:00.858 --> 01:41:03.149 iteration of connect to be able to stand up.
01:41:03.159 --> 01:41:07.309 These integrations very quickly to say this is connect.
01:41:07.369 --> 01:41:08.819 Here's what it does out of the box.
01:41:09.019 --> 01:41:12.182 Not only does connect do this thing out of the box, but your
01:41:12.182 --> 01:41:15.449 particular systems do this thing out of the box, and we expect
01:41:15.449 --> 01:41:18.612 these workflows, if they're not so say you don't want to use
01:41:18.612 --> 01:41:21.775 web, something we can change that we can customize, but this
01:41:21.775 --> 01:41:23.279 is what we do out of the box.
01:41:23.689 --> 01:41:27.166 So I anticipate that being the next big transformation for
01:41:27.166 --> 01:41:30.583 connect, especially when it comes to client satisfaction,
01:41:30.583 --> 01:41:32.999 right, because we're going to tell them.
01:41:33.109 --> 01:41:35.339 Here's what we do out of the box.
01:41:35.349 --> 01:41:38.461 Instead of saying, how would you like this to look, which is just
01:41:38.461 --> 01:41:41.384 too big of a a broad spectrum for a client, and they're gonna
01:41:41.384 --> 01:41:42.799 take too much liberty with it.
01:41:42.969 --> 01:41:46.088 So this will let us come up with better estimates, better initial
01:41:46.088 --> 01:41:49.018 architecture, better discovery process because we can clearly
01:41:49.018 --> 01:41:51.995 say, hey, if you refer to the documentation, look this is what
01:41:51.995 --> 01:41:52.279 we do.
01:41:52.509 --> 01:41:53.719 We're only doing updates.
01:41:53.729 --> 01:41:56.987 We're not doing creations or whatever for that particular
01:41:56.987 --> 01:42:00.357 system, and we can more clearly define what is your CONNECT
01:42:00.357 --> 01:42:03.727 project going to look like without as much hassle as far as
01:42:03.727 --> 01:42:05.749 like discovery hours to figure out.
01:42:05.799 --> 01:42:07.199 Oh, this is a standard integration, right?
01:42:08.069 --> 01:42:11.384 So for us on the Connect team, these three areas, you know it's
01:42:11.384 --> 01:42:14.543 it's been like I said a huge undertaking, but one of the the
01:42:14.543 --> 01:42:17.702 biggest improvements I've seen over the years that I've been
01:42:17.702 --> 01:42:20.810 here in a single year is not only just rewriting the entire
01:42:20.810 --> 01:42:23.814 version of connect, taking what we learned from the past,
01:42:23.814 --> 01:42:26.714 bringing it forward, updating the whole thing, creating
01:42:26.714 --> 01:42:27.439 documentation.
01:42:28.049 --> 01:42:30.883 So like I said, huge kudos to the team for going through and
01:42:30.883 --> 01:42:31.719 doing all of this.
01:42:31.729 --> 01:42:33.379 It's been a monumental amount of work.
01:42:33.559 --> 01:42:37.487 At the same time as juggling, the client needs, so I just want
01:42:37.487 --> 01:42:38.859 to say thank you guys.
01:42:38.869 --> 01:42:39.589 It's been an awesome year.
01:42:42.369 --> 01:42:42.929 Here, here.
01:42:42.499 --> 01:42:45.159 I threw a I threw a question in chat.
01:42:42.559 --> 01:42:44.399 Any questions?
01:42:42.939 --> 01:42:44.829 Well said, very well said.
01:42:44.409 --> 01:42:44.739 Comments.
01:42:44.749 --> 01:42:44.949 Concerns.
01:42:46.459 --> 01:42:46.819 What's that?
01:42:47.649 --> 01:42:48.989 I threw a quick question in chat.
01:42:50.139 --> 01:42:51.149 The new mapping UI.
01:42:51.219 --> 01:42:53.969 Ah yes, it's a focus.
01:42:54.759 --> 01:42:58.126 I think that the the bigger piece has been this one, so it
01:42:58.126 --> 01:43:01.265 would be on the 2024 road map where we're torn between
01:43:01.265 --> 01:43:04.689 creating a better scheduler versus creating the mapping UI.
01:43:04.699 --> 01:43:08.809 So in my eyes, it's one of those things where we are running into
01:43:08.809 --> 01:43:12.172 limitations of hanging fire itself so that the client
01:43:12.172 --> 01:43:15.909 projects aren't able to perform at the bandwidth they need.
01:43:16.119 --> 01:43:18.689 So I'm torn on whether or not you know.
01:43:18.699 --> 01:43:20.877 Should we create a more performant version of a
01:43:20.877 --> 01:43:23.009 scheduler or should we give them a mapping UI?
01:43:23.259 --> 01:43:24.469 It's a tough choice in my eyes.
01:43:24.479 --> 01:43:27.216 And Ron, I'd love to have more conversations with you to say
01:43:27.216 --> 01:43:30.132 from a value perspective, from a client perspective, yeah, let's
01:43:27.389 --> 01:43:28.209 Let's do both.
01:43:29.589 --> 01:43:29.809 Yeah.
01:43:30.099 --> 01:43:31.059 I know it's not that easy.
01:43:30.132 --> 01:43:31.029 do both the exactly.
01:43:31.039 --> 01:43:31.439 I love it.
01:43:32.649 --> 01:43:35.545 Yeah, unfortunately, unfortunately I'd prioritize
01:43:32.759 --> 01:43:33.509 Yeah, I love it.
01:43:35.545 --> 01:43:39.194 scheduler, although personally I'd want the UI the mapping UI,
01:43:38.579 --> 01:43:39.139 I know, right?
01:43:39.194 --> 01:43:39.889 right? Yeah.
01:43:39.979 --> 01:43:42.796 I'd love to see a better product or better looking product that
01:43:42.796 --> 01:43:45.524 we can give to clients, but you know, like I said, ultimately
01:43:44.569 --> 01:43:44.809 Yep.
01:43:45.524 --> 01:43:47.329 this just runs in the background, right?
01:43:47.339 --> 01:43:48.799 Like they don't wanna look at it.
01:43:48.809 --> 01:43:50.929 The less they have to look at it, the better job we're doing.
01:43:51.039 --> 01:43:53.676 So if they're looking at connect, it's because there's an
01:43:53.676 --> 01:43:53.949 issue.
01:43:53.959 --> 01:43:55.819 Most of the time, so that's how I see it.
01:43:55.729 --> 01:43:59.144 Right side, though, uh, part of getting that scheduler will be
01:43:59.144 --> 01:44:02.016 somewhat of a new UI, so that would at least lay the
01:44:01.599 --> 01:44:01.779 Yep.
01:44:02.016 --> 01:44:05.539 groundwork with even having the ability to have it about the UI.
01:44:05.989 --> 01:44:06.469 Exactly.
01:44:07.109 --> 01:44:07.329 Yeah.
01:44:10.839 --> 01:44:12.119 So yeah, on the road map for sure.
01:44:14.199 --> 01:44:17.695 But like I said, the idea for me would be getting these out of
01:44:14.359 --> 01:44:14.679 Thanks.
01:44:17.695 --> 01:44:18.139 the way.
01:44:18.149 --> 01:44:21.673 Now you know it's it's a larger initial investment that as these
01:44:21.673 --> 01:44:25.197 connectors mature out, we should be able to knock out the client
01:44:25.197 --> 01:44:28.450 projects, deliver on that SAS license, use that profit like
01:44:28.450 --> 01:44:31.811 Chris said with the Clarity Lab stuff to be able to invest in
01:44:31.811 --> 01:44:35.172 our product and really have that transformation that next big
01:44:35.172 --> 01:44:38.317 Leap only having a better framework to fall back on while
01:44:38.317 --> 01:44:40.919 we do that which is what we didn't have for C4.
01:44:46.469 --> 01:44:46.739 Yeah.
01:44:46.749 --> 01:44:51.078 I think one of the other things that's really interesting is
01:44:51.078 --> 01:44:55.335 just like basic UM, like simple activities where things are
01:44:55.335 --> 01:44:59.664 currently like in different places where someone has to kind
01:44:59.664 --> 01:45:04.134 of know or get to them somehow and making it, you know, really
01:45:02.669 --> 01:45:02.999 Umm.
01:45:04.134 --> 01:45:08.108 straightforward and another like, so an example of that
01:45:08.108 --> 01:45:11.869 would be like all of the different system documents.
01:45:13.749 --> 01:45:17.773 Certainly something that the CONNECT team is is well versed
01:45:17.773 --> 01:45:21.595 in accessing and and even updating directly, but getting
01:45:21.595 --> 01:45:25.686 that so it's available well probably not available, but just
01:45:25.686 --> 01:45:29.575 like, umm, everyone knows where the links are because I'm
01:45:29.575 --> 01:45:32.459 guessing it's available to the whole team.
01:45:31.329 --> 01:45:31.579 Umm.
01:45:33.419 --> 01:45:37.174 Umm, but just making sure the links are in a place where
01:45:37.174 --> 01:45:38.689 everyone can find them.
01:45:38.899 --> 01:45:42.292 I know that the sales team and I'm, I'm sure the project
01:45:42.292 --> 01:45:45.744 management OPS team might occasionally need them as well,
01:45:44.869 --> 01:45:45.169 Right.
01:45:45.744 --> 01:45:49.315 but I'm sure the sales team will use them occasionally with
01:45:48.289 --> 01:45:48.589 Yeah.
01:45:49.315 --> 01:45:50.089 access, yeah.
01:45:49.539 --> 01:45:51.369 And the idea would be JL.
01:45:51.379 --> 01:45:52.489 Could you share the link to?
01:45:56.069 --> 01:45:58.039 The documentation we created the MD book.
01:46:07.069 --> 01:46:10.317 And so the idea would be, you know, nuclino's fantastic,
01:46:08.099 --> 01:46:08.479 You're muted.
01:46:10.317 --> 01:46:10.659 right?
01:46:10.669 --> 01:46:15.709 We wanna have nuclino to where it's a centralized place.
01:46:15.719 --> 01:46:16.439 So you can go right now.
01:46:16.449 --> 01:46:17.479 These live inside Azure.
01:46:17.549 --> 01:46:20.380 The reason we put them in Azure so that we can track the changes
01:46:20.380 --> 01:46:22.209 and stuff having these in source control.
01:46:22.389 --> 01:46:23.659 Obviously very, very important.
01:46:23.769 --> 01:46:26.614 So what we've started doing for some of these client projects is
01:46:26.614 --> 01:46:28.846 taking this type of documentation and if you go to
01:46:28.846 --> 01:46:31.559 the link that JL provided and he'll throw a password and then
01:46:31.559 --> 01:46:31.909 to chat.
01:46:33.859 --> 01:46:37.920 This is a hosted documentation that the client can log on and
01:46:37.920 --> 01:46:41.719 look at which is gonna be different than nuclino or Azure
01:46:41.719 --> 01:46:42.309 would be.
01:46:42.399 --> 01:46:47.170 So we have this, this guy and now we can log in and we have
01:46:47.170 --> 01:46:52.100 documentation for the project that the client can take a look
01:46:52.100 --> 01:46:52.339 at.
01:46:52.349 --> 01:46:55.424 So a technically minded client or the FSD all of these things,
01:46:55.424 --> 01:46:58.451 could live inside here that we could all browse them and view
01:46:58.451 --> 01:47:00.989 them and have them contained within source control.
01:47:04.379 --> 01:47:08.021 Another benefit is we're more able to add modifications to
01:47:08.021 --> 01:47:11.355 this page than we can with nuclino so that we can add
01:47:11.209 --> 01:47:11.319 OK.
01:47:11.355 --> 01:47:14.997 custom formatting and stuff that's automated versus having
01:47:14.997 --> 01:47:16.849 to manage it for each section.
01:47:19.089 --> 01:47:20.439 Let's not worrying about someone.
01:47:19.219 --> 01:47:21.609 We may end up going to something like this.
01:47:21.709 --> 01:47:22.369 Ohh sorry, go ahead.
01:47:22.889 --> 01:47:26.125 I was gonna say and not worrying about someone accidentally
01:47:26.125 --> 01:47:28.659 erasing something because we've had documents.
01:47:26.549 --> 01:47:26.819 Umm.
01:47:28.669 --> 01:47:32.935 Just lose demo videos and we're like we have no idea what was
01:47:29.019 --> 01:47:29.389 Ohh.
01:47:32.935 --> 01:47:33.279 here.
01:47:33.289 --> 01:47:34.959 Something was here Once Upon a time.
01:47:35.109 --> 01:47:36.829 We have no idea what, but.
01:47:36.629 --> 01:47:39.978 I can personally tell you with new cleaner when I think Justin
01:47:39.978 --> 01:47:42.955 and I were first starting, we would we had both deleted
01:47:42.955 --> 01:47:46.411 something out of the onboarding videos because we had our cursor
01:47:44.849 --> 01:47:46.389 Yep, to write a.
01:47:46.411 --> 01:47:47.049 on the page.
01:47:47.479 --> 01:47:48.829 It's a right of passage, really.
01:47:49.679 --> 01:47:50.219 Exactly.
01:47:50.209 --> 01:47:50.419 Yeah.
01:47:52.789 --> 01:47:56.755 Yeah, we are using it for fine tuning training, so I am running
01:47:56.755 --> 01:48:00.039 backups of it that way and then we download backups.
01:48:00.049 --> 01:48:04.190 But still, yeah, we we definitely need to do a separate
01:48:04.190 --> 01:48:08.701 project to pursue a different wiki tool at some point in the
01:48:08.701 --> 01:48:09.219 future.
01:48:09.229 --> 01:48:11.959 So that's a good call out, but this is great.
01:48:11.419 --> 01:48:11.599 Yep.
01:48:11.969 --> 01:48:12.179 OK.
01:48:12.189 --> 01:48:13.149 And so can we link this?
01:48:13.569 --> 01:48:16.795 Umm, just and you may have already said this, just
01:48:16.795 --> 01:48:19.199 confirming like from nuclino to this.
01:48:18.709 --> 01:48:18.969 Right.
01:48:19.209 --> 01:48:22.059 Just so OK, cool. Awesome.
01:48:20.399 --> 01:48:21.019 Yep, Yep.
01:48:22.919 --> 01:48:25.684 And one thing that you can't quite see right now actually
01:48:25.684 --> 01:48:28.449 broke some reason I'm trying to fix it in the background.
01:48:28.779 --> 01:48:31.769 There are comments that could be left on the page.
01:48:32.399 --> 01:48:35.080 You can't leave it on a particular part of the page, but
01:48:35.080 --> 01:48:37.149 you can obviously you know, just reference.
01:48:37.529 --> 01:48:39.489 Hey, here's the quote from this.
01:48:39.919 --> 01:48:41.799 This doesn't sound right to me, right?
01:48:42.599 --> 01:48:42.799 Yep.
01:48:43.509 --> 01:48:44.989 If you if you minutes here, I'll put.
01:48:43.699 --> 01:48:45.469 So a little collaborative environment for the clients.
01:48:46.069 --> 01:48:47.699 I'll put in chat once that's fixed up.
01:48:48.379 --> 01:48:48.609 Perfect.
01:48:53.349 --> 01:48:54.099 OK, awesome.
01:48:54.289 --> 01:48:55.689 Any other questions, feel free.
01:48:57.599 --> 01:49:01.659 Or comments and then I'll wrap us up if not.
01:49:03.119 --> 01:49:05.329 I have a a comment or question.
01:49:05.029 --> 01:49:05.499 Please.
01:49:05.929 --> 01:49:06.409 Yeah please.
01:49:06.059 --> 01:49:06.279 Yep.
01:49:06.149 --> 01:49:10.664 You know who else needs a better scheduling system and an and a
01:49:10.664 --> 01:49:11.369 UI for it?
01:49:13.169 --> 01:49:13.329 Who?
01:49:13.399 --> 01:49:15.409 A little a little bird named Phoenix.
01:49:15.529 --> 01:49:17.549 Chris, Chris.
01:49:17.269 --> 01:49:17.899 Perfect.
01:49:17.599 --> 01:49:18.789 Chris does for Sydney.
01:49:17.909 --> 01:49:18.859 Let's let's chat.
01:49:18.869 --> 01:49:19.469 Let's work together.
01:49:19.199 --> 01:49:20.109 Yeah, I do.
01:49:20.119 --> 01:49:21.929 I need to know I scheduling tool.
01:49:22.159 --> 01:49:25.069 Yeah, that would be a great Christmas present.
01:49:25.649 --> 01:49:27.359 To do schedule a tool code, they've Sydney.
01:49:28.049 --> 01:49:28.399 Yeah.
01:49:28.409 --> 01:49:32.299 Our our OPS team would appreciate that. Awesome.
01:49:35.049 --> 01:49:35.279 Cool.
01:49:35.289 --> 01:49:35.679 Thanks guys.
01:49:35.339 --> 01:49:35.759 Umm.
01:49:36.549 --> 01:49:38.079 Well, thank you, Sir Rose.
01:49:38.089 --> 01:49:38.509 Umm.
01:49:38.519 --> 01:49:40.399 And and thank you to the CONNECT team members.
01:49:40.409 --> 01:49:41.599 Great work everyone.
01:49:41.669 --> 01:49:45.894 It has been a lot that that you've each pressed on this year
01:49:45.894 --> 01:49:50.328 and you know I think that's so powerful that as a team, each of
01:49:50.328 --> 01:49:53.999 you are contributing in different areas of strength.
01:49:54.549 --> 01:49:56.519 And I'm sure that makes it more enjoyable.
01:49:57.049 --> 01:50:01.169 It's really nice to see too, that we're making headway and
01:50:01.169 --> 01:50:05.009 we're we're sort of owning the ground once we take it.
01:50:05.649 --> 01:50:06.019 Umm.
01:50:06.489 --> 01:50:09.368 And I think that's been one of the challenges, you know
01:50:09.368 --> 01:50:09.779 overall.
01:50:09.789 --> 01:50:12.906 So I think with Jeremy's leadership and with each of your
01:50:12.906 --> 01:50:16.022 individual leadership and your respective area, it's it's
01:50:16.022 --> 01:50:17.849 working and we're making headway.
01:50:17.859 --> 01:50:18.589 So great work.
01:50:20.679 --> 01:50:25.141 I like we got a video from Brent on a I I'm gonna share that in
01:50:25.141 --> 01:50:25.769 the chat.
01:50:25.779 --> 01:50:26.569 So you have it.
01:50:27.199 --> 01:50:32.013 I also went ahead and did a chat GPT E and asked it to make us a
01:50:32.013 --> 01:50:36.309 little poem for the end of the year going into next year.
01:50:37.359 --> 01:50:41.289 I think it is quite funny, but also kind of cool.
01:50:41.579 --> 01:50:44.689 So I'm just gonna post that into the chat right now.
01:50:45.599 --> 01:50:50.439 So you can check that out and let's see.
01:50:50.699 --> 01:50:51.889 It's pretty verbose.
01:50:51.899 --> 01:50:56.539 I think it, I think it took a a page from the Chris Reddick
01:50:56.539 --> 01:50:58.859 book, but take a look at that.
01:50:58.869 --> 01:50:59.209 Awesome.
01:50:59.659 --> 01:51:01.199 A poem?
01:51:01.209 --> 01:51:05.915 I think it's pretty amazing, uh, but just one of the things that
01:51:05.915 --> 01:51:10.620 I'll note is it really has been a a lot for a lot of growth that
01:51:10.620 --> 01:51:13.299 we've had within the team this year.
01:51:13.309 --> 01:51:16.339 We we have grown our top line revenue.
01:51:16.949 --> 01:51:22.077 I think that our client SAT has dramatically improved just with
01:51:22.077 --> 01:51:23.279 objective data.
01:51:23.729 --> 01:51:27.887 We certainly have a substantial amount of recurring revenue and
01:51:27.887 --> 01:51:31.915 a large amount of our revenue comes from client projects that
01:51:31.915 --> 01:51:33.929 keep coming back with new work.
01:51:34.079 --> 01:51:37.487 And so that's always a good way to measure what client SAT is is
01:51:37.487 --> 01:51:39.269 you know, what their behavior is.
01:51:39.359 --> 01:51:43.493 Umm and uh, you know, I think one of the other things just
01:51:43.493 --> 01:51:47.277 going into this next year is reflecting on how we can
01:51:47.277 --> 01:51:51.831 continue to make headway and how myself and the other leaders on
01:51:51.831 --> 01:51:56.175 the team can serve each of you individually to help make sure
01:51:56.175 --> 01:51:59.959 that you're moving ahead in the way that you want to.
01:52:00.709 --> 01:52:03.699 Certainly for me, let me let me turn my camera back on here.
01:52:04.149 --> 01:52:04.729 So wrap up.
01:52:05.659 --> 01:52:10.456 Certainly for me, I can tell you that I really consider it to be
01:52:10.456 --> 01:52:14.958 a, you know, a responsibility for the role that I'm in to be
01:52:14.958 --> 01:52:18.869 able to serve and help you get where you want to go.
01:52:19.459 --> 01:52:24.149 We made the leadershape and then the level of meetings.
01:52:24.199 --> 01:52:26.949 So you're welcome to attend those if you're interested.
01:52:27.279 --> 01:52:31.538 And we also record those, if you'd like to get Nuggets and
01:52:31.538 --> 01:52:35.652 have accountability for areas where you want to grow and
01:52:35.652 --> 01:52:39.839 improve and just generally ideally learn from experience.
01:52:39.849 --> 01:52:40.809 That was hard.
01:52:40.859 --> 01:52:44.698 Hard earned and expensive without having to pay those dues
01:52:44.698 --> 01:52:45.219 in full.
01:52:45.229 --> 01:52:47.599 Hopefully so.
01:52:47.649 --> 01:52:51.765 I've personally just wanna say as we go into the holidays here,
01:52:51.765 --> 01:52:55.559 certainly wishing each of you a very happy holiday season.
01:52:56.269 --> 01:53:00.172 I certainly hope that you have safe travel and for those of you
01:53:00.172 --> 01:53:03.830 who are off next week, I hope you have a very relaxing week
01:53:03.830 --> 01:53:06.879 off and you know everyone has the next four days.
01:53:06.889 --> 01:53:09.679 So I hope you have an awesome weekend.
01:53:09.719 --> 01:53:10.949 An awesome holiday.
01:53:10.999 --> 01:53:13.623 Get all the presents that you want and that you got all the
01:53:13.623 --> 01:53:16.029 presents that you should have gotten for other people.
01:53:17.059 --> 01:53:18.589 But yeah, happy Friday.
01:53:18.679 --> 01:53:20.869 Hope you have an awesome holiday.
01:53:20.979 --> 01:53:22.469 Anything else to wrap us up?
01:53:22.479 --> 01:53:22.829 Feel free.
01:53:23.759 --> 01:53:24.719 At the holidays, y'all.
01:53:23.959 --> 01:53:24.419 Anyone else?
01:53:25.719 --> 01:53:26.869 Alright, awesome.
01:53:25.889 --> 01:53:26.439 Yeah.
01:53:26.509 --> 01:53:27.089 Merry Christmas.
01:53:27.199 --> 01:53:28.069 Thanks, everyone.
01:53:28.419 --> 01:53:28.709 Yeah.
01:53:28.719 --> 01:53:29.359 Merry Christmas.
01:53:29.369 --> 01:53:30.209 Happy holidays.