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.

Phone call with Calvin Chipman. Going over things and ideas. Lots of talk about AI and also about following the prompting that you get (spiritual help and promptings). They tend to be steppingstones for things down the road. Good phone call.

After talking with Calvin, I spent some time and updated the adilas investment options and opportunities PDF document. Made a few new changes and pushed up the new file. Here are the links to the web site version of the adilas investment options and here is the link to the PDF version.

Demo with Calvin Chipman to go over some AI technology that he is using and working on. We jumped on a zoom call. He is thinking about an exit strategy and trying to jump in on the AI race while it is hot. He is using an AI agent to go over dead or old leads and trying to reconnect with some of those people. We did a demo, and he will send me a video. He is using his Gmext product (group mass texting) to help send out those SMS messages (texts for a chat bot). Fun little fusion and combination and what he is doing, what he already has, and where it could go. I enjoyed the demo.

Working on more AI options and prompts. I have a small list that I would like to add and make happen. See EOT # 12286 in the shop (private).

On a meeting with Steve. We went over the adilas mini API and the new AI filters (sub filters within the main filter). We then talked about some proposals. I was pitching for some guys to help us out and work on specific projects. There were three code masters (Calvin, Brian, and Cody), maybe give them each 1% of adilas, plus $20K to cover (3-4 months). Just some thoughts. Steve wanted to know what they would be working on. I showed him the ship A MVP list that I have. Talking about how AI can help with training. That would be so awesome. Going over adilas lite and I showed him that we have the first 4 done. We also set a rough goal of putting adilas, llc percentages up for sale as of October of this year. Trying to generate some capital to keep pushing things forward. Other talks about projects and AI stuff.

Emails and phone call with Calvin. He is getting into tons of AI and wanted to meet with Steve and I to show us what he has been doing. We would like to meet with him next week. General to do list items. Paying bills, entering expenses, and other stuff. Had to update some API keys for the guys who are testing the AI agent for the POS (point of sale stuff). More expenses and paying bills.

A couple of days ago, I had a small dream about using the adilas label builder to help people market and sell their products. Nothing too special, but I wanted to record that I was dreaming about it. We are currently on version 3, made by Cody Apedaile. The code is live but we haven't really had people go in and start working on it yet (testing and playing with it). The new label builder is pretty cool and has tons of potential. I'm hoping that we will have people in playing with things and building labels within a few weeks. It is currently at a MVP type level. We have a number of other things we really want to do with it, but it is coming.

Just for the record: The adilas label builder - version 1 was done by Calvin Chipman. It was a standalone Windows app that connected to the backend adilas database through an API. Really good product but it was limited to Windows.

The adilas label builder - version 2 was also done by Calvin Chipman. We wanted a more open web version. He subbed some of the development out in order to make a JavaScript or web version of his original product. It ended up costing quite a bit and we basically ran out of funding. It only got part way done. We were planning a revamp of that code - version 2. After looking into it, we decided to take what we liked, and build a whole new version.

The adilas label builder - version 3 incorporates a new label homepage, a build new interface that is super flexible and powerful. It can handle static text, dynamic text, rectangles, circles, images, barcodes, QR codes, layering, stacking, and other cool dynamics. This is probably way too big, but here was an internal demo that we did back in December of last year (12/2024) to show off the label builder. Anyways, it is looking really good. I can't wait to help people use it and market their stuff, items, and products.

Prep work and looking around on the deli style barcodes. Making a plan.

Meeting with Bryan to go over some code. Going over projects and light review on some code and small bugs on accounts receivable reports. He is going to fix one more thing before we push those new changes up. We then flipped over to a different project and looked at some new code on Bryan's QuickBooks API stuff for invoices on account. He is making tons of progress there. His new code pushes up on account invoices and then records the external alternate id behind the scenes. Then, when that invoice gets paid off, internally, he used that external alternate id and pushed up payments to the correct invoice inside of QuickBooks using their API sockets. He is getting good at using that API route.

Sent a small email and error message to Calvin on an FTP error.

Meeting with the Lucky Puppy or Puppy Palace folks (dog nails and grooming service). They are looking for a multi-relational pets to owners, pets to techs, color based key, and tons of other things. I showed a small demo of the backend code and where we are at with things. They wanted to know where we are heading moving forward. They are a potential client and we are looking for ways to help them out and solve some of their problems. Suzi recorded the last half of the meeting when they were showing us some of their needs. These are some of my notes:

- As a disclaimer... I went back through the video and refined my notes. Original meeting was on 8/22. I rewatched the video on 8/26 and added a few more notes on 8/27/24. We already have a ton of these pieces. This meeting was to show us what they are wanting and needing and how we will need to put it all together. Just guessing, but I'd say we have 85% of all of these things right now. We just need to tweak a few things out, make some plans, add some new settings, and alter the flow a little bit here and there. That's awesome!

- Choose a customer, choose a pet, choose a service(s), choose a color, choose other assistants, check in/out, create a cart, manage the tips (split tips - they really want this... this was huge). Be able to copy the booking and rebook it (docking and rebooking). Email and text message back to the client. That's kind of a summary of sorts.

- Be able to edit the cart and add discounts during checkout

- 100 appointments a day - phone calls, changes, super-fast paced

- Show cancelations - what was there - They like to see what has changed, moved, or been canceled

- Adding a new client and making it quick - currently, they are using first name, last name, cell phone, email, and zip code. Be able to add more if needed. We have tons of settings there already.

- Notes on pets ... name, type (breed), age, size, up to date on vaccine, does it bite? etc. - thinking about flex grid tie-ins or a custom table there. On the notes and records for the dogs, maybe group things and then allow a subset to be shown. Go from simple groups (say per pet name) to more complex, everything tied to that pet.

- Each service has a time (block of time) associated with the service - there are some pros and cons to that approach. Anyways, just making a list of things that they were showing us and asking for.

*** Fast... they love drag and drop - They would love to be able to easily drag and drop and edit a time slot (length of the appointment - longer or shorter) all done through drag and drop.

- Making the appointments, changing the appointments, etc. - planning for the next step

- Major color code key - they are using multiple colors - each one means something - allow them to set up their own keys and values and colors.

- Tie-in the monies a little bit tighter - they would love to see it more or better - currently they are using multiple systems and then running the cards on the side. They would love to see it all tied in together better. Ideally, they are wanting a mix of an integrated scheduling software package, CRM (customer and pet relationship management), full POS (point of sale), ability to mix both products and services, and manage the money part of the puzzle. Sounds like our kind of game.

*** Tip splitting is huge... keep track of things... tight - reporting the tips split by person (by tech). Help automate this for them. Currently, they have to do it manually. This feature is big enough that it is a make-or-break level feature.

- They are having a problem with tracking their dogs... and having to read the notes for each one, over and over. They need the multi-relational database between owners and pets. We want to really help make this nice. I was originally thinking flex grid tie-ins... We may want to look into a way of doing sub queries or special grouping to make it smoother. We could also do some sort of custom table or custom joiner table.

- Being able to see the whole picture... they need techs, time slots, rooms, services, and needs (client and pet needs). All tracked in one place. Fully customizable - show simple to more complex.

- Alerts on the appointments - little flags - possibly even color-coded tags and flags

- A 3D view of the techs, the rooms, the appointments, the needs, the conflicts, the crossovers, etc. - that would be super cool - just an idea

*** Email and text messaging - app messaging - they really want normal text messaging including conversations back and forth. Here are a few other things related to text messaging needs: - Send message when booking the appointment, send reminders - multiple, send appointment confirmations - auto and manual, send booking reminders - some of their appointments are booked out 4-6 weeks in advance. There was also some talks about sending out auto emails for different actions or steps. Those would need to be defined.

- Switched to a different software package - They started showing us "Rosy" (used for 8 years - lots of data and history) - this is a human salon based software package. Part way through, the switched and showed us a dog or pet care solution called "GrooMore". They, the client, currently used Rosy in one location and the GrooMore software in another location. They are looking to get the best of both worlds. Ideally, we, adilas can come up with a mix and blend of both and become/be used as a newer or custom software option.

- They would like customizable enterprise - multi-location controls and flow of data, pricing, processes, reporting, etc.

- There are going to be transition strategies that need to be involved as our relationship develops. They want to keep going, with minimal issues, get back data, and make it all smooth. At some point, depending on what we can show them, we may need some transition strategies.

- There are too many appointments - a glitch could really be a problem - high volume

- They would like the option of seeing the last service, if known, per client/pet

- They want the appointment to hold all services and all assistants vs each service being its own appointment and each helper being its own mini appointment. More relational database connections.

- Their customer and service look-ups were really fast - asynchronous calls - like ajax or dynamic select or predictive text searches

- Be able to set settings for future interactions - what they normally get - be able to save that (speed things up by saving choices per customer and per pet)

- They need both owner names and pet names to show up on the view - They also want to see both names, client and pet(s), along with all services (cart line items), as well as other assigned flags per appointment. These would show up on the rollover or mouse hover action (aka the popup or rollover popup).

- They are constantly checking the schedule (visual display) to make sure all is well - help them out - simple look and feel with all of the details under the covers.

- Simple to add the other assistants - some appointments require 2-4 extra techs - make that quick. As a side note, the main appointment may be for a certain time and the assistant may be for a subset of that time. All tied to the correct pet.

- Showing conflicts - on the fly - both from calendar view and through a setup flow

- Showing the scheduling for any other assistants. Along with that, booking multi-staff appointments and then making sure that things stay tied together.

- Simple process (how long - in minutes) - add the drag and drop (super cool). Allow for both manual changes or drag and drop changes.

- Docking - saving or moving things - everything that is attached (all attached) - be able to move or put in the holding queue (session or memory) and then pull that back out when ready. Even having multiple things in the memory queue if needed. That would be cool. If needed, we could reuse quotes as a template of sorts. We could also allow for multiple things to be put in the queue. Kinda like a multi copy and paste board of sorts. You just get to manage it (really simply).

- Confirmed or unconfirmed appointments - checked in/out, paid, etc. - different flags and colors per appointment

- Colors - new dogs, bite risk, etc.

- Be able to book multiple staff members at the same time

- Multi-level sliding modals to add things - pretty slick

- Birthdays - it is nice to be able to just put in years and months and back figure the birthdate (help them out). Allow for either a real birthday or back figure based on the approximant (years and months combo).

- Being able to add tags for clients and tags for dogs - each their own tags and flags. Each tag gets a name/title and a color.

- Medical issues and comments - be able to add/edit

- Vaccination records - tracking that info

- Vet info - doctor info and such

- Dashboards

- Conversational text messages and using a huge texting tool

- Intake forms - QR codes or links - they add their own documents or forms (confirm and accept forms) - let the clients put in their own details. These client intake forms would be handled through the ecommerce or client portal section of the application.

- Quick jump from day to day, week to week, and month to month

- Notes - intake notes, appointment notes, ongoing list of notes. Being able to search and filter notes as needed.

- Be able to add/edit the tags per person or per pet

- Being able to search clients or pets by the tags. Thinking flex attributes for this.

- They are doing some mobile on-site appointments. They want to pull up clients in that area to say we are in the area. They like to tag their client's general location (area) to help with targeted marketing efforts.

- Bulk text messaging based on filters or tags - batch send out things based on applied filters of the larger record set.

- Searching by pet name and then finding the client based on the dog or pet name

- Deceased dogs - dogs that have passed away - they still want to see it - maybe just flagged vs not fully deleting the pet profile.

- They would love integrated financials - in the end

- Reach out to Jen if I have other questions. Debi and her crew seemed to be pretty busy (booked).

- Just an idea, currently we allow for photos and media/content to be added to the main customer or client records. Up to 100 photos per client. Do we want to open that up and allow for sub groupings withing the photos for the specific dogs? We do allow things like this to take place for parts and general inventory items (photos and media/content for subs). Anyways, this could come later as well, if needed. Just an idea.

- Empower them on the setup and layout... Let them drive it - block sizes, what to show on the title per appointment, what to show on the hover (rollover popup), color keys, flags, etc.

*** vertical time view (a design has been built by Chuck - branch CAS-93)

- For me - claim some time - make time for it - review the video and make a plan... make sure that we have access to the correct demo site and make things flow there. Thinking about settings and putting the power in their hands - put them in the driver's seat. Wow - great meeting!

1/13/25 Bryan and Brandon meeting 

To outline what it would take in time/money to complete this project.  Then take the information to Steve and Suzi to decide if we are moving forward or putting it on hold. 

A ball park estimate without outlining each project would be at least 200-250 hours ($20,000-$25,000).  At 20 hours per week (which Bryan has available) it would take 3 months.  This project would be utilized in similar pet grooming and salon type businesses.  Currently Puppy Palace would utilize this.  At $300/month the ROI would be 5 years.

1. Vertical time view. (20-40hr project)

    a. Populate Charles' layout

    b. Already have a time slot view.

2. Add drag and drop. (done fairly quickly because time slots already exist - Javascript edit).

    a. outsource this to Cody (20-30hr)

3. Tip splitting. (20hrs)

    a. tips field exists (Eric) on the main invoices if using CC.

    b. open up so that any cart can utilize it.

    c. create a tips page.

4. Texting/email API. (30-40 hrs)

    a. Garrett/Calvin created apis with Twillio.

    b. General filtering (no "cannabis", other reserved words).

    c. They pay 3rd party directly, or pay through Adilas? Monitor and record that.

5. Flagging and Tagging tweaks (15-20 hrs).

6. Pet specific needs. Owner to pet, pet to vet, etc.

*** could be used for multiple Adilas projects.

Various things going on. Emails, phone call with Calvin about his FTP uploader and some new changes. Phone call with Cody about using asynchronous calls between JavaScript and ColdFusion. Started putting together a small sample file of using JQuery with ColdFusion. Sent some time building a special clean-up page to help with updating barcodes and adding leading zeros (padding with zeros - dynamically - as needed to reach a certain size). Busy evening!

Meeting with Hamid. He's learning and going through some ColdFuison training stuff. I gave him a small mini project to work on. I'm going to have him work on a small budgeting tool. Really simple. I also sent an email to Calvin requesting a version of his MySQL Editor for Hamid. See attached for some notes on the budget project.

Random start to the morning. I was planning on doing some yearend payroll updates. I ended up doing about 2.5 hours of phone calls instead. Emails and then a quick phone call with Calvin Chipman. He was trying to help a client with some changes to an inventory API socket for custom labels.

I then got a phone call from Steve. We were chatting for over an hour. Good update on where things are at, current projects, upcoming projects, sales, networking connections, update on ship A and ship B (current adilas vs fracture or adilas lite). I told Steve that we have gathered tons of information and notes. We are now formatting things and trying to make that information get into a presentable version and format. We have tons and tons of the main things researched and prepped. Anyways, that will continue to unfold as we roll into 2024. Great phone call. We also talked about developers and clients.

After talking on the phone with Steve, I got on a call with Bryan. He had some questions on where we are going with certain projects and looking for direction. Jumped back on a call with Calvin and we did some testing and debugging on the API socket calls. We ended up on the phone for over 45 minutes. Testing and looking at things on data 4 for the client. Emails back and forth with info.

Sean, Shari O., Michael, John, and I were on the morning meeting. We all checked in and said what we were working on. After that, we all either left or went on mute and worked in the background. Shari O. had to take a tech support call and Sean was waiting to chat with her once she was finished. John had some flex grid tie-in questions. I was doing some research on MVP's and past data that we had recorded for what we wanted in some of our MVP (minimal viable product) stuff.

Here is a short MVP list that I'm thinking about - for the record, we already have some of this, we just need to refine it and make it watertight:

- Special accounts and in-store credit - We already have loyalty points, and round 1 for gift cards. Eventually, we would like to do in-store credit, vendor credits, punch cards, and other ones. The next biggest need is for the in-store credit stuff (in my opinion).

- Round 2 on gift cards - We've been gathering ideas and wants and needs

- Coupons and promotion codes - clear out and through ecommerce and internal shopping carts

- Take Calvin's adilas label builder to the next level - we've already done some planning and prep work there

- Standardize the merchant processing options - We have like 9 different integrations. Here's my next goal, pick one, make sure it flows from start to finish and is super simple. I want to do normal sales, pre-auths, captures, tips, refunds, voids, and reoccurring payments, etc. We have to be able to do manual key (like ecommerce mode), swipe, chip/EMV, and tap to pay hardware integrations. I want to do and offer all of the merchant processing functions. I was thinking that we could do a big push and try to get all hooked up with Datacap and then let them handle all of the different hardware pieces and different merchant gateways. That's my thoughts right now.

- Revamp the internal shopping cart, my cart favorite buttons, and general look and feel. I would love to head towards the fracture project - we have a bunch of R&D on where we want to go with that.

There are tons of other things on my list, but that is my quick MVP list for right now.

Zoom session with Calvin. He was showing me some of his new OCR (optical character reading) data extraction from images and PDF's. Pretty cool. I could see a company getting an invoice and then have the system OCR the data into the right spots. Tons of options that way. He was even showing me how it did with stuff like blacked out lines, scribbles, or scripty type handwriting. It wasn't perfect, but pretty darn good.

Both Sean and John checked in. John and I were going over Calvin's bulk server FTP tool. John has it setup and may need some help configuring things. I went in and was working on emails and then I spent some time looking into a small clock in/out bug. Pretty quiet morning.

