There were 5 people on the call when I got in. Each of them asked some questions and then eventually bailed out to work on their own projects. Here are some things that I pulled out of there discussions.

- What is the real purpose there? Thinking on a per page level. If that is known, that can really set the tone for the project - aka a focus. Basically, being more clear on the objectives and then sticking to it. That really helps. Idea was presented by both Russell and Danny.

- Some marketing ideas from Danny about free software and then charge for other pieces and/or services. He was talking about a product out there for music lovers and how the sound mixing software was free but they had to pay for specific hardware. Lots of options.

- Eric was talking about being able to build business processes. I would love to take that to the next level. Think how cool it would be if we could setup an area where people could build a business process, name it, setup defaults, determine layouts, requirements, and flow. Then, once those pieces are set and in place (saved), we then could show and use those real settings. Imagine being able to setup your own data assembly line and then the system helps you keep and maintain those business processes. If you need to alter something, you could go back and just tweak some of the setup pieces. That would be so cool.

- Talking about auto printing from the web and using a queue of sorts and then doing the print jobs based off of a service that monitors that queue.

- Talking about custom code jobs. How are jobs coming in and being completed? We have lots of independents and what is the plan for the adilas shop (dev shop) and the projects being passed through? Along those lines, we need to take care of the house. The house being adilas. Often, some of the independents do the work, they get paid, they move on, but they suck tons of resources from adilas without paying for any of those usages. Time, talent, and money are all resources... we need to make sure we are managing and taking care of those pieces.

- Eric was talking about rough estimates and how he likes to bid a project. If needed, he sets up an estimate and then says he bills by the hour regardless. If things get deeper, he then lets the client know that it will be different then the original estimate. It flips it back on the clients and they get to say yea or nay. It's a way to somewhat protect yourself.