Talking with Kelly and Steve about the balance sheet.

- The original balance sheet was developed in 2009/2010. It needs to be updated.

- The development of outside requests and how it almost creates legs or outshoots from the core.

- We want to consider the balance sheet in all of our development processes.

- If Kelly helps with project management, how does that look and where can we take it?

- The buck stops at the balance sheet. We really want to get more into the accounting market. The balance sheet will be a huge value piece of that puzzle.

- Seeing and paying for the value that they are getting from our continual efforts, meaning our clients.

- How do we roll this out in order to help our clients see the value that we are bringing to the table.

- On the coding side, there is more than just code languages that need to be understood. There is theory, there is concepts, there is a way of thinking.

- Some of the coders/developers are only as good as their plans are... We need to help and fill in the gaps. Also, some of these guys have a hard time seeing all of the connection due to the fact that they aren't in there working on everything all the time.

- There is a huge amount of education that is needed to help translate to the developers as to what is going on.

- Steve was talking about how we are trying to do the projects and get those things going.

- If we start messing with the balance sheet... we are technically messing with all of the financials (cause and effect and multi-facetted).

- As we roll this out, we need to look at the progression and the succession plan (how it rolls out) for this part of the project.

- Due to requests, we get pulled in many directions. Sometimes that makes it tough.

- What is best for adilas? What is best for our customers? Often we get turned from our own projects due to funding and heat/pressure.

- There are a limited number of people who really know what is going on in the background. We need to expose some of that knowledge and/or know how.

- Our customers get drunk on technology... they just want more and more. That is both good and bad.

- Sometimes we have a disconnect between adilas needs and customer needs. No one is really planning and coordinating those needs. Many of them line up, but might be stated differently.

- Talks about how we can standardize things and get a better buy in from the CPA and accountant side of things.

- Starting out of thin air vs a process to get the ball roll - talking about where and how things start and how to help standardize the system.

- We are looking at aggregated systems (cross corp summaries)... before we jump there, we really need to focus on the individual corps first.

- What if we go back to the balance sheet and show how that is really your business (the core).

- Education and helping others know what is going. Maybe even as part of the adilas university.

- Talks about who is adilas and what do we want to be? How can we create a stable infrastructure that allows for more passive type management?

- What we have learned along the way are invaluable. Look at the last 10 years of development, ideas, and new development/inventions.

- The balance sheet is the report (snapshot in time) that helps us know where things are at.

- Back in October of 2010, we spent a ton of time trying to map out the system and what happens and how it relates to the balance sheet. That exploration process showed us a lot of things that have been super important in the past few years.

- Kelly really liked how Russell worked with and rolled out the Snow Owl theme. There was a plan, a product, a presentation, and education to go with it. The full meal deal. 

- We started talking about project management and people who have helped with some of these projects and helping to setup these requirements, maps, directions, tech specs, etc.

- What roles are we all playing? We've got talents and ways to contribute to the whole, but sometimes we are trying to bring things together but may be in the wrong spot or wrong role.

- We also talked about helping with training to get others involved and in the know.

- There were some funding options discussed and proposed by Kelly.

- From Steve, adilas just needs to be the software piece. We may not need to be all of the other pieces.

- Making less work for a user by harnessing technology and AI type decisions. All kinds of things happen all the time, we just need to figure out which actions are key indicators and/or triggers. Learning to harness those triggers.

- Automation of onboarding and that flowed information into corp-wide settings, industry types or verticals, and how to help that information translate into settings, permissions, and user happiness.

- From Kelly - Some of our biggest clients have come from some of our little guys that started years and years ago. We have basically helped them bring value to their organization. There is a difference between little guys and enterprise levels.

- Some of the people who help to service the solution have made way more than the actual tool itself has made.

- Talks about charging for support and how does that look and roll out?

- One of our biggest walls (internally) is who is going to build it and make these things happen? We have some people who can plan things and figure out the requirements. We need more people who can actually do the building/development.

- Live chat and making certain help options as a value add-on. Small talks about Full Circle (3rd party) and using some of their technologies. We talked about auto responses, automation, and human side stuff such as support tickets, live chat, phone calls, etc.

- Steve and I get so bombarded with meetings, we struggle with some of the other things that are on our plates. Too much of a good thing. As we keep growing, we keep hitting some new levels and then can't seem to push past that level. Eventually we get past a certain level just to find that there are more limits later on.

- Looking forward to some future meetings to help push this project forward. We need some time to plan this (the balance sheet) project forward.

- We may need an outside source to help us really focus on what is important. Sometimes we get too close to the subject matter.

- Versioning and maybe building some new pages and new functionality. We need to look at how we roll these changes out and how it plays into the main financials.

- There was some talks about life cycle dates and ranges. We may need to start out and show certain things as of certain start/end dates. Accurate, reliable, repeatable - that is the goal. As we change and move forward, we may be able to charge more for some of these new pieces. Evolution of the system.

- We are built on a good foundation - we can really build from here.

- There may be a future split between legacy vs enterprise solutions - everything has a value. We want to be scalable based on the size of the client and what they need.

- If we are reducing the number of systems required to run your business - there is a value there. If you start listing out the costs, you will be surprised. We bring value and we need to show that value. Finding that balance point. Real money savings can also be equated to time savings. That is huge.

- Let's do something about this! Keep making it better.

We did push up a video online. It is called kelly_steve_brandon_talking_about_balance_sheet_plans.mp4 and may be found at www.adilascontent.biz/videos and it is 1:37 hours.