Frequently Asked Questions

Q: The preliminary pricing for the Systems sounds a little too good to be true. Why are you guys almost giving this software away? What's the catch? 

Q: I'm comfortable on a computer, but I'm not a geek. Am I getting in over my head?

Q: I don't know anything about programming. How can I use the toolkits?

Q: All this testing and tweaking sounds ominous. What can I realistically expect?

Q: Why don't I just wait until everything is finished and perfected?

Q: The pricing for the System sounds a little too good to be true. Why are you guys almost giving this software away? What's the catch? 

A: No catch. The pricing is meant to be attractive and it's a limited time offer. Once we get the wrinkles worked out this deal will go away and more rational pricing will take it's place. You can also be sure the unlimited support option will disappear faster than you can say "Come on down and get some of this before it's all gone"    

Q: I'm comfortable on a computer, but I'm not a geek. Am I getting in over my head.

A: We don't need you to provide any computer expertise. We have plenty of that. Just the process of getting you running will help us determine what is needed in the way of training videos and tools.

Q: I don't know anything about programming. How can I use the toolkits.

A: You have several options. First, you may never need to crack open the toolkits. We have plenty of flexibility built in, so you can use the system as is. Or you can find one of those young kids who was born with a silver mouse in their hand (might even be one of your kids).

Q: All this testing and tweaking sounds ominous. What can I realistically expect

A: Creating software involves three steps. First, we write a bunch of code and get a program that appears to work. At least each step along the way we hammer the code until everything seems to work.

In the process of writing code for new parts of the program, some of the older code ends up under water. Of course it's possible for the  programmer go back to the beginning and test everything all over again, but our experience with customizing convinces us that this is impractical. We've found the best method is to have the user test the earliest possible version. Even if it doesn't work flawlessly. Changes are much easier at that point. It makes no sense for us to polish and refine code that might end up on the cutting room floor.   

For this process, you don't need any special skills. Just a little patience and tolerance for that new bug that appears after some changes. It's no big deal. We fix the bug and email you the corrected program. Life goes on. Keep in mind these bugs appear in all software, but it isn't every day you have the opportunity to have them fixed almost instantly.

Q: Why don't I just wait until everything is finished and perfected.

A: Like one of comedian Billy Crystal's characters says, "Life is harsh. May not be for everyone." This Charter Customer Deal may not be for everyone either. The reality is that software is complex. It's never finished, and every time you add new bells and whistles and features you introduce new code. New code = new bugs. It's just part of the process. Like trying to type a 20 page letter with no typos. You find bugs, we fix them and we all move on.

Waiting may involve less testing and fiddling on your part, but once the Charter Customer Deal is gone, you will have to make whatever changes you want to the program yourself, or pay us to do it. And don't forget, that unlimited support deal will disappear soon.

He who hesitates will pay a lot more money.

Back to top