Phone call with a business consultant out of California. We chatted for about half an hour. He just wanted to get some information about me and our business. After the meeting, I sent him a text with some info, contact stuff, and a small elevator pitch of what we do. It was similar to the other elevator pitches that I have made but I reversed the order and added a little bit to it. Here is what I wrote him:

We offer all kinds of operational business tools. We also help companies with the accounting side of the puzzle, if they choose. We are web-based and do all kinds of services that support our platform. Our clients can get started using our system within 24 hours. If they need changes or custom solutions, we can do that as well. Very diverse.

Here are my other notes from our conversation.

- Get your go to market strategy setup up first.

- Figure out your 30-day execution plan or playbook.

- Make sure that your packaging is ready to go (the business plan and/or pitch deck - for whomever the audience is)

- Do some simple process mapping. Where do things start, where does it go from there, where will it end up? That is kinda like a roadmap for your clients to know what to expect and/or plan for.

- Look at what needs to be automated and how can you gain from efficiency changes?

- What role does AI play in your rollout? Look for ways to help with creating improvements.

I got up and started doing some planning and brainstorming. I was just planning on doing a little bit and the ideas kept coming, so I wrote them down. Here is what I got.

- Do some 1-pagers (one-pagers). Maybe even 4 or 5 of them. Quick reference stuff that could be used alone or used together as part of a group. This could be for sales, intros, quick guides, showing pieces. Make them all simple 1-pagers.

- Include the elevator pitch on one of the 1-pagers

- Show correct web links on the flyers or 1-pagers

- Link to the plan - fracture or adilas lite

- Old adilas GPS core image

- Old adilas formula flyer

- Old adilas map or interactive map flyer

- Maybe update some of those older one-page flyers

- Link to the presentation gallery

- Talk about ways to invest - 1/10th of a percent, 1% (full percent), 10% - show some levels and options

- 75% of the company (adilas, llc - adilas.biz) is available for purchase

- We are doing a capital raise - Looking for 2 million to 10 million for a new buildout

- Setup some small rules - this would be for investments and raising capital for the new buildout. Straight prices, don't worry about taxes (basically with tax included). Simple 1-pager, you get x percentage for y dollars. Super simple and cut and dry. No promises of future value. Basically, if you buy in, you then own part of the company. In the case that it sells, you would gain from that sale. There are differences between buying a percentage and active funding of projects. Maybe make small 1-pagers per section with some super simple rules. Add links to the web site for investment options.

- Talk about options for commissions - 10-20% - leaning towards 20%

- White labeling - minimal starting investment of $100K - buy in at a percentage (could be small), then do a plan and figure out the scope. Detail things out. Then figure out the plan from there and how complex the new white label is going to be. The initial $100K pays for the ability to build on top of the kick butt engine and the detailed scope and development plan. The rest will be determined from that point. The goal with the white labeling is geared towards future revenue and rolling things out in scale (future reoccurring revenue from multiple clients or business verticals). White labeling is an investment and plan for the future. If the project feels like less than $100K, we may push you in the direction of custom code vs actual white label.

- Dealing with white labeling - This is something that gets built on top of the adilas engine, ideally built by our team for a 3rd party vendor, that 3rd party vendor would then run the marketing, billing, tech support, etc. for their clients. We would most likely host their white label on our servers, and let it ride on top of what we have. It could even limit access to the underlying pieces. If someone wants to host it themselves, code it themselves, and just use API's (backend connection sockets and such), that is different. That would be a 3rd party solution and would go through the adilas marketplace.

- For white labeling deals or buildouts, we will end up setting some rules and prices for monthly fees, profit sharing, wholesale costing, dedicated or shared hosting, and other details.

- Talking about scope, timelines, feature creep, and change orders. If the plan changes, in any way, we need to be able to adjust (change orders). That could affect scopes, timelines, deliverables, budgets, milestones, etc.

- For me, think about the trystorming type approach with a known need to circle back around and refine things

