Types of Service Engagements

Few of our customers have the exact same needs; we often craft a custom solution for each customer, and we will be happy to do the same for you. However, to give you a sense of how this works, our services usually fall into one of the following groups:

• End-user support for specific applications or specific application features

  You don't need Microsoft Office; you need Bob's Deluxe Vegimaster for Windows. Or maybe you need Clippy to run in Microsoft Office (we don't support that). Either way, we are happy to help (well, okay, maybe not with Clippy...). Read about our Application Support Services for more details.

• ISV Porting of Windows applications to Linux or Mac OS X

You're Bob (publisher of Bob's Deluxe Vegimaster), and you want to broaden your market. Rather than spend a million bucks and 3 years on a truly native Unix port, you're wondering if we can get you a fast and cost effective path to the Linux and Mac market. We believe Wine and CrossOver are extremely effective tools for ISVs. Read about our porting services to learn more.

How to Start

We generally find it is most effective to enable you, our customer, to try your application within CrossOver. Often, your application will work well enough that you can survey it carefully and come to us with a specific list of issues. However, other times, your application will not start at all, or is missing a crucial feature. In those cases, we often start with an initial Kick The Tires service engagement to help us assess your application.

For almost all service engagements, we like to start with an introductory phone conversation, in which we arrange to have both a sales representative and a technical person from CodeWeavers available. Please write an email to sales@codeweavers.com or call 651-523-9300 to arrange an initial consultation.

The Catch

While we are thrilled to help our customers as much as we can, the truth is that there are times when Wine is not a practical solution. The work that we do on Wine is time consuming and hard, which unfortunately also makes it fairly expensive. For example, we have a rough working metric that each bug in Wine costs us between $1,000 and $1,500 to fix. Thus, the example of a person who would happily give us $39.95 if we could just fix these two bugs doesn't make sense, economically.