all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 7/1/2015 to 7/31/2015 - (49)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 3898 |
|
Daily Tasks | 7/1/2015 |
• Working on numbers and prepping a file to present to the adilas interns and developers about wage changes and options. • Went into Logan to work. Got setup for a special team meeting to talk about wages and payment options. We did a GoToMeeting session. I presented numbers and did a presentation. We ran reports, looked around, and went through a number of Microsoft Excel documents, graphs, stats, and different payment models. We went through loan options, proposals, and wage options. We had a good group discussion and talked about limited hours, limited dollar amounts, or some other progressive – hybrid models. We also drew out some different models and talked about sales & services. One of the best subjects and topics was cookie cutter projects and things that we could duplicate over and over again. Doing custom is fun and awesome but it takes very highly skilled developers and each project is different than the last. That takes time, training, project management, and multiple moving pieces. Anyway, a great meeting and session. • After the meeting I worked with an intern and did some prep work on a project. • The rest of the day was spent helping other interns, developers, support people, etc. 30 miles. |
|
|
AU 3923 |
|
Daily Ideas | 7/1/2015 |
Normal Rep Model for Adilas: - Clients --- Reps: Independent Relationships - Clients --- Adilas: Direct Pay $ - Rep --- Adilas: Commission paid to rep % - There exists an independent relationship between the rep & the clients - The clients pay adilas directly. This is for their monthly service. - As needed, adilas pays the rep a % (percentage) commission based on the monthly. Other models & how to grow adilas: Normal Rep Model: - Clients – direct relationship with Rep - Clients – direct pay to adilas $ - Rep – commission from adilas % - Other reps & independents - Direct pay for servers - Super systems with their own servers and subs – repeatable shop or business hub model - Hub or Shop Model: (direct pay) o Support o Sales o Project management o Custom code o Consulting o Setup o Training o Hosting - They could buy their own servers and/or boxes and bill, provide support, training, setup, and other SaaS (Software as a service) features. -There could be as many hubs, shops, stores, or niche products as needed. Virtually unlimited growth options. White labels, independent clusters, niche products and services, etc. -We could serve up niche products and services, generic business options, small clients, medium sized clients, or even big huge clients. Basically, we farm out or sub out the different services and adilas focuses on the core product or data engine. -Adilas wants to be the core product, the data processing, storage, usage, etc. Basically, the backend data engine piece. |
|
|
AU 3899 |
|
Daily Tasks | 7/2/2015 |
• Went in to Logan to work with my guys. I had a 2.5 hour meeting with a developer going over ideas on models and how we could stack and grow this thing. See other page for some model ideas. • I worked with some other developers on mapping out a project to automate expense/receipts and balance sheet items. Lots of training and showing them they why behind the need. • I got on a conference call a developer, a client, and my dad. We went over the progress that we are making in the GPS world and land. Good meeting and the developer was able to get some new information. The GPS landscape is kind of random with hidden little pieces scattered all over. People are holding pieces and not sharing information very easily. Interesting! • The owner of the building where our office is, called me in to chat with me. He wanted to know what we do and what we offer. We had a great discussion and ended up filling up an entire whiteboard with drawings and sketches. We covered: dynamics, systems, player groups, functions, settings & permissions, rep models, server structures, 3D world building concepts, data assembly line concepts, stats, and even possible 3rd party predictive models for stats and other analytics. Great little meeting. • As a fun side note, Dave helped me out twice today by pulling me out of very long meetings. He pulled me out of the meeting with a developer this morning and with the building owner this afternoon. I kind of needed that extra help to pull out of those meetings that just keep going and going. Good meetings, just long… : ) 30 miles. |
|
|
AU 3924 |
|
Daily Ideas | 7/2/2015 |
-The heart is project management, project coordination, and getting things pumping through the system. Tons of other models – use adilas as the core or data engine in each model - Adilas core with different off shoots, hubs, independents, etc. - Departmentalized sections & divided infrastructure. Hub or shop model. - Add-on model – start with a core and add on, bolt on, as needed - Industry or niche specific model o Trailers & automotive o Ag & Farm o Medical & clinics o Retail & point of sale o Food & deli - Think about: military, GPS, scheduling, rentals, dispatch, financial, services, yard & tree care, specialty shops, boutique, online, digital, logistics, schools, etc. - Don’t stop here … these are just some ideas |
|
|
AU 3900 |
|
Daily Tasks | 7/3/2015 |
• Working on some new changes to the application errors and error reporting pages. Trying to make the error reports more human readable and friendly. Added in some new verbage and descriptions. • Went into Logan to work. I looked at my brother’s new bubble layout in flash. It looks great. • A developer came by to work with us for the day. This was his first time coming by the office. • I had a small sales meeting with consultant to go over models. I drew him a couple of models on scratch paper. • Another developer showed me his multi-site FTP tool. This will help with bulk uploads, staging, and possibly large files being pushed via FTP. Lots of possible options. • I had a small session with a developer going over mixing the different pieces between code, project management, and sales. • Basically, the custom code level is currently built out more than any other piece and feels slightly out of balance. The next phase will be project management and sales in the weeks and months to come. • I uploaded and tested error handling that a developer had created originally. Small display and layout changes. 30 miles. |
|
|
AU 3925 |
|
Daily Ideas | 7/3/2015 |
-Slight disconnect between custom code, project management, & sales. Current percentages: - 80% customer code - 25% project management - 10% sales Ideal percentages: - 100% custom code - 100% project management - 100% sales |
|
|
AU 3901 |
|
Daily Tasks | 7/4/2015 |
• Recording bills and scanning invoices. • Adding a new wholesale tax category to the list of options. • Started working on some new personal settings for my cart favorites. • Reviewing some past entries – lots of neat memories as I searched for “personal settings” in the adilas university (developer’s notebook) section. I ended up going on a walk and recording some thoughts in my little mini notebook. Good evening and a great 4th of July. |
|
|
AU 3926 |
|
Daily Ideas | 7/4/2015 | -Idea from my sister… Flag each digital timecard to help record clock in/outs and payroll status per timecard. Basically a flag to note if a timecard had already been processed through payroll. | |
|
AU 3902 |
|
Daily Tasks | 7/6/2015 |
• Working on graphics for the adilas.biz community funded projects. I redid a couple of other graphics. Trying to create a new look to expose the adilas world building concepts and more. I really think that some new graphics will help our users know more about what we are doing and where we are headed. Communications are somewhat tough to keep on top of. • Added some new ads and layout for the main login page. • On the phone with a developer going over pay rates, hours, and how to transition over to custom work. Great phone call and GoToMeeting session. We were talking and running numbers and scenarios in Microsoft Excel the entire time. We came up with a good plan to help with the transition. The plan dealt with our top four players at the Shop right now. • Went in to Logan to work with my guys. I worked with a developer to get some generic PDF labels created. This is for a bulk print labels project. • I then met with another developer and looked over his plans to further define the adilas shop and key roles within that environment. He had a nice Excel spreadsheet with graphs and such all laid out and displayed. • Later on, he & I got on a GoToMeeting session with another developer and went over his ideas and new documents. We further defined roles and responsibilities and even put names with the different roles. Lots of work with spreadsheets and such. • At the end of the day I got to play with some new Flash interfaces that my brother is working on. Super cool stuff. I want to get them wired up – so that I could use them. Awesome! 30 miles. |
|
|
AU 3903 |
|
Daily Tasks | 7/7/2015 |
• Went down to Salt Lake City with my sister. We talked all the way down and all the way back about adilas, life, the gospel, etc. Great conversations. • While in Salt Lake we did two main things. First we had a group orientation meeting with the Utah Micro Loan Fund people. They gave us a packet and went through it with the group. A good presentation and lots of good info. • After that my sister and I drove around Salt Lake and looked around. We ended up driving up both Big Cottonwood Canyon and Little Cottonwood Canyon. We went all the way up to Brighton ski resort up Big Cottonwood Canyon and then all the way up to Alta ski resort up Little Cottonwood Canyon. Beautiful drive, very green, and very pretty. • We then met with some clients at the Murray City Library. We had a couple hour meeting on a two-deep affiliate program, gift cards, customer credits, and web based promotion codes and coupons. Lots of notes on an information packet they gave us. We went over the information packet in detail. • On the way home my sister and I got into a pretty deep talk about boundaries, expectations, saying no, and protecting ourselves and our team. The goal is not to get into a pressure situation, a timeline crunch, or a price war. • Basically, we need to setup some processes and/or procedures to help us buy some time to fully look at things and make informed and thought out quotes and promises. The quick quotes and timelines are taking a toll. 200 miles. |
|
|
AU 3927 |
|
Daily Ideas | 7/7/2015 |
-Put up a new PDF flyer and new help file dealing with the concepts of the data assembly line. See entries in September and October 2014 for more details. See sketches on scans in photo gallery 7/7/2015 of: - Static - Dynamic - Dynamic with time, checkpoints, & permissions - X = Time, Y = $, Z = Space - 3D Assembly Line for data – include objects & data over time, resource tracking, & spatial elements (space) -Put up a new PDF flyer and new help file talking about expanding the concepts of world building, systems, and different levels and how they interact and play… Universe, galaxies, clusters, solar systems, worlds, locations, groups, individuals, data level, and run all levels over time and through space. -“We teach people how to treat us.” – My sister. This could be good and bad, abusive and helpful, pushy and firm, etc. Very interesting concept. She and I were talking on the way down to Salt Lake City about clients, relationships, and expectations. -I hate to say it, but we have trained a number of our clients to push and demand the moon for pennies or almost nothing. We have jumped almost every time. It turns into an abusive type relationship. Nobody likes that. This is just me confessing about adilas and some of our clients. Adilas has just taken it on the chops, time and time again. We’ve got to put our foot down. This is for me personally as well. I barely make it from check to check with no wiggle room. -My sister and the Project Manager are going to help make some safety nets (processes & procedures) for our development team. Virtual safety nets for our development team. -See notes on 7/29/15 for an expanded view of this graphic. |
|
|
AU 3904 |
|
Daily Tasks | 7/8/2015 |
• On the phone with Steve talking about projects, needs, and developers. We then got a developer on the phone for an hour and talked about custom projects. Lots of stuff going on in adilas land right now. • Went in to Logan. As part of the standup meeting, I rolled out part of our plan and where things are at on an internal level. I covered limits, expectations, options, etc. • Basically, a quick review of the last couple of weeks. Things have been changing very fast. I worked with a developer on checking in his code for the bulk print labels stuff. We made a couple of tweaks and then pushed and merged files with our master code copy. We pushed up to servers and tested online. We used a developers multiple FTP client (app) to push files to multiple servers at a single time. That will be a huge time saver. • I worked with a developer and went over adilas shop options, flow, and opportunities for new services. • My brother showed me a bunch of his new graphics and interfaces. They are looking awesome and will be super fun. • My sister came by we worked together on some billing and tech support options. • My sister and a developer worked and talked about custom support, consulting, and tech support packages and options for adilas clients. The developer is thinking about options for the shop model and other reoccurring revenue streams. Busy day! 30 miles. • Recording hours and calling and talking to a potential developer about starting on his mini project. • Recording bills and invoices from my guys. |
|
|
AU 3928 |
|
Daily Ideas | 7/8/2015 |
-Special corp-wide settings or a world level master control board to set up corporations, worlds, and inter-world (between) settings. Idea came from Steve. -Both a developer and the Project Manager have had the ideas to use the sales reps and consultants in communications between adilas and its clients. A great resource. -Communicate and share tips, news, new features, and even what other people are doing as custom projects. |
|
|
Adi 1174 |
|
Financial History Report - All Activity As It Plays Out Over Time - 3rd Part of the History Homepage | 7/9/2015 |
This would be the 3rd history report type on the history homepage. The other two reports are the effectual (what shows up for roll call) and the historical (who touched what). This other financial history report would be what shows up on the financials over time. This would virtually allow us to watch a company progress, almost like a movie playing over time. See the adilas university site (developer's notebook) for financial history for more info and notes. |
|
|
AU 3905 |
|
Daily Tasks | 7/9/2015 |
• Getting caught up on emails. • Replied to clients, developers, and reps about different questions. • I read through a developer’s first round draft for an employee model handbook for the adilas shop and hub model. • Reached out to an intern about building out the adilas API socket connections. • Created some light verbal quotes on some custom projects. • Recording bills and writing checks out for interns. I will be gone for the next week and a half. This makes the bank look negative but we won’t hand them out until there is money to clear them. |
|
|
AU 3906 |
|
Daily Tasks | 7/13/2015 | • Recording notes from loose pages and post-it notes into my notebook. It is crazy how fast I get behind. | |
|
AU 3907 |
|
Daily Tasks | 7/14/2015 |
• Going through tons of emails and messages. I’m currently in California as part of a family reunion and family vacation. • New logo and colors for a couple of clients. • Research on personal settings. Added two new personal settings for my cart favorite buttons. One is for who’s buttons to use by default and the other one deals with Flash or HTML my cart favorite buttons. |
|
|
AU 3908 |
|
Daily Tasks | 7/15/2015 | • Working on signing off on GPS and RFID tag tracking code. Original changes were made by an intern almost a month ago. Going through things page by page and testing and signing off on code. | |
|
AU 3929 |
|
Daily Ideas | 7/15/2015 | -The main time homepage would be really cool if we could make and create my saved favorites for that page. This would include the calendar, the time slot report view, grouped results, and details. This could really help the elements of time page to play a bigger role in the entire site. | |
|
AU 3909 |
|
Daily Tasks | 7/16/2015 |
• Working on elements of time and light math changes for showing aging and total times. • Emails and project management for a project for some interns. Started writing up an email and it morphed into a 5 page word document with graphics, screen shots, and details. Possible overkill but trying to line out a $2,000 project to auto populate the 2nd entry of an expense/receipt that is tied to a balance sheet. Anyway, trying to line out my guys. • More work on detailing out the auto post expense/receipt to balance sheet item project. Sent an email off to the guys. |
|
|
AU 3930 |
|
Daily Ideas | 7/16/2015 |
-By your own style! -If you are hunting for treasure – look around you to see what you already have – you may find that you already have a treasure. |
|
|
|
Adi 1177 |
|
Custom code | 7/17/2015 | Gift card set-up and paperless flow with electronic signature | |
|
AU 3910 |
|
Daily Tasks | 7/17/2015 |
• Recording notes and prep work. • Adding in sub dates and times and grand totals in a number of different pages. These are some totals that help with invoicing time. As a note, the elements of time already had invoicing options from back in July and August of 2011. This was just some enhancements to help with auto math calculations and totals. As part of this update we spread the math values to multiple new pages. Trying to ramp up elements of time. |
|
|
AU 3911 |
|
Daily Tasks | 7/18/2015 |
• Emails and recording bills and expenses. • On the phone with Steve. Our whole conversation was dealing with funding, developers, and how to cap and control labor costs. Our costs are currently far out weighting our revenue and monies coming in. That is adding stress to everyone’s life. We are going to need to make some cuts and do some clean up. This is a touch subject and runs deep due to the amount that we have invested in our different guys and gals. The discussion and conversation was civil but definitely heated as varying opinions were expressed. The nuts and bolts were basically, I need to clean things up and make some cuts or Steve would do it and only keep a few selected people. Basically, we need to change gears from training, grooming, and internal development to fully client funded projects and production mode. We have to produce. • Making a plan, goals, and a budget of who we could keep and why. Lots of thinking, brainstorming, and prayers. • Went out to a developer’s house to meet with he and his wife. We discussed lots of options and went over plans, budgets, goals, and a history of where we have come from. The history and story of how things have developed really helped his wife see better what was going on. Great meeting and I think it really helped. I’m planning on doing similar meetings with a couple of other key people and players. 20 miles. |
|
|
|
Adi 1178 |
|
Paperless custom flow | 7/20/2015 | Paperless office flow | |
|
AU 3912 |
|
Daily Tasks | 7/20/2015 |
• Emails, recording notes, and resetting passwords on all servers. • On the phone with Steve going over the new game plan, goals, costs, developers, projects, and options. • We spent quite a bit of time on two main topics. One was our new developer’s budget. The other was direction and details on the sub inventory and cost controls (packaging) project. Good stuff. • On the phone with a developer getting him tech support numbers and remote server credentials and information. He is going to be tweaking on some of the remote servers and such. • On the phone with a developer going over what our plans are and new developments after talking to another developer and Steve. Good stuff. • Recording notes and prepping. • On the phone with another developer talking about new options and transitions for client funded projects and wage options. • On the phone with a couple of developers going over options and transitions. • Went in to Logan to work with my guys. I worked with a developer on a business plan for the Shop model. We went through his document one page at a time and talked about things. We also revised verbage and updated the plan as we went. Lots of drawings and scratch paper work to talk about different scenarios and different models. • I talked with another developer on the phone about lightly delaying the cuts and custom code switch for developers. • I then talked with another developer about upcoming changes. • I met with both Dave, our Project Manager and my brother and we went over budgets and sales goals. At the end of the day, Dave and I went over projects, needs, and direction. I have really enjoyed his help. He has been a great leader. Busy day! 30 miles. • Made a number of phone calls to interns and developers about funding and budget plans. I left a lot of messages, chatted, and even sent some emails. Good response from the guys and gals that I chatted with. |
|
|
AU 3931 |
|
Daily Ideas | 7/20/2015 |
-At some point, we will need to make an internal ticket or invoice that will be tied to elements of time. Very similar to internal repair tickets or invoices for stock/units. Basically a way to take internal inventory items and/or labor services and apply them to elements of time. This will be part of the event tracking and job costing model. We will also need these pieces to show up on the elements of time to show the costing and mini P&L (profit & loss) per project, job, event, or whatever the element of time is called. We’ll use the stock/units as model or how to do it. -All of the guys need to start wearing multiple hats and doing other pieces of the project. -The less they depend on me the better. Help them learn to fish for themselves! -As we keep going… it is interesting how we keep coming back to phases and smaller pieces. The big grand design still exists but is too big to roll out at once. We keep going back to bite size pieces and doing things in phases and smaller steps. At least that is doable. -One of the hardest things about bidding a job is fixed dollar values and fixed dates. Our project manager was teaching me that we need to teach our clients how to treat us by teaching them our system and process vs. fixed dollars and dates. Very interesting and it makes sense. The best model that I used with a developer today – talking about transitioning over to the Shop – was a core and then stacking on new products and features model. Here are a couple of drawings that we used: (See photo gallery for sketches) - Start with a core piece - Bolt on a new piece, This could be a new product or service - Grow as needed - Keep the core and then expand from there Here is how a developer drew the Shop model. It has a light umbrella that keeps it together. It has different services that fit under that umbrella. The base, for our shop is custom code and developers. - Base: developers & custom code work - Shop umbrella: other services such as sales, consulting, customer service, project management, setup, training, hosting, design, etc. |
|
|
AU 3913 |
|
Daily Tasks | 7/21/2015 |
• Recording hours and ideas from yesterday. • Emails and checking application error reports. Sent off a couple emails to developer to have them check and update some of their pages. • New logo for a client. • Fixing a small bug on default expense types for vendors. Other tech support calls. • On a GoToMeeting session with a developer going over his project to help auto populate balance sheet numbers. • Went into the Logan Office. I spent some time with a developer working on icon menus. • I worked with an intern and signed off on code for a multi-day sales report project. Great job. • I did a little bit of work with an intern on the adilas API socket project. • My sister and I worked on some processes and procedures. We are trying to put up some safety nets to help protect us. • She and I then did a brainstorming session on a client’s affiliate program. Lots of concepting and documenting ideas. This was one of the first times that one person was at the whiteboard and one person was at the computer. That seemed to work out very well. Great breakthrough. 30 miles. |
|
|
AU 3932 |
|
Daily Ideas | 7/21/2015 |
-“You know enough” – what a great way to conquer fear – comment from my sister. -Build and help each other. The rising tide raises all crafts. -People value something if it has value to them. The value that people put on something is not an automatic – it depends on the person and how they see and/or interpret the subject at hand. |
|
|
AU 3914 |
|
Daily Tasks | 7/22/2015 |
• Emails and tech support. • Great meeting with a developer and a contact of this developer. They came over to my house for a meeting about GPS. As a fun side note, we only spent about 10 minutes talking about GPS stuff. The rest of the time was spent on how our business model grows and prospers. See other notes for more details. I took 2 pages of notes from our conversation. Super good meeting and even an answer to prayers. See other notes for a railroad and platform analogy. • Went in to Logan to work with my guys. After stand-up meeting, I explained the railroad and platform analogy to our Project Manager and a developer. • I helped an intern on the API socket stuff. We had to do some deeper debugging. • I worked with a developer and an intern on a project to simplify the add new customers and custom family members to the system. • My sister and I worked with our project manager to rough out a number of new projects. This is the round one stuff to get an idea and scope on the project. After the rough out session we assign a value so we can quote the job. Anyway, we went through 8 new project in a small amount of time. Dave and I were at the board and my sister was recording notes on the computer as we went. Super slick and very awesome process. • After that my sister and I went into more details on the affiliate program. The project is quite deep and it is more along the lines of three projects rolled into one. The scope of that project deals with gift cards, loyalty and reward points, an affiliate program (2 deep – backwards referring process), and promotion codes. Pretty deep with lots of access points and backend wiring. Good stuff. 30 miles. |
|
|
AU 3933 |
|
Daily Ideas | 7/22/2015 |
Notes from a meeting with a developer and his friend/associate: - Analogy of a railroad (or pre-built platform). So, the story goes that this gentleman wanted to ship a load of used cars from back East to the Mountains (Rockies). Anyway, he called up the train company and tried to get them to ship his vehicles. The company actually said no, they only shipped new cars (insurance stuff). So, he asked about other options – here is where the analogy comes in – the person said back to him…. You can do it, but you need to: o Buy the land o Put down the tracks o But the train or buy a rail car - Basically, the guy was saying – you can do that but you need to build your own railroad system to do that. - This answer shocked him and at first he was kind of taken back… then after he thought about it, the answer made more sense and he learned some lessons from it. This little analogy ended up being an underlying topic on platforms that we used over and over again in our discussion. Basic railroad tracks: - Buy the land - Put down the tracks - Buy the train Basic railroad tracks: - Think of different industries and/or niche products or pieces - Railroad tracks with different spurs or branches - Once the main track system is built, you can create offshoots or spurs Going along with the railroad analogy (continued): - What about spurs of spurs, niche products, custom lines, etc. - Once the main system is laid down, all kind of options could be added on, bolted on, offered by 3rd parties, etc. - Sketches of basic tracks & tracks with spurs & branches -What about the virtual real estate around the tracks? That is an open market and available to outside parties. -If a railroad is too old fashion – maybe call it part of the data highway or virtual data assembly line – whatever. -Anyway, if 75% of the system is fully in place, the other 20-25% is basically custom stuff. -As the main priorities get taken care of, the customers will want the next and next priorities taken care of. This process virtually creates a reoccurring customer because they keep rolling from priority to priority. That is awesome! -In the railroad analogy, if you buy a box car and put a sticker on it (the other 20-25%) that becomes your part of the system. The tracks are still owned by the railroad company but you, as a customer, are allowed to use the system as your own (in a certain way). Basic Rep Model: - Client --- two-way relationship (key) --- Rep/Consultant - Clients – Adilas – Direct pay for service - Rep/Consultant – Adilas – sales commission 20-40% - The key piece is the two-way relationship between the clients and the rep/consultant Basic Shop or Hub Model: - Clients --- two-way relationship (key) --- Shop or Hub - Clients – Adilas – Direct pay for service - Rep/Consultant – Adilas – sales commission 20-40% - See entry from back on 7/20/15 to get more info on the shop model - The Shop or Hub model offers a number of different services but could be the same as a Rep/Consultant only bigger. Basic 3rd Party Solution Model: - Clients --- Normal two-way relationship --- 3rd Party (product solution) --- secondary two-way relationship – commissions --- Adilas - Clients – Adilas – Direct pay for service plus possible payment for 3rd party solutions - A 3rd party has an additional relationship with Adilas More notes from the meeting with a developer and his friend/associate: - 3rd Party Solutions could be spread around the platform or railroad model. Think of different products, solutions, niches, add-on’s, etc. - Main track system: spurs or branches off of the main tracks - These could be other 3rd part options and solutions - Each one could be industry specific - They could be products, services, solutions, etc. Think Historically… - Imaging how town across the west were setup to support and use the railroad - Once the train came to town, that allowed for people to come, products to come and go, businesses to support the new needs, etc. People ended up building whole towns just because the trains would stop there. - The train company didn’t own the other businesses and the other businesses didn’t own the train company. They worked together in some kind of relationship – both parties needing the other. This creates a dependent relationship. - Adilas is starting to see a number of new dependent relationships starting to show themselves. Our clients need a rep and/or consultant. The reps and consultants need a developer to help them build custom pieces. Developers need project managers and designers to help them produce the new code and features. All of these people need a way to track things and help with billing. The process keeps going and provides numerous new jobs, careers, businesses, services, etc. - Because one thing feeds and grows another… The growth of adilas will be somewhat like the spread of the railroad to the Western United States. Our product, the adilas system, brings with it tons of jobs and opportunities. That is fun! - So, if our product and system creates jobs and opportunities, how can we help that part of the system grow? - We could start recruiting people who want to help and service those positions. Maybe colleges, tech schools, business schools, consulting services, insurance people, sales, accountants, data entry people, designers, developers, trainers, etc. Basically start building small communities. - Most of the growth comes back to training and education. - Training and education cost money. As a side note… The cost could be flipped depending on where the need is. If a business pays for a person to be trained they gain an employee. If a person pays to be trained you gain a student who can then do something. Interesting twist. - How do you keep your guys and gals (sheep) in the fold? Often it is through training, education, set standards, and then some form of return and report type system. - Sometimes growth and pain are parallels. - Part of the model may be pushed towards marketing and training as well as recruiting and retention. You’ve got to keep things somewhat together. - Don’t promote them out of their abilities. As a fun story, this guy was saying that they had two guys on the night crew that were doing awesome. They promoted them to a different position and things fell apart. The company was about to fire them it got so bad. Right before they fired the guys, they decided to switch them back to the night crew. Both guys flourished. Basically the point was… don’t promote them out of their abilities. - The adilas model may end up looking like this… with independents, shops, hubs, 3rd parties, etc. o 3rd party with added features & products o Sketch of how things connect – model (Adilas, 3rd party, clients, independents, & the shop). |
|
|
AU 3915 |
|
Daily Tasks | 7/23/2015 |
• On a GoToMeeting session with a developer. We were wiring up the auto populate expense/receipt to balance sheet project and functionality. • Recording notes from loose pages into my notebook. • I also had a couple of developers give me call to chat. • On the phone with a new intern and a developer. • Went in to Logan to work. Spent some time signing off on code for a multi corp sales report. • I spent most of the day working on the affiliate proposal. • Both my sister and the project manager helped me do some planning. Both were helping me to protect myself from myself – over promising and/or working for dirt cheap. He and I worked at the board and my sister took notes on the computer. • After that, I sat down a wrote a three-page letter and proposal to a client. The document had a one-page narrative, one-page project details for Phase 1 of the affiliate program, and a final page that highlighted phase 2 and 3 of the project. Once I got done with the page, I sent them off via email. Long day today. 30 miles. |
|
|
AU 3934 |
|
Daily Ideas | 7/23/2015 |
-Thought from a developer… What if we flipped the model and charged for education. Basically, allow different parties to certify to different levels. We could than help people who wanted to be certified become so. -Turn education into the business of education. -We have a lot to offer… including business opportunities and potential. |
|
|
AU 3916 |
|
Daily Tasks | 7/24/2015 |
• On the phone with a new intern for about an hour. We did a GoToMeeting session and set him up his own little world. I showed him around and did some training on sub dates and time for tracking billable hours. We did an invoice together and just chatted. Good meeting. • Tech support call with a rep. We were talking about duplicate entries in the system. • Recording notes in my notebook. • Went in to Logan to work. Spent quite a bit of time with a developer. We ran through a number of scenarios and tracked projects all the way through the financials. It was fun to run the numbers on the scenarios. 30 miles. • Recording notes in my notebook from a meeting with a developer and his friend from a couple of days ago (7/22/15). More ideas about the platform or railroad analogy and pre-built model. Lots of fun ideas about education as well. • Talking to an intern about setting up cookie cutter pieces and products. We talked about industry specific setups and how things like that could fund the whole process. • Signed off on code and pushed up a multi corp sales page. This was an intern’s custom page and project. We expanded the day limit from a week at a time to a month at a time. Posted file on all servers. • Signing off on code for elements of time, billing for time, and the GPS and RFID tag subs of time. Signing off on an intern’s code. • Recording more notes and catching up on my notebook. • Signing off on code and tightening up the update cart logic for calculating time and other minor validation pieces. |
|
|
AU 3935 |
|
Daily Ideas | 7/24/2015 |
-On the main adilas eCommerce site we still need to add options for shipping and PayPal. We also need to check code for additional contacts, customer/invoice tie-in, and in-line discounts for eCommerce. -Add value through education. -On the eCommerce pricing page… maybe modify the pricing. |
|
|
AU 3917 |
|
Daily Tasks | 7/25/2015 |
• Working with my brother to wire up two different sites. They are a basic sales page for vehicles, trailers, RV’s, and motorsports. Awesome graphics and very loose flow. The other site was the one my brother did for his practicum and internship back in February and March of this year. It is a training website for adilas university. I got really excited about the graphics and options that it has. We spent quite a bit of time going over the photo gallery which has graphics of 3D world building, the adilas interactive map, core business functions, main system players, etc. Lots of fun. Here is the current URL or link to photo gallery page: http://www.adilasuniversity.biz/training/photo_gallery.html • Recording notes about my session with my brother and other light brainstorming on how to get the word out. • Signing off on GPS and RFID tag tracking code done by an intern. • Working on the advanced sub time search and search results page. |
|
|
AU 3936 |
|
Daily Ideas | 7/25/2015 |
-Tying into the recent railroad analogy… what about a book or article with a title of… “Creating a modern day railroad town.” – just an idea. -My brother would like to develop some basic standard starting packages – per industry or as a preset starting template. This would help flip the settings and permissions around on a more global and standardized model. -My brother also wants to do specific training videos for specific clients or for a specific industry. That would help them get up to speed quicker. |
|
|
AU 3918 |
|
Daily Tasks | 7/27/2015 |
• Phone call and GoToMeeting session between Steve, a developer, & I going over the sub inventory and cost controls (packaging) project. Steve was on the call listening but mostly it was the developer and I going over known pieces, flow, and direction. • After the phone call and GoToMeeting session, I spent a little bit of time going over project details and pushing content up to the servers. I even uploaded one of the videos from back on 6/15/15 that had the intro to the project. • Went in to Logan to work with my guys. I worked on cleaning out my email inbox and passing along possible projects to Dave our Project Manager. • I met with another intern and we chatted about his mini project. I did a number of new icon graphics for the icon menu project. The rest of the day was spent on other phone calls and emails. 30 miles. |
|
|
AU 3919 |
|
Daily Tasks | 7/28/2015 |
• Went in to Logan to do a sales call with a consultant. We met with a principal from a local charter school. We talked needs and pains and how adilas could help. Lots of back and forth. The principal has needs for expense tracking, a check request process, and inventory tracking. The other thing that they would like is a way to handle and monitor budgets and forecasting. That seems to be a growing need for systems. After the meeting I helped the consultant grab some office furniture and we hauled it over to the office. 30 miles. • Went in to the office. We had stand-up meeting and told everybody how the sales call went. • I spent a couple of hours with different parties either looking at what they are working on or helping to get things going. • A developer showed me some GPS stuff for a phone app. • Some other interns and I got on a GoToMeeting session and we went over some projects and possibilities. They are going to make some calls out to clients. • I then spent quite a bit of time with a developer working on a custom page process for a clinic and getting new patient into the system. After hours I did some office clean-up and restocking of supplies. |
|
|
AU 3937 |
|
Daily Ideas | 7/28/2015 | -We are seeing more and more need for budgeting and forecasting models and features. I think that could be a great sub of time. This may also tie into watchers and feeders. The budget settings need to be able to hold projections, forecasts, and goals. We then need to go through and track real usage and application of those pieces. People want to be able to see and tell where they are at as compared to the projects, forecasts, and budgets. | |
|
Shop 3815 |
|
Virtual Post-It Note | 7/29/2015 |
See scan for visual. This was a quick drawing of some of the developers walking a high-wire. The net below the developers has a number of key posts to help support the net to catch and support the developers walking the high-wire. Some of the posts are things like: handbooks, maintenance, project management, budgeting, billing, communications, payouts, sign-offs, admin, requirements, recording project details, contracts, etc. The concept was, if you are doing something that is high risk, you need to have a number of safety pieces in place to help catch you as you fall, fail, and/or play the game. Good stuff. |
|
|
AU 3920 |
|
Daily Tasks | 7/29/2015 |
• Emails, tech support, and recording notes in my notebook. • More emails and tech support stuff. • I wrote a long email to a rep about the railroad analogy of cause and effect needs and business opportunities. It is crazy how systems seem to keep gong and building and expanding. • A developer came over to my house to work. We had a great talk about the adilas shop and what we need to do make it work. Lots of drawing and sketches. See other notes for ideas and details. • Went in to Logan. Most of the day was spent doing project management in one form or another. • Dave, an intern and I met in a side room and roughed out 5 projects. Dave and I worked together at the whiteboard and the intern did some note taking. Great little session. • I helped a developer with his custom wire job project and we made some progress. • The last hour and a half was spent between a developer, Dave, and I talking about our project management process and how we could help watch each other’s back. See the additional notes for more info. The focus was on safety nets, systems, and key pieces. 30 miles. |
|
|
AU 3938 |
|
Daily Ideas | 7/29/2015 |
-Systems tend to cascade, grow, and expand… -It is really hard to fit a real system into a box or a static environment. Systems are dynamic and have cause and effect relationships. -Systems need room to expand, respond, and interact. -Certain actions and reactions keep expanding like ripples. -Systems don’t really fit in to boxes or static environments. An analogy between people on a tightrope and a safety net to help keep them safe. - Handbook or guidelines - Maintenance - Project management - Budgeting - Billing - Payout - Sign off & approval - Admin & management - Expectations - Requirements - Documentation & details - Goals & vision - Communication -Some of the key stakes and posts are: A handbook or guidelines, maintenance, project management, budgeting, billing & collections, payout & payroll, sign-off & approval, admin & management, expectations, requirements, documentation & details, goals & vision, & communication. -There are more key points but the above list and graphic are enough to get things started. -We need to allow our shop members to do internal cross billing if they need help. We may need to cap this but imagine that a developer needs help with a project. Whoever helps (if it is more than a quick help out or direction) could figure out an agreeable amount to help offset time. Personal time management of sorts. -Maybe have the two parties pass it by admin to get approval and changes made to payouts and payroll. Help document the story. Possibly 3rd Party Solutions that are needed: - Rentals - Forums - Gift cards - eCommerce & websites - Blogs - Affiliate programs - Appointments & scheduling - Some of these could be some great ideas for the adilas shop or some other entity to build and then sale to adilas clients as extra add-ons. |
|
|
AU 3921 |
|
Daily Tasks | 7/30/2015 |
• Emails and tech support. • Recording notes from yesterday’s meetings. The words that stuck out from yesterday are systems, maintenance, processes, and communication. • Working on the CMC adjunct contract form. Changing some rates and working on the contract. Posted file online. • Went in to Logan to work with my guys. • I helped a developer on a project that captures a canvas drawing and makes a digital signature of sorts. Dave, an intern, and I planned out 5-6 new projects. It really helps to have someone recording notes as it happens. • I jumped back in and worked on some code to help with signing off on the GPS/RFID tag tracking as a sub of time. 30 miles. |
|
|
AU 3939 |
|
Daily Ideas | 7/30/2015 |
-Talking with a guy that wants to do budgeting and forecasting on projects on a weekly basis. Maybe even smaller internals. Quick and easy checks to go along with his goals and budgets. This would be a great little sub of time or an add-on to go with elements of time. -The two key persons in his organization are his financial person and his HR (human resource management) person. Both do a great job and help take stress off of other management and other team members. -He also said that he got the same accountant as his banker had. That increased the banker’s confidence because they used the same one. Scott also has his books professionally audited twice a year to help keep his people on track. The audits help people get things done and done quickly. He also said that he often asks his banker for advice and the bank has become somewhat of a free financial advisor of sorts. Anyway, some cool ideas – good conversation. |
|
|
|
Adi 1200 |
|
Real-Time Budgeting & Forecasting - Sub of Elements of Time | 7/31/2015 |
People are wanting more and more options to budget and/or forecast per project, per week, per month, per year, etc. We have even had people asking for budgeting options per person, per day, etc. Basically, the older long term budgets are starting to see the advantages of allowing smaller increments and more measureable outcomes. Most traditional budgets have been on a monthly, quarterly, semi-annual, or annual basis. What we are seeing is people want smaller, quicker, and more real-time budgeting options. This may require options for watchers, feeders, and just in time calculations. In order to do that, you have to have the data in the system. Our proposal would be a sub of elements of time. This would allow you to show budgeted or estimated values (hours, weeks, dollars, quantities, etc.). Then as things get budgeted, estimated, or expected, we could help by tracking the actual or real time values that match-up with the budgeted values. We could use budget frequencies, budget types, and populate things with real-time data. Anyways, some cool ideas are coming down the pipeline. The key is real-time numbers, values, math, and comparisons. Where am I at and how am I doing? Even on a sub level or smaller goal based level. Good stuff! |
|
|
|
Adi 1201 |
|
Web-Based Forums & Blogs - Options for Customer & Client Facing Webpages | 7/31/2015 |
Lots of modern-day websites have either forums and/or blogs of some sort. What if we made those easy to use and add to your website using backend adilas tools. We now have a number of developers who have worked with popular forum and blogging tools that could make that happen. Both forums and blogs sound cool and easy but sometimes have a lot of stuff going on in the background. Anyways, this project would be to get new tools and features to allow for direct connection to forums and blogs right from inside a site that is hooked up to adilas. The forums and blogs could be news events, media, video, podcasts, updates, sales, promotion stuff, calendar events, etc. It could also be user groups, friends, support groups, requests, social media, and even a mini Facebook or Twitter type apps. All kinds of cool stuff. |
|
|
AU 3922 |
|
Daily Tasks | 7/31/2015 |
• Emails, recording notes, and adding a couple more community funded projects. I added a new one for budgets and forecasts and another one for blogs and forums. • Steve called and we chatted on the phone for about an hour. Lots of updates on new projects, options, and vision for the future. • Scanning in expense/receipts and invoices from developers. |
|
|
AU 3940 |
|
Daily Ideas | 7/31/2015 |
-We need to create a PDF flyer that David could email around with his monthly bills. -We could also send the PDF flyers around to the reps and consultants. That may help them know about some of the new changes and what options are available. As a side note, we could also add a custom code commission for reps that help us sale custom code jobs. |
|