- Contact info on the 1-pagers and in the packet(s)

- Old graphics about ecommerce, system players, choose your skin, show your stuff, etc. See image.

- Ideas - You could go around with some flyers and do some seeding...

- Get people to go door to door in neighborhoods and/or in business districts

- Promotion codes and lead tracking - tie back to commissions and affiliate programs

- Social media influencers and people who push products - sometimes people trust these guys/gals/people

- We start with the main adilas MMLLC (multi-member LLC) - then we open it up into the other MMLLC's - adilas.biz, adilas shop, adilas university, adilas marketplace, adilas cafe, and maybe adilas funding or adilas management - there could be others - adilas employment, adilas staffing, etc. Along with that, allow for investment options of 1/10th %, full percentages, and bigger percentages (say 5 to 10% and above).

- When ready... maybe a small glossy folder with a few key 1-pagers in it - small packet

- We need to do some market research on the pricing. This will help us be more confident in our pricing. We have to follow the market value. There is an optimal range. And, the market is changing dramatically right now with AI and SaaS mixes.

- Most credit card processing fees are around 2.5% of your credit card sales per month. We are pricing adilas around 5% of your total sales (cash and card) per month. Also remember, most companies are doing the mash-up option and paying for multiple systems to make up the whole. Paying 5% for one integrated system, is great!

- Small samples on pricing... Basically, take a monthly sales number and times it by 5% or 0.05. Samples for some starting numbers: Monthly sales from $0-$400 x 0.05 = $20 (smallest monthly fee). Then show values for $1K, $5K, $10K, $20K, $40K, $60K, and $100K - using the same formula. Make a note about multiple locations. Simple math. If one or more of the locations are at a different size (sales volume), no problem. We can set those values. Once a monthly is set, we can hold that number for six months, and then we may review it if needed.

- In sales, if there are custom needs, we are willing to talk and chat about quantity discounts, franchises, seasonal usage, clients not using the sales features but using other parts of the system, etc. We can provide special quotes and structure deals. We can't go lower than 2.5%.

- This is for me... Just as a reference, we at adilas, pay about 15% for servers and web hosting. As of end of 2025, we are paying around $12K per month just for servers.

- $1,500 starter package - list it out - setup, turning things on, and up to 15 hours of training and/or help getting things configured and going. Monthly fees are separate. This is just the starter package. If you don't need the training hours, it is $500 for a one-time setup. You have to have a prior system to just do the new setup fee as a standalone. If custom circumstances exist, we recommend that you get ahold of us and we can figure out a deal. The goal is to get you going and make sure that you off to the races.

- Once the training and setup hours are done, if you need more help with monthly tasks, special tasks, or whatever, we bill at a rate of $65/hour. This could be for consulting, setup, bank reconciliation, data entry, etc. We want to help you get going strong and we offer services where needed. The future goal is to use the adilas marketplace or adilas cafe to help fill these needs.

- Get the flyers done professionally - make them nice

- Use a temp service to help get the word out - get them the information and/or packets and let them manage it

- At some point, we will need an internal training meeting for our team members

- Make some new page (web link) redirects - some of the files and places have longer web addresses - make a number of smaller redirects - folders and path stuff - links like the adilas lite or fracture plan, investment opportunities, and the presentation gallery.

- Fix the adilas pricing page - show some other options - line it out a bit. It is pretty simple right now.

- Help work with Bryan on his sales channels - Finetech (merchant processing) and Host Huskie (web hosting). We could do similar things over and over again as needed.

- The existing software package (adilas.biz) can handle 75-90% of any business - out of the box.

- Just a thought - what if I put all of this into AI to see what I get - that would be cool. Maybe wrap it all up together.

- Get out of the way!