All kinds of random stuff. Emails, local computer setup, installing Calvin's tools, Microsoft Office, printer drivers, scanner software, entering expense/receipts, antivirus stuff, and a phone call with Dusin. All over the place.

Installing new software and tools from Calvin. Phone call with Eric to go over inventory snapshot project and how to get certain info back out of the system. I spent some time being stuck on a database problem.

Phone call with Calvin about Emerald Fields, Gmext, and possible Mac version of the bulk FTP uploader tool. We also chatted about some of his other tools. They have been a huge help and we, at adilas, use them every day.

Shari O. and I met on the GoToMeeting session and went over new USAePay accounts, settings, and logins. Part way through I got a call from Calvin and we chatted for a bit. Shari O. and I jumped back in and were looking at more settings and playing around. As part of the meeting, she was showing me what she does to track and correctly process the reoccurring invoices that done inside of adilas. There are a lot of places that we could help her out (automation). We may have to circle back to that.

As part of our meeting, we also went in and looked around on some of the new Trinity Payment stuff as well. Basically, a small look-y-peek into their backend card processing interface. It looks good.

Work session on Calvin's custom label builder. I took a bunch of notes. Cory and I were doing a virtual tool beat-up drill and pushing on the adilas label builder - prototype. John was in the background working on his own projects. At the end, he and I talked a little bit about the code and what kind of backend needs will come into play as we dive in deeper on this project. We have spent over $20,000 on this project but it still needs a little bit more. Trying to figure out what it does and what we want it to do. Good session.

Meeting with Cory. We were talking about projects for Eric. We also want to get back to Calvin's label builder (review and make a plan). Other tech support stuff.

Long meeting between Steve, Cory, and I. Cory was reporting on tons of different projects and getting our input and suggestions. We covered tons of different topics. Here are some of my notes (from 10 pages of post-it notes - didn't know it/we would cover so much). The original meeting was only setup for an hour. It went a wee bit over... :)

- Talking about tons of custom label options. More talks about what to do with Calvin's custom label builder. We've spent a lot of money there and want to really get a return on that investment.

- We talked about bringing projects more internally with our guys and breaking things into smaller and smaller pieces.

- On labels, we had a request to be able to do serialized labels (up or modify counts and counters based on batches or packages).

- Using tons of our existing tools and refining those pieces. We have a ton of tools in the shed (virtually).

- Lots and lots of talks about breaking up the bigger projects into multiple smaller pieces. Along with that, we need to be able to charge money for bigger estimates. Everything takes time and effort. Either that or be able to recoup the amount within the bid or estimate.

- If we are doing real custom work, we need to charge for that. Often, we end up taking a hit.

- The trend seems to be (globally) transactions and details going into aggregates and summaries. We have had so many 3rd party analytical companies wanting to use our API sockets to harvest and use our great data sets. We would like to do a bunch of that analytical work inhouse vs farming it out to a 3rd party. All of these 3rd parties are just working for individual companies, but you can see the trend happening. Our clients are really wanting to get to the business intelligence level (BI) for viewing their data, snapshots, counts, summaries, and other aggregated data or stats.

- We went over some pros and cons of using the adilas API sockets. Back and forth on monetizing those channels and also making sure that they don't get abused or flooded.

- Lots of talks about the item catalog and the image catalog. As we use more and more API sockets, we could really use bigger and bigger bulk tools to help with data standardization and speed of deployment. Lots of positives. We, as a company, could also sell more systems if we brought in the enterprise level (way up - cascading info down to lower systems). Good stuff.

- More bulk standard tools. This just adds to the votes for building out the value add-on core model with different levels. Just as a recap - the value add-on core model deals with 5 known levels. They are: 1. Transaction core (current adilas system), 2. Industry specific skin, tools, and features. 3. Any custom code on top of the main system. 4. BI - Business Intelligence levels (stats, sums, counts, averages, mins, maxes, aggregates), and 5. Enterprise levels - connecting multiple worlds in a hierarchical type system (roll ups, roll downs, transaction corps/worlds, aggregates and sum corps/worlds - also dealing with permissions and access). We really want this type of a system for our future fracture project. We already have a number of pieces to this project (all kinds of prototypes spread all around the system), it just isn't all put together. That would be so awesome, clean, powerful, and hopefully pretty!

- We spent some time talking about our clients. Sometimes they get pretty creative. That is both good and bad. If they get creative, and find errors or break things, we just fix them and keep going. Other times, they totally use certain tools in ways we never would have imagined and/or foreseen. That can get interesting.

- There have been some requests for bulk tools for updating sub attributes and bulk sub inventory tools.

- Cory kept asking - Who are we? We tend to build generally but then we have all of these industry specific demands that keep coming at us. It makes it really hard to know where to focus. We really need to decide who we are and then hopefully that or those choices will help guide us.

- Dealing with Metrc (state compliance systems), we've had the request to build out more individual user type functions. This is dealing with more employee/user type permissions and settings. Currently, most of our Metrc transactions are done on a corporation or world level. The new requests are to do the exact same things but break it down on a per person basis. That sounds awesome, but that could be hundreds of thousands of dollars in development. We would have to create the one-to-many relationship, make sure that they were valid, then sync up users and permissions between systems in order to play. Then, to further make it kinda crazy, you would have to check user permissions (remotely) then attempt the connection, then if it failed, figure out if there was a global (higher up) option that you could do so that it wouldn't break all of our code and processes. It could be a huge project. Lots of unknowns. As part of this project, we would also have to add more history tables, who did what, who changed what, who has permission to do what, and making sure that each individual keeps their keys and tokens updated. It sounds like a small nightmare.

- We seem to build in general and then use it specifically as needed. Custom code on top of our own standard package, tool, or feature.

- Going over the cost of building and building. One you have to build it, then you have to maintain it, and upgrade and support it. The costs keep increasing. This topic lead us back to questions about who are we and where should we be focusing?

- There is a growing need to use asynchronous type loading like AJAX or some way of breaking huge datasets into smaller pieces. It is totally common for us to need to show or export 10,000+ or even 100,000+ records at a time. The current process tries to take that whole thing as a single bite or single attempt. It's just too large and slows things down.

- Some time was spent talking about loyalty points and keeping track of the total liability. More talk about other reports that show sums, grouped values, look-back capable reports, and using ACV (actual cash value) for recording loyalty points. We do a bunch of that, just refining the process and making it even smoother.

- Need for messaging or using the message marketing features that we have already built. There is a growing need for push notification and two-way communications outside of the main app or website. The client portal is growing in needs and options. More mobile ready or full mobile pieces are going to be coming down the pipeline. Everything seems to be trending in that direction.

- Question - do we fill in the gaps on functionality or try to update the look and feel? It sure would be awesome if we could virtually turn things on/off based on the UI (user interface) and settings. We would love to set things up super simply and then let the users add on or take away from our smaller base level. A new mini version of the shopping cart is in great need of these fracture type level settings. Start small and simple and then let the users build on or configure things as needed. Hide anything that we can unless asked for. Then when it is done (using the tool or feature), it can be hidden again. Every page needs show/hide options on a per page or per section level. Totally customized.

- Along with the show/hide options talked about above, it would be so cool to show all of the options and then say - what do you want? You tell us. More fracture stuff (where we are headed). Mountains and iceberg analogy stuff (it still needs to be there, but what is shown and/or exposed).

- We talked about extra costs and prices for some of the other add-on tools and functions. Some of our stuff (tools and features) takes a major amount of work and effort. We would love to sell more training, consulting, automation, and other professional services.

- News and updates and the importance of keeping our users up to date and informed. This seems to be a constant need and keeps evolving. Content and making and creating new content (creation and maintenance).

- Lots of talks about prioritizing efforts for different persons (parties). Diving out responsibilities and sharing info across departments and across people (users).

- Using videos - the value of education and training. Selling our other services. Scheduling and setting up ongoing training efforts. We would love to make lots of polished smaller videos. Laying it all out for our clients (on demand education or just in time education). We could really use our website to toot our stuff for different business verticals. For example: Revamping our manufacturing site and pages. We can handle... (fill in the blank) for manufacturing or whatever. That is a deep pool (manufacturing and production type businesses). The trend seems to be leading us more in that direction.

Emails, text messages, and other follow-ups. Recording notes. Installing some new tools from Calvin Chipman. He has a new image converter and a file renaming tool. Got those installed and ran some tests. Calvin is the tool guy. He loves making his own little tools to make things go faster and faster.

Got on a GoToMeeting session meeting with Shari O. to over our existing options for USAePay and getting re-familiar with the USAePay virtual terminal for credit cards, refunds, batches, and other transaction look-ups. We took a couple of screenshots and will be sending some emails to Newtek tomorrow to help get things going in the right direction.

This is just for fun, but earlier today I heard Cory say - "We the bananas from so and so (a client)". It made me laugh. The term "bananas" is what Shari O. uses instead of saying money. I told Shari O. that she is rubbing off on us... :)

Cory, Steve, and I talking about merchant processing with both Elavon and USAePay gateways. Trying to figure out the best approach for those two solutions. We already have active code and implementations with both gateways, we are just trying to figure out which one to sort of lean on and favor (business decisions). Both seem pretty good, just weighing options.

Steve, Sean, and I jumped on a small fix it project for the complex labels (QR code and normal barcodes). We got in there and made a number of changes and pushed up some files. As we were talking about labels, we brought up Calvin's dynamic labels and the need to get back in there and work out kinks from his dynamic label builder. Marisa joined and had some label questions. That shot us over to the barcode custom labels and using the complex label generator to store sub packages, fixed quantities, and fixed costs, all tied to a single barcode value. Kind of interesting that the custom labels came up multiple times this morning alone. Pretty crazy!

Quick phone call with Calvin to touch base and talk about some future projects and wish list pieces. We have been working on some custom labels and would like to get back to that project. It was on hold for a few months as Calvin was working on some other projects.

Going back through my post-it notes and recording entries from today and all of last week. Got behind a bit. I also got on the phone with Steve for a bit to go over some more possible options for the adilas trust or how we want to split some things up (shares and percentages). Making progress. All part of the plan that keeps unfolding in front of us. I honestly don't think anybody could plan for everything that has and is happening. I surely couldn't comprehend it all. You almost have to take a step and then deal with what you see. You can plan certain things, but there are many things that just start happening and unfolding along the way. It makes it responsive and more dynamic as you go. Good stuff!

Cory and I going over projects. Talking about some of the upcoming internally funded projects and budgets on those projects. Here is a small list of some of the things that we know are on the horizon.

Future Development & Projects
- Client facing scheduling – bike shuttle
- Global or enterprise item catalog
- Dustin's Cultivation & Harvest Stuff
- Invoice due date & auto collection on A/R's project(s)
- Labels & label printing - Calvin's tool(s)
- Compliance and SOC reports (SOC=service organization controls)
- Switching over to Lucee vs Adobe ColdFusion - potential $2,000/month saving – reoccurring - $24,000/year savings
- Our own project costing

We also talked about meetings and which ones are the most important. We would like to trim that down a bit as well. Trying to get schedules and timing all figured out.

Danny and Eric talking about PDF labels. Printing and controlling hardware is tough over the web. Lots of talk about possible settings and allowing users to either interact or manage settings to get the desired outcome. There was also some talks about specifying certain hardware and then fully supporting it. Currently, bigger decisions than we want to make or commit to. In the meantime, we talked about some options and possible hacks (quick solutions) that could help advance the ball and help us know where problems reside.

We already have one, but it needs to be refined and tweaked out a bit, but we need a full dynamic web-based label builder app. Calvin has built us one, but we haven't had the time to get in there and tweak things around like we want them. It works, it just needs a little bit more loving.

Reviewing code with John on some small state payroll updates. John is working on new state withholding calculations for the state of Massachusetts.

Eric and I were going over a customer automation process for a client. Eric is working on a custom (client funded) project for a trailer dealership and their needs. 

Doing some scheduling for the next couple of months. Planning, emails, follow-up, and recording notes. I got on a phone call with Calvin for about an hour. He has been super busy and doesn't see an end to the projects that he is on. We may have to take some of the projects that we wanted him to do for us and pass those along to others. Great call and good to catch-up a bit.

On a meeting with Bryan going over the Paypod project. We did some research on Google and tried a few things. We are stuck on some Windows certificate pieces and how to connect and pass data back and forth with the hardware (or even the hardware simulator). I think that this project is going to take an actual Windows developer who could create a small piece of software as a bridge. Both Bryan and I are web developer, and I'll speak for myself, this project is over my head right now. We are going to need help from someone of the Wayne or Calvin type level. Hardcore software/hardware guys.

As a note, I told Bryan to hit the pause button on this project. I also sent text messages to both Cory and Steve letting them know. We are spinning our wheels right now.

On Friday, June 11th, 2021 we had an internal conference day for just the adilas team. We went from sales to internal code to ideas and plans. All over the place. See attached for my notes. Many great things were discusses. Once again, this was an internal team meeting, but we don't mind sharing what we were talking about. :)

//////

The attached notes are better formatted, but I wanted to push some of them here for searchability:

//////

Group Sales Meeting

Marisa, Danny, John, Cory, Sean, Steve, Dustin, Shari O., Dawn, Brendan, Steve (mac), Brandon, Chuck, Alan, Kelly, Bryan

- Kelly was saying that there is some public records per states

- We may try to pull our own list

- Questions... who, what, where, how good, etc.

- Maybe look at a sample of 10

- We may need a more focuses approach

- What about different industries?

- We need to get the name out there

- Kelly was pitching a social presence

- Do we know anybody who wants to do the social stuff

- Word of mouth

- Testimonials

- Some new video graphics

- To the penny, to the gram, every day

- What about small streaming commercials – focused and pointed

- Kelly recommends that we maybe focus on a slightly larger pool

- Dawn – maybe focus on start-ups or that small to medium range

- Get them at the beginning – maybe even tradeshows

- It is a pain in the but to switch over – pain creates options for change

- Focus on services... deployment, oversight, consulting, training, best practices

- How can we deploy something easily and repeatable?

- It is tough to get some of the people started, but once they get all in, they tend to stay

- Kelly has done this over and over again

- Using the professional resources that are available

- From Kelly – Help get the clients all the way in – full system and platform

- Getting the success on the first implementation and then building from there

- What about focusing on those who are having trouble and/or are struggling

- Dawn loves the support, training, and feel good part of it – duplicate that feeling to others

- How quick can we respond – we jump pretty quickly on custom needs, development, training, and support

- Get more testimonials from our clients

- We have some experience to offer to those who want it

- What about pitching best business practices

- It's ok to be non-traditional

- Being Relevant!

- Focus on helping over sales – from Steve (mac)

- Simple things that bring the relevant pieces

- Social webbing – group effort

- Danny, straight up, I don't want to be the social media guy! We have to find the right person and/or persons (small little team)

- We are not QuickBooks... what does that mean? Be our own style!

- Packaging this platform based on the target audience

- Formulating a plan – ease the lift – maybe a monthly meeting with some planning

- Influencers and YouTube options

- Small info tips...

- New age marketing – we have to play to the current market

- Big Dumb Animal Pictures – super simple

- We have to do a cost analysis to see which one(s) make more sense for us

- John, what if we setup our own little social piece (aka maybe the adilas cafe) – we could allow all of our users and power users to pitch and promote – we may need to approve things, but we have tons of very knowledgeable people and users

- We are looking for engagement – back and forth – a relationship – maybe get an intern to help handle this

- Danny – Switching over to the modal message marketing

- How to save the app to your phone

- Make the email piece better

- Small web tool to help with building special html links to embed promotions, direct add to cart, discounts, campaigns, etc. A simple form to help with the backend tech of those URL's and web links.

- Maybe, we need to upgrade our email platform. It is a small holdover from years gone by.

- What about the delay on the outbound emails?

- Marisa – maybe outsource things as needed

- Steve – would like more input on the bulk tools

- Better filtering and target marketing

- Steve wants to work direct with Dawn and Branden

- Matrix and target marketing – even predictive

- Maybe a little itty bitty (super small) native app on the different phones – iOS, Android, etc.

- Steve wants to get into possible predictive marketing

- Steve – looking for great feedback and even ideas and dreams...

- Archiving, saving for later, dismissing, etc. We have the data, what do we want to do with it? – Wet clay...

- Danny – Going back to past clients

- Version 1 vs Version 2 – type attitude

- What kind of clients do we want? We may not want certain kind of clients.

- We love people who like details and are willing to play

- We love people who take things to the fullest level

- We love people who just need a small little piece – there is a gap in their current model and they need some help. We can then grow from there.

- Do a full comparison of what we offer

- Pitch what we do differently – we help deploy and maintain your ERP

- White glove approach

- Playing with the tools that we have and flipping those into marketing messages

- Chuck – maybe check out some groups on Facebook

- Blog posts, articles, info snippets, quick videos

- Talking with Kelly – how have we helped small businesses become bigger or big business – showing the potential – dreams to reality

- The small goals to achieve – steps to get to the next level

- Small goals lead to bigger goals – getting some small successes along the way

- Clients and expectations – not all money is the same – budgeting and planning – what kind of client do we want

- Reoccurring revenue vs one-time revenue

- A quote is just one of many pieces that needs to be done

- People, skills, and cogs in the wheel

