Meeting with Sharik Peck and his wife Cheryl Peck. They own and operate Maximum Function Physical Therapy and a company called Rezzimax (managing pain and stress through tuned/calibrated vibration therapy). I've known the Pecks for years and I wanted to get some ideas and info on entrepreneurship, crowdfunding, and basic advice for business. They served up a might big helping...

We met at the bagel shop in Smithfield and chatted for about an hour and a half. Great meeting. See attached for some scribbled notes. We talked about a number of fun topics. Here are some of my notes:

- One of the first things that Cheryl said was - pay your tithing. We talked about tithing and making generous contributions (oferings) to God and church. Pay more than you think you can. You can't out do God's blessings.

- Turn your existing customer base into your brand or product ambassadors. They know it, use it, and hopefully love it. Use that momentum. Help to educate them so that they can pass it along. It's totally worth spending time and money on this group. Incentivize them with products, education, and other money or perks. In a way, try to duplicate yourself. Sharik really spent some time talking about this. It seems to be a big key and a great group where you can focus both energy and efforts.

- Your product should have a tiered structure with incentives and other benefits. We talked about entry level, basic certifications or cert levels, and ambassadors or torchbearer levels. If they are excited about your product or service, they will tell others.

- Promote your success stories - use testimonials, small videos, word of mouth, and natural networking.

- Don't try to sell - just share the possible - It's ok if the purchase is delayed a bit - they may circle back around and really want what you have to offer. Let them want it and seek after it.

- Financial takes care of itself - help people and help the world.

- God and an abundant model - put your trust in God, be willing to do His will. A mindset change and then let God take over. Don't try to limit God.

- Knowledge - share, share, share - if you died and didn't share, that would be tragic - knowledge not shared is knowledge not gained (I don't know who said that, but it was a quote from someone).

- My job - leave as many people with understanding of what I know before leaving this world

- We talked about public speaking and asking to speak at events. Getting the word out - from the source. Not every speaking gig is the right fit. Know when to walk.

- From Jeff Young - 2 things about employees. Give it a 3-month trial period. If it is right, you will be happy and will gladly write that check (virtually everyday).

- Recipes and allowing those recipes (with their ingredients or pieces) to be modified. Some sort of starting point and/or package. It could always be tweaked, but it is at least a good starting point to build off of.

- Sometimes your biggest critics can be your best promoters and biggest fans.

- Ideas on doing your own conferences and putting on your own events. For their company, the highest level of cert requires an in-person training event. Getting everybody together in one place is huge. Record it and then use that content. That is worth a ton and there are a number of intangible benefits as well.

- Flexibility - physically and mentally - being flexible and allowing for growth.

We had a great meeting and I learned a ton. See my notes for a few other things that I didn't write down here. Great way to spend the morning!

Got a text from Shari O. asking me to jump on the GoToMeeting session. The guys had spun up a new server and she was trying to get in. We ended up contacting Wayne and Cory and worked through a few things. Some of the settings weren't quite right. We got it all figured out. This seemed like a special case. We had copied images and a database from data 33 to data 39 and then Wayne had flipped some values and ids. Basically, a company needed a full deep copy and then wanted that new corporation to be able to be completely separate and run independently. I'm glad that we have some talented folks on our team. We did something similar years ago and it took me days and days.

Playing the constant game of recording notes. Finished up notes from 6/14/23 and started on 6/15/23. It feels like I'm always about a week behind. I will say this, as you go back through things, it really helps to see the progression of things over time. Good stuff.

Meeting with both Alan and Aspen. I took some notes and Aspen took some notes. After the meeting, I did some more note recording and note digitizing for 6/15/23 and for 6/16/23.

Alan was on with us for the first hour. Here are some of my notes. See attached for all of them.

- Let's build out the MVP for the plan - general fracture or adilas lite planning session - what documents does that mean and/or require?

- Two of the first main things we want to do is define the jelly fish model (business structure) and the value add-on core model. Those two are some known needs of where we are heading.

- We spent quite a bit of time talking about how to break functionality and features up. We want to keep those separate as far as options.

- I showed Alan the presentation gallery and the outline of the business functions. There is quite a bit of work that has already been done there. Great resources.

- Small packages and/or starting points - We could call it whatever - recipes, packages, templates, industry specific skins, presets, etc.

- Alan wanted us to think about tiers and scaling - both vertical and horizontal. I was thinking, what about the Z scale or the depth/layering axis. Just for fun 3D scaling and 3D world building. It might be fun to explore this.

- We talked a little bit about pricing and tier levels. We would like to set breakpoints, ranges, and fees for going over.

- We asked Alan about his vision for adilas lite and fracture - He is really excited about creating a solution that is light weight and very efficient. In his words, he said, How can I get the most power with the least amount of drag? We went on to talk about hiding things that they don't need and getting them to the meat of the operation as quickly as possible. We will do future planning sessions where we look at each section and slim it down to the minimum or minimal requirements.

- This is a side note, but as I have been thinking about minimal pieces, I keep coming back to a concept that we were looking into called standalone declarations (full entries without any other connections and/or supporting documentation). They exist by themselves but they also may be mapped and pointed to the right place. We could sum them up, count them, map them, and keep it super simple. Originally it was going to be something that could be made for financial documents (P&L and the balance sheet)  but technically we could use them in any way. Simple standalone pieces.

- Spend the time and do some market research on what business verticals we could hit and take care of.

- Lots of talk about automation and even automating the setup of new systems. Let people try things out as a free or limited version. We would setup thresholds, limits, ranges, or whatever. We want people to try it out and like it.

- We talked about ice bergs and mountains (perception of how big it is). We also switched and talked about the depth of the water... pretend levels of swimming - Imagine that you are at the beach - you could get your feet wet, do some wading, swimming, snorkeling, or scuba diving. All at the same place, just how deep and serious are you or what are you looking for?

- Once we have a list of things that need to be done and/or worked on, we get to prioritize that list. What do we want to build out and when?

- Alan had the idea of putting our outline information into a database. That way we could just query things (just in time) as needed. That way we could make the lists super small and then allow for it to be expanded at will. Great idea. Simple displays with drill-downs. Almost the presentation gallery for sales, marketing, pricing, features, and education.

- We also want to highlight future plans and what is up and coming. We change things all the time. Make that part of the plan and the part of the presentation. Put it in a database and let our users pull back what information they want and/or need. Self-building templates, feature lists, tiers, and other levels.

Poor Shari O. - I got so busy I totally forgot about this appointment. We will meet up later, but this didn't happen. My bad.

Recording notes for the day. Most of the time was spent working on the notes from a breakfast meeting with Sharik Peck and his wife Cheryl Peck. See element of time # 10252 for more details.