Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

There are notes from this morning... 1/12/26 - these notes may seem personal - they are what happened on Sunday 1/11/26 - I recorded them on Monday. They play into the mix as this is the backing for us trying to do what we are doing. It is personal, but still super important (to me at least).

- I was fasting yesterday - good session - had a great "download" (term from my mother) session and filled out some post-it note pages. See EOT # 12616 for details.

- I spoke in church on Sunday - I had fun - hopefully it went okay - I tried to follow the spirit.

- I also enjoyed some of the other meetings at church - Lee Lower gave a fun thought in Bishopric meeting about a guy and some healing and mending relationships - really good message.

- In the next meeting, young men and young women leader training, Reese Hulbert gave a great thought on Satan and how he tries to make us run and hide - then talking about overcoming that fear and following the Lord - how can we dispel that encroaching darkness, shame, fear, and negative thoughts - super good message.

- I was praying - as I finished, I was looking at a quilt on my bed - the diversity is awesome - all of it fits and lays together to make the whole - so fun.

- During sacrament meeting, Lilly Atkinson spoke on cheering each other along - she ended with a challenge - "take one more step" and "bear your testimony" - I really liked the take one more step challenge. Sometimes, that is all we can do.

- Heather gave a great talk in church as well. I took a bunch of notes in my church notebook - great message - moving forward with joy - becoming - "be" & "coming" - breaking things apart - we all get to be part of His work.

- Plan as if for year - act as if for years - D&C 51:17

- In priesthood meeting, Ed Herrmann, was giving the lesson on new beginnings from Elder Kearon from the October 2025 general conference. Jesus went about doing good - At the end of the lesson - Ed was talking about an action strategy that they use in the military - It was...

1. Intel (info or gather info)
2. Plan
3. Rehearse
4. Execute
5. AAR - Pause (after action report)

- Small note... I was typing these notes and got to the note above this about the military action plan or action strategy. I was able to use that little piece in a meeting that I had with Shannon on 1/13/26. That is awesome. The timing was perfect. I just finished typing it before the meeting and then I had to use it. Small mini miracle and blessing. My notes were able to tie into another piece that I was looking at on Monday night (1/12/26). We were helping our daughter do some goal planning for the new year. In the pamphlet, it kept prompting for putting your goals into this format: Discover, Plan, Act, Review - As I was working with Shannon, I was drawing a parallel between the child goal setting strategy vs the military based strategy. They are very similar. They use different words and the military one has a whole section for rehearsing or practicing before doing the actual event or action. I thought that it was very interesting. I was telling Shannon that she was technically helping me do some planning and rehearsing for where we are heading. Good stuff.

Back to my notes from Sunday, 1/11/26 that I wrote on Monday, 1/12/26... I got side tracked

- After church (on 1/11/26), I spoke with Bryan Dayton and told him that I was planning to talk to Steve tomorrow (Monday) about pushing forward - gave him a few small insights into my plan from my shaving session on Sunday morning - see other notes.

- Came home, played a game with Brooklyn

- Super yummy meal after breaking my fast - potato soup and corn bread

- Made chocolate mousse

- Played a game with Heather and Brooklyn - Heather won

