Jim Dougal (tax atterney in California and works with differnet CPA's) jumped on and had a few questions for Steve. We also had Pat Dolan join us. Pat has been helping out Adilas with sales and customer relationships. We also had Timothy Lyons (lead IT and tech for Herbo) join in the meeting. The subject of the meeting was dealing with pricing, technology, and how to move forward.

1. Price piece - discussion between Jim and Steve

2. 3rd party solution - Herbo ecommerce solution - We want to allow all of the customers access to this option. Having said that, we need a 3rd party solution switch that would allow for an actual switch (on/off).

3. Integrating with Square (payment processing) - They are in the process of finishing up the contract between Herbo and Square. Steve has already talked with Bryan Dayton (adilas developer) for the Square integration.

4. Other - On the server side, we briefly talked about dedicated servers and how we can proceed. We could commission physical dedicated boxes or virtual cloud clusters. Along with that, we talked about custom URL's and/or domain names. There were some questions about when does a company need a dedicated box vs a shared stack or semi-dedicated server model. What are the thresholds and capacity levels? How many transactions are we looking at per company, per server, per group?

Looking forward on AWS (amazon web services)… we get away from a physical dedicated server but it gets into a dedicated stack and/or dedicated cluster. The AWS environment allows for virtual load balancing and then automatically adding and subtracting dynamic power to help with the processing.

There were some conversations about splitting up the bus and getting each company on its own corp-specific database vs a shared database. As we get bigger and bigger, we will need to split things apart to make them faster and more efficient. Having said that, that also increases the need for back-to-back API sockets and data exchange between clients and clients and corporations and corporations. As things grow, we end up seeing lots of cross-corp type connections and functionality.

Tim had a couple questions:

1. Where are we going to host things? We would like to setup a meeting with our current hosting provider. Tim would really like to be in on this conversation. We, from the adilas side, need to get both Wayne and Alan involved in our decisions. As a side note, we have a physical dedicated environment that works and can work in the future. All of the AWS and/or dynamic cloud interfaces are in the process... but we don't have a physical fully working environment.

Steve was talking about once we get things settled, we can still jump up to bigger servers, clusters, and even migrating data and systems to the more robust virtual environment. Lots of options. There may even be some pricing options such as economy level, mid level, and deluxe type levels. Some of that may come back to where are things hosted and what are the environments that get setup.

Tim was talking about umbrellas and having dedicated and shared servers underneath the main umbrellas. Basically, a way to stack the systems. In a way, we simulate a hosting company by sub dividing our IT assets as needed.

- What are the timelines for AWS or Newtek?

- There are some discount options for pre-buying and/or pre-paying for servers.

- There were some talks about charging for hosting as a pass-through type charge. Currently, if our clients are on a shared type environment, we only charge a monthly fee, similar to a ski lift (pay for a seat and the chair is just spinning). However, if we have a dedicated client, we charge a server fee and then the monthly within the dedicated server. Kinda like a private chair lift per server. Adding in some options to help do normal charges and then also help the clients pay for what they are using (being able to track the stats and real usage per client). They were also talking about watching and monitoring each box and getting the best ROI (return on investment) per server. Basically, the standard fee structure that we currently use may need to change to help deal with pass-through and new and upcoming costs.

2. What about code branching? They, Herbo, would like to offer a specific version (branch of code) and then be able to mix and blend and cross merge code as needed. If they develop things, we could merge them in, if we develop things, they could merge them in. They would be separate branches. We would like to have another meeting between Wayne, Alan, Tim, Steve, and others.

- We briefly talked about themes (separate internal sub folders) or are we at an API socket level (external data sharing) where we are just exchanging raw data back and forth. The difference is, it built internally or built externally and just played at the API socket level (play at the wall). If they play that way, external API sockets, they could use AJAX and just push and pull data through the API sockets. If they work on the API socket level, they could code it any way they want with any look and feel and any backend coding languages.

- Steve kept bringing it back to use what exists and what works and we'll go from there.