- We all care... where would you and your skills fit in best

- Seeing the bigger picture

- Maybe looking at personalities and figuring out the mixing and blending of our options and resources

- Slowing down and taking the time to see where we are at? Virtual time travel – child, youth, adult – as a company

- What's the difference between a goal and dream? A plan!

- The internal group summary that we did... a great start

///////////////////////////////////////

Second session - Servers & Infrastructure - Refining Our Processes - Tech Support & Training - Project Management

Steve wants us to show the online label builder

- We had some good talk about where we want to go

- We pointed to our internal summary report

- Steve McNew – helping with the strategic marketing plan, technology road map, timelines to position, plans for action

- Scale – can we grow and can we shrink

- Conversation between big and small – perspective – big and small (sales, number of team members, lines of code, etc.)

- Molly – Is adilas the big guy or the small guy? Think of code (lines of code). We could be considered a big guy if you were looking at code and functionality.

- We like being small (ish), but what if we are big already

- If we want to grow, that means that we want to get better – grow in a good manner and sustainable manner

- The underlying services that support the whole

- Be your own style!

- Steve McNew – old classmate with Steve Berkenkotter – guest speaker – part of the adilas team to help us get some things more standardized – processes and procedures

- Defense contractor for the military – 28 years

- Testing, software, management, auditor

- He has already called, interviewed, and talked with a number of different team members

- He did a 20 page audit and report on what he was seeing

- Getting into some testing and processes – he would like to see more of this

- Not trying to derail the train – we are trying to polish the Ferrari (spelling – awesome car)

- Whitepapers – catering to a higher audience – going beyond stick figures and into technical docs – not everybody will want to read some of these, but there will be some that require it

- Steve B – if we try to sell our product to those who can't afford it, it doesn't really work. They have to be able to pay for what we do (really do – billing for our time and efforts)

- Fin-tech – financial technology

- Using whitepapers as part of our marketing plan

- John M – unit testing – confidence of the developer team – currently only Wayne and Alan are doing this (unit testing)

- Going to ease into this – refining our testing plan

- Version control and when do we update these systems? The older way was wild west... we may want to figure out some specific micro builds.

- It would be nice to keep track of the versions and options.

- The balance between core and custom development

- The application needs some spring cleaning – what is being used, what isn't, what is going slow, etc. – Refactoring

- Priorities – customer priorities or our internal priorities – what is the mix and blend of these pieces

- We all ware many hats... we may need to define that so that we don't overstretch ourselves

- We all use (and can use) the system in different ways – how do we translate that information to our clients, other developers, and other team members (upstream and downstream)

- 2 minute videos – no more

- Work instructions – even giving it to someone who has never done anything in the system

- Danny – Shoutout to Steve and Brandon – we have done great – what is coming next? Resources?

- Talks about earn and burn ratios

- Prices have to match the services

- We are a growing business

- Kelly – going from 1.5 to 10 (millions) – that is a huge change

- We are competing with companies that are hugely funded... what do we want to do?

- There are some real things in our path – there is tons of potential – what do we want to do with it – also, sometimes there is shelf life on potential or advantages

- We don't want debt – however, there is a time for debt – cost analysis and being smart about it

- Making choices, but also being willing to fail

- Marisa – look at our new website

- Steve – there are some percentages of adilas that are available – not looking for vulture capital (just being silly – vulture vs venture)

- Someone looking to take on some risk but helping us to get to the next level, without taking over the company

- Kelly – pitching our vision and business plan – we have to define the vision – Danny seconded the define the vision before looking for the funding – goals, sales, budgeting, maintenance, and getting a business plan.

- Adilas Trust option – co-founders

- Possible option – Maybe take some of IP (intellectual property) and sell that to a new entity and then restructure those new pieces

- Dustin – thoughts on corporate structure – we are all on our own little islands – Ferrari to a tricycle – frontend compared to backend – splitting up those pieces and functions – he wishes that we could be more collaborated.

- John – teams and buddy projects – small sub teams – full stack (all levels) vs specific skills or somewhat limited skills – this needs to be part of our plan.

- Sean – we already have some small teams that are working on some of these projects – cogs of the wheel – buddy tagging the workflow and processes

- John – the adilas docs project – and being able to go to it and also add to it – working on standardizing the pieces – filling in the gaps

- Danny – Navy Seals – two is one, and one is none – at least two on a project – two-by-two

- Kelly – scale – having a back-up

- Danny – accountability back and forth

- John – confidence levels

- Kelly – what about a succession plan?

- John and Dustin – real life buddies and how they help out each other – seeing a different angle or perspective

- Marisa – tooooooooo much weight gets put on single persons

- Kelly – relieving pressure and helping with scale

- Marisa – Cory, Kelly, and Marisa – wonderful training slides, presentation, and delivery for the conference. Awesome job!

- Alan – modularize things – able to be reused – code concepts can relate to business functions – one to many relationships – translating knowledge into real life and different scenarios

- Chuck – last summer Chuck was on a joint project with he, Russell, and a different John. It worked out awesome – Keep pushing towards that kind of rollout of the project

- Molly – thinking and coming up with ideas. Keep it going!

/////////////////////////////////////////////

Next Session - Deployment & Oversight - Design & Layout - Internal Core Development - Custom Development 

- Deployment – where are we going and how can we make this all work – team effort

- Shari O. – first touch and setup corp, Sean and Shay first hour or so, Sean helping to coordinate the next steps and pieces

- Sean does a great job of reporting back

- Report on things, record the notes, get back with us to help us keep pushing

- Doing great with testing and prototyping

- Kelly – who is on settings, who is on planning, maybe even looking at pre-deployment options

- Before Kelly even does a demo, do some consultation – figure some things out without doing any pitching or selling. This is called listening.

- What are you looking for, wanting, expecting, hoping for?

- Make the demos custom to the pain points or key wants and needs

- The prep work is huge to help them be successful

- This platform is not a turn on and go type system – there may be pre demo, consulting, custom planning and demo, then custom hand holding to get them going down the road

- Picking the point of contact... who is going to own this thing?

- Owners, managers, and users

- Users want the easy button – Steve calls this the tail wagging the dog vs the dog wagging the tail – what is and how can we get buy in?

- Tools are great, but solutions to problems and pain points are even better

- Give to get! If you give too much, it can get you into trouble.

- What is the cost to fixing things... on the other hand, failing does help with major learning – there has to be a balance

- We tend to remember pain – setting people up for success

- Often users are looking for a quick switch. This system takes work. Please sell it that way.

- Not going to custom too quickly – learning the manual way – then automating it

- User buy in – light pain and then helping them learn a better way

- Change proposals and scope of work – setting up boundaries

- Feature creep – setting that scope of work – cause and effect of what they want and what they give – expectations and timelines

- Sometimes I start with NO – interesting

- A saying no - sandwich... Yes, I'd like to, no, I can't. Yes, I would love to help do this... - people think that no is a bad word

- Having a plan to say yes, vs just saying yes

- We like to please people – that is awesome – what does that cost?

- Help make the plan to say yes. Maybe, no (first), however we could do this...

- Making things repeatable

- What are the internal costs to do deployment?

- Say $350 for a setup fee – does that cover it? If yes, great. If no, where does that put us?

- Maybe on the setup, prep, an activation fee (define this – turning on the lights), setup and deployment fee (range), training, custom code, imports, labels, etc.

- We like to cater to everyone – that had bitten us

- Actual prices and then use discounts if needed. You can't really ever raise a price after the fact.

- Back-up our prices

- Use adilas to run adilas!!! This is our communication tool, let's use it.

- We are good at the dreaming and software building part of things, we need some major loving on the service side

- There is demand!

- What pulls at our time - It is time, money, skills, etc.

- Kelly – earn has to be more than burn

- Flipping the demand to sales or services that could be provided

- MVP – minimal viable product, plan, player, etc.

- Intangibles

/////////////////////////////////////////////////////

Next Session – Show and tell! What are you working on?

Calvin – Advanced file and folder finder, resize images, convert images

Brandon – harvesting assets from element of time

Steve – parent attributes report, items not on a recipe (manufacturing), modal message marketing for customers, log notes for vendors and employees (payee/vendor logs), backorders homepage, mini units, auto add item (quick PO behind the scenes), bulk update on the vendor – master copy paster... :)

- Branch 122 – fun

Bryan – cfqueryparams – stop SQL XSS (database hacks – cross site scripting)  - SQL injection – converting from dynamic queries to secure dynamic queries - Example: Corp_id = #Trim(some form or URL var)# or Corp_id = <cfqueryparam etc, etc,> - this stops the SQL hacks

Bryan is also working on eChecks for eXPO, Hypur checkout in the shopping cart (eComm), new API's for delivery (with documentation and samples)

John – Payroll project to allow holiday date picking, timecard flags, timecard totals (pre summing the math to go faster and lead towards bulk payroll), new timecard reports showing grouped sums and totals.

Page templates and style guide defaults with Chuck – Going from old school tables and links to the newer grid and mobile ready code. Part of the adilas docs project. Build once, use many (effective copy and paste). Basic templates (3 new ones). New information icons and popups (modals). Style guides and usage of those pieces.

Servers with Wayne

Chuck – Huge new web site!!! Awesome Job!!!

Global Design Dashboard, adilas docs, and new presentation gallery (sales tool).

Danny – message marketing, custom labels, sales team meetings – hats off to all of us! Keep listening and keep finding solutions. Open table – follow your highest excitement and be yourself! Be happy!

Alan – enterprise level catalogs, refactoring code (custom page settings), standardizing code for speed and reliability.

Random comments – Cory really liked having access to all of the team members, right here at the conference. Marisa – great to meet everyone – keep floating the boat. Sean – he likes the team. Molly – loved watching and wants to be involved. Chuck – idea of everyone joining slack

On the phone with Calvin going over the upcoming conference and touching base on the online label builder project. He is really swamped right now with a project for his son. As soon as he surfaces again, we'll get him going on things that we want and need for the online adilas label builder project.

Sent an email out to Calvin and Chuck dealing with the online adilas label builder and some new changes that were pushed up. It is getting closer but still needs a little bit of work. After that, I spent the rest of the time prepping files to switch primary web sites and homepages. Changing thousands of links from www to data0 sub domains. Lots of water under the bridge (years and years of development).

Going over the online adilas label builder app that Calvin made and adding in some navigation, spacing, and helpful hints and tips. Removed the flash interface options from the chooser page and pushed up files. I'm sad to loose the flash interfaces. They were some of my favorites. Oh well, on to bigger and better things!

Went out to Calvin's house to meet with him and talk about timing, funding, and projects. Took him a good sized check to get him all caught up. 20 miles.

There were a bunch of guys and gals on the morning meeting. They were talking about custom labels and we decided to look and take a sneak peek at the online version of Calvin's adilas label builder. We just had Chuck make some upgrades and changes to the look and feel of the label builder. We pulled it up and let everyone get a sneak peek. It needs a little bit of loving, but I would give it a 90% or completion rating. Looking good. Nothing a few more hours can't fix.

We also talked about some new JavaScript functions and how to use them globally across the whole system. Lots of input there. We also had a few fixes that we pushed up online for a couple of pages. That is what we do, constant refinement.

The last thing that we did as a group was some general training and a small Q&A session with those on the meeting. We have a great team!

Phone call with Calvin about upcoming projects, goals, and vison. Goo phone call.

Working with Eric again on the sales tax aggregation code and checking things out. Small work session.

Calvin joined Chuck and I on a GoToMeeting session. We were looking over the web version of the adilas label builder project. Calvin has completed his part for round one, and Chuck is putting a facelift or skinning it, to make it look good. We broke a few things while trying to make it look good, so we pulled in Calvin to see if he could help us re-fix them (a color picker and his dynamic input values). We'll get it all working before we launch it. Good session with both Chuck and Calvin going back and forth, trying different things, and looking up assets and code pieces. We made some to do list plans and then we got into some light training. Good meeting.

Met with Chuck for about 15 minutes. We drew out an overview of the invoice due date project. There are two phases there. One is the actual invoice due date portion. The other is using API socket connections and checking those invoice due dates on login to see if there are any outstanding invoices and then warn/prompt the users (our clients) for action, if needed. Basically, a way to chase down monies owed and accounts receivables.

Chuck and I did a small session on the web version of the adilas label builder that Calvin has been building. Chuck is reskinning it and making it look nice.

Emails and paying bills, after Chuck popped off the meeting.

On a GoToMeeting with both Calvin and Chuck. Calvin has released some code to us for the web version of the adilas label builder. It works and is live, but we wanted to give it a little look-and-feel lovin before we released it (letting everyone know). Chuck will be do the re-skinning job on the adilas label builder. We met and recorded a small portion. Basically, we went over what we wanted and needed and some finer details of the label builder project. See attached for the recording.

After that, I jumped back on trying to catch-up and record meeting notes, emails, uploading videos, etc.

Phone call with Calvin going over over some details about the web version of the adilas label builder. I merged in some code for him and pushed it up online. We are going to use some of the existing permissions for label building to tie the new web version in with the main adilas.biz system. We will also get Chuck involved to help with a small face lift for the new web version.

After talking with Calvin, I then called Cory and we did some planning and coordination on different projects.

Debugging the web version of the adilas label builder with Calvin. Recording notes form post-it notes to the developer's notebook - elements of time entries.

On a meeting with Wayne and John. We were looking at stuff on the content server. We were checking into FTP options, database stuff, server-side logging, and API socket connections. The content server mostly sits there and serves up files and media/content pieces. However, as we keep pushing things forward with Calvin and the web based adilas label builder, we are using the content server more to help with the processing of those pieces. Anyways, things are moving more in that direction.

On a Zoom session with Calvin working on the web version of the adilas label builder app. We were trying to get some logging going and having a database issue on the content server. We also were having issues with the API sockets on the content server because it couldn't connect to the database.

Working with Calvin on the label builder web interface code. We merged in 25 new files to help with the web version of the adilas label builder app. It isn't quite ready for full web use yet, but getting closer. The older adilas label builder app was a Windows only app. This new version will be available over the web for any and all users. We are excited to get it to the next level. This project has cost us a pretty penny but hopefully it will be well received and used by lots of users.

1-2 pm - Performance review with Mike and other developers. We met for an hour. We had a couple of the developers report on some of their projects. We had Eric, Bryan, Alan (Cory did it for Alan), and Steve all report on projects that are underway. Good meeting. We will be doing these follow-up and progress meetings every week. Schedule is yet to be determined. See attached for the meeting notes.

2-3:15 pm - Steve, Cory, and I got on a meeting with Calvin, going over the progress on the web version of the adilas label builder. He, Calvin, did a demo for us and we took some notes and asked some questions. We are getting closer and closer. There will be other versions and pushes on this project. It is amazing to see how much it takes to get something going. It then takes even more to keep it going. There are constantly new ideas and new perceived needs and wants.

After Calvin left, Steve, Cory, and I kept talking about other pieces of the puzzle. We see a need for frontend users (simple interface that is already setup and ready to go). We see an increased need for a middle-end or medium level developer/user (slightly more complex interface to setup the simple interface - settings, permissions, custom stuff). The last or other level would be the backend or behind the scenes level. There may be some other levels, but for sure front, middle, and backend users and developers. Very interesting.

We are going to be pitching some more ideas to certain clients - we are pretty good at going from project to project and building and lining things out. We would like to keep going with that and try to capitalize and monetize those ideas and values.

Spent an hour with Calvin on a demo/review of the web version of the adilas label builder. It is really coming along. Calvin built a fully functional Windows version of the adilas label builder a couple of years ago. We are now getting closer and closer to having a fully functional web version of that same (similar) tool. That is awesome. It's been fun to watch the progression. I wish it happened faster, but it is still super cool to see the progress.

After that, I was doing emails, paying bills, checking on funding options, and talking with Eric about some aggregation options for sales tax totals.

On the phone with Calvin going over AJAX and JQuery calls and how we use them. Also got some recent bank statements and sent them over to some funding companies, just shopping around.

Phone calls with Calvin. We were talking about internal and external API socket calls and best practices for each. After that, I did some emails and checked on some funding options. Looking into a business line of credit or something like that.

Zoom meeting with Calvin going over setting up a fake or simulated content server on his local environment for the adilas label builders project. After that, I ended up on the phone with Eric talking about funding, funded projects, code review and code reviewers, and other project management type tasks. Calvin called a couple more times as well, quick questions and answers. Trying to help automate things where possible.

Recording notes and doing emails.

Helping Bryan over a GoToMeeting session with a payment process and some of the logic tree stuff. Lots of order of operations type questions and placement stuff.

On a Zoom session with Calvin. He was showing me the web version of the adilas label builder and the progress that we are making there. I authorized him to keep going, as we are getting close on our first round budget numbers. We really want it, but it is not quite ready for use. It still has a ways to go, but making progress. Looking good.

I was having problems pushing up a video for John. I kept getting FTP errors. I got some FTP log files and sent them to both Wayne and John. Trying to figure out what was going on.

Zoom session with Calvin. We went over the progress on the adilas label builder and where it is at in the development stages. I took a couple of screenshots, but mostly we just talked and touched base on where things are at. We also briefly talked about other possible projects that might be coming down the road. Calvin may be interested in some of those projects. We'll talk as we get things done and setup priorities and figure out funding for those projects. I honestly can't see an end to the list of projects. It just keeps going and going.