- I got a blessing from my dad - we talked and chatted for a bit and then I got a blessing (father's blessing) - I have had many of these - Lots of great love, advice, inspiration, and remembering my worth - I doubt myself sometimes - Here is some advice that he gave me: Take care of yourself, your family, your church calling, and then your profession. Even though profession is forth on the list, that doesn't mean that you give it a forth rate job. He also felt that I should go and meet with Steve - face to face - really try to help - even help repair the relationship. It has been super stressful. He also recommended that I read a few poems (motivational poems) - I have those in a different notebook.

- On the going out to Salida to meet with Steve, I was thinking, maybe we have a team meeting - in person - to go over plans and such - going back to what Ed said (military strategy - intel, plan, rehearse, execute, AAR (pause - after action report) - focus on the plan and rehears sections.

- I have been in so many meetings... tons of training - that is an asset (meaning church and business meetings)

- Quick 1-pagers - Bishop Shawn Smith loves the quick - at a glance - what is going on

- I saw Reese Hulbert use a few quick - at a glance - one pagers for a training meeting. They really seemed to help.

- Contact Gene to see about getting some funding for a big push. Sent him a text on 1/12/26.

- Graphical homepages

- Finish up the MVP list - Estimating somewhere between $500-$750K to finish up that push and those pieces.

- Work as if for years

Follow-up with USAePay and getting more info on merchant processing stuff. On the phone with Steve talking about all kinds of stuff. Mostly about the multi member LLC and percentage ownership stuff. Steve and I were on the phone for well over an hour and a half. Here are some of my notes... all over the place.

- Trying to get our guys and gals to focus on one thing and getting it all the way finished. From top to bottom. We have a lot of stuff that feels 50-75% done. We want to get it all the way across the finish line. Our goal is to give them a single project so that they can get it all the way finished before moving on. We are hoping that if we extend them some ownership in the company that it will help to motivate them to play the game.

- Need for more news and updates. We also thought that it would be good to do some internal news and updates for our internal staff. That idea came from Steve.

- We need someone who is able to get into some deep JavaScript stuff and really help out there. We have a number of projects that are very heavy in that area and need some loving.

- We chatted about different developers and their skill levels. As a side note, the deeper we get, the more things start breaking down into smaller and smaller pieces. So many interweaving and interlocking pieces. Lots of dependencies and requirements.

- Kelly seems to follow trends very well. It's almost one of her skill sets. In the book, "Who Moved My Cheese", there are two mouse like characters. One is Sniff and the other is Scurry. Kelly seems to have those type of instincts.

- Divesting possible ownership and management options to an outside company. Just playing with options.

- For our internal team, we have been talking about a price of $1,000 per percent of adilas. That is about 1/100 of its actual value. On the open market, 1% would be somewhere between $50,000 to $100,000 at a $10 million dollar valuation.

- Steve was mentioning options for an operating company, a holding company, a management company, and maybe a retirement company. Just talking possible options, down the road.

- There seems to be a huge gap between sales and demos. If we get the demo and get to talk to people and show them what we have, we shine, and they want it. If we can't make it that far, it doesn't go very fast. Kinda interesting but logical.

- We are trying to stir the pot on the sales side of things. We talked about doing a sales sprint, daily sales standup meeting, and getting some of our guys really going and focused there. We really want to manage it properly as well. It is one thing to say go, it is another thing to have a plan, accountability, and be able to measure efforts. We really want to lean on the manage it properly type level.

- As far as sales and travel. We were talking that if they log their miles, we could pay $0.25 per mile. That covers gas and some light wear and tear on the vechiles. We would have them log those miles inside of adilas. Ideally, we would tie that into a general budget for what they are charging us or what we are budgeting for their help.

- We would like our salespeople to stay as local as possible so we don't burn up tons of travel costs. This is at least true for getting started out and getting things up and running.

- One of the goals would be to help the guys and gals be more accountable. Along with that, dealing with sales, we need them to log the contacts, touches, and daily standup meetings. Ideally, we want to record these notes as real-time as possible, while they are fresh in your minds.

- Sales is a game of numbers. The numbers should tell the story.

- I'm going to reach out to Shawn and get his instructions for his sales and contacts that need to be logged into adilas, in the CRM (customer relationship management) section of the site. See attached.

- Both Steve and Sean would be the main contacts for the sales guys. The main adilas morning meeting would have a small standup for sales everyday.

- For me, keep pushing out gift cards as we get them - perks for the guys and gals.

- Steve and I went over some percentages and who was going to be selling what percentages. We made a list on a spreadsheet. Our initial internal offering is going to be 5% from Steve and 5% from Brandon. These will be sales made to us as individuals - checks made out to Brandon or to Steve vs adilas llc. We will come up with a promissory note of sorts to document the sales of those percentages.

- There is huge value in getting in there, out there, doing it and learning from your mistakes and successes. We build and break, we build and break. Don't overthink it! Just keep going!

- When we present our offer to the guys and gals, Steve wants it to be pretty simple. This is the deal. If you want to play, great. If not, here are the options. Keep it as simple as possible.

- In closing, Steve was making some comments on having sufficient money to play and make other plans. Hinting at some other fun things to come... It just keeps going!

Steve and I ended up working on a training session with Sean. The whole thing was dealing with stock/units, floorplans, and adding in subs to stock/units. Things like outside repairs, internal ticket, interest, shipping, and even phantom costs and adjustments like slush fund stuff.

On a GoToMeeting session with Shawn going over plans for 2021 payroll stuff. Shawn is going to work on states and John and I are going to do federal taxes and forms.

Met up with Shawn Curtis to talk about payroll and plans. After that, I got in and did some testing on the changes to the check writing app for adilas. I made some notes and sent some scans back to Spencer.

Payroll stuff - I spaced this appointment. It didn't happen. I sent Shawn a text and we'll reschedule. My bad.

Helping Shawn get his local environment setup and back up to speed. Sometimes, Shawn takes big breaks between times of working with us and what not. We re-cloned some code and repository stuff for him to give him a new start.

Bryan coordinated a late night, after hours, code push for 2 corporations on the data 3 server. Kelly, Anita, Bryan, and I were on the call. We got things up and got the thumbs up from the client.

Met up with Shawn Curtis to setup some times to meet to do payroll stuff and update all of the new withholding settings for 2021.

Checking in with Shawn and responding to emails dealing with payroll. Quick touching base. Nothing major.

Did the digital hand-off with Shawn to check the new payroll changes and code. He had done lots of the original stuff, I made some changes, and just passing it back to him for a review on his end.

Shawn and I were looking over payroll changes and touching base.

Texting back and forth. Shawn is still advancing the ball on the new W-4 and payroll calculations.

Meeting with Shawn to figure out where we are at regarding new 2020 federal payroll calculations. We spent an hour on the GoToMeeting session. Towards the end, we scratched out a plan and Shawn pushed up code for me to work on and clean-up.

Working with Shawn on new 2020 payroll changes and new fields from the W-4 form that need to play in. Big changes this year with federal calculations. Shawn and I were on the GoToMeeting session almost all day. We were on and off from 8 am to 5 pm. I'm only going to claim an active total of 4 hours, but it was an all day deal. We were pushing code back and forth on a branch. I would do something, he would pull it and add to it, and then vice versa.

Going over a plan with Shawn for some new federal W-4 fields and changes. We made a plan and decided to call it a night and hit in the morning on Saturday.

Alan was on the earlier meeting with Chuck and I. After that meeting, we touched base quickly and talked about a few projects. Our goal is to help get a few of the close ones over the finish line.

Our meeting ended early so I started working on the new 2020 state and federal withholdings. I did some testing and pushed up files to all servers. Shawn and I have been working on new withholdings for a few days now. Trying to get everything up and online.

I met up with Shawn over the GoToMeeting channel. I prepped some federal withholdings from an email (data) that he sent me. I then sent it back over to him in a formatted view.

Working with Shawn. He passed me over a few new files with new withholding values and changes. I'll get them pushed in and merged on Monday.

4/6/20: Completed end of March 2020: Brandon and Shawn met and talked about some new needs for 2020 payroll and withholding settings. There are new needs to gather and collect the settings from the W-4 form.

Still to do: They also talked about being able to set up some show/hide settings to show/hide the commissions for trailers, vehicles, toppers, labor, parts, etc. Basically be able to make the whole payroll section more dynamic and be able to change verbiage, show/hide settings, etc.

Shawn and I jumped on the meeting. He was working on 2020 W-4 stuff and other federal withholding stuff for payroll. I was going through emails and uploading new training videos. Other general stuff.

Working on 2020 payroll stuff. Part way through, we found some major changes for Federal withholdings and new settings that are required.

I had an appointment with Shawn but was unable to get ahold of him. I think he is still sick.

The rest of the day was spent catching up on recording notes, brainstorming, and emails. Lots of notes from today. Good stuff.

Didn't hear from Shawn today. He must still be sick.

Spent the time recording notes and trying to get caught up.

Shawn called earlier in the day and wasn't feeling well. No meeting took place but we did touch base.

Emails, tech support, and phone call with Shawn. Also some quick work with Bryan on some adilas API socket stuff for the customer queue.

Shawn gave me a call and we chatted on the phone. He was going to be running some errands so I just worked through the time frame. I did email, recorded notes, and uploaded videos for other elements of time. I also built a small sub menu for the adilas shop and how to manage our different calendars by showing new buttons that filter things based on time templates for monthly, weekly, and daily reports all based on the current time templates (custom stuff for us - internally).

Shawn and I got on a GoToMeeting session. We worked on different projects. I was working on database updates for Oregon, South Carolina, and Vermont. I also did some county updates for Indiana and other small things. We setup another meeting for tomorrow to work on some more new updates. We also got Shawn's local code branch up to date and ready to go. It is amazing how far behind you can get if you don't keep up with the main master branch. Constant change.

Working on state tax withholdings and updates for 2020. Emails, recording notes, and talking with Shawn.

Working on more new 2020 state tax withholding updates.

Working with Shawn on 2020 payroll and tax table updates. Working on changes for Alabama, Colorado, Iowa, Maine, Minnesota, New Jersey, and New Mexico. We should finish it up tomorrow.

Meeting with Shawn to go over new tax withholding changes and updates for payroll. We setup another time to meet tomorrow night. Other odds and ends.

Shawn came over to my house and we did some work on payroll stuff. He was busy working on new state and federal withholdings. I haven't started yet, but will be working on W-2's, 1099's, and other PDF reports for payroll.

As a side note, I got a call from Shari O. with an update as well as a call from Russell with an update on where he is at with things. Lots of good stuff happening.

Shawn had a fever so we connected through text messages. We will try to get together later this week.

I spent the afternoon doing emails, recording notes, following up on things, and trying to clean off my plate of things that needed attention and/or a little bit of loving.

Shawn and I touched base about tax and withholding stuff. We planned a different time to work on things on Monday before Christmas. After that, I spent some time working on emails, recording notes, and transferring things from small post-it notes into adilas. Busy times. If things are going at a normal pace, I can put them directly into adilas. If things are flying faster than normal, I scribble things on post-it notes and then have to go back and add more details. The never ending process.

Around 3 pm, I got on a Zoom meeting with Russell. We were chatting and pitching ideas back and forth. Russell has been working on a project and as part of that has created some different assets. He has been working on a business plan, code, and some marketing ideas. We are really hoping to be able to join forces and bring some of those pieces to the adilas family. We were chatting about a number of different options. Here are some of my notes.

- If we open up things for outside developers to work on our new testing environments, make sure and add plenty of checks and balances. The absolute ideal would be a full API socket interface and have them play at the wall. That is still a ways out, so we may have to open up some other channels.

- Make sure we charge for our time. That is huge.

- We spent some time talking about ownership and being able to get a residual back from that.

- By helping others succeed, we succeed. That is really true in many ways.

- Some of Russell's priorities are to help stabilize, improve, maintain, and plan for the future. I thought that those were fun priorities.

- Russell would really like to help with project management and job costing.

- There are these things called web components. They are virtually like mini code snippets or functions that can be used over and over again without rewriting all of the code necessary to make them run. A simple call, with some parameters, and it does its job. Russell and I talked about some new adilas web components like table components, ajax search components, cards and actions and moving things between stages (like trello cards - project management software), and modal components (interactive pages that could display or show more details where needed without leaving the underlying page). We had some great discussions about some of these options.

- As a side note, on the cards (both tasks and actions) and being able to move things from stage to stage. We also talked about an even deeper idea of being able to allow users to build their own processes and then move things simply through those processes with point and click setup, rules, validation, automation, defaults, etc. Basically, a way to build your own virtual data assembly line by using tools that already exist and being able to string things together in such a way that it works, is simple, is custom to you, and fits your needs. All from pre-built tools and processes that could be strung together to create these custom processes. Great idea.

- We talked about the company culture and how important that is.

- Making a business plan and putting things in writing. We have a number of very loose business plan type things. Steve and I are on the same page (ish). It would really help to get everybody else to know what the plan is and how we intend to roll things out. As part of this, Russell showed me a small plan that he is working on. We went over some of the ideas. See attached for Russell's proposal and business plan (starting point document).

- We talked about models and how to best combine all of the pieces. There are lots of moving pieces. We talked cores, layers, themes, industry specific stuff, custom code, etc. It gets pretty deep, but it gets fun.

- As part of the model, we also need to be able to strip things off and get rid of extras that are not needed. That is just as important and being able to add new features. Keep it simple, where possible.

Touching base on 2020 tax and withholding updates. Other emails and to do list stuff.

Shawn joined the meeting and we touched base on 2020 tax and withholding updates. We decided that Shawn would take care of the new numbers and data and I would handle the PDF's for 1099's and W-2's.

Touching base on 2020 tax and withholding updates. Shawn and I touched base and will be hitting things next week.

Original plan was to touch base and work with Shawn on some payroll stuff. I tried calling and reaching out but was unable to get ahold of him. We'll try again next week. I left both some voicemails and text messages.

In the mean time, I replied to emails and did some light tech support stuff.

Shawn and I were supposed to touch base today but that didn't happen. I ended up doing emails, checking on a duplicated user on data 8 (got it fixed), and recording some notes.

Shawn and I were touching base on 2020 tax and withholding updates. We also had Josh join the meeting and he asked some questions about tiered pricing stuff out in ecommerce land.

Touching base on 2020 tax and withholding updates. We setup a soft due date for all new tax changes for December 18, 2019. We also setup some reoccurring times to meet for the next couple of weeks.

- We talked about setting up dummy type records for the new year. Basically, copying this year's forms and putting in new code for the 2019 tax year. We can then update those files and forms when we actually get real values. Sometimes, the government takes a while to get us new rates, brackets, and forms. That way we are fully prepared and kinda ahead of the game. Idea from Shawn.

We had Bryan, Wayne, Russell, Alan, Steve, Josh, Shawn, and myself on the training meeting.

Alan was presenting and we started really light and did a small review. We were going over components, objects, inheritance, extensions, and using some cfscript tags. They were getting into overriding attributes, values, etc. Lots of talk about the difference between tag based code vs script based code. ColdFusion allows both tag and script based languages. Adobe is leaning more toward script based as they go forward. Just an FYI.

We did record it. See attached for a copy of the recording.

https://www.petefreitag.com/cheatsheets/coldfusion/cfscript/ - cheat sheet link to some cfscript stuff

Basic to do list stuff. Calling on some business funding, emails, and follow-ups. Called and talked with Shawn about some upcoming payroll stuff for 2020. Also read a new developer's resume and some project details that he had been involved with.

Shawn wasn't able to make it. So, I ended up doing some review on the adilas café project and re-reading a number of past entries that dealt with that project. Trying to formulate a plan and get a new adilas designer (graphics guy) up to speed on that project. I also had Eric pop into the GoToMeeting session and asked a couple of questions. Mostly a research session.

I merged in some code for Will and did some email follow-ups on questions dealing with the adilas label builder. Sent some emails out to Calvin with some questions.

Working with Shawn to back fill some sub inventory data and data migration. Part of the meeting was spent getting Shawn some dummy data. I then did some research on copying database tables and how best to do things like that. Emails and uploading videos from earlier meetings.

Met up with Shawn. We got caught up and went over some billing stuff. We then spent most of the session going over future projects. I'm going to have Shawn help me prep the field and do some prep work on the round 3 of sub inventory. We are going to go in and back fill some data on certain tables and such. It should really help speed things up.

Helping Shawn get his local environment updated and up to speed. Touching base and briefly talking about other upcoming projects and options.

Steve had some questions and updates. Working in AJAX and JQuery and having Dustin do some cross training and helping Steve with some of the new technologies. He is also working on some new production stuff and even possibly looking into tying in full recipe/build type stuff. Some of that is getting pretty deep.

Dustin is going to be adding more subs of elements of time to help with his harvest pieces. He is going to be using sub flags and tags and adding some new harvest types. They are already doing sub phases, sub groups, and now sub types. That will be really cool.

Eric popped in and had a number of questions about sub inventory through adilas API sockets. We ended up talking about the need for better and better documentation and someone to help with API socket stuff and keeping up with documentation. We also have a number of projects that are done and need to be pushed through the code sign-off process. There are a number of projects that have been put in my court, but I just haven't gotten to them yet.

Wayne popped in and gave us an update on some of his AWS transition stuff. We talked about which companies were going to be pulled over for some live testing. Wayne gave us an update on the document and image processing stuff. We also talked about some new functions and how Amazon is starting to build up a giant community of alternate functions and globally accepted options. We also had a fun futuristic talk about AI (artificial intelligence) and using computers doing translations (languages), OCR (optical character recognition), etc. Lots of good stuff going and coming down the pipeline.

Wayne and Eric are going to be working together on a few things. That is awesome. We are going to be changing from an application .cfm (auto include file) to an application .cfc (auot include component). Getting things ready for a single corp structure (splitting corps out to separate database - world building concepts). We also need ways to build in the payee/user integration stuff. There are potentially a number of duplicated records out there.

Steve was telling me some stuff about sales and where things are going. We then talked about some of the other developers who are out there, both established developers, and also the ones that are hanging around and may be very valuable, based on their skills. We specifically talked about Shawn, Spencer, and Josh. Those are some developers who have already played the game and could go even further.

Steve and Josh were talking about an "inventory engine" (max, mins, reorder process, etc.). The inventory engine would help manage the re-ordering of inventory and reporting on inventory levels. Currently, this is just going to be some settings based on a per category level of what is needed (eaches or grams). Think of algorithms of how fast certain projects are being used, consumed, and/or turnover rates. Helping to automate the re-ordering process and even showing some forecasting on inventory items and levels. Helping the system tell you more about selling habits, turnover rates, and the virtual batting average of some of these items.

On sales (and in life), Steve loves to look at things in halves, thirds, quarters, etc. If you can break things down a bit, it becomes more manageable.

- Who can help Kelly? She needs access to a developer.

- One of her main requests is getting data out of the system. One page that she would like is a full parent inventory with all flex grid fields. See the top_secret/custom/full_customer_list.cfm page for a sample that does the same thing but for customers and flex grid.

- Pieces of pie analogy - and who gets access to those developers and how do we get everything tied back together.

- Symptoms of the problem - a non whole-listic approach

- Kelly is having to take the information out of the system and run her own reports

- Two main parts that Kelly wants tracking money and tracking inventory

- What are the minimum levels for a code developer? Looking for talent. Kelly and I talked about beginners, intermediate, and advanced developers.

- Project management software for adilas

- We need money and funding to keep going

- We need to focus on our own system and get it across the finish line as a product

- The model of independent consultants and/or developers can get very scary - the scary part is the inconsistency of how the money comes in - somewhat of a feast or famine type feel

- Developers: Wayne, Alan, Eric, Calvin, Bryan, Shawn, Josh, Dustin, Brandon, Will, Steve

- People believe in the tool and like what they are doing

- In order for adilas to get bigger, we will have to change some things

- Revisiting the entire business model

- Investments - pros and cons - period for two year (funding numbers)

- Let's setup a whiteboarding time and come up with a new model

Working on the special account transaction homepage. This is part of Eric's special account tracking project (sub of the balance sheet and deals with customer loyalty points, gift cards, and in-store credit type stuff). Made some headway on the special account transaction search and homepage (what are the individual recorded details).

Also helped Shawn with getting back into the invoice due date project.

Jumping back on the invoice due date project with Shawn. It is amazing how much time it takes to transition back into an older project. Shawn is going to be helping and working on merging in current master files to the old project branch files, to help get things up to date.

Reviewing code on Eric's sub special accounts (sub of the balance sheet for customer loyalty points, gift cards, and other special accounts). Also working with Shawn to get him started on the invoice due date project. Trying to circle back around and get that project going again.

Dustin and I worked on his cultivation phases and getting some of the queries and filters a little bit tighter. He already had them in place, we just helped get things a little bit tighter. After doing the phases and phase counters, we switched and worked on the location counters section. All of these pieces are in a section called cultivation that he and Steve have been working on for months and months. It is really looking good.

Eric joined the meeting and had a couple of questions. I really appreciate that fact that he tries to look global or general adilas before just making a one-off custom report. His questions were dealing with showing discounts, discount ranges, min/max discounts, etc. He also had another request for some sub inventory and RFID tag reports. We talked about options and also talked about custom dashboards that have prebuilt buttons that allow our users to get to the reports that they need and want within a single click (precode the buttons and/or page links to contain the filters and search criteria.)

Working with Shawn and getting him setup on a new branch. Shawn and I also talked about two new projects that are coming up. He will be doing Oklahoma taxes and withholdings and the two of us will be working on the invoice due date project (old one that Russell and I were working on middle of last year). We need to pick that project back up. Called and talked with Calvin.

Code review for Shawn. Pushed a couple of payroll updates to all servers.

Shawn joined the GoToMeeting session and we worked on payroll updates and changes. He was testing the new changes and had a question every once in a while for me. While he was doing that, I was updating an adilas sales flyer with new contact information. The original flyer was dated back in 2014. Lots of water under the bridge since then. Kinda fun.

It must be Monday... We started out on the morning meeting and only Steve and I were on at first. We chatted about the transition over to the AWS (amazon) stuff. We have a number of questions and aren't really sure which way to turn. Steve needs to provide some of our clients with an answer, can we service them or not, and we need to know how long it will take to get the AWS stuff fully up and running. Lots of unknowns, but some great potential. Part of us wants to return to what we know (older stable ground) and the other part of us wants to keep pushing forward (new and uncharted but promising ground). It creates an emotional battle of sorts.

We switched gears and Steve had some questions about a project where he is tying in balance sheet numbers to vendors. As part of his project, he was trying to come up with a switch that we could flip to help us know if a vendor was an inventory (parts or items) vendor or just a normal vendor. As we talked about it, we decided to take it out to an app type level (the 12 main system players). We talked about that and Steve liked that idea. I got him some code to help him get started. It is amazing how much, as we keep going, that the system keeps organizing itself into main player groups and what kind of relationships are needed per system or main player group. Very interesting. Almost like it likes to be organized into groups and related functions. We sure have learned a lot along the way.

Alan joined the meeting and we were talking about some of his projects. He is still working on automating some of the reoccurring invoice stuff. We also talked about having Bryan work on the dynamic field names and settings per main player group. That is pretty deep and we may keep it tabled for now. Also, as we were talking about it, we were talking about how an object oriented programming approach may be a better solution for some of these new settings and defaults. Currently, we build and break, build and break (speaking about pulling and accessing settings). It may be nice to keep and hold some of the persistent or permanent settings and features. An object oriented model may be better equipped for that type of transaction. Currently, we look things up just in time. In the future, we may need to catch and hold those settings and maintain them in the user's session (stored in memory) options.

Eric popped in and we did some check in and follow-up with his code review on the sub special account tracking project. This project is a sub of the balance sheet and deals with special accounts (mini bank account type objects) like customer loyalty points, gift cards, in-store credit, etc. That project is promised by next Monday. I will be trying to focus on the code sign-off this week.

After that, Eric and Steve and I started talking about some of the new look and feel, CSS, and user interface stuff that Eric is wanting to help with. Both Steve and Eric were talking about a virtual "Adilas Cafe" or a global landing spot for the adilas users. This all goes back to separating the users from the main application code. There will still be a tie-in, but we are seeing a bigger need to keep users on the outside as a single entity and then allow them to go in and work or be a part of a corporation. We have many users that  have and/or will need access to multiple corporations, and even be able to bridge across physical servers. Currently, our model is based on users per server and then tied to corporations based on active permissions to those corporations. We are seeing a need to break that down even further and have a master or global user id (virtual pool of users) and then allow them to be bridged to different corporations on a more global scale vs just per server (physical box) vs the possibilities of dynamic cloud networks.

As we got deeper into the conversation about the potential of the Adilas café type model, we were talking about doing mock-ups, flow charts, etc. Eric had some questions about authentication servers and how that would all roll into the mix. We told him that he would need to get with Wayne to get more details. As we talked, we decided that Eric and Wayne should work together in a mini team type environment. As we explored the options, some of Steve and I's concerns (listed at the top of this entry) started to go away. We ended up somewhat asking Eric to be a project manager type role for this transition project between Newtek and AWS. That little tweak in the plan and how the developers were paired up, made a ton of difference and some of the anxiety started to go away.

We need to crate a list of specs for Wayne and what we want the application to do. Plan and play as if for years. We also talked about in-house coordination and communication. That is a huge key and helps all parties involved. Steve was talking about skating to where the puck (pretend we are playing hockey) is going to be. He and Eric were talking about the existing login pages and the corporation chooser page as being the beginning of the adilas café (landing spot or centralized common ground area). Good discussion.

We would really like to keep pushing the ball forward and making each system its own entity. This means having a centralized database controlling users and access to different corporations and/or entities and then having the individual entities having their own database or system for just their stuff. Currently, there are a number of tables that are shared between parties. For speed and efficiency, we really need to split things up more. This may also affect how we are able to bill for storage and processing vs a set monthly system fee. Anyways, as the conversation progresses, Steve and Eric were talking about using the choose corporation page as the starting common spot or commons area. Steve was also saying that he would like the users to be able to go to work (assigned or authorized corporations) as well as go play (demo sites, play grounds, or play sites). Basically, anybody could have an adilas account, and then they could either go into a real site (aka work) or a play site (aka play and testing). Fun ideas.

One of Eric's and Wayne's first item of business will be to do a virtual inventory check of where things are at on the project and what will still be needed and/or stands in the way. That will be awesome. It really was an mini answer to prayers that we decided to team up Eric and Wayne. It helped us let go and be willing to embrace some of the unknowns. As part of that, we are hoping that having the guys work together in mini teams helps us prioritize what really needs to be done and when. Sometimes, by yourself, it is hard to know what needs attention first, especially if it feels like everything is vying or trying to get the input, attention, and/or priority. Crazy stuff, I'm been there before and will be back again.

Steve and I talked about cycling through hardware and how that is just part of the line of work we are in. Later this year, we will need to buy some new laptops and upgrade some of our development environments.

One of the breakthroughs for today was the mini team concept. We have Steve and I, Steve and Dustin and Josh, Brandon and Alan, Wayne and Eric, Shari O. and Pat and Drea, etc. There are starting to be all kinds of little teams. That is awesome.

Shawn popped in and reported on some payroll updates and changes. We scheduled a time to meet again tomorrow. He is also willing to help me out with some of my projects and such. After that, I spent the rest of the session recording notes and trying to get caught up (as good as I could).

Got on to work with Shawn. He was working on payroll stuff so I ended up on a tech support call with Pat and Shari O. We spent about 1.5 hours working on getting those two, Pat and Shari O., setup and using the adilas label builder wizard that Calvin Chipman created. They got a pretty good taste of what it can do and we did some light playing and training. Lots of potential there. After that, I worked on some other emails and notes.

Merged in some new payroll withholding updates from Shawn. Ran the new updates on all servers.

Working with Shawn to get his system up to date with new code.

Steve was out all week, last week. He gave us all a report on some of his outings and adventures. Good stuff and Steve is excited to be back in the saddle. Alan reported on his reoccurring payment stuff. We talked about more charts, eye candy, and other reports. Alan and I also talked about working on some code sign-off and trying to get back to some of those other projects.

I helped Steve with some code merging and pushed up some new files. I then got on a call with Eric and we touched base on his sub special account tracking project (loyalty points and gift cards). I told him that I was going to be pushing more on that this week. We also talked about an upcoming project to look at the adilas look and feel (over arching look and feel). This doesn't exist yet, but I was just talking with Eric about looking for ideas and making a plan. Anyways, he is interested in helping us out there.

I setup a time with Shawn to work with him. I recorded some bills, did some email stuff, and recorded some notes. Trying to push the ball forward.

Steve was on with Cory (an adilas rep) and they were going over some production and cultivation processes. Cory is going to be helping with some news and updates. After that, Wayne joined the meeting and we briefly went over the transition progress between Newtek servers (existing dedicated models) and upcoming AWS (amazon web services) stuff.

Working on some code merges and tax withholding updates from Shawn. Got a call from Shari O. and Dustin and I had to do a quick fix on a page that was pushed up earlier today. Minor tweak, but somewhat urgent.

Emails, follow-ups, phone calls, and light research on a custom project that is coming up.

On a GoToMeeting session with Shawn going over payroll things. He committed some new files on the sdc7 branch. Started to do a code review and code merge.

On a tech support call with Shari O. We were looking into some expense/receipts and running things through auto pay outs for splits (making payments on account).

Emails and tech support. Added in a new link on the customer log page if the corporation allows for online bill pay. Also worked with Shawn to get some new numbers and federal tax withholding numbers.

Steve and I were on the GoToMeeting session for about 2 hours this morning, just the two of us. We were both working on other small projects and just talking back and forth. Lots of good things are going on. It has been quite the journey. Some of our subjects were things like: progress, small micro tweaks, continual growth and tweaking, building for the future, countless blessings, laying down stepping stones, building on foundations, willingness to learn, skill levels, being inspired by one another and what we are doing, our guys and gals (developers, sales, tech support, reps, consultants, etc.), and how many untapped avenues there are in front of us. Tons of potential.

As a side note, sometime it really helps to have someone else along with you on the journey. When one gets tired, bored, or burned out, the other may be able to help, encourage, inspire, and/or lift. It really helps to have a friend and just keep going. Sometimes that continual pushing is better than one short burst of energy.

Wayne came on and had a few questions. He also reported on a few of the things that he is working on. After he left, Steve and I kept talking about some of the talent and team members that we have, that are going along with us on this epic journey. Those other people are carrying the load and helping out. That is awesome and we are very grateful. We are hoping that they are having fun and being supported as well. It takes a team to do these things.

After chatting and working on small projects, Steve and I decided to look into a report that some of the sub inventory searches were struggling when finding certain sub inventory values. These problems were only reported in certain cases. We did some local and live testing and couldn't make it fail. We came up with some possible issues or scenarios and then tried to fix what we could. We may need to go deeper, but we got a few things tightened up. We removed some spaces in the code and in the display for sub inventory items. We did some data trimming to help make sure we were getting what we were expecting. We pushed up the code and did some testing.

Just a little after 11 am, I got a hold of Shawn and he jumped on with us. He is working on some payroll numbers and withholdings. Shawn and Steve were talking briefly about gardening and greenhouses. Both are somewhat hobby gardeners.

Shawn and I got on a GoToMeeting. He wasn't quite done, so we both just worked on our own projects. I finished up some custom code for Beaver Mountain. They wanted me to modify their add/edit process for adding new ski/snowboard lessons (new elements of time).

Reviewing code and running some tax table updates locally. Passed the existing files back over to Shawn.

Touching base with Shawn. We setup some time for tomorrow. I started working on some other pages.

Contacted Shawn but wasn't able to connect to work on payroll stuff. I ended up working on some other code and fixing some known bugs.

Paying bills, working with Shawn, pushing up code for Dustin, and checking new state withholdings.

Steve and I were on the morning meeting. He is still feeling kinda sick. We worked on a small query for his code and then tried to work on Calvin's adilas label builder. Steve's copy of the program is stuck in a login credential error. We tried installing and uninstalling the program a few time. We will most likely have to reach out to Calvin to see what to do. Along those lines, I also made some notes on my to do list about some other tweaks that may be needed.

I spoke with Shawn, Eric, Bryan, and Dustin at different times during the morning session. Some were simple questions and others were trying to setup times to work on certain projects. Lots of email stuff. I used the last part of the meeting to look over new state and federal tax withholdings that Shawn submitted.

On the GoToMeeting with Shawn. We also had Pat and Drea pop in and ask a couple of questions about the state of Oklahoma.

Brandon, Shawn and Shari need to get in and work on it.

I got some new code from Shawn dealing with 2018 W-2's and 2018 1099's. Looked over the code, made a few changes, and pushed to all servers. Sent an email out to Shari and Drea to help do some checking.

Meeting with Shawn about where we are at with end of year tax updates and changes. He has a number of new state and federal tax changes. His code isn't all the way done quite yet. We will be meeting again tomorrow. In the mean time, I will be running the tax table copier code that we have. We have to run this same report every year. It allows the payroll system to keep working and running. Then, as Shawn has his new changes, we run each smaller section and it strategically updates just certain pieces and parts of the federal and state withholdings tables. Good stuff.

After my meeting with Shawn, I started checking emails. It looks like there was a SQL injection hack against one of the servers yesterday. A SQL injection is where a hacker takes existing code and tries to find a weakness in the existing code. It basically has the server run a normal SQL query against the database, but part way through the normal process, it tries to break out of the normal flow and set some values, variables, and/or inject custom code. Wayne Andersen, one of our guys, was able to track it down and put a temporary patch on the code. The hacker was calling a sleep command on one of the servers which was virtually locking the database for a certain period of time. Not that I applaud this, but there are some pretty creative persons out there. I'm glad that we have some top level guys on our side. Anyways, I spent the rest of the morning making a few code changes to push up to all servers to keep things nice and tight.

10/6/22 Videos for the auto email, email report and invoice due date functions.

10/6/22 Page URLs for completed project. Note: These URLs are primarily from the auto email part of this project.  The URLs for the email history report, use credit terms and invoice due date project were not included as it would take a significant amount of time to dig up this past information. 

Large edits

1. public/afb_email_preview_action.cfm

2. public/auto_email.cfm

3. publictop_secret/cfc/Services/EmailService.cfc

4. top_secret/cfc/Daos/EmailDAO.cfc

5. top_secret/secure/classic/email_report_body.cfm

6. top_secret/secure/email_report.cfm

6. top_secret/secure/afb_corp_email_home_action.cfm

6.top_secret/secure/afb_corp_email_home.cfm

Small edits

1. Application.cfc

2. public/auto_email.cfm

3. top_secret/cfc/search_15.cfc

4. top_secret/cfc/security_4.cfc

9/29/22 The auto email project was pushed live and  tested.  It will be used by Shari O for a week or so then the automation will be added to each of the servers by Wayne.  The auto email project was completed and pushed to data 0 about a month ago.  Several bugs were identified by Bryan and Shari O, but were put on hold as other higher priority projects were being completed.

6/13/22 Met with Brandon to clarify some specifics on the 2.2 plan.

2.2 Email history report (email_history_home)

1. new table (not the same as invoice history)

a. new update that creates table

I. Look at tables for examples (history and text) 

II. Email_history table variables – like custom_text table: email_history_id, corp id, payee_id, datetime, app_type_id, main_id, table_name, special flag, history_note (13, 3076, statement).

III. Types of special flags: Invoice, quotes, pos, statements, customer, eCommerce, custom, auto due date, multiple invoices.

2. Set up history capture on email

a. design email capture (from/to email addresses?, status: success/failure) 

b. search for pages to put history code on by using adilasuniversity.biz

c. add email capture on all pages

3. Create email reports page

a. be able to search by: type, time period (day, week etc).

I. model after invoice_home_basic.cfm

4. Show email history on invoice history, PO history, quote history, and statement history reports  (invoice_history.cfm etc).

a. bold line below reports saying “Email History Actions” and then email reports

b. ? auto_sent column in email_history. 

5. Report on my_history.cfm page

a. Tie to invoice app type similar to how statement works.

6. If it goes out manually it also goes into the history.

5/31/22 Met with Brandon and developed plan for part 2. Broke it down into 3 sub-sections

    2.1 Add setting (Use Credit Terms) and if selected change due date on Cart

        2.1.1 Add "Use Credit Terms" settings to Corp Wide Settings

            1. create database update and add tiny int

            2. research standard invoice credit terms

            3. standardize credit terms on Corp Wide Settings, add_edit_customer.cfm page and Corp Email Settings page

            4. Add verbiage to Corp Wide Settings Page

        2.2.2 Use Credit Terms to switch out default session due date

            1. Working on cart_4.cfc

            2. check if "use due date" has been selected in settings

            3. get due date session default

            4. check if "use credit term" has been selected in settings

            5. if "yes" get credit term variable.

            6. check if a number exists in it and it is less than 100

            7. if "yes" switch out the session default variable

    2.2 Check due date and automate email (not planned out yet)

    2.3 Email history report (not planned out yet)

5/27/22 Met with Shari O regarding moving forward to add auto email to the Invoice Due Date function:

    1. Bug on invoice due date: the due date is showing current date. Is this a normal bug or  happening at server update? (1:59).

    2. Can we make due date default "Credit Terms" on the Customer  (add_edit) page.  If Credit Terms is different than due date it will trump.

    3. Email template "due date" reads from due date or credit terms.

    4. Different (edited template if paid). Reads from due date or credit terms.

     5. Auto send out reminders if 5 days from overdue. Adilas is due upon receipt, late fee at 30 days and shut down at 45 days overdue.

Alan is making good progress as of August 2019.

Brandon and Russell were working on this. It got to a point, and then got dropped. Finishing this up would really help with accounts receivable and cash flow. See branches ram-37 and BWM-33. Steve asked me to work with Shawn on this project. I lightly got Shawn started on the project on 4/10/19.

This is an invoice due date project. It is a prep step to get a corp-wide header that could go from server to server to help prompt for overdue payments. Basically, a way to speed up the adilas receivables or A/R accounts. Once the invoice due date feature is in place, we can then figure out the aging of how old an invoice is, regardless of payment history. Once again, this is a prep step for a bigger project, but much needed.

Russell and Brandon started the project back in December of 2017. Due to craziness, it got almost finished and then mothballed. We (both Brandon and Russell) picked it back up on 2/23/21. Project turned over to Bryan on 5/17/22. See media/content for a 26-minute video overview of the project.

Working with Shawn to track down a bug in some new state payroll calculations. Shawn is working on Missouri and Mississippi state payroll withholdings. We had to get in deep and look through numerous lines of code. While Shawn was looking over code, I was emailing and doing random to do list items.

Towards the end of the meeting, Josh had a few small questions about tracking active GPS entries and how to flip his own internal route status values. He is doing great and it sounds like he is being pretty creative on what he is planning and doing. Good stuff.

On the morning meeting with the guys. Steve wanted a report on Wayne's cross-server database sync tool. We reported and talked about some future options and where we want to go. Lots of potential there. After that, Dustin and Josh started talking with Steve about some of the Metrc stuff that they are working on. They are making some great progress. Steve was the leader there. He knows his stuff because he has been in there in the trenches on implementing the Metrc and state compliance stuff.

I was doing emails and light tech support. We have a client who is wanting to charge some special fees based on certain payment types and then not have those new collected fees show up in revenue. That is possible, but kinda tricky due to the mapping of non-revenue based fees and still having the fees show up as an invoice line item. I also was working with the guys on the Bear 100 mile race and getting their runner list for this years race. The Bear 100 mile race uses adilas as their race (leg and aid station) tracking software piece. Lots of different projects.

Eric checked in and we chatted on the phone for a bit. He has a random error coming from one of his custom shopping carts. We will look in to it more later on today. Shawn popped in. Alan popped in and chatted with Steve. It seems like all of the guys are going in a good direction.

Working with Bryan and merging in some code for refunding Expo payments. This is a 3rd party solution and payment service. They are also trying to be a white label solution and help to resale adilas using the Expo name.

Part way through, Shawn showed Bryan and I some YouTube videos that he made with multiple takes of himself singing the same song. He said that it might be fun to do something similar and have adilas both show a teacher and a student and show some basic adilas concepts. Great idea. Who says it has to just be one person. It could even be animated and/or two fun characters having a conversation. It all comes back to time and available funding. Some fun ideas.

Live Adilas Class. Logan, UT - Bridgerland ATC, Custom Fit, Room 810 (computer lab). We had 4 live paying clients and a number of internal team members in the class. We had Steve, Shari O., Dustin S., Alan, Bryan, Calvin, Russell, Shawn, Jeremiah, and myself from the core adilas team. Not all of them were there everyday, all the time, but they all came and participated quite a bit of the time. We also had a number of folks join us online in the GoToMeeting sessions. We recorded all of the training except for two main sessions.

Here are some links to the videos.

video from day 1 - morning session
small adilas demo, intro, and core concepts

video from day 1 - afternoon session
new features, open q&a, and historical stepping stones

video from day 2 - morning session
POS - point of sale features part 1

video from day 2 - afternoon session
POS - point of sale features part 2 - open q&a, and world building in use

video from day 3 - morning session
CRM - customer relationship management overview

video from day 3 - afternoon session
exploring ecommerce & custom email settings - BI - business intelligence and big data

video from day 4 - morning session
tips, tricks, & best practices - small custom consulting session

video from day 4 - afternoon session
meet the adilas developers, adilas model, and wrap-up

///////////////////////////////////////////////////////////////
other notes that I took during the class.
5/29/18
- Drag and drop custom fields - they really like the custom field settings for customers. They would love that to cascade out and filter through the whole system. Point and click, toggle on/off fields, sort, customize verbage & instructions, and be able to effect the display as well.

- The need for more one-to-many relationships

- Light request for more settings on the main salesperson and other salesperson settings - be able to split the names instead of just one setting.

- A custom preset on permissions "copy and/or duplicate" permissions.

- Setup a master and then apply those settings. This could be templates and/or master files - a virtual job description.

- Floating up and down nav to help minimize the scrolling.

- The power of "templates" - elements of time, sub inventory, payee/users, look & feel, etc.

- Start by setting up the templates and then assign them as needed - that makes a great starting point.

5/3018
- Alan was doing an exercise - he had everybody list what they could for two minutes on all of the fruits that they could think of. Fun little exercise. After that, he was comparing this to development. We try to hit the fruit that is on your list. Things keep evolving and sometimes you forget things and have to add that in later.

-  Corp-wide settings and allowing you to set certain verbage stuff.

- Bryan Dayton was showing the adilas market (adilas world). We really need to get others into the marketplace.

- While Bryan was showing his profile... I was thinking that we need to help him get some better screen shots for his demo graphics. You could tell that they were done with a low end and/or free graphic editor (kinda fuzzy and pixelated).

- It helps us to have a flow and/or a clear picture (talking about custom code and custom development).

- Small demo on a custom dashboard for Global Design

- Steve and Shari O. were talking and doing a demo together. Steve was talking and Shari O. was driving. Later Steve and I did similar things. It really helps to split that load and have a helper. The person talking can focus on what they are saying and the demo person (driver) can draw, highlight things, and show focus areas. It seemed to work out quite well.

- Steve and Shari O. started out in a coffee shop and did some quick split cart stuff. They then went into some of the corp-wide settings to show how they were able to do what they were doing. Good flow from normal usage to how it is done based off of settings.

- Eventually we need a deep merge (find and replace) on customer records.

- Our users would like to be able to compound a discount. For example: double up points, do a 1.5 mark-up, etc. Lots of time based sales and promotions.

5/31/18
- Not many notes from this day... We started out and Steve and I were presenting on sub inventory. See the video links above for more details and info.

6/1/18
- Steve was going over the new cultivation functionality. 4 main levels for the cannabis guys... they need cultivation, production, distribution, and retail.

- Some of the these white label options should really build out and use all of the pieces.

- Page and function level settings

- Interesting topic of hardcoding & concepting vs dynamic code & production - speed, limited scope, and testing.

- Being able to lock-down certain pieces, features, and virtually ice things down (ice-down dates).

- Also, interesting as we get deeper and deeper into the industry specific code... the verbage, lingo, & the flow are really important. That is what makes it feel like native or custom code or custom software.

- Comment from Dustin - We need guide rails, guard rails, settings, templates, and easy configuration options. Help lead the people down the paths that we want them to go.

- On the data tables - it sure would be cool if you could sub filter things. It comes down to space, coding, page real estate, and planning. People want more and more custom options - to setup their flow, work space, and environment (requests for deeper and more robust world building options).

- On numeric entry fields, show the unit of measure to remove the questions (if applicable).

- Making the label options show up and be available from multiple pages and such.

- Settings are preset choices & decisions - super important.

- On Calvin's tools... Just an idea, but what about dynamic or user input boxes and text fields? This is for text that may be added on the fly. He currently has static text, HTML enabled text fields (allows formatting), and dynamic look-up text (text fields mapped to data or dynamic output). What about user input text boxes?

- Making labels and empower the users.

- We had a client/participant that recommended that we put a small icon on each page that could be a default homepage and then have a quick link to set it as the default homepage. Great idea. Basically, let them navigate there (to the actual page) and then set it as their homepage if that is what they want.

/////////////////////////////////////////////////////
Comments from Bryan - who talked with one of the participants

- When starting the class, for someone who is brand new... it might be nice to give a 15-20 intro and general overview. We just started out and jumped right in. Basically, somewhat of a canned explanation of what is adilas and what do you get with this software package. A really simple and organized intro.

/////////////////////////////////////////////////////
Notes from Dustin - See attached for full notes

General To Do's:

Need to Have each page check for the color of the background and adjust the card to be a lighter complimentary color (universal). (4,5)

Need to have api key capability for each employee that performs metrc api interaction.

Need to set up custom permission setting capabilities so that they can set permissions for multiple employees over time without having to do a redundant process. Themes and standardized user type templates.

Make a excel or csv spreadsheet that templates the fields needed for api integration to give to a customer to fill out. Maybe a master list that passes in all of the general fields and passes over unneeded fields based on customer needs.

Need a graphical repesentation of the entire seed to sale process with tie-ins to each adilas feature/tool.

Need predictive on the search vendor field on the add/edit page.

Need to have customer password fields auto-populate wherever needed. (e-commerce)

Need to have a set to default button on the nav menu for setting any page as a default homepage.

Need to have a toolbar button for page relevent tips and tricks with links to news and updates.

Need to update how people reset thier login attempts: lets add a captcha or at least put the copy paste link on the same page. Maybe two step varification would work.

When you are switching corps, instead of needing to click on the little box link, make it so that you can click on anywhere on the corp piece.

Need to have UOM type indicators on any field that holds wieghts. In most cases this could probably be hard coded.

Need to create the ability to check a box that opens all of the subs for inventory search for adding to cart.

Russell and I touched base first things this morning. He is working on payee/user level filters for the news and updates section. Lots of emails and text messages. Light tech support and helping here and there. Shawn popped in and we signed off on some new code and calculations for North Carolina state withholdings. I merged things into master, updated databases on all servers and pushed up new files. I let a client know who was waiting for that state.

Calvin and I got on a Zoom session and worked with Mike Harman from Caisson Labs. They are just starting to use the new hybrid desktop app that Calvin created. We had to flip some settings, check some pages, and give some light training. They should do good, once they all get going and into the groove. That is exciting.

Working with Shawn to get his local database updated and ready to go. He was missing one small piece that was buried underneath a database update. The update checked one of the fields and because it was ok, it skipped the rest of the update. We had to update some payroll tables manually. This only happened because Shawn was the original developer on the payroll project. I added the second table change after the code was submitted. Long story made short, he only had half of the needed changes.

On a Zoom session with Calvin. We looked into an error on an advanced main invoice search through the API. It turned out that he needed a table in his local environment to make the API socket run. It is amazing how quick things change and move. We really need to be pretty flexible in order to play our own game. Good stuff.

Finishing up the sales tax calculator page. Working on help files and testing the page.

Online team meeting to cover security, adilas API sockets, black box code, and upcoming white label options. We started out with a number of reports by the different guys.

/////////////////// here are some of the quick reports by the developers:

- Eric - Fixing custom carts and working on the pricing engines. Lots of custom one-off's. Working on loyalty points and special tracking accounts.

- Russell - News and updates - new API socket feeds and such. WordPress site and other look and feel things.

- Wayne - Refactoring code, testing based design, and underlying framework. QuickBooks integration stuff - imports and exports. As a side note, Bryan has had many customers asking about similar type features. Wayne is also working on other database stuff and migration.

- Bryan - White label stuff for outside parties. Tons of custom projects.

- Calvin - Hybrid API to Windows desktop app. Custom PDF labels and printing.

- Alan - Helping Steve with Metrc API stuff. Working on tons of tax and in-line discounts. Helping Brandon with other projects.

- Danny - Generating sales - Props to the developers who are creating the functionality. He pitches the idea that the developers are accessible. Custom labels.

- Shawn - Helping with payroll, federal withholdings, state withholdings, and county level withholdings.

- Brandon - Helping the developers and doing small projects. Merging code and maintenance stuff.

- Steve - Grateful for the help with the Metrc API stuff. Working on phases and sub locations. Steering the ship. New approval levels on other state traceability systems.

//////////////////// meeting notes:

- Talking about the Adilas API and system - dealing with security. Facebook was brought before the senate due to a breach. They allowed an outside company to come in and develop an app for Facebook (basically a 3rd party solution). The problem was... what does that outside service actually do and have access to? The app ended up doing some internal data mining and then sold that data.

- We want our users to be successful - we want to enable them but we also need to protect them.

- Small switch in the sales focus. The older model was one-by-one and dealing with reps and consultants. We are seeing more of a switch to bigger companies that virtually take over the sales force and are wanting to sell our product more as a white label type application. Lots of mixing and blending of products and services. They are allowed to provide all of the supporting services that support our product.

- Ideas from the group about security:

- Russell said, bold it or make it red and let them know what they are exposing (meaning the API sockets). Allow the agreements between the parties... we are part of it, but we let them create the relationships between themselves.

- Steve said, we don't want to make our users work harder... to turn things on, but we do want to make sure that the clients know what they are getting in to. Example of what happened with back in 2015 with Hypur and Emerald Fields (two of our clients). Basically, the 3rd party solution (Hypur) got turned on and then it kept growing (what Hypur was doing and/or requiring) and eventually was trying to get at more sensitive sales and inventory level stuff. Eventually the client was super upset due to the lack of disclosure of what was going on and what was open/available to the outside party.

- We are seeing that most of these 3rd parties and white label people tend to expand what they are asking for. Bryan is seeing that more and more auditing type levels are wanted by these 3rd parties. We have also had a number of questions about different server levels and certifications. Our clients want to make sure that their data is safe and secure.

- Russell brought up the point and the difference between a couple of if statements on a page vs a full on white label type solution. We need to develop and standardize that white label type path. They need to pay for it and also be able to help maintain it (meaning the white label company). Taking things clear out to a white label theme (actual files and folders). White labeling is basically bulk black boxing but you can still use any of the classic pieces. We drew some small diagrams and talked about possible options.

- Shawn chimed in and started talking about building a city. Basically, kinda like urban sprawl or older parts of a bigger city - no plan, no alleys, buildings touch other buildings, and not a well planned layout.

- We need to stay on top of things. Keeping code and the database structure up to date. If we do this... it will help us be more efficient and save us time.

- Eric chimed in and said "process" is the solution vs simple communication only. Basically, as we are growing, we need to get to a more standardized process of development. We have a huge landscape to consider. Lots of moving pieces. Ultimately we need to adopt a process oriented approach. Wayne agrees. Different levels within software development. From critical and saving lives to making sure that we have solid code and pieces. It gets into speed and flexibility against slow and more stable type processes. Maturity in software development is sometimes measured in how well you implement internal processes. Eric thinks this is the next step we need to take as a company.

- Danny has been threatened... :) He was talking about levels that people rely on our solution and how all of that plays in and such.

- Small little analogy of the little red hen... everybody wants it but they may or may not want to participate. In real life, things cost money and take time to get done.

- From Brandon - Let's make this thing what we want it to be!

- Any core elements need to be merged into the master branch. This is required.

- Steve was saying... be on the lookout for companies and what they are wanting. That could help us know how to play with them... Maybe look deeper than the current project. We really need to protect our client's data. He was talking about the adilas market (adilas world) and also the 3rd party solutions page. We need to point outside parties to come through the main monitored pathways. We need to keep those sections updated and let the clients know what is being opened/exposed. Very important.

- The value of oversight and/or having someone to help watch them and help them out. This seems to be new trend. If that is the case, we need to make sure that they know what is going on and what is opened and what is closed (talking about data).

- Brandon will write up some super basic pieces of what our current rules and processes are.

- Alan pitched the idea... Local, live, and then into production - talking about a testing server that will be coming this year.

We ended the meeting and allowed people to jump off the meeting. We basically said we would be doing this again (meaning a team meeting) and would get them some info and instructions.

/////////////////////// after the meeting

- Alan and Steve were talking about breaking up code into logical pieces and making the road map more object oriented. Basically, organizing the use and flow of data - making the map for others to follow. Currently, we are just using Brandon's memory to help guide people to the right spot. We need a better road map that others can follow.

- They got into some technical conversations about threads, processes, RAM memory, read/write times, etc.

- Part of our process needs to be setting up and monitoring the servers (actual eyes and reports or dashboards). We need more information, stats, what pages are being used, what processes are running, and what data is being accessed and how often?

- We talked about caching, traffic, threads, database transactions, data mining, and changing from transactional data to more of an aggregated type model (summing up things and organizing things for reporting features). We need to keep allowing day to day operations but also need to optimize things for reports, exports, and other bulk reporting features.

- Alan and Steve were talking about the challenges of using outside API's and syncing up data between systems. Lots of options, but also lots of moving pieces.

- On the API sockets... We need to provide good samples of how to call things and also good response type data. It is really nice if we can format things as well. It just makes it easier for our guys and also outside developers.

Emails, paying bills, and on a Zoom session with Calvin. He showed me a new demo of where he is and we chatted and talked about the next steps. He is making good progress.

Talking to Steve about buttons, barcodes, labels, coupons, etc. They are all ways to get things into the cart and/or affecting pricing and discounts. That is an interesting point.

Steve has really helped me delegate more. He is good at it and even encourages me to do the same. Sometimes it is just an idea or a suggestion, and other times, he may help nudge the boat in the right direction and then it makes it easier for me to do what I need to do to advance the ball. Good teamwork stuff.

Spent most of the afternoon doing tech support, emails, recording notes, and talking to Shawn about new payroll changes. Shawn and I got his system all up to date and new files pulled down. I called and chatted with Steve (see a couple small notes above) and then did the other things. Busy day.

In early working on the new payroll changes that Shawn submitted. This is dealing with county based withholdings and new state calculations for Indiana.

Steve is seeing the 3rd party solutions page extending into a virtual permissions for those outside solutions to get access to any of the 12 main players. We need to show what is available and allow for what windows and doors are open. This is really common for some of the clients that are dealing with oversight or overseeing certain pieces (virtual auditing and such). We need to keep our clients data safe but also need to allow the different parties to allow or dis-allow between themselves. Maybe the secret is allowing the clients to build their own relationships between the possible different solutions and/or outside parties.

At some point, we may need some kind of history of who is opening and closing the API socket windows and doors. That may help later on if we need to figure out who is changing what.

Eric will be popping in around 10 am to talk about loyalty points and gift cards.

Meeting with Anthony Harrington about loyalty points and gift cards. Eric, Steve, and Brandon were on the meeting with him.

- There are tons of daily discounts. It gets crazy in order to manage all of those things.

- There are a number of steps that need to be done in order (on carts and checkout process). One of the things that they would like us to do is - dumb things down and make it more simplified.

- They would love to have preset discounts, sales, and promotions. Also, a lot of the different discounts are based on a day of the week and/or a specific time.

- Eric has done a number of these custom discount and pricing engines. Eric was saying that some of the discounts are not created equal... bogo (buy one get one) vs auto calculating all similar items and then repricing based off of quantity (just as an example).

- Some discounts and promotions will be standard (hoping to catch 80% or more). There may be others that are just plain custom. Those still needs to stay on that level, meaning we may still need the option for custom code.

- Anthony would love to help push the development forward in such a way that the users (adilas clients) could use the system to tweak the system. If they, our clients, need to call a developer all the time, that gets crazy and very expensive. The solution needs to be out to sales and promotions and virtual campaigns. Eric and I have also talked about allowing discount rules and such.

- Anthony has some price grouping and some needs there. Similar to smart group buttons and tiered pricing structures. He would love the cart to be able to keep track of those pricing tiers and virtual groups. He would like the ability to move and manage pricing structures based on groups (even a subset of part/item categories).

- Lots of needs for time based discounts such as happy hour, certain deals, etc. It would be super cool if we could setup all of these rotating discounts and the cart is able to apply those on the fly and as needed. Basically, we need an automated pricing engine.

- Some of these discount rules may need to be built and held in a coupon, sales, and promotions type system.

- Eric was talking bigger volume shops vs the mom and pop shops. They all want that kind of feature but it comes down to cost. If we could build it into the system, it would benefit all parties.

- Eric would like to see a printed list of what kind of discounts they offer. That would help us in the background make sure we can build out the rules that would be needed.

- Anthony would like to know a cost and timeframe. Eric was talking about phases and options for deployment and development. Then Eric talked about building out the standard features, all-a-cart features, and then also being able to customize things if needed.

- They would really like the pricing tiers to work similar to the smart group buttons without having to tie them into a button. Basically, behind the scenes, they have rules (what to do) and assignments (who can play). That is the same basic model that is still needed, just not tied to a button. This may end up being part of the pricing engine. The cool thing would be rules that could also be tied into time and time-based promotions. The higher level (meaning the top level or group level) of pricing really helps with speed to market and ease of use.

- Steve was saying that sometimes it takes years to get a stable picture of what is really needed. That is a huge key.

- Sharing knowledge and helping others be able to run and go forward. Anthony has some great operational experience... we would really love to tap into that. A huge knowledge base of experience. Another huge asset is perspective and vision. Those are both huge assets.

- There is a huge training need. Some people will use what we have but they may not even know we have it. That comes back to ease of use and education.

- Molly popped in - what comes first, the pricing engine or the coupons and sales?

- There are a few main pieces to help everything play in and work together. We are seeing sales and promotions, pricing engines (cart logic), custom labels, sub inventory, mini conversions, discount rules, tiered pricing models, customer loyalty points, gift cards, coupons, etc. They all play together and have similar pieces that need to be coordinated. We know we need all of these pieces, the trick will be what comes first? And how do we pull things together?

- As a side note... when setting up pricing groups, we may need to pull in parent attributes to help us create good groups and grouping.

- Small complaint on packaging and sub packaging, when they add a new one (sub), they have to re-enter the price (every time). They would love it to be tied to a pricing group. They also want to make sure that we keep them in a good process path. They would love the new subs to pull in the price from the group pricing vs setting it every time. They do want to be able to change it if needed, but they would love it that price auto pulled itself into a preset pricing group. This is a big priority to help make it easy and more standard.

- Mini conversions are really needed here soon. The deeper we go, the more we are needing that ability. What they are calling (our clients) packaging is really mini conversions of sorts. There are a number of clients that are doing internal manufacturing inside their systems. We need to help them out with that. Also, when the customers buy things, they want to be able to search for one item (not 50 million), and then be able to buy and sell those items in different sizes, packages, and conversion pieces. In the frontend, they want it really simple. In the backend, we need to mix and blend and cross-tie things in and maintain the correct relationships. That is really huge.

- The more we help to automate things, the less chances for user error.

Our code is one of thousands of possible options. If we have to protect something, we will protect the concepts that support the code not the code itself. It technically could be coded in any number of languages and in many different ways and manners.

Eric popped in and we chatted for a bit. He will be checking in around 10 am tomorrow.

I spent most of the morning working on new payroll files from Shawn for adding in states, counties, and new code for the state of Indiana. Shawn got on the meeting and was reviewing some code on his side as well. Mostly a work session today.

In working on payroll changes. Shawn got me some code and I was looking over things. Reformatted the code and ran it locally to test it.

In working on some new payroll changes and looking over code that was done by Shawn.

Morning meeting... got reports from Alan, Steve, and Russell. I was working on some small changes and taking the rounding error off of the mini invoice (3" customer receipt). Other small changes.

Eric will be coming in at 10 am to talk about loyalty points. Eric and I talked for a couple of hours about the special account tracking project. This deals with loyalty points, gift cards, in-store credits, you name it... We did a lot of drawing and even got into some small scenarios. We went full circle... we decided that they all go together and then not all together and then back to all together. Eric was tasked with looking into things a little bit deeper to see what we can do and what plans we can make.

Shawn came over and was working on state payroll stuff.

On the morning GoToMeeting session. We had Steve, Alan, Eric and I on the meeting at different times. Shawn came over to my house part way through as well. Eric, Alan, and I were working on the sales tax expansion and rounding error stuff. Steve was doing his own projects and Shawn was working on county specific payroll stuff for the state of Indiana. Mostly a work session today.

-Contact Bryan and Shawn about Texas Trailer forms - 130-u and VTR-141 - $100 for the VTR-141 form.