As a request comes in for custom development we explain our shared library philosophy and ask if you would like us to work on that basis or on a strictly custom "source code" basis.

If it's to be strictly "source code" then the process is simple, we start with a clean sheet of paper, and also of course, with years of experience and a set of standard "C++" and "VB"libraries from the manufacturer(s). Since we don't want to re-invent the wheel if future a project using similar code arises, we may ask "source code" clients if they would sell rights for us to use all or part of the code in a given project.

If the customer chooses to use the shared library alternative, then quite a different process is used. First we evaluate the requirement based on our existing code to see what can be used to speed up development time. Second we evaluate whether the customers request can be improved upon or made more useful in future projects. And last we determine an estimated price to produce what the customer asks for.

We may determine that a project will take for example 20 hours to deliver what a customer wants and that is the amount charged to the customer. But we may choose to add another 4-5 hours to provide extended functionality. This additional programming time might help the current customer and provide us with a more useful tool to add to its' library for future application development.

When this happens both the reseller wins, the customer wins and we win. The customer wins by getting a better or more flexible product at a fixed price and we improve our library of code for which it may charge module fees in the future.