Emailing the team about the new functions for bulk adding PO line items (mini reverse shopping cart functionality). Small email to Wayne about a possible global database for helping to train the AI agent. I would like his opinion and thoughts. Spent the rest of the time working on a training plan to help train the adilas AI agent. Spent time working with ChatGPT to make a plan and start rolling it out. Towards the end of the session, I was having ChatGPT help me generate some PDF's to help with some of the adilas quick search functions.

As a reference, here is the share link for the AI training session that I was having. Some good stuff there. Light elevator pitch, a few small PDF files, some help files, and making plans. https://chatgpt.com/share/69377fb0-4594-8007-81af-a48edbc72690

Doing some AI agent training inside of adilas. Training on help files and adilas elevator pitch. More AI testing and even doing some testing and training from different servers and different user id's. See attached for some of our notes.

Emails. Take adilas and accurately distill it down... keep it super simple, even if the tech is quite complex. Just for fun, I sent a simple elevator pitch to an email contact. Just playing around. I spent some time updating help files and web page id's on other servers. Recording notes from 12/4/24 to 12/5/24.

Meeting with Steve and Alan. Going over budgets, pay offs, timing, talking about the approach, don't talk about positions, pitch the sale ($150 internal vs $75/hour - using some of our guys directly). Steve was and has been selling pieces of custom code to our clients. He would like help there and have the guys pitch their own services.

We spent some time talking about our identity and who and what we want to be. Taht is coming along. Here are some other general notes from our conversations (multiple topics):

- Help protect our clients...

- Set some caps on how much our developers can charge

- Communication back to the clients - weekly reports and billing

- Billing - weekly

- We can't let our developers rough up our clients

- Helping our guys succeed - plans, billing, communication, oversite, etc.

- Possible kickback - commission to adilas

- It takes so much time to crunch things up - sales or custom code - the reality of what it takes

- Can't keep pushing things over to the balance sheet (code or projects for Kelly) - it costs of too much. We pay the developers and we owe money back to Kelly.

- Consultation document or a checklist type doc

- We are generic on purpose - if you want it custom... you've got to pay to optimize it

- Setting up boundaries and being firm on that

- An add-on cost for custom work - they need to pay for it - they may need to keep paying for it (reoccurring) - maintenance

- Selling what we have

- Our development and sales focus is as a general business tool

- Elevator pitch - web based, SaaS (software as a service), we focus on operations and accounting, we have a base model, and we allow custom

- We want to be generic. We want to cover a number of industries. We want to be a great companion software for any business.

- This is who we are - defining ourselves and what we do

- Plans for our upcoming meeting with the developers - take care of business and setup another meeting where we have some plans all made up.

- The developers may have some ideas on how to make things work

- How can we get some of the cool stuff exposed to the public? Selling what we have. - sales - nobody is pushing it, our tools and features, as a product.

- Alan had the idea of using an outside marketing firm - when ready

- There is a need for marketing, education, etc.

- YouTube influencers - quick, short, and powerful mini messages - short and to the point

- Podcasts - how to run your business, tips, tricks, and best practices

- Piece work - we have tons of stuff - what if someone could harvest that kind of stuff? - YouTube, Facebook blogs, podcasts, etc.

- Alan would like to talk about the future - looking short term, medium term, long term, etc. - talking to Steve, Brandon, Shari o., Wayne, Cory, etc.

Prep for a meeting with my dad and his friend Harry. I made a small list on a post-it note for some ideas that I wanted to go over with them. Here are a few of the ideas and notes:

- Go over the elevator pitch for adilas

- Playing the game of add-on as a business model

- Finding pain points and coming up with solutions

- History of where we came from and how things developed over time - it's part of our story

- Demo login and letting them get in and start playing around

- MVP - minimal viable product, plan, person, presentation

- Graphics and world building concepts

- General rules and setup - what's the flow process

