Compiler technology => Doing business
| ||
Compiler technology: Doing business | ||
Typical scenario |
Since our product is highly dependent on the characteristics of the target (both the
architecture and the compiler), the first step is usually an exchange of technical
information.
After some discussion between you and us (we much prefer meeting in person,
but it can also be done by phone/email/web)
we submit a proposal specifying the features to be delivered, the schedule, and the licensing terms.
| |
Business model |
We actually have two business models. First,
a master license fee/sublicense fee arrangement
(there are no runtime fees). The master license fee is usually distributed
over several milestones: typically, some portion at contract signing, some
portion at initial delivery, and the major portion after passing of a mutually agreed-on
acceptance test. The master license fee covers unlimited internal use.
A sublicense fee is due for every copy (or derivative product) given to an end-user customer.
However,
we try be be flexible and fit in with the customer's usual way of doing things.
(For example, it could be structured so that the sublicense fee is proportionate to the
compiler price, or even zero.)
Our other option is a fixed quarterly or annual payment that covers both sublicensing and maintenance.
We offer both source and object licensing.
| |
Cost | Master license fees range widely, depending on the number and complexity of features delivered, the amount of customization, sublicense fee arrangment, source license vs. object license and other factors. A source license costs more than the equivalent object license. |