Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 12/14/2019 11:51 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 5322
Template/Type: Brandon Time
Title/Caption: Adilas Time - Brandon and Steve
Start Date/Time: 12/17/2019 2:00 pm
End Date/Time: 12/17/2019 4:00 pm
Main Status: Active

click to enlarge - photo by: Brandon Moore - Some rough sketches from a meeting between Steve and Brandon - talking about a way to setup and manage a testing account type scenario with some of our bigger clients.
 
 


Notes:

Meeting with Brandon and Steve to talk about business plans and options.

- We talked about our independent model. Both pros and cons. This is for both developers, designers, and our rep/consultants.

- We are looking for people who want to be part of this model. We really want to focus on those who want to play the game with us.

- Running at max output levels and how to work on efficiency stuff.

- Making those hard decisions. That gets really hard.

- On training... is that really helping right now? In some ways yes, and in some ways no.

- Using the community funded projects to help manage flow of expectations and funding.

- Selling what we have and getting people started at that level. More things could come in later on.

- Seed money and how does all of that work out? We are still trying to figure that out.

- We really need to get some of our guys down to one project and help them get focused and stay focused. That gets really tough.

- We have so many projects... we almost get lost.

- Getting our guys to be responsible and accountable for what they are working on.

- We are spending monies on all kinds of things... which ones are really valuable? There has to be a balance point.

- Sometime it takes a hot plate or major pressure to make you want to change (burning platforms).

- How long does it take to get a new developer? There is a big lead up and a long transition period.

- What if we restructure things a little bit? What would that look like and where would we turn?

- What about a proposal and some planning to get to the hub type model?

- We want to have a small team. We know that we need help. How do we structure that? We love the idea of independents, dependables, and even cofounders. We know at some point we may need to get some employees (keeping it small) but we want to keep it at a manageable level.

- What if we had companies hire their own developers? We help with the project management and meet with them to keep them going and what not. We could really gain there without getting super overwhelmed. As new code comes in, we could virtually cherry pick and harness the work and efforts of other developers. Some of the big companies may really benefit from having their own developers.

- We sub stuff out to Newtek (the server farm). What if we allowed some of the development stuff to be subbed out and virtually use their own developers?

- Play at the wall - this was an API socket dream. Any outside developer could play and code against the virtual wall.

- We may need to step back and help mange the flow vs coding all of the pieces. These other companies could really benefit from what we have to offer. How can we help them get over their pain and get past the next level.

- How do we bill for our time? Talking about Steve and I. Currently, we work for adilas and adilas pays us. If we work for the clients, they really should pay us for our time.

- Question that was asked by the business consultant... What is your exit strategy? What are you doing to get there? Are you looking to get a pay off, reoccurring revenue, a retirement plan, etc., etc. Good questions.

- There is a difference between core development and custom development.

- Talking about developers... What if we figure out their rate (the developer) and then add on to it (for our time) and we then help them charge for it and we then pay out and also make a little bit. Normal add on services.

- Steve was saying - we need to say no more free lunch. We have a viable solution. If you want more, you need to bring your checkbook.

- What about charging for our time? Meetings with Brandon? Meetings with Steve? Meetings with Alan? Meetings with Russell? etc.

- Steve and I really love the dreaming process.

- If we could charge more for the custom development, that would help.

- Sometimes we keep beating our head against the wall until it hurts. At that point, you start looking for options and how to relieve and/or get rid of that pain.

- Making a switch... instead of the business running us we need to start running our business. Steve loves the idea of using technology to run our business and solve our problems. That is awesome.

- Selling our services (custom code, design, and project management) and not just our software.

- Charging for productive hours. This could be for our time, code sign-off, project management, custom code, etc.

- What if we went to more of a controlled open source type model? Going beyond software as a service (SaaS) model and getting into a virtual open source model that is tied into the underlying SaaS model. What does that combo look like or what do you call it?

- We haven't had a project that we couldn't handle yet... Sometimes it takes a lot of time and requires a number of different steps, we've been able to see the steps and then setting up a plan to get there. It takes time, money, talent, and the plan.

- Steve and I want to get out of the middle of the volcano (analogy that we were talking about). There are lots of fertile valleys all around us.

- These companies want to succeed. They really don't want to build out the whole software solution. They just want it to work.

- Making a scalable model. We even talked about a new virtual testing environment for these companies.

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

Talk about the automated cross corp stuff and aggregated totals being pushed between corps (herbo project - see email).

We need to talk about our plans with the product lab.