- Operations and accounting - horse and the cart - operations has to lead (it's the horse) and accounting follows (the cart)

- Permissions and settings - configuration

- Going over flow and processes

- Systems and relationships

- Simulating reality or simulating the real world - what really happens and why?

- Non-linear system - concept of the data assembly line

- Adilas quick search and standard navigation

- Our current goal - fill in the gaps

- Help files and videos

- Reach out and ask for help - use the whole team

Good meeting this morning. Steve had just come off of a multi hour demo yesterday afternoon. He was reporting in and going over things that he had learned. Both Sean and I were listening as Steve was explaining and teaching us. Good stuff.

We talked a lot about solving pain points and how that helps make our product a viable solution. Steve got into some financial training and where things come and go (ways that monies move or track) and how that creates a cause and effect type relationship. As he was talking, I was plugging in numbers on the financial flow calculator to illustrate the flow of the monies. Steve had me build that page to help with just such trainings. The real goal is capturing and recording the story. The numbers then play into and through the story vs just being a standalone number (plugged or adjusted value). That is super important.

As a part of the financial flow, Steve was talking about being able to mix and bled while in the same system. If you run your operations on one platform and then try to do your accounting on another, you will always have disconnects. If you run things as they happen and then report back (roll call) then you can capture the story and thus get the financials or accounting (what really happened). That is where we are heading.

They were talking about software and different releases. With what we do, we release new things and features all of the time. Constant releases and constant refinement. That lead to a discussion on what are called "mash-ups" or "mashups". This is where a software company takes a number of different tools and applications and basically mashes them together to get a whole. There are pros and cons to that, but that type of business is also prone to major disconnects and paid points. We are striving to make a fully integrated system that lives and breathes on its own.

As the guys were talking, Steve was telling Sean how Kelly (adilas rep) was doing the demo. He brought up how well Kelly will say something like "We will help you and here is what that will cost." Both assurance, help, and tying it to cost, in the same sentence. Sadly, I'm not very good at that. It usually comes out something like, "Yes, we can help you do X and Y. And, oh, by the way, we should probably give you a quote." Or something like, "Great idea, I'll build that in and/or make a note of that (assuming all costs or taking it on internally)." Anyways, I'm not very good at the monetizing thing. Light discussions about styles and goals.

The discussion extended into talks about promises, expectations, and what those things really cost. We also talked about how much prep work and knowledge is needed to do certain things, tasks, or jobs. Sometimes those things are a barrier to entry. One of the things that we have found, mini gold mines, is getting first-hand knowledge by helping customers solve their problems. If you can afford it, those clients help by transferring real-life knowledge of what it takes and what is needed to get the jobs done. Invaluable, hard to put a price tag on those things. We love doing that when we can. It ends up in a net benefit. We tend to do what we call piggybacking. We build something for one client and get to pass that on for free or as part of the system to the next client. Then that client will help push something else forward that the other clients get to benefit from. It becomes a form of piggybacking. Kinda fun!

Custom work! That is one of the things that sets us apart from the rest of the software solutions out there. We love and are willing to do custom work. That may not sound that big, but it's huge. As we were talking, we were reminded of our elevator pitch (condensed sales pitch). It talks about us offering a standard package and then being willing to customize on top of that. That's pretty cool. Here's a link to our mini elevator pitch (also one to Sean's expanded elevator pitch). We really do offer a lot of options.

We will just keep working on sharing what we have and how it can help people solve their business problems and needs. As a small side note, Steve was talking about ecommerce and how that little solution is actually becoming a way to sell and interact with clients without even using the main internal tools. It's so simple and connects everything together, we actually have some companies that help people use the ecommerce options and solutions vs using our internal shopping cart tools. It keeps it simple yet limited in options. I just find it interesting that some companies are using that tool vs the internal tools. I don't think that I could have anticipated that. Interesting.

This is an expanded elevator pitch - submitted by Sean Carlton on 8/17/22