Recording notes and doing emails.

Code review with John on a some new snow owl data tables for expense/receipts and the main advanced expense search results. The only problem that we came across was trying to pull too many records. Due to pagination, the data tables seem to do really good under a 1,000 records. Once you get above that, it really gets complicated and takes a while for the server to return all of those records. The old way, we built in our own pagination (next page) stuff and it goes much quicker, because it is only returning 50-100 per page vs thousands and thousands at a time. Pros and cons, every way you turn.

On the phone with Calvin going over progress on the web version of the adilas label builder. Touching base and getting a report from him. Making progress.

Questions on the adilas label builder app that Calvin made. We went over some of the permissions and how things interact. We recently got 20 new serial numbers for the adilas label builder from Calvin. We are going to be using that existing product until the more expanded web version is fully ready.

Working on a quote and project management, detailing out project scope and requirements, for a custom email report for customers and customer contacts. Cory was recording notes and I was saying what needed to be done on the project. Then, we go back through things and refine the notes and details. Good work session.

Recording notes, going over new serial numbers for the adilas label builder app from Calvin, and touching base on other projects. Steve and John were going over some custom reports and what they needed, as far as new logic and/or tweaks. The reports were dealing with cross overs between PO's, elements of time, and sub inventory - lots of mixing and blending. Anytime you get so many things involved, it can get kinda deep, kinda quickly. Basically, the users love how it is recording the data (catching all of the data points), they just want the reporting to be super easy and almost know what they want without asking the system for it. It's just the next logical step, but sometimes, they get really demanding and add some crazy pressure. We just keep going and taking that next step. That's all we can do. Keep on faking it till you make it!

Zoom meeting with Calvin and getting his local environment all setup and ready to use. Small Q&A stuff, back and forth.

Started out with Steve checking in and talking about labels and label building. Talking about the new Flash conversion stuff, JavaScript Canvas libraries, PDF's, and even Calvin's adilas label builder project. We then got asked by Cory about complex data labels and how those worked. We did some drawing and explaining. Without getting too deep, we are seeing limits on normal barcodes and are wanting to get into more custom labels and QR codes. As a side note, I'm supposed to reach out to Calvin to see if we could get a number of the existing adilas label builder apps, so that we could distribute them vs having our clients go through him to get the app. I haven't done it yet, but it's on my plate. We have to use what we have right now. More will come as we keep going, but we have to harness our current assets in order to make it to the next steps or phases.

On a phone call and Zoom session with Calvin dealing with local setup and installation stuff for his local environment. I then worked with Chuck to do some code sign-off on his RMA project for the gun dealer or firearm dealer. We ran out of time, but it is ready to push up and test.

Working on payment stuff and error handling for a 3rd party payment solution with Bryan. We got into other projects and small bugs and tracking down small fixes. We talked about labels, server addresses, and getting with both Calvin, Wayne, and Russell. We then rolled into the project dealing with customer photos out in the ecommerce land. We looked over pages, made some suggestions, and talked about CSS design options.

After that, we ended up doing some testing and found a bug. We worked on a fix for over an hour. We ended up finding that it was a name conflict between some objects. Two objects had the same name and were overwriting each other. Here is what made it tricky... we added the code, tested the code, even tested multiple times, but still were getting the error, just for one corporation, everything else was good to go. We found that the corporation had a small custom include file (custom code) that had the same variable name (for the object or structure) and that is what was causing the problem. We changed some names and all was good. That is a problem with too much copying and pasting... It works on one page so they (the developers) assume that it will work on the next page, but don't check to see if there are any name conflicts. Sometimes that gets tough if you are dealing with multiple includes... because all of the code is on separate pages (special or smaller include files).

I got a call from Calvin and he wanted to show me some new code dealing with a web version of the adilas label builder. He had subbed out some code to come up with a custom grid/layout piece. He gave me a demo and talked about options. This project has been a long time coming. We are really excited to get the adilas label builder fully on the web. Currently, there is a Windows software app that Calvin created and it ties into the web display and usage of the PDF custom labels. We've done a lot of work on this project over the years. This next phase will be to replace the Windows app and make the full thing fully web ready and part of the adilas site. Taking steps, little by little, but making great progress. Once again, slow and steady wins the race.

Emails and recording notes to wrap up the day.

Steve and I got on a GoToMeeting session to talk about options. We spent some time going over ideas and drawings for the adilas trust and how we could set that up. I have another Word document with a bunch of notes. Steve and I met for a good hour, talking and going over ideas and options.

Calvin called and we chatted for a bit. Calvin was pitching a proposal to work on the adilas label builder and getting that whole product web ready and transferred over to adilas vs being custom Windows based software that he developed. We talked about budgets, timelines, expectations, and other options. One of the things that Calvin was pitching was outsourcing a JavaScript grid layout engine. If we got that built, we could use that same layout engine to configure custom labels, custom invoices, customer receipts, check printing, PDF forms, and other layout type projects. Good stuff.

Here are a couple of other quick side notes from the conversation with Calvin. We talked about doing focused sprints vs big long drawn out projects. One, the developer's lose momentum and two, sometimes funding runs out. Time and resources, those are major pieces to the puzzle. Plus, this is the major killer, transitions... you lose so much in the start/stop, start/stop process. We gain some advantages as we do small pushes to minimize the length of the project and the number of transitions that will happen. We already knew this, but sometimes it is a good reminder on efficiencies and flow.

After the other meeting and phone calls, I merged in some code for Steve on branch that he was working on.

Built some database updates for Calvin and the adilas label builder app. The new updates deal with getting all of the single label sizes and Avery label sheet label specs. This is all part of the adilas label builder app. We are working to get the whole things on the web and being a full blown web app vs a desktop app. Cool.

Part of this session was a meeting with Calvin. He and I went through some of the differences between the desktop and the web version of the adilas label builder. We also talked about the difference between test and live (data and setup configurations). As we go forward, we are going to need a sharp JavaScript developer for the adilas label builder app and web version.

Calvin showed me some web based canvas and layout programs. Here is a link to one called flowSharpWeb. Not exactly what we are looking for but it has some of the concepts that we are looking for. Basically a full blown web layout program to allow our users to build and connect all of their custom labels designed and entered into the system.

There are always multiple ways to do these things. We just have to figure out our way and style.

We had some talks about outside consultants vs the primary developer. The new guy doesn't know the product as deep as the original or primary developer. Sometimes that is good and sometimes that is a disaster. We are going to work on creating a stepped plan... Going from a working Windows app to a full featured web app.

Calvin and I looked at some database tables of what we have and what we still need. We will need some of his sheet label specs and sizes. As part of this process, both Calvin and adilas will be passing different sections and pieces over to each other to get this plan and process in place. As we move forward, we would also like to get some training for the label builder and what the user expectations are/could be. We also talked about recording one of our next meetings as we try to transition existing code from Calvin over to the adilas side. We want to capture what we can without having to make Calvin do the same things over and over again.

After Calvin and I were finished. I did a bunch of emails to finish out this time period.

Meeting with Calvin.

Page with a bunch of GMext light videos from Calvin - https://lite.gmext.com/how_to_videos.php

See other entry for the notes. This one got double booked in the elements of time.

Meeting with Calvin, Steve, and I. Cory was unable to make it. Both Calvin and Steve were talking tons about text message marketing and possibilities to use Calvin's GMext text marking tool and combining it with adilas contacts, options, and using it as an internal 3rd party solution offering. Lot of potential there. Here are some of the notes from the meeting:

- People keep wanting things to be easier and easier. We have the same requests for text messaging and for labels. We want it, we also want it easier and easier.

- There were talks about the onboarding process and being able to do it or set things up by yourself.

- There was some discussion about text messages and the cannabis industry. The two of them went over some history, lessons learned, and some of the legalities.

- Texting deals with phone numbers. There are things called short codes and long codes. This deals with the length of the phone number. A normal number like (555) 555-5555 is considered a long code. A number like 55555 is considered a short code. They talked about pros and cons and levels of regulations for those numbers or values.

- We talked about Twilio and tying those services into adilas for different text messaging services.

- We have a 3rd party solution that is trying to leave the text messaging arena. There were talks about maybe seeing what they have and seeing if we wanted to take over any of that and/or reuse some of those pieces. Just talks and discussions. No plans were made here. Just options.

- Circling aback around to labeling - we would love to get that code on our (adilas) side of the fence.

- There were talks about how that could look and what kind of structure would need to be in place (transfer of code ownership and maintenance responsibility). Along those lines we talked about building projects and tools (one process), supporting those products (a whole other process), and extended updates and service plans (ongoing maintenance for those products - a whole other process as well). All of those things need to be considered. Who plays what role and how do we play together?

- To make super cool web-based tools, we keep seeing more and more need for high level JavaScript developers and coders. Spencer Garner, who does some adilas stuff, was mentioned. There are others and we could even potentially farm it out if needed to other or outside developers.

- The GMext product comes in a light version and a professional version. The big difference is how many texts need to be sent at one time. The GMext light version can only send up to 1,000 texts at a time. The GMext professional version is able to configure multiple long code numbers to run in tandem and thus be able to send more messages at once. Each setup of the professional version needs to be manually setup in order to get the correct number of outbound phone numbers (long codes).

- The discussion turned into topics of automated vs manual process and which scenario works best for what application and client base.

- They got into discussions about predictive marketing and even AI (artificial intelligence) stuff.

- Being able to use classic desktop software, web based version, and mobile responsive versions. Most things are leaning towards the web based and mobile versions of those products.

- Good marketing requires a plan and then being able to execute that plan over and over again. At some point, you need to pass the marketing load and decisions on to the users (until the predictive and/or AI stuff is ready to use and deploy).

- Calvin is using AWS and Lamda functions to do some of the magic for his text messaging stuff.

- We talked about being able to schedule outbound text messages. Calvin showed us a small demo. We recorded, but he asked that we not make it public. See note at the bottom of this page for more info on how to get to the video.

- This is a page with a bunch of GMext light videos from Calvin - anyone who wants to learn more may go here - https://lite.gmext.com/how_to_videos.php

- At the very end... we spent 5 or so minutes talking about the adilas label builder. Calvin and Brandon will meet and make other plans there. Most of the meeting today was dealing with touching base and text messages and GMext marketing tools and options.

We also recorded a small 7 minute video that showed Calvin using GMext light. He setup a couple quick contacts, assigned those contacts to a group, and then prepped and scheduled a text message to that group. It is inside of the adilas shop, but he asked us not to publish it via this element of time. Just go to the media/content advanced search and search for "GMext" and find the video with the date of 9/1/20.

Meeting with Calvin. He was reporting on some bug fixes in the adilas label builder app. Small side note, some times good comments in your code really help. Eventually you may need to go back and fix things... Sometimes months and months or even years later... Why did you do what you did... Without good comments, sometimes that is hard to tell. We were running into that on some of the code that we were looking at.

We ended up finding the problem and it was dealing with case sensitivity and switching servers (hosting environments).

Eric and I jumped on a meeting after Calvin and I were finished. We were going over new ACV (actual cash value) math and accounting for customer loyalty points. We can take it to certain levels, but at some point, you have let the users make decisions. Lots of talk about our responsibilities and due diligence on our part - helping the users make good decisions.

We did some testing and were getting good results. After that, back to more emails and such. That is constant.

On the phone with Calvin going over some adilas label stuff. Talking about the content server and small bugs. Working through things.

Emails and tech support stuff.

On a Zoom meeting with Calvin going over the adilas label builder and needs and wants there. We ended up doing some debugging and walking through the code together. We also made some notes of other possible hang-ups. Especially with sub inventory and different sub attributes per part category. That gets really deep.

Cory jumped on and had a few questions to go along with her projects and coordination stuff. We talked about a new table to store bowling pro shop drilling specs for bowling balls, figuring out where the adilas label builder project is at with Calvin, and some other small details. Going back to the adilas label builder app that Calvin made. It is currently a Windows application and we don't have any of the code. We would love to keep pushing it forward and make it into a full service web app (able to use by any of our clients). Currently, if anything needs to be tweaked and/or updated, we have to get with Calvin to get those changes made. Sometimes that is hard to find the time in his busy schedule. Because of that, we are feeling somewhat limited as to what we can do with that piece of the puzzle. We really want to get that code over on our side so that we could make changes and upgrades easier. We currently don't have a Windows developer on staff, other than Calvin, but we may need to look into different arrangements.

As part of this discussion, I think that it is important to note that many developers know that there may be maintenance on things that they build. What they don't count on, and we don't want to count on this either, is years and years worth of maintenance and upgrades. It drags out the projects. Also, it is no fun if someone else introduces something new and it breaks an older process what was working. Basically, sometimes, a new error may be introduced that affects older code making it appear that the older code was in correct. That may not be the fact, but the reality is, it breaks something going forward and there is a constant need to keep updating and doing maintenance on almost all code that gets written. Kinda like a shelf life for code. That is good to keep in mind.

Another thing that makes some of this code work hard is the number of ways things are used. That comes back to settings, configuration, and use cases. Sadly, yet kinda fun in some ways, we have users that use our products in ways we never would have imagined. That's tough to code to all of those use case scenarios. It sure keeps things interesting (good and bad).

There were 4 to 5 of us on the morning meeting. Wayne and Steve were talking about storage solutions and options there for client-specific storage (potentially even in different places per client). Apparently, they had been on a meeting since 8 am. As a fun side note, we need to make sure that each system could be configured to both store and retrieve stored content from different places. Currently, we push all images and scans to the local box on a per server basis. We also push all bigger files, graphics, PDF's, and other document out to the content server. What if we could configure both of those pieces per client? That would be super cool.

Along those lines, we could specify a location say on AWS where there images and content could be stored. We would then directly charge those clients for the storage of those files and assets. Currently, it is all part of the monthly fee but no one has been watching or monitoring how much storage space that really is. We have one client that has well over 200+ gigs of outside files that we are storing for them. To put this in perspective, google drive allows for 15 gig for free and then you have to pay. They are at 200+ gig. They add to it daily as well. We have other clients that have thousands and thousands of scans and images. Once again, unmonitored. We need to be able to configure the systems to handle those changes as well as pass those file storage and hosting fees on to the client. It's their data, they need to pay to store it (within reason). Also, some of the storage is stored over years and years.

There was also some talk about having active and inactive content and files (levels within the storage solution). For example, new files, images, scans, and media could stay active for a month (or whatever time range). Then they (the files) could be moved a little bit deeper but still exist. Think more of cold storage vs active or hot storage. This is all just a dream right now, but it may play into some of the configuration needs for fracture (upcoming adilas project).

Danny and Steve were talking with Wayne about labels and what not. We need to get Calvin's label tool fully online and working over the web. Currently, the adilas label builder is a custom Window's app. Things keep changing (for labels) on a constant basis. Danny wanted to make sure that Wayne knew about some of the label changes so that we didn't overwhelm him with tons of files and merge requests.

The guys were talking about adding in a fee for those clients who use Metrc - a state level 3rd party solution for sales and compliance. That would be great as it literally costs us around $20K per month to keep up with Metrc and their changes alone. Pretty crazy.

Sean is going to be reaching out to some of our current clients. Steve and Sean talked about some current and future plans to reach out to different clients to see what they need and how we can help them. Steve was talking about small custom homepages, or small dashboard type interfaces to help them get around and move around in the system efficiently.

There was also some great talks and ideas about doing live or on-sight training by our clients for new clients in the same or similar industries. Basically, instead of having an adilas rep train someone, have an active client in that same industry or line of work train the persons. That allows our clients to get the training, from the source, and our clients could make some money by charging to show and train the clients using their existing systems. Some cool ideas there. Use the client's facility and train other people in your same industry by charging them to train them.

The last main topic of the morning was dealing with servers, IT help, and server resets. Wayne and Steve are going to be looking into options of using the existing IT staff of our commercial web hosting companies to help with extended server and support issues. They already have full access to the servers and know the infrastructure at the hosting company. It would be so cool if we could sub some of that maintenance and hot fixes out to them. Both Steve and Wayne will be making calls and setting up meetings to advance that ball forward.

Two different phone calls. One with Steve and the other with Calvin.

Talking to Steve about plans for the group meeting on Thursday morning (tomorrow). He is going to help present some ideas and concepts on adilas as a trust. We also talked about goals, team work and collaboration. 45 minute call.

Calvin was calling to talk about some of the question on the adilas as a trust document. We talked about custom software and following the client dollars and money. We also talked about quality software and the value that brings. The conversation went into some politics and how often the politics tend to win out. Sad but true. Next, we talked about maintaining enough control and watching the back door (say you open things up too much, you have to then watch the back door).

We also talked about people errors, compliant issues, underlying and alternate plans of individuals and groups, and eventually cause and effect decisions and then the trickle down based on those decisions. Calvin recommended that we build in some checks and balances. We also talked about analogy of rowing a boat in a lake without any landmarks. Without the landmarks, you don't know if you are going in the right direction. We were relating this to goals and focused approaches.

As a fun story, Calvin and I talked about a raft flipping over and one of his sons getting caught under the boat. He couldn't get out without help. We talked about picking a single direction and trying to get out based on that single direction. Sometimes we over think it and second guess ourselves and virtually go in circles vs picking a direction and going for it.