Adilas is a complete business solution for business-minded companies. We handle all of your operations, such as Point of Sale, E-Commerce, and Inventory Control, and tie them directly to your Financials, such as Time Clock and Payroll, Accounts Payable and Receivable, Profit and Loss Statements, and your Balance Sheet. We operate in high-compliance industries, such as Cannabis, Firearm Sales, and Liquor Stores, as well as high-value Unit sales, like Car and Trailer Dealerships. No company is too big or too small, with complete systems, starting at $97 per month. As great as Adilas is, "out of the box", we also offer very affordable customization to fit your flow and processes, instead of making you adapt to ours.

Just pushing it up for the record. Good stuff!

Meeting with Sean over the GoToMeeting channel. He gave Steve and I a new expanded elevator pitch. We went over that new pitch and made some suggestions and ideas. We also spent a bunch of time talking about merchant processing and how things are organized. I showed him the datacap website and I was pitching their ideas and how they connect to multiple gateways and use multiple pieces of hardware to make that happen. I'm excited to see if that will work out. Eventually, we want to either use what they are doing and/or create our own process along those same lines. Good discussion.

Huge email back and forth with the underwriters at Trinity Payment Solutions. We are in the process of switching merchant processors. They had a number of questions about our business model and how we do certain things. They wanted clarification on billing practices, pricing, and contracts. Spent quite a bit of time giving them answers and explaining what we do. I went into tons of details and provided links, logins, screenshots, statements, etc. Just for fun - we are a high-end SaaS (software as a service) company, dealing with operations and accounting. We have a standard package that we use and then do custom work on top of that. Mini elevator pitch.

Danny was on the meeting this morning with some of the other guys. He and I were talking about the little interview session that we had yesterday. I was really happy and on cloud nine yesterday after that little session. Super fun! Anyways, Danny was talking about the question that he gave me about the elevator pitch. I quickly reviewed it and sent them over a link to the basics of the 3 part elevator pitch. Real quick - 1. High-end software as a service model (SaaS). 2. We service and cover needs in operations and accounting. And 3. We have a core system, ready, out of the box that we use and then we customize on top of that as needed. Those are the nuts and bolts of the super quick elevator pitch (at least currently).

John had some questions and was asking about some code samples and style guide (adilas docs) stuff. I gave him a bunch of samples and hopefully pointed him in a good direction. Chuck joined the meeting and John and Chuck were talking about some tweaks and changes to both the style guide and the docs (code snippets). I'm really happy that they are using that. Just by them using it, it brings value to that project.

Chuck and I did a small work session on the view parts page. He is doing a face lift on that page. We went over some things, I helped him with his settings, we added new my cart favorite buttons, we added new flex grid tie-ins, etc. Lots of talking and bouncing ideas off of each other. The current view is very top to bottom linear. We talked about doing two different mock-ups. One that would be linear (top to bottom) like the current page but with new look and feel. We also decided that we could break the page into some horizontal tabs to use the space more efficiently. We could also use those tabs to categorized the different sections. This is not exact yet, but things like main item details, photo gallery, sub/child inventory, recipe/build tie-ins, my cart favorite buttons, flex grid tie-ins, etc. Each tab would hold the respective data below it and thus somewhat hide what is not wanted unless clicked.

After that, I was recording notes, checking emails, and trying to help.

A bunch of the guys were on the meeting this morning. There was Sean, Danny, John, Dustin, Steve, and myself (Brandon). Steve and I were working on some string manipulation stuff. This is where you take a string (notes or alphanumeric data of any sort), find sequences and then do certain actions based on those findings. After we made some progress we switched gears and got into some sales type talks and discussions. Danny had some great questions and was asking the group for some feedback. Sean presented some sales outlines that he was working on.

I ended up grabbing the screen and pitching some ideas and doing some drawings. We talked about how adilas is a great companion software package for any business, regardless of what else you have. We can fill in the gaps or be the whole solution. We are able to play at all of those levels. I gave my 3 point elevator pitch and explained it a little bit. The 3 points are: 1. Adilas is a high-end software as a service type product (SaaS) - meaning web based software solution. 2. We cover anything dealing with operations and accounting - very broad but still direct enough. and 3. We have a standard package (the software application or site) and then we are able to customize on top of that.