Talking to developers over the phone. On the phone with Calvin going over things. Then on the phone with Russell and Chuck to help out with payee/user images on the new user homepage. I ended up on a quick Zoom meeting with Russell and Chuck.

Cory and I met and chatted about a new bug that some users are seeing with the adilas label builder. We decided that we needed to pass it off to Calvin, the label master. I did record a super small video and it is on my local machine if needed.

The morning meeting went long. We had two servers that were being moved. They were data 4 and data 6. The data 4 server had a problem and the databases were slightly switched around. We have a test database and a live/production database. The web server was pointing all new transactions towards the test database and we couldn't see the live data. It was still there, we just couldn't see unless we logged in directly. It took us a bit, but we (mostly Wayne Andersen) got it fixed and headed in the right direction.

Calvin called and reported in on some things and projects. He has been helping users with the adilas label builder, doing more gmext (group mass texting) stuff,  building new tools, and more mobile development. We chatted for awhile and ended our conversation on CMS (content management systems) and the need to be able to tie-in files and documents to different pieces of the puzzle. As a side note, Calvin built a tool that allowed files and documents (media/content) to be added to certain objects. He said a funny comment, "I have recreated only a small portion of what adilas already does." That was pretty cool. We do a lot and allow media/content, photo galleries, and files to be added to all 12 main application player groups (invoices, deposits, expense/receipts, vendors, users, customers, stock/units, elements of time, quotes, PO's, balance sheet items, and parts/items and general inventory).

Switching back to the servers and what not, we really need to take care of Shari O., Drea, and Wayne Andersen. They have all been rock stars in doing tech support and server stuff. They get my vote and appreciation. Long days for all of these guys and gals. 

Touching base with Calvin about custom code and potential on some servers and upgrades. Mostly just touching base and chatting.

Bryan and I worked on some ideas and requirements for the thresholds and inventory engine stuff. We want to take it way further than it is, but that takes time, money, and planning.

Part way through our meeting, Steve jumped on and showed us a bug on one of the servers. We flipped into emergency mode and made the changes. A file folder had been moved on the server and it was causing all kinds of errors. We got it fixed.

Calvin called and I gave him an update on where we are at and what projects are going on and being worked on. He reported on the web version of the adilas label builder and what not. Good catch-up session. We've both been super busy.

Wayne popped in and we talked about the need to get multiple databases connected to single machines. We need to virtually get some of the users off the bus and on to their own vehicle and/or motorcycle (smaller entity). We also talked about setup options, custom image tags, mappings, and making the new system setup process even easier. Thinking towards the future and being able to duplicate things on a larger scale.

Emails, follow-ups, and calling and talking with Calvin. Touching base on the adilas label builder and heading towards a web based interface. He has been super busy with his gmext (group mass texting) products but will keep us posted on progress on our stuff.

3/4/20: Add auto print for new quotes or invoices:

Get a hold of Calvin to build something we could all use to do this. Has built for another client. Would like to make it core.

Add a noise when a quote is added to fulfillment homepage: This would be a setting. Brand new= red? Not sure how to do noise. Browser has control. 

Calvin called and showed me a small demo of the adilas label builder and the progress of moving it to the web. Nothing super fancy, but progress is being made there.

I also had to answer some emails about mini conversions and what they are and do. See attached for a small explanation of mini conversions.

Meeting with a number of folks. The goal was dealing with the shopping cart. We had Steve, Chuck, Jonathan, Cory, and a client on the meeting. The first part of the meeting was the client going over some of their requests. Here are some highlights from them...

- They would like to be able to send text messages from the customer queue

- They would love to have a hand-held scanner and have it automatically be able to update an unmanned cart. Some talks about using the built-in cameras on certain tablets and such. Other talks about hardware and software problems and solutions. Through the web, sometimes those pieces are hard to get to perfectly talk to one another.

- Lots of questions about barcodes, labels, and auto/bulk actions.

- They would like possible popup/modal type windows to see customer notes, maybe the last invoice, and even a modal popup on the ++ or advanced add to cart (haggle tools)

- The also spoke about major needs for tiered pricing - the same options that work on my cart favorite buttons and smart groups and tiered pricing. As part of this discussion, there were options mentioned about parent attributes, barcodes on buttons, advanced barcodes (QR codes), mini conversions, etc. This becomes a bigger and bigger need. It also needs to be more standardized. Lots of options, but because it could go so many ways, it is hard to find the correct path. Too many options.

- Along the tiered pricing vein, there was also a request to be able to assign items (subs or child packages) to a pricing tier through the build new PO process (bringing in the items and assigning them to a pricing tier as part of the inbound process).

- They really want a fully interactive cart, yet still locked down, yet still super powerful, yet super simple, yet, yet... Lots of requirements.

- Training mode, how to get to the best training and how to connect the dots. We have help files, news and updates, videos, etc. - but we need a way to get to that really quickly. They, the client, were also requesting that each new feature has a full tutorial and/or video. They only wanted the things that were fully done to be added to the news and updates.

- They would love for more onsite or local training options. They love the time and are willing to spend the money. They would love to get the training options to be standardized and regular (scheduled and consistent).

- They love the bulk update cart functionality

- Being able to bulk print labels and skip steps (save as a quote or cart checkout). The also wanted to be able to flag certain items that they only need one label vs multiple new labels per quantity, etc. It sounds like it could be pretty deep. There were also requests to be able to bulk print labels from the PO. Calvin's new adilas label builder does do bulk labels for invoices and PO's. They just might need some training.

- Online orders, ecommerce, and even options for delivery.

- In the cart, being able to see it at all times. Having some sort of split screen where there are items or look-ups on one side and all of the items on the other side. Lots of one pagers with asynchronous connections and easy flow through the sections and/or pages.

- We love ideas and helping to push the ball forward. The needs keep coming. We just try to keep solving those pieces as we can.

- We also allow the clients to chime in and help us prioritize, fund sharing, and have a say in where things are going.

////// more notes after the client left - Just Chuck, Jonathan, Brandon, and Steve

- Steve - a big thank you out to both Chuck and Jonathan - you guys are stepping up the game. He was also talking about collaboration between the different developers and how cool that will be.

- There may end up being 8-10 versions or variations of the shopping cart. At some point, we need to separate the logic from the view/design. Jonathan was also talking about putting the specialty features into settings so that each cart may be more configurable. Good stuff.

- Questions from Jonathan about market analysis and what does that say for us? Sadly, the reality, we haven't done anything there. Lots of options.

- There were some talks about having a system to run your stuff vs trying to marry all of the individual pieces together. There is pain on both sides, but we are heading towards the systematic type approach. Trying to bring all of these things together.

- Time to value - how many clicks to get those needs fulfilled. Not that we can't do it... we just need to figure out how to help speed up the process and make it easier and more easy to get to those pieces and features.

- Smoothing out processes and making it easy to get to the places that they need to. It kinda comes down to navigation and visual flow process. Aka - the full user experience.

- Steve was talking about how making these pieces work together to get all of the POS (point of sale) systems, inventory tracking, CRM (customer relationship management), CMS (content management systems), accounting, reports, and backend storage all in one place. That is the dream.

- Some of our clients are virtually starving for instructor lead training. Jonathan is saying that there is a barrier to entry to this... meaning the learning curve to fully know adilas. We need to help provide it and also help to standardize it. Small talks about competition, reps/consultants, and ways of teaching the processes, pieces, and principles.

- Small mention of the adilas café and how some of that would help us provide training and service type options. You could get training from the adilas university or you could get direct training and/or hire a certain person to help fill a certain need. Think of all of the power users that could offer services and/or training. What if we could show user stats on who has done what and what level they qualify.

- From Chuck - what about a monthly webinar? We could plan it out, record it, charge for it, etc. We could do digital meetings, in-person training, instructor lead trainings, etc. As we keep updating the system, we need to keep updating the videos. Maybe even using YouTube as a primary source of training. Possible Facebook groups, tips of the day, etc.

- From Chuck - doing light idea mining when we are out and about. For example: Hey, what processes do you do to sell things? We then record that and start making some settings, permissions, and selections together to help them with what they are doing. Presets per industry. Sometimes it is so overwhelming... we could really create virtual profiles and help with settings and configuration stuff.

- From Chuck - small talks about web components and being able to customize things on the fly. Separating logic, functions, views, displays, processes, etc.

- Lots of settings and even helping those people get to those settings and help it make sense for each industry. Settings and configuration options. Groups, categories, settings, nested presets, tiered pricing, labels, etc.

- From Chuck - he really doesn't like it if we do a process and then virtually dump him in an unfamiliar page (backend navigation). That comes back to page flow and user interface. We will keep working on this. If we send the users to the correct spot, we don't lose them and we even help them know what the next step should be. This may take some mapping and design stuff.

- Trying to stay small but still looking for talent and help.

- Help file on barcodes - Web link - help.cfm?id=413&pwd=cart - barcodes can really speed up shopping carts and there are tons of options. This is an area that could still be developed out further and enhanced. Just an idea.

See attached for a number of other resources. There are a couple of videos and some research on shopping carts and POS interfaces (point of sale interfaces).

General stuff. I reviewed a video that Russell sent over for the new and upcoming shopping cart (12 minute video). Also did some other research on the cart and what we are looking for. Lots of good stuff going on.

On a phone call with Calvin going over the meeting and training/demo yesterday for the adilas label builder. I sent him a list of servers and he will be updating his list. This is a setting inside of the label builder. Also, he reported on his progress of taking his Windows app (hybrid app) out to the web. He is making progress and reported on where things were at.

We had a great demo and training meeting on the adilas label builder. The primary presenter was Calvin Chipman of MyEasySoftware. In this hour long presentation, Calvin goes over the tool, shows you around, makes suggestions, shows samples, and also allows a small demo from a power user. Good stuff and great training event. See attached for a full copy of the video recording. 1 Hour.

Phone call with Calvin to go over up coming training and webinar for the adilas label builder. We went over an agenda and chatted about some ideas and options.

Danny had some questions about multiple barcodes on PDF labels. I recommended him to get with Calvin and see if he could get the adilas label builder wizard installed and configured. That product already allows for multiple barcodes and QR codes per label right now. Here is a link to some more info on that product.

Steve and Dustin were on the meeting and introduced a new developer Alex Hearding. Alex will be helping Steve and Dustin with different tasks and what not. Light intros and talking about next steps.

Alan and I met for another half an hour after the designer meeting with Chuck. We talked about personalities and where each of us are heading and what we are wanting to do. If any of us get too much on our plates, we each tend to curl up and not get much of anything done. I've seen it happen over and over again. We talked about some project management stuff and getting a good direction and some traction going in that direction.

After that, I helped Eric out with some questions. I then got a call from Calvin and worked with him for a bit. I showed Chuck how to enter a reimbursement into the system to get paid for some of the stuff that he is doing. In between times, I was recording notes and pushing up screenshots for Chuck from our meeting today.

Calvin and I were working on getting a newer version of MySQL installed on his machine. He was on version 5.6. We needed to get up to version 5.7 and then up to version 8. Lots of little hoops and what not to walk through. As Calvin was working on his stuff, I was doing little odds and ends on my end.

On the phone with Calvin going over some plans. We talked about moving more and more towards the web version of the adilas label builder.

- Setup dates for February

- Setup a date/time to do a training session on the adilas label builder (record the training and invite some of the reps/consultants). We set it up for 2/24/20 at 10 am to 11 am. We'll work out the details prior to that meeting.

Calvin and I got on a phone call together. We are sending Calvin off to work on the adilas label builder and the hosted or web version of that product. The current product is a hybrid product and has a Windows software portion as well as a web version and/or portion. The new adilas label builder will be completely web-based. Calvin and I also touched base on a few things and talked about direction and vision. I approved him sending in some hours for emergency tech support that hadn't been submitted. For a while, we were somewhat between some talks and negations on how to handle billing and support requests. Calvin is working hard with a partner to create a new company called the IT Dream Team. Most of his time has been spent there. We are excited to get some dedicated time to finish up and work on some of the adilas projects. Good stuff.

Josh and I met up and pushed up some new code for the driver license scans and being able to populate data into the add/edit customer records. After that, I did some email stuff and got back with Calvin and Jacob from the IT Dream Team. We are trying to setup a consistent monthly effort to keep pushing things forward. That's exciting.

Steve and I got on the phone and chatted for 45 minutes after the meeting with Calvin and Jacob from the IT Dream Team. We were talking about business decisions and what path and/or direction we want and need to take. Good conversation. There are lots of options out there. Our plan it to keep going and try to keep things small, tight, and growing naturally. We have some good direction and some great people who are helping us and playing the game. We are going to keep following that path.

The conversation was fun and we jumped from subject to subject. Those are always fun conversations. Steve is super hard worker and we are surrounded by lots of great people. The sky is the limit.

- 4 things that they offer - technical support, strategy (all kinds), architectural design (all kinds of managed services),  and outsourced CTO (chief technical officer)

- They are good at programming, collaboration, networking, VOIP (voice over IP), integration platforms, and other technical things.

- Steve asked about costs for coding, fixes, and future development. Jacob was talking about strategy vs an hourly rate. Trying to turn it more towards the results of what is accomplished vs a straight hourly fee. They would like to help solve the problems and look toward the future as possible white labels.

- Adilas is on the edge of a growth spurt - we need some help keeping things going - help dealing with growing pains.

- Offer from the IT Dream Team - help us out with our current needs (coding, bug fixes, and even new development), they would like to commit a day a week to helping us out. Say 5-10 hours (it may flex). They would like to be at $300/hour or $6,500/month. There are also some options that we could explore dealing with revenue sharing.

- We want someone to virtually come in and help with certain parts of the process.

- We just want to be the software piece that deal with hosting, processing, data storage, etc. All of the other pieces are up in the air. There are huge needs in setup, training, onboarding, consulting, custom code, support, etc.

- They, ITDT, are already tied in with a few partner setup type scenarios. We are looking for people who want to be a white label supplier for or of our product.

- Our, adilas's, biggest needs are on the development side and also on building out the bigger picture and/or dream.

- Steve was proposing that the sweet spot is outside the system marketing the virtual byproducts on or around the other services that could play into things.

- We fit into the gap between the do it yourselfers and the really big players like SAP and Oracle.

- We allow custom code and we don't cost a fraction of the big dogs. Our biggest competition is tradition. We do compete with other companies but most of the other companies sell pieces, modules, or components. We sell a full system.

- We offer shared servers, semi-dedicated servers, private servers, clusters, etc. From small mom and pops to bigger enterprises. Lots of variables.

- Talking about the value of our time - stepping up to the bar and paying for that value of time, effort, and direction.

- There needs to be a shift in the direction that adilas is going so that we could get the value out of what we are all doing. We are somewhat in a tricky spot... we either need to keep growing naturally or we need to go bigger. The middle ground is a dangerous spot to be.

- We are really trying to get white label companies to run with the potential of running and supporting an industry or business vertical.

- Steve would like to get another pitch from Calvin on what would be possible.

- If we do need to go in different directions, what about the existing pieces? Is there a way to get that code or do we setup an agreement to keep things going on a reoccurring model?

Talking with Calvin and Jacob from the IT Dream Team. Steve joined us part way through the meeting.

- What is the dream?

- Who has access to Calvin and what would that look like and/or cost? Currently, Calvin may be approached by clients, reps, consultants, adilas tech support, and other adilas developers. This may need to be defined more.

- Problem and incident management. Also, change management and future development. We may need to look at some standards such as ITIL (information technology infrastructure library). Great starting point for setting up best practices.

- Communication breakdowns and having too many middle men - adds to loss of communication.

- Helping all of our clients take advantage of new changes.

- Building processes to help standardize things.

- Products that are on our future tick list - text messaging (big and small, group and individual), auto processing (transactional data to aggregated data), label building, and other API socket tools.

- IT Dream Team would like to help us get a strategy of where we are going. Basically an IT partner or part of team on an ongoing basis. An outsource CTO (chief technical officer) type role

- Vertical design and keeping the user involved

- Challenges of just in time project management, just in time funding, just in time bug fixes, just in time development, etc.

- What trends are we seeing and needing? Along those lines, where are we headed and what else if needed? Even to the fact of reoccurring services (IT, servers, developers, management, software, consulting).

- There tends to be a few type of programming - maintenance, bug fixes, and enhancements (new things that need to happen). There is also operational vs emergency needs. If we can be proactive, we could eliminate lots of the emergency type levels. Making a plan and then working that plan.

- We have an independent model... which also allows us to have work (jobs) for you guys as well. There could be a lot of back and forth sharing between clients, projects, and needs.

- Steve was talking about how our end goal, for our model, is helping to bring together operations and accounting (the zipper analogy). Steve was also talking about helping the users really want our product to the point that they need it. The system becomes one of their favorite and most used tools.

- There are tons of other sales type options - we can dream it up and then put together a plan. We would love to play together in different ways. Let's figure it out.

- Knowledge management - key players that have the correct knowledge pieces of the puzzle.

- There was lots of talks about oversight, helping, managing, and even finding the correct solutions on the accounting side of things.

- There were talks about setting up a marketplace that service the adilas clients and markets. It come back to our planning for the adilas café type model. Here is a link to some of our research on the adilas café.

- We were talking about outsourcing some of the babysitting pieces to different CPA firms. Lots of options and vision - huge potential.

- How do we move this thing out to the next level? Let's get some proposals going.

- We have two main things that we could look at. One deals with the development side of things (building and maintaining things) as well as a possible relationship in the revenue sharing and bigger picture.

Met with Caisson Labs and did some planning. They are doing year end inventory stuff right now. They are in an interesting place. They have an old system that needs some loving and a new system that still needs to be setup. They are going to be counting inventories and getting us new data to put in place in the new system. Steve joined the meeting and will help them learn some of the core production features inside of adilas. That should really help them. Steve was talking to them about location specific items, vendor specific items, and homogenous inventory items. Lots of moving pieces and options.

They are currently using a custom hybrid app from Calvin Chipman and MyEasySoftware. It combines custom software and web based API sockets back to adilas. They love some of the pieces, but there are some challenges. They want to keep using pieces of the custom app and normal core web pieces as well. We are working with them to help get everything moving in a smooth way.

Three of the pieces on the custom app are working really well. They use those pieces every day. They are the Packaging Log, the Label Printing, and the Shipping tabs. See screenshots for a reference.

More work with Steve on the logic for his custom gram controller pages. We also chatted and talked about our meeting with the IT Dream Team and possible options. Calvin and I also did some back and forth debugging on the adilas label builder app. Calvin got it all fixed. The problem ended up being a change in the SSL (secure socket layer) encryption level and that was causing things to fail. Basically, we had to open the connections up a bit and allow for multiple different types of secure connections (multiple or statements to allow different options). Some changes were made and we did some light testing.

Talking with Calvin and his partner Jacob from the IT Dream Team. Good meeting. Both parties came away with some new ideas and options. We listened to their pitch and took some notes and tried to catch their vision and position. They then let us talk and explain a few needs and pain points. By the time we were done, we had somewhat of a short term plan and scheduled an additional follow-up meeting for next week.

I took a bunch of notes. There are under Calvin's folder under a file name of meeting_with_calvin_12_24_19_modified.txt

There were four of us on the call. Calvin, Jacob, Steve, and Brandon.

Dustin joined the meeting with Alan and I today. He had some syntax questions and he and Alan ended up working together for an hour on one of his projects (cultivation and pagination on some of the phases). They switched between ColdFusion code and JavaScript code to get it to work. They both did awesome. In the mean time, I was setting up my new laptop with FTP accounts and installing programs from Calvin.

Once Alan and Dustin were done, we decided to break off and each work on our own projects vs doing the paired programming. We will pick it up again next week. All in all it was a good session.

Calvin has been working on a new business called IT Dream Team. It deals with coaching and consulting and helping firms get their IT needs met. Calvin is working on building up a business that could be sold and/or used as a reoccurring revenue source.

As a proposal, what if the IT Dream Team (Calvin's new business) works with us as a consultant/IT department? That might be an interesting joint venture.

We ended up going short on the meeting in order to update the servers. We had some server issues on data 0 and data 2.

Emails, small bug fixes with Calvin, installing new software updates, Bear 100 stuff, and server resets.

Added some more security info to elements of time # 4978 - dealing with security documents and screenshots.

Calvin had me cascade some new database tables and settings to all of the servers. After that, I tried running the new label builder. Calvin and I ended up on a Zoom session and spending some time together and working through some small bugs. That took up most of the afternoon.

Paying bills, invoicing and doing a deposit, recording notes and going back and rereading entries from earlier this week. I got a demo from Calvin on the new sub inventory stuff on his custom PDF labels, using the adilas label builder. Pretty cool.

I also spent a couple of hours writing some answers to a security questionnaire that was presented to us. I have included a copy of my answers. Hopefully they are honest and thorough enough for the task at hand. See attached for a copy of the security document.

https://www.newtekwebhosting.com/our-infrastructure/ - server infrastructure at Newtek hosting - adilas security

https://www.newtekwebhosting.com/disaster-recovery-solutions/ - disaster recovery at Newtek hosting - adilas security

Just Dustin and I on the morning meeting to start with. I spent most of the session recording notes and doing research on system mapping and direction for the future.

Part way through, Wayne joined the meeting and gave me a small report. Here are a few notes from that discussion.

Wayne - looking into generating an auto renewal of SSL certificates. Data 6 has this tech installed - small test run.

We talked about the old dedicated servers, new VPS servers (virtual servers), and AWS (full virtual stacks).

Wayne was stating that he was kinda frustrated with the service level at Newtek on this last go around. We were in a waiting pattern for over a week without anything or any communication. This was our first round of VPS serves with Newtek. It ended up being days and days that we normally don't have to deal with. Wayne is wondering if something is changing and/or slipping there at Newtek. Lots of frustrations and delays.

We want to make sure that we have multiple options, going forward. We currently have a lot of servers out there and we are kinda feeling like we have all of our eggs in one basket. We would like to expand that presence.

There were some other talks about config files and how some of the config files are seaming to revert back to defaults vs staying at a higher tweaked out level. This is mostly dealing with the database config files. Wayne is setting up a file level monitor to help track that down.

After Wayne left, I kept working on my projects. Towards the end of the session, I got a call from Calvin. We switched over to a Zoom session and he showed me what he was working on with his adilas label builder and pulling in sub inventory and sub inventory attributes. It gets pretty deep. I liked what I saw and gave Calvin some feedback. He is quite busy right now and we talked about some options and priorities.

Quick Zoom session with Calvin. We went over some queries for sub inventory and had a small discussion about how to do it and best practices. Small little meeting.

On the phone and then a Zoom session with Calvin going over needs, direction, and mappings for sub inventory. He got a bunch of new tests data and we were hooking it up and going over things.

Working with Steve on a project that he is working on with the adilas community funded projects. Also helped Calvin on a Zoom session get some new local data setup for working with sub inventory and sub attributes for his label builder app.

11/12/19: E2 Solutions is asking for this as their client runs a payroll for 200 employees.

Many clients have asked for this over the years. Most recently Herbo has been interested, and on 8/26/19 C_ - -c (client of Steve in Denver) is also asking. Steve B. asked if perhaps they might want to chip in? Herbo could be asked the same thing perhaps? Steve B also suggested having Calvin work on this?

Years ago $2500 was paid in for this project- wanted 3 checks on one sheet (not one of our options). This would be another project. There can also be a printer printing problem- ie eats check. How to keep the numbers of the checks in order?

The power of recipe/builds. Both Cory and Steve were talking about the potential and ways that the recipes could and do help the build process. They were even talking about unitizing some of the costs using certain recipes.

Cory and Steve wanted to see a demo on the rewards and customer loyalty points. We went through things and they made some comments and had a couple of questions. Mostly they were excited to see us get it ready for release.

Working on the project list and refining some requirements on the multi vendor, multi corp, invoice to PO - one of the time consuming pieces is bringing in bulk raw goods. On the subs being transferred in... could we keep the barcodes the same, both on the parent barcodes and the sub barcodes? The other time sucker is relabeling and printing the labels. Some of the clients are using complex labels (bring a sub package in and tie it to different units of measure). They, the client, are using the custom labels with qr_subId_quantity_price (label format) type thing. They really need mini conversion with the ability to do cross-corp barcode labeling. Mini conversions almost gets into the level of grand children and so on.

Steve would love to build out our internal project management stuff. We would like to build out project timelines and showing progress via timelines and check points. Helping our clients see the work that goes into some of these projects. Including funding, time, labor, check points, progress, etc.

Small talks about bulk check printing and using the keyword "bulk" to help the system assign check numbers on the fly. Steve had a number of be careful/got ya's - such as missing checks, printer eating or destroying a check, jumping out of the process, different check types - say 3 on a page vs single check per page (default). It gets deep on the got ya's. Calvin did some work on the bulk check printing project a couple years back.

Crazy sales tax stuff. We were talking about multi tax rates, buying and selling products and services and then being able to tax things based on where they were sold from and where the products were going to end up. Kinda crazy taxing stuff and mixing and blending special taxes. It seems like taxes are already complicated, and it seems to be heading even deeper. Special sales tax rates per zone, per city, per county, per municipality, per entity, per location. Invoicing, transferring products behind the scenes, special taxing, special reporting and the list goes on. Crazy, crazy stuff.

The deeper we go, the more we are seeing the usage of locations and stores and keeping things straight. That could be inventory levels, needs, sales, transfers, taxes, users, permissions, clients, vendors, etc. It get's pretty crazy. Locations are a huge piece of the puzzle.

We were talking about flex grid tie-ins and being able to expose certain things to the public and certain things internally based on show/hide on the web settings and the reflexive side of the flex grid (crisscrossing flex grid tie-ins and relationships). We are seeing a need for this (it already exists but may not be being used) and we may want to employ more of this type of function.

There was also a small discussion about ideas, limits, and setting up priorities. There are so many ideas... sometimes it gets tough to figure out what or where to jump first. Eventually it comes down to priorities and setting those priority levels.

Bryan joined the meeting and had a few questions. One was about a new money type called "credit card" - basically a generic for all types of credit cards (visa, mastercard, American express, discover, etc.). We talked about how easy it is to add the money type and then how much work it would be to make it flow through the whole system. We estimated a little bit over 10 hours for the project.

We also talked about Full Circle and how to help re-do some of the settings and permissions.

Later on, Calvin called and updated me on some developments with dedicated clients and their want to get at underlying data and the databases on their boxes.

Working with Calvin on a custom database project for data 9. He issued me 6 new MySQL Editor licenses to use on different servers. The MySQL Editor is a custom database program (database tool) that Calvin created for us here at Adilas. It is lightening fast and simplified. The project that he is working on involves a client wanting more raw access to the database vs going through the established channels in the Adilas.biz system. This is a dedicated box and the raw data is going to be a view only access type app. All changes will need to go through existing and established channels. It is interesting how much people want access to their data and also want to run certain queries to pick out trends, stats, and other details. Kinda cool. Data is becoming a new kind of currency.

Back working on the special accounts project.

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.

This was some text from an email about barcodes and how they work inside of adilas. It has some good links and info:

Hey guys,
This is Brandon. Just chiming in on this topic. The main Adilas barcode generator is Adobe Flash based. There are no Adilas settings for what label printer, what label scanner, or what brand a client may use. That was on purpose. Eventually, it comes down to the individual drivers, hardware settings, and browser settings. Adilas does not control any of that.

Here are a couple of help files with some good information about barcodes:
https://data0.adilas.biz/top_secret/help.cfm?id=361&pwd=barcode – barcode generator
https://data0.adilas.biz/top_secret/help.cfm?id=362&pwd=tech – tech info on barcodes
https://data0.adilas.biz/top_secret/help.cfm?id=413&pwd=cart – how adilas scans and uses barcodes

Another option that exists now, thanks to Calvin, is the adilas label builder app. This plays with Adobe PDF (Acrobat) technology. The new adilas label builder requires a little bit more technical knowledge on the setup, but it is available. I would recommend that we possibly go that route. If they don't have anyone who wants to play, I would be willing to work with the client. I'm not a master, but I've seen numerous demos and have played with the product before. The new app allows for labels from invoices, customers, PO's, and inventory items. It can do individual labels, custom labels, and all kinds of sheet labels.

Calvin is currently working on sub inventory items, sub inventory attributes, and flex grid connections. That will be really cool.

Here is a link to more information about the adilas label builder app.
https://data0.adilas.biz/MyEasySoftware/adilas_label_builder_app.cfm

If push comes to shove… I'll be their label tech. I'm a $100/hour but happy to help. Anyways, just chiming in. Thanks guys and gals and have a great day.

Brandon Moore
435.258.5504 (home/office)
435.881.1536 (cell)
brandon@adilas.biz :: www.adilas.biz
"all data is live and searchable"

Met with Alan for half an hour going over the existing internal API socket system. We talked about web page id's, API sockets, requirements, and how things are validated. He has a project (invoice due dates and automated watchers for overdue invoices - collecting on a/r's or accounts receivables). He will either be using the existing path way and/or slightly modifying it to work better for future development. Good stuff.

I got on a call with Drea from tech support and she had a number of questions about barcodes and settings inside of adilas. I assured her that beyond creating and generating the barcode, the other settings are on a printer driver, scanner setting, or a browser setting. We don't have any of those pieces in our system. We also briefly went over options between Adobe Flash barcodes and Calvin's PDF labels and sheet labels, using the adilas label builder app.

Grabbed some older notebook sketches and put them together into a single image and uploaded them to element of time # 4791, here in the shop. The combined image is a quick break-down of the data assembly line analogy and model.

We were talking about parent attributes and sub inventory attributes. We need a way to flatten the data in order to work with labels. Calvin and I were on a Zoom session. We did a lot of drawing and talking about ways to show the human side of things and the computer side of things. We ended up looking at data samples, drawing database schema maps, and brainstorming ideas on how to help flatten and/or standardize sub inventory attributes and other dynamic data driven objects. The tricky part is that sub inventory attributes could be anything... we virtually let our users build their own databases (specific data points that they want to catch and/or track). We then have to allow them to use those values in labels. It gets pretty deep.

Helped merge in some code for Eric and his Spring Big integration project. I also talked on the phone with Calvin about what is needed for the adilas label builder (sub inventory and flex grid). I then did some emails and tech support stuff.

Working on sub inventory API socket information and API socket documentation.

Got a call from Calvin and we talked about some options for a web-based adilas label builder app or application. Good stuff. The cost was around $15,000. We've already paid well over $20,000 for the existing label builder app. The new one would be web-based and include sub inventory and flex grid stuff.

Spent some time looking into a cross corp invoice to PO error that was reported. Apparently, the page was working as of last week and now that same page is not working. I checked and the same code that we have in the master branch is on the server. It also has a modified date of back in April of this year. The next step is to look deeper and see what might possibly be the problem and/or disconnect.

Going over some new database updates that Steve was working on. We then switched gears and started working on some internal API socket connections. Steve is working on a small internal project that takes sales data and passes it between servers for a consolidated mini report of sales per corp.

We then got into a small brainstorming session about corp-specific aggregated data (summed up data) and how we could help with a multi-corp consolidated aggregated data type model. Eric said something the other day about having a master corporation and then getting data from that one (from the master) to feed the smaller or sub corporations. We talked about taking that option out further and how another corporation could be a great collecting spot for the cross-corp and/or consolidated aggregated data.

Random notes from our brainstorming ideas:

- Start with the corp-specific aggregated data. Each corporation will end up needing their own corp-specific aggregated data table. Our goal is daily totals per location and per category (we need to figure out what those categories will be, but pretend that they are at the category level).

- We were talking about terms and how best to state and/or call the consolidated aggregated data - if they (different and multiple corporations) want consolidated data... we could sell them another system and get cross-corp aggregated data passed back to that system - not sure which way it sounds better (two options): aggregated consolidated data or consolidated aggregated data

- What about cascading our model - we may not want to alter our model, we may just want another consolidated corp and use internal API sockets to update master controls.

- How do location(s) play into the model? What do location(s) look like on a corp-specific model vs consolidated data and what location(s) are/do out there? We talked about maybe having different mappings from corp-specific data to consolidated data and what is tracked and shows up and what may be combined together. In a small way, it almost feels like application flex grid type mapping and such. Fun ideas and concepts.

- Going back to a master corporation. We could setup a master lists of items, a master lists of customers, etc. If any of the subs add/edit things... we could figure out if those add/edits go uphill or only roll downhill (direction of updates and changes to data and master lists).

- We may need to take the part/item categories to a multiple level (deeper one-to-many system). This is an older project, but it has laid dormant for awhile. We may need to pick it back up.

- Technically, we could do the cross-corp consolidation stuff right now, we could remove the double entry out of the solution and help automate things. Figure out the flow of data.

- Eventually, we will want (or our clients will want) location specific aggregated totals, even out in the consolidated aggregated model.

- We talked about maybe having a special mapping table on the consolidated corporation side. More application flex grid and advanced mapping stuff.

- There may be some huge advantages by using existing tools such as invoices, deposits, expenses, PO's, balance sheet items on the consolidated side of the equation. Many of those things are already mapped to income statements (P&L) and balance sheets. That might be a good approach to helping out with the consolidated reporting.

After the brainstorming session, I left the meeting and starting do some other smaller tasks. I payed bills, did some emails, and got on the phone with a couple of other developers. I chatted with Calvin about custom labels and maybe getting into sub inventory and sub attributes. I also talked with Alan about helping out for the rest of the week as I will be out of town on a scout trip.

Eric and I touched based on some questions. Most of questions had to deal with adilas 3rd party solutions. Either new requests, small tweaks, and ideas on how to handle certain custom requests. We were looking at API sockets, documentation, possible expansion on certain areas, and basic flow (web interface) for other projects. Eric has three or four projects right now and all of them touch the adilas 3rd party solutions page in one way or another. Interesting.

On a different note, Steve joined and reported that he has been talking with Calvin Chipman about running C# and C++ code out on AWS (amazon web services) through Lambda functions. Wayne, had been doing tons of that kind of stuff. Steve wants Wayne and Calvin to touch base and see what we can figure out. That was some good news.

Questions for Calvin:

- What/when on your time lines and load? Timing and budgets.

- Having a hard time getting them setup (login credentials and who gets to do what)

- Charging for the adilas label builder wizard setup - once they get through... they can go far, it is just hard on the frontend

- How can we get this more inside the system? Maybe move more towards the web and setting things up that way. We need to simplify the frontend. Instead of full API credentials, maybe just check their username and permissions (web-based). Maybe going in doing some research. What is the next level.

- Maybe fill out a form and then send that to Calvin vs just an email

- 3rd party solution stuff - security

- Custom formats - currency, decimals, med date, sm date, long date, time 12, time 24, integer, other

- Being able to nudge selected fields with arrow keys - currently just drag and drop

- We need access to core sub inventory and sub attributes  - this could be a major challenge - super dynamic - on the PO side, invoice side, cart side, and normal part side

- bulk print from the cart (session stuff) - Crazy mixing pot - People are used to printing from here, but maybe we need to make it easier on the finished invoice side. How can we make it easier to get to?

- As some point, we will need flex grid values, vendor info, store/location info (could come later) - maybe even being able to mix some of these things.

- At some point, we may also need access to parent attributes (could come later)

- Audience questions... common user, tech user, designer, programmer - How do we select and train them - Ideally, we would like to have one person per corp that could do labels.

- Defining the database terms and fields

- Videos and other training materials

Wayne had some questions about some of the photo galleries. Especially on the stock/units and general inventory items (things that you sell either smaller widgets and/or serialized or bigger inventory items). Wayne is going through the code and taking code that is very repetitive and pulling it into custom tags and then doing some mappings to get to those tags. Lots of little tweaks to help speed things up and actually use some of the browser caching as part of the solution vs trying to force an auto refresh every time. Making good progress.

Steve and I had a small meeting about what we wanted to cover with Calvin in an upcoming meeting. As a random side note, we have to monitor time lines, budgets, and bang for our bucks (return on investment - ROI). We also talked a lot about education and how training and education keep playing into the mix. They are some of the easiest pieces to leave out, but they are critical for better turn over and long term usage and retention. Good conversations.

Getting started and getting all caught up. Steve had some files that needed to be merged in. Wayne popped in and helped to answer some more questions on the transition to AWS. See attached for the latest notes. We are calling that transition document done, at least for now.

Working on merging in code for Steve. Also got a call from Calvin Chipman and we chatted about some things. Lots of moving pieces. Steve and I got back to the code merging and while we were working, we were chatting about some of the great people that we have and get to work with. That is awesome. We would love to do another training event, here soon. Even if it ends up just training our own team, it is worth it.

Dave Forbis called in and I chatted with him for bit. He is on the outside edge, but he could be a great asset when the time comes. He has a number of customer relationship and project management skills that could really play into the mix, if the conditions were right. Great potential.

- 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

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.

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.

Joined up with Steve on the Monday morning meeting. He was showing me some new pages that he was working on and using some prebuilt CSS templates that we purchased. Russell Moore got us started with those CSS templates a few years back. Steve has been in there playing around and is grabbing code and pages and plugging in real code and database values. It is starting to look pretty good. As a side note, a couple times today, we have circled back around to prebuilt templates and what they offer.

Steve and Dustin were talking about some of their combined efforts and different demos that Dustin has been giving and doing. He has done a great job and is very easy to work with. That is a huge plus.

Calvin joined in and had a few questions. He also helped both Steve and I get the latest versions of his adilas label builder wizard. We worked with the label editors and then also gave Calvin a few change order to do list stuff. We would love to get some data formatting functions to help make the data look good. The other major topic was talking about 3rd party solutions and how we secure those pieces. I told Calvin that I would work with him on what is needed and how best to get the desired outcome. We are planning on adding a section for Calvin and MyEasySoftware in the adilas 3rd party solutions section.

One little nugget from todays talks and discussions was: We may be better off getting one or two key persons trained up on certain features and implementations and then allowing those parties to charge or get paid to help setup the others who need those pieces. It helps get specialists and also really cuts down on the tech support required to do harder or more complicated tasks and processes. The summary is: Get people to pay for value added services, especially somewhat technical or complicated setup or in-depth processes vs trying to teach everybody how to do it on their own. The other option to that, which would be nice if possible, is to make the setup and/or processes more simple and intuitive. Somehow we need to monetize some of these deeper tools. Either charge for setup and training or increase the monthly reoccurring.

Wayne joined the meeting and had a few questions. He and Calvin chatted about AWS, windows services, and how they may be able to use AWS Lambda functions to do similar things that we are doing under the current Windows server model. It got pretty techy. We setup a new permission for Wayne to use in his open id user pools and how to grant or deny access between open id users and different worlds or corporations.

Steve and I did some more work on templates and getting a good starting place to work from. Steve was talking about how awesome it is to use prebuilt CSS templates due to the fact that you start from a working picture (static or fake data) and then build in functionality from there. We did a code merge for Steve and I had to help out with some page view icons for some of the new pages.

Towards the very end of the call/session, Wayne popped back in and had some questions about changing the MySQL data engine from MyISAM to INNODB type tables. Techy database stuff. He also had a question about the scan and add to cart process and how complicated it seemed to be. We talked briefly about some performance tuning and options. Basically ways to help go in and split things apart and/or speed up certain queries. Afterwards Steve and I chatted and talked about some of the cool things that are coming down the pipeline. Keep moving forward.

Working on a fix to help Calvin with a custom project. We had a mixed cart search that returned sub inventory and their values. I had to rework the method call and logic to return the correct number of decimals in the quantity sums. It was treating the sums as integers (whole numbers) vs sub inventory quantities with decimals. Anyways, made some changes and pushed up new files. Let Calvin know to go and do some testing.

Steve and Alan were talking about frontend automation on the credit card side of things. We are looking into API sockets for USAePay (our credit card gateway that we are using) and being able to pull reports that show customer credit cards that have expired, will expire, or expire during a set date range. It would be super cool to get this information in order to help our billing department.

- Steve is really excited to see what the AWS (all of the stats and such) side of things will bring to the table. We really want switch our billing based on storage, throughput, bandwidth, requests, etc. That would be awesome.

- Two parts, the gateway side and the adilas side of things... we need the header and app side of the communication process (extension of the invoice due date project). The goal there is to use adilas and be able to communicate back to the users (different companies) and let them know if their invoices are getting to a certain age. Based on settings, the goal is to warn and help get a payment and if needed, to shut off and prompt for payment before usage resumes. There are more details, but that is the general idea.

------

Got on a Zoom session with Calvin. He was having a problem with an existing API socket. As he was looking deeper, we recently made a number of changes to that page back in January. It is dealing with sub inventory, searches, and calculating sub inventory quantities. I scheduled an hour, later today, to look into his question.

------

About 11 am, Steve, Bryan, and I got on a meeting to look at Bryan's adilas community projects page. This is an area where adilas users and consultants can submit and vote for what projects they want us to work on. Basically a way to get outside input on priorities and what is needed and wanted. Steve sees some of this as each user having their own little individual user account (almost outside of adilas). They then could do whatever they need to outside of any specific corporation, just as a user. When they want to go in and do some work, they would need to enter a corporation and/or world. Basically creating a separation between users and worlds (adilas accounts).

Some of our conversations turned to possible misuse, abuse, rants, and managing potential problems. In a way, it is almost like opening up a virtual forum and public facing entry point. We also talked about design and styling out the page to make things look more modern. It is crazy how deep, sometimes just a single decision goes to crazy deep levels, and it is hard to see what is going to happen. Lots of cause and effect decisions. Steve was talking about how the look and feel almost helps guide the process. How well does it show? Do people want to spend time doing something that looks old? If it looks modern and smooth, would they use it more? What do people accept? What do people want?

After the discussion about look and feel, Steve ended up back on the master user accounts topic and being able to use a single sign-in type interface. This deals with users being able to independently use certain functionality outside of an assigned corporation. We also talked about being able to submit projects and notes and having some sort of sign-off and/or approval type process.

We also talked about timelines and being able to show other projects, ideas, completion rates, what project are on target and/or in progress, and other ways of communicating as to what is going on. Long story made short, we love the ideas and concepts, but it still needs some loving and direction. Eventually, we want to open this adilas community forum and community projects to all users and consultants.

-------

Talking with Wayne about the new open/general login process. He was talking about an open id (somewhat of a master user id - a hashed username string). We were talking about questions about what happens if a user gets setup but hasn't been associated to a specific world and/or a corporation? How do we allow those assignments to be made, requested, and eventually approved. Wayne was talking about an authorization queue and a way to approve and allow access to certain users.

------

Worked with Dustin on adding new entries in the sub GPS/RFID tag table. This is a sub of elements of time. He is tying things into his cultivation and production pages.

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.

Going through adilas pages, changing page icons and verbage to help with Calvin's new adilas label builder stuff. Also trying to help do a little bit of advertising for Calvin and MyEasySoftware.

Pretty quite meeting today. Steve was sick. I was working on small to do list items. Nobody else jumped on the meeting. I was making some small code tweaks. Phone calls, fixed a small graphic, and worked on some new pages to help promote MyEasySoftware and projects that Calvin has done.

The attached graphic is a small one that I made for our GoToMeeting account. We needed to put a logo up for when people join our meeting. It says "Think of where we can go!". It has a mountain trail, an adilas interface, and the adilas logo. As a side note, maybe we should sell potential. We've got a lot of that. Interesting angle.

Shannon and I met up and went over some things. We started out and I gave her a demo on a couple of the new things that are being released. I had some struggles with Calvin's Adilas Label Builder, but it got better. I took down some notes and will be reaching out to him. I also showed her a demo of Josh's discount engine and where that is at. We talked about some other converging projects, including Eric's loyalty points and gift card stuff (sub special accounts). We briefly talked about some sales flyer stuff and encouraged each other to keep chasing the dream. sometimes it feels kind of allusive and hard to catch. Good meeting.

Calvin was slightly delayed, so I kept working on the adilas tick list project (getting notes off of post-it notes and into a bigger spreadsheet document). Got the spreadsheet ready and sent it over to Steve. There were 50+ projects just on that new spreadsheet. Calvin called and we touched base. I am going to make a page for him to help promote his Adilas Label Builder app and wizard type editor. He will send people an email with a download link and serial numbers. Calvin will also finish up the last little tweaks and push up those files. We are getting close on this round. The next phase will come after we allow a few users to get in there and beat it up a bit.

This is round 2 piece. Bid out for $15,000 to make it into a web app.

Steve would like the login and API setup page to be more user friendly. Currently it requires some very techy info and we need to tie it to better security. We may also need to allow corp keys that are aliases vs the old way (use-53). I had a small problem with doing a label and then not being able to get back to it to edit it. I couldn't use the new labels using Internet Explorer. We still need help files for the new label builder. It may also be nice to record some training videos and publish them. I also told Calvin that I would help build him an adilas 3rd party solutions page. Also, as a reminder, I was going to send Calvin an email and request some formatting options. I would also love the option to be able to nudge a selection around using the arrow keys (moving the actual fields in the label editor).

Wayne and Steve were having some good discussions on the new AWS (amazon web services) stuff. Lots of talk about bringing new corporations on and getting them all setup out in the AWS landscape. They were even talking about rewriting our API to match the AWS environment in a better manner.

Calvin was giving us a demo of his Adilas Label Builder app. He showed us a full build from the ground up. We built a PO label and then did a number of live tests. We had Wayne, Steve, and myself on the demo. Calvin is doing a great job. I will be meeting with him later on today to finish up some pieces.

Briefly working with Eric on some local JavaScript validation and questions. He is getting further along on his sub special account tracking project (loyalty points, gift cards, etc.).

Working with Wayne on media/content stuff. He is going through and testing all kinds of stuff on the new AWS environment. Currently, we have provided him a list of some known bugs and he is working through them. That is awesome.

Spent some more time working on the adilas tick list (giant to do list). Still just trying to get all of the smaller projects listed out and on one spreadsheet. That's a pretty big project in and of itself.

Monday morning... here we go again.

Steve, Dustin, and I were on the morning meeting to start with. Each of us has our own to do list stuff. We touched base and then started working on our different projects. One of my projects for today is to take all of my post-it notes on my desk and put them all on one giant to do list and/or tick list. I only made it through a couple of post-it notes before I got pulled off that project to help with another one.

Eric joined the meeting and had a number of questions about the sub special account tracking project and some decisions on how and where to do the safety checks. We got in to it and decided that he would need both local validation and server-side validation. We talked about mixing JavaScript (local) with ColdFusion (server) and how best to do that. I showed him some examples and pointed him in the right direction.

Calvin joined and had some questions about direction and working with multiple servers. He is working on the adilas label builder app and wizard-type project for custom labels. Steve and I setup a demo for tomorrow. Calvin also needed some help accessing some live data to do some tests and what not.

After that, I went back to adding in to do list items on the big spreadsheet. I paid some bills and light tech support stuff. One of the tech support questions was dealing with custom field settings for customers. This has been somewhat of an issue since 2016. Long story made short, we added a page where a user can change names, show/hide, sort, set defaults, require, etc. for basic customer fields. That options exists on one page... it also only applies itself to just one page. The problem and/or request has been, why don't you cascade those settings all the way through the system? To answer that, I would say, we would love to... it just takes time, planning, a goal, and funding to get it done. We would love to finish some of those things up.

Towards the end of the call/meeting, Steve and I talked briefly about priorities and needs within the system. Lots of demands and we have to manage the resources based on both internal demands and external demands on the same resources.

Calvin and I met up and he gave me another demo on his progress for the adilas label builder. He now has a web-based system that collects user inputs and quantities and passes that data over to the label builder app.

Met with Calvin over a Zoom session. He was showing me progress on the adilas label builder. He is now working inside of adilas and doing connections, links, forms, and API socket calls from adilas to his label builder program. He has it working locally on his machine. I gave him a few requests/suggestions but it is looking good. The next major step is building a Windows service and being able to do the same thing live on the adilas content server (where we will serve up all of the custom PDF labels using his label builder). I authorized him to keep going and sent a small update over to Steve.

Eric and I were working on his project. I ended up on a call with Calvin and going over some of his adilas label builder stuff. As it progressed, I ended up flip flopping between both Eric and Calvin answering questions and helping them here and there.

After working with Calvin earlier, he gave me an assignment to help prep a new page for him. I built him a new page that was black box ready and had a number of basic adilas features built into the page. I sent them over to him to help him get a place to start coding and integrating the two products together.

Calvin and I worked on his adilas label builder app project. His first round project is getting close. We moved out of his Windows based app (the actual label builder app) and into the web and tying the two programs and platforms together. The label builder is very powerful and dynamic. Anything you can think about may be added to the labels. That includes any number of graphics, lines, QR codes, barcodes, static text (fixed values), input text (open for typing), and dynamic text (pulling in data from a database). Any of these things may be used in any context and any number of times. If you wanted a label with 4 different barcodes on it, no problem. Pretty crazy.

Anyways, our new goal is providing a way for us to connect to user data (normal adilas stuff like PO's, invoices, items, parts, customers, etc.) to the power of the adilas label builder. We went into adilas and determined about 7 access points for the custom labels. Calvin is going to start working on those pages and passing information from page to page to start sewing up the functionality. Great progress.

Got on a Zoom session with Calvin to see some progress on his adilas label builder app. He had added in some quantity options for parts, PO's, and invoices. He also showed me some other features such as about (light marketing stuff) and options to reroute back to the start to do a different label. He is making progress and we scheduled some more time for tomorrow.

Calvin was giving Steve and I a demo on the adilas label builder. He was showing us new label options for invoices, PO's, and items. Prior to this, he only had customer info ready. Good progress.

Calvin and I jumped on a Zoom meeting. He is working on pulling in label values for invoices and invoice line items for his adilas label builder app. Tons of data and it gets kinda tough to cycle through and figure out what is needed and what is not needed. It gets pretty deep with multiple queries and multiple one-to-many relationships. Most of what we were talking about was strategy on how to gather, filter, and only advanced data that is needed. This is stuff that makes your head hurt... :)

Talking with Calvin over a Zoom meeting about the adilas label builder application. He has been off on other projects and this was just a meeting to get back into the project. We briefly talked about goals, priorities, and options. We also talked about putting some of his Windows based tools out on AWS for Mac users. Somewhat of a small workaround between Windows and Mac stuff.

Alan, Steve, Dustin and I were on the morning meeting. The first little bit was each person reporting on what they were working on and what issues are still outstanding. Steve had a couple of questions for Alan and Dustin. They are following up on different tasks. I spoke with Alan a little bit about our plans for some changes in how the sub inventory and sub barcodes were going to be searched and filtered.

Next, I gave Steve a small update on my meeting with Spencer and Wayne from last week. He asked for some drawings on what was going on. I explained that Spencer was at a turning point where he was going to be needing access to actual data. He doesn't know Adobe ColdFusion very well yet, but he is a PHP master. PHP is another open source server side scripting language. Wayne and I decided that we would let Spencer build out his new prototype in PHP and use the adilas API sockets to get and pass data back and forth. That sort of spun us off into a small discussion on where are we going and how are we planning on integrating all of these pieces. That, of course, is a whole other topic. We touched on the need to build out the adilas API sockets (play at the wall - allow outside data connections) and how that would fit.

Calvin jumped on and a couple of the other guys bailed out. Steve and I had a good talk with Calvin. Our current project with Calvin is an outside label builder for custom and bulk labels. Part of our conversation was helping both adilas and Calvin get our communications being built up and on better levels. We chatted, got on the same page, and will hopefully be back on task next week. Calvin still has some other projects that he is working on right now. Good meeting.

Steve and I then spent some time talking about how the trend is kind of going toward 3rd party solutions and 3rd party build outs and then trying to inter connect them with internal adilas flow and processes. This took us back to a subject of PHP and other adilas API socket connections.

Eric popped in and had a couple of questions. He is building an project for sub special account tracking stuff like loyalty points, gift cards, etc. Some of our discussions today were dealing with page flow and naming conventions. We talked about having a new sub homepage for the special account tracking stuff. We then talked about how the user would have to let us know what special account type they were looking for information on, and then what that process would be like as they walked from step to step, adding filtering, and then finally results with drill-downs. Lots of concept level talks about flow and data. Good stuff and I think that Eric is making some good progress. We'll still need to tweak and refine things, but progress is being made.

Lots of emails and other things, just trying to get caught up and going. After that, Steve and I jumped back on the discussion about PHP, adilas API sockets, playing at the wall, internal vs public files, what servers would look like (just Adobe ColdFusion boxes, just PHP boxes, or dual setup of both ColdFusion and PHP per box). We have some questions that we will be asking Wayne about options and direction. We also made some good break trough's by noting which files and servers were private (owned and controlled by adilas) and which files and servers were public (owned by 3rd party and/or outside entities). Just adding what was public and what was private, really helped the conversation and get both Steve and I on the same page.

What we are seeing is that we need to keep pushing for a full separation between the data (database, storage, and access to the data), the logic (functions, methods, API sockets, and flow), and the actual display (what things look like, where they focus, and what they do or don't do - visual interfaces). Those three things data, logic, and display are huge. The more we separate them, the more modular our application becomes.

We didn't spend a ton of time on this... but all of our discussions were somewhat pointing to the greater and greater need for the adilas market (adilas world) to play a part in the puzzle. Currently, we have a saying "Play at the wall" for the adilas API sockets that we expose to the outside public. That wall is basically the access point between the adilas database and logic and the outside world. We are almost seeing a 2nd wall (virtually speaking) starting to form up. That second wall or outer wall is the adilas marketplace and who has what, who offers what, how is it obtained, or who has made pieces that  virtually are able to be plugged in and/or integrate with adilas core functions and functionality? I'm betting that the open market will end up playing a bigger and bigger role as things progress. Our challenge is how to manage that as it grows. Good stuff.

Steve, Dustin, Wayne, Eric, and I were on the morning meeting. I gave a small update on my "on site visit" yesterday with the tool company. Tons of new notes and pages of ideas and requests. Wayne wanted to talk about ways of standardizing code, and how things get implemented. He pitched a couple of fun and good ideas. He had us look at an article about ways to use Git (version control software) and have a number of different stages and/or branches. He was also explaining about how he could implement things like this inside of adilas. Super talented and we've never even been able to consider some of these concepts. Very interesting. Here is a link to the article... not exactly this process but some similarities.

https://nvie.com/posts/a-successful-git-branching-model/ 

After Wayne was finished, Eric and I chatted about the sub special accounts homepage and what that would be and/or look like. We made a small plan and then Eric jumped off. Steve and I then started talking about how some of the developers are really wanting to jump in and play the game. We talked about Russell and what he wants to do, Wayne and what he wants to do, Alan and his goals, where Calvin is at, Dustin, Spencer, etc.

Right about that time, Eric popped back on the meeting and was asking Steve about some ideas and concepts of revenue sharing and how we could build things out to a more and more stable working and development environment. Eric was talking about how much better adilas as a whole would be if he was able to build out core features and projects vs doing the custom one-off implementations all the time. Some of these developers work and work and work and then their projects are done. Most of them want something that is reoccurring and/or can be reused over and over again. That seems to be a trend. Very interesting, almost the exact or similar topic that we were on. While Eric and Steve were talking, I was listening and making some mental notes. We don't know which way to jump yet, and we don't want to overload the boat so that it tips (get too far extended by debt and/or payables), but there are some awesome opportunities right in front of us. We have a great talent pool that we know, like, and have the skills to do what is needed. We just need to figure out how to keep funding the journey. That is awesome.

From Steve - he thinks that we have crossed a new checkpoint. We are having guys with talent that are virtually knocking on our door saying - I want in.

Russell's word - "Dependable" on what we called the people on our team.

Steve was also talking about some supplemental experiments with salespersons and people helping to push our product out there. We are going to start funding some small sales missions and covering certain individuals for 10-20 hours a month doing sales. If they get a sale, they are able to charge their normal setup and/or consultant rates. If they are prospecting, they will be on a small adilas budget to help them cover prospecting time and maybe some gas money. Basically, a small "low to no" budget sales force, but helping to augment and/or supplement the sales efforts. Fun stuff.

Towards the end of the session, I took some time and recorded some notes. To some, it may seem like a waste of time. To me, it is what I do and that's part of the job and/or what I like to do. I gain from it in big ways. Whatever I write, I have to think about it, record it, re-read it, and it improves my memory going through that exercise. Anyways, that's why I write so much. Once it is down on paper (virtual and/or physical) I can refer back to it and it lessens the stress load. There is an old saying, the faintest scratch on paper is better than the sharpest mind.

9/9/19: Cory has completed customer tax categories in the cart, customer purchase histories from advanced add to cart, reoccurring eots, alt text for barcodes. 

Drea is going to complete new corp wide show email contact settings, Louisiana metrc update.

Waiting on delayed inventory counter (wasn't totally working- need Alan to take a look), also waiting on sub inventory updates as Bryan is still working on these...

Cory is working on most of these updates and will check with Drea on her status. 

Customer tax categories going through the cart, customer purchase histories being available as a quick look-up from the advanced add to cart, and update for inventory counts and new delayed inventory counter (check with Alan to make sure everything is uploaded on this one). Reoccurring elements of time, alt text for barcodes, discount engine for Josh, labels for Calvin, loyalty points for Eric, sales tax update, etc. Bryan had some new ones for 15 new flex grid fields, new corp-wide show email contact settings, maybe check with him as time goes by.

Wayne and Steve were talking about servers and some of the new updates that are going on. Wayne is helping to fine tune and monitor the servers. He wants to be in charge of that portion of the puzzle. He is very good at it and knows what he is doing. Steve and I are trying to encourage him to keep going in that direction. Some of the discussion items were dealing with servers, up-time, redundancy, database table locks, response time, active vs passive monitoring, and empowering our users and clients to view stats (maybe limited views) on the server. There was quite a bit of talk about new news and updates talking about the server monitoring and even possible mirror and/or redundancy back-up and/or mirror server options (insurance and roll-over technologies).

Wayne was asking some great questions about the current model and where we want to go with things. Steve was responding and answering the questions. We left off with a charge on Wayne to get in there, dig around, and come back with a plan. We may end up rolling some of the new changes out over a series of months. Good stuff.

We touched base with some of the other developers on the meeting and then broke out into our own work sessions. I was working on the sales tax branch and trying to cascade new sales tax changes through the black box pages. As a fun side note, there are around 400 (ish) black box pages that are part of the master code branch. That doesn't even include ones that are created and uploaded without being merged into the master branch. What that tells me is, that our clients like custom options and that section, black box or custom code, is a huge part of our model. It can be a pain in the rear some times, especially if we are trying to update things, but it also fills a need and our clients seem to like the options of being able to customize things. That is awesome.

Once everybody left the meeting, we all just worked on our own little projects. I was doing tech support and follow-up on some sales calls. Towards the end of the session, Steve and I chatted briefly about the client who may want to do some tracking on their assisted living facilities. We talked about maybe setting up a play site for the assisted living and running things with locations, elements of time, etc. Lots of good ideas.

We also talked about the adilas label builder that Calvin is working on. We are getting close on this round of the project. We would like to see where all of that goes and what comes out of it. We are looking to close out phase one and then start using it to see what else may be needed (round two or phase two).

Steve - we are a solution for solution minded persons. We are really seeing that the clients that like customization, they tend to be some of our greatest clients. Very interesting. We are also seeing that some of the reps are a great resource and are throwing some ideas and monies at things (pieces of the puzzle) that they need and/or want. Some of them are getting funding from their clients to help push things forward.

Random idea... what about opening up the door to our customers to get their own developers and let the custom side of things grow a little bit deeper. Maybe use the adilas market and let some of the independent developers run with things a little bit.

Training - we were talking about ideas and timing. Things are a little bit crazy right now, but we don't want it to get out too far before we circle back around and setup some more training. We were also talking about costs and paying for that. On a different note, we have tons of hidden benefits like hooking up Marisa and Drea on training. We also have Calvin who was at the last training and got tons of great info and feedback about his labels and Gmexting (group mass texting). Lots of hidden benefits and getting people trained and more involved.

On the morning meeting with the guys. We had both Wayne and Calvin pop in briefly. Most of the morning session, Dustin and I were working on his code to auto increment these huge RFID tag numbers. Basically, you start with a huge 24 digit and/or character tag and then increment just the tail end. It has tons of zeros, alpha/numeric values, and an incremental portion. We spent a lot of time going over the sub loops and loops within loops. We got it and it seems to be working great.

Around 11 am (ish), Steve was showing us some cartoons about a dog. Anyways, Kat, Danny's wife, was telling Danny (one of our sales guys and label developers) that adilas was kinda like a dog. You tell it to go and do something, and it tries to go and do it. Anyways, Danny took this idea and worked with a guy from his church and came up with some fun cartoon dog images. Really fun. The artist's name is Naters Art from the Salida, CO area. Adilas is the word Salida spelled backwards. Kinda fun. Anyways, Naters came up with some great images of this dog, rolling over, with a bone, searching, and tilting it's head. The developers on the morning meeting were saying that they could see some of these images being used as icons while waiting, searching, success messages, error messages, info messages, etc. Lots of good laughs. See attached for a screen shot.

11 am -  meeting with Gene Spaulding with the SAL Management Group. GoToMeeting

We started out the demo and meeting with letting Gene show us around in his spreadsheets and what was connected to what. Really cool and he has taken things to a huge and super deep level. Steve and Gene were able to briefly talk about how both of them started at the spreadsheet level and then eventually grew out of that and into a database type technology like adilas. Good stuff.

One of the main pages that they had was titled - Census and Roster - who is where and what is what (simplified operational and accounting data). This fed the rest of the reports and pages.

Steve - what would be mission critical for you guys? They answered that it was the census and roster reports (getting data into the system). Simple screen to gather that information and then disperse it as needed.

They do have a 3rd party that does all of the onboarding platform stuff. All the paperwork, contract stuff, legal stuff, etc.

They have looked at some of the big huge platform applications out there... they are kinda looking for something smaller and maybe more custom. We did a demo and I think it went pretty well. I had Dave Forbis and Steve on the call with me. They had a controller and head manager on the call. Good back and forth and we had some fun.

On the morning meeting. We briefly talked about some updates from the weekend. We had a number of different developers pop in and make small reports.

Steve and I were about system stats and reports at the higher system level. We also need some rules and how we allow and/or don't allow play. Not just reports on how much data we are carrying along (total stats and counts)... but also, what is added new per day (incremental reporting). We need to be able to analyze usage, storage, and even analyze bandwidth. What are they truly using.

From Calvin, there may be potential in monetizing the usage of the application. If we are incurring a cost, we need to pass that on, plus adding in some profit. We have some clients that come in at a super low rate. Then they grow and develop and build and become more successful, but the system fees haven't increased to match that (at all). Basically, no one is monitoring the growth, storage, usage, and system stats. We need some report matrixes that we could show and then charge for. 

Calvin popped in and gave Steve and I pretty deep demo of the adilas label builder. We got pretty deep, we played, asked questions, and even got into some of the funding and financing of how do we pay for this, how do we fund it, and how do we keep supporting it? Good stuff.

Some people want to buy it modular (every little thing) and some people want to buy it as a package (get everything and use what you want).

Some of the matrix values might need to be: How many things get created? How often are they being used? How much data is being transferred back and forth?

How do we monetize things and get a real ROI (return on our investment)? It comes back to sales, rules, and what we setup. Steve and Calvin were talking about putting all of the tools out there and then letting them (the adilas users) use what they need. Kinda like a big giant rental center... they could use the big tools, the small tools, and everybody could use whatever they needed. They were talking about small mom and pop shops, percentages, set fees, or some kind of mix between those different models. Lots of options.

By us not monitoring server stats and usage, we and kinda killing ourselves. We want to come up with something that is fair and workable for all the different parties. That is where we want to get to. We want to track the cause and effect of data storage, file storage, processing (API socket calls, queries, data in/out), and maybe usage and bandwidth.

Looking forward... We may need some snapshot info (aggregated data) to show corp to server stats. We may need to start counting reads (queries and looking at things) and writes (inserts and updates). We may need just counts per day per corp. This could become some of our general matrix values. Steve and Calvin were talking about possibly charging for the net results (what are they getting out of it). We need to store it, and then go back and use that as the histories, stats, and usage.

Just an idea... what about showing stats per user and what they are browsing (who is generating the usage - who is looking at what). We could add some counters on the actual method calls (yep, Holly used me or pulled me).

Steve - Every year that a company is with us, we keep adding a virtual train car to what they are pulling and/or hauling. At some future point, we may need a way to snip and clip some of that older data off (how much are they hauling). This could be in and may include standalone declarations and other watchers, feeders, and triggers. Certain tables just keep ballooning and we are storing and storing data. We need to figure out a way to archive some of that data.

Happy Halloween! As a fun side note, both Steve and Josh have Halloween as their anniversaries. They were able to chat and have fun talking about that.

Calvin popped in and we got some API stuff working on the adilas content server. He needs that functionality for the new adilas label builder app. Good stuff.

Alan, Dustin, Josh, Steve, and I were on the morning meeting. Steve had a couple of questions about some emails that were going around. We pulled in Alan and chatted about some database restructures, re-indexing of records, and full table rebuilds. We then talked briefly about a client that has a bunch of custom code but hasn't really been able to get things going. They are currently not paying their monthly bill and not responding to the David B. and Shari O. We have decided that we need to turn them off as it is costing our company trying to chase their company. If they want it, we can easily re-flip the light switch back on.

Wayne jumped in and we did some checking on his database migration code. We logged into the dedicated server and ran a couple reports. All of the data looks good and he will be contacting the client to let them know. This project has been ongoing for about 2 months now. Basically, we migrated about 10 corporations off of one of the shared servers to their own dedicated servers. Well, once we finished and released the new dedicated box, they came back and said, what about this other corporation that we had no notes and/or record of. Because it missed the normal migration process, and the new server was already live and consuming auto id numbers in the database, we couldn't do our normal migration process. Instead, Wayne had to write a new program that allowed for both servers to keep running at full speed and still be able migrate and copy database records across between servers. That may sound easy, but think of all of the auto id number and foreign keys based off of the auto id numbers that could get messed up. This was a very deep project. It looks great and seems good to go. That is awesome.

We intend to use this same program (actual software we have to run on the physical servers) to help us migrate other clients off of shared environments and into either other shared servers and/or to their own dedicated boxes. That is a huge break through for us. Good stuff.

After that, I jumped in and did some emails and tech support stuff. Towards the end of the meeting, Calvin jumped back in and we made two of his permissions go live for the adilas label builder. We then did some light testing on the live servers. It still needs some lovin, but we had a successful live test between data 0, the content server, and Calvin's adilas label builder app. That is pretty cool. He was going to make a couple changes and then get back with me. Pretty cool and some great progress.

Alan - Reported on some database changes, new session and application based permission changes, and talked with Steve and I about possible corp-specific database tables. We are still in the pros and cons state of some of those decisions, about the corp-specific database tables. Alan also asked Steve some questions about the upcoming part/item weight and part/item count stuff. That is one of his current internal projects that he is working on.

Calvin - Popped in and showed up some progress on the adilas label builder. He has a bunch of things working on the local level. The next area is interacting between servers and using API socket calls. The last part of our session, we went over what it would take to make and create an adilas API socket section on the adilas content server. It already does some of that, but needs to be updated and retrofitted to help with Calvin's adilas label builder pieces.

After that, I spent some time doing emails and trying to help point Will in a good direction for a thing we are going to be calling "Transitional PO's" - these are a cross between an order/request PO and a live PO. It deals with when do you start paying for parts/items, when do you record them as inventory, and how do track the transitional date range when it is somewhere in the middle of an order/request and an actual live PO that affects inventory and payables. Basically, extending out the order and fulfillment process to a deeper level.

On the morning meeting. Alan and Dustin were working on complex forms and passing dynamic data between different pages. Lots of AJAX, JavaScript, and JQuery. Alan did some demos and explanations on some new session based permissions checks. He should be launching the new graphical invoice homepage today. It has tons of charts, graphs, and summarized data.

Calvin popped in and went over some of the new API sockets that he will be using for the adilas label builder. He is going to be using about 8 or 9 custom MyEasySoftware API 3rd party sockets (custom built for his label builder). He also went through some other flow and button options to show us some of the progress. It is looking good. He passed me some new table definitions and I wrote a small database update file for him so that all servers and developers could get updated records. As a future note... eventually, we will need to update every page that currently has adilas paperwork (custom document assignments) so that they can look-up and show the custom labels and assignments that get built through the adilas label builder application. Cool stuff.