We got into a small discussion on selling what you have, even if it is not fully finished. I showed some of the guys my old LTF (learn to freeride - snowboarding interactive product and multi-media app). I told them that I got the whole thing done and then tried to sell it. A marketing guy had us repackage it, go to some trade shows, and then we ran out of money before we could really push it all the way. I still have some older products and pieces at my house, under my stairs. I related this to selling adilas and even the concept of what we are trying to do. Steve has been great on that and has landed client after client, even if all of the pieces weren't done.

By way of a history, the adilas corporation id is in the 20's and all of the earlier corporation numbers either already existed or wanted in even through things were just barely functional back in 2008. We started in 2001-2002 but didn't officially become adilas until 2008. Prior to that, it was called the Morning Star System and was a custom write up software package for Steve's used car dealerships and trailer dealerships. If you want more info, here is a couple pages of a brief history document (pdf).

It takes all of us. No one person could tackle the adilas monster. It literally takes all of us. Whether it is ideas, coding, tech support, sales, development, maintenance, servers, etc. It takes all of us. Be your own style. You will fit in and be a great part of the adilas team! We love it!

Towards the end, Steve and I were lightly pitching some vision and where we are headed as well. Fun little session for those who were on the meeting. Good stuff.

Going over option for inserting meta data in key pages. Danny was heading up a discussion about SEO (search engine optimization) with John M and myself. I was taking notes and the other guys were commenting and providing ideas and info. We started out with intellectual property and went from there. Here are the basic notes.

- IP - intellectual property - natural flood - you can't copyright or trademark or paten things that already exists... if we flood the area with prior art, that effectively prevents others from claiming things as their own intellectual property. Fun discussion about where we are headed. We are sharing to protect ourselves.

- SEO - buzz word - science and art of making things show up for searches and on search engines

- Seen and unseen - matching SEO content with real natural content - light talks about the history (good and bad) of SEO

- Marketing and getting a new website for adilas - we really want to get a good plan in place and then follow that plan - up until now, it has been a very natural progression that just sort of happens. We want to be more specific and deliberate on our efforts, messages, and marketing. It is time.

- We have a bunch of different levels - main website, secured content (SEO not needed - due to login and permissions), shop (ecommerce - a little bit more tricky), web/API sockets, and other pages and documentation.

- Web content - they virtually and really score your site based on responsive design (mobile ready), same domain name (traffic and visits), amount of time on that domain (frequency and length of time on certain sites), reciprocal links (who links to who), matching content (good natural content), etc. Going over the basics.

- Meta data - key words, buzz words, include photos and videos with built-in meta data

- Sometimes it is the little itty bitty things that help - small things but a lot of small things really start adding up - almost like a virtual score sheet

- We don't want to do anything that is sketchy... off canvas text, hidden things, tags and random content, etc. Play well and be honest.

- We want a main landing page and home base that deals with what adilas is and does (as a whole). This is not industry specific, but who and what are we.

- Animated story lines and time lines

- Some other links - see chat - elevator sales pitch, presentation gallery, outline, chuck's new sales tools, etc.

https://data0.adilas.biz/adilas_formula.pdf - adilas formula

Web link - elevator pitch

Web link - presentation gallery outline

Web link - internal questionnaire summaries (sill working on this - progress)

- Put Danny in charge of the team - pick a team, get a plan in place, set a budget, and help to roll things out.

- What do we want to sell and pitch? Up to this point, we have been pretty off the hip... we need a strategic plan as we go forward. It is time.

So, I was in a line waiting to go see my daughter in a marching band performance. The guy in front of me asked me... what do you do? Here was my answer...

"High-end software as a service (SaaS) company. Anything dealing with operations and accounting. We have a standard package that we use and then we customize on top of that."

Very simple, but has a lot of loaded statements.

1. High-end software as a service (SaaS) company - This is the whole package without saying it. Monthly, service package, and full business platform.

2. Anything dealing with operations and accounting - This is another whole package type statement dealing with the range that we try to cover. Most people understand different operations and accounting pieces and even know where they have needs and/or struggles. Easy foot in the door, yet very diverse.

3. We have a standard package that we use and then we customize on top of that - This says that it is somewhat ready right out of the box and with different settings you can configure almost anything... Plus, we do custom on top of a standard piece or process. The sky is the limit. You dream it up, we'll help you wire it up!

This meeting didn't happen. Cory and I were going to record a video for my cart favorites and the flash buttons. Instead, Sean, Steve, and Cory were talking about sales and the needs to be able to sell in bulk, including items that are not yet in inventory, and still keeping the inventory tight and manageable. That is a challenge. Steve was showing Cory and Sean a demo on his orders homepage (orders is another word or alias for quotes).

If you think of quotes, you may get hung up on the name. If you think of it as a tool and are able to name it whatever... it becomes more clear what is going on. Basically, they have clients who are requesting products and inventory. They want to keep track of the orders and/or virtual requests but don't want them (the orders) to affect inventory until they are ready to be shipped and sent out. There are also all kinds of backorder type needs. A quote, or a non inventory invoice of sorts, is the perfect tool. It just needs a little tweaking and it could be the order process. We could then track the fulfillment of those orders as they become real invoices.

Currently, one quote can have one invoice as a built-in relationship. We are seeing the need to expand and/or extend that relationship from a one-to-one to a one-to-many, meaning one order (quote) could be filled with multiple invoices. The difference between what is ordered and what is fulfilled, becomes the backorders or what is still wanted.

As part of our conversation, we also talked briefly about a possible elevator pitch for sales and marketing. Here is the brief pitch - High-end software as a service (SaaS). Anything dealing with operations and accounting. We use a standard product and then allow for custom on top of that. Click here to see more info on the elevator pitch (30 second intro into adilas.biz).

Web link - elevator pitch for adilas - ideas and concepts

On the morning GoToMeeting with Russell, Eric, and Steve. Eric and Russell were talking about tons of ideas on loyalty points and gift cards. Both guys have clients who have offered monies to push this project forwards. We are going to be trying to bring them both together to get the bigger master plan recorded and planned out. We will then build towards that and release things in phases to get it up and functional as soon as possible. See attached for a Word Doc that had a number of concepts and specs for the loyalty points and special account tracking stuff.

For the record... Steve said that yesterday he was able to help out Calvin - The grasshopper helped the master. Steve wanted to get that recorded. It was dealing with PO's, subs, and recording things in bulk backend processes.

Also for the record... Steve is saying that he is hearing Russell say "us" more than "you guys". We are happy to have him more and more on the team.

On the theme... We may want a bulk update to help flip users over more easily.

On news and updates... Steve was recommending that we build some standards for what is showed and what is displayed. Russell was saying, let the people write and build them and then let Russell virtually approve and get them up live. We are trying to go more to a template type scenario where we can virtually plug and play. What is it? What does it do? How do I use it? Videos, written instructions, screen shots, etc. Help make it as smooth as possible. Russell also wants all of the key players to help populate some of the features, updates, and help files. It will be a great team effort as it keeps going forward.

On barcodes and populating PDF labels with barcodes, we (Bryan and Brandon) did a job the other day that we had to crop (make the barcode height smaller). That way, we could put smaller barcodes on labels.

We talked about seeing adilas at the 10,000 feet level. Basically, what is the short elevator pitch? Steve and I were talking with Russell about how to present our model, what we do, how we do it, and why we do it?

Two good virtues - Being able to stand for something but still being open enough to listen. If you aren't open to change... how can you ever affect or make changes happen.

Labels are really heating up... We can do custom but we may need to build it so that individuals can do their own things and manage things as needed. We need to empower the users to build and create and store their own labels.