Merge OEM | FAQs

Q.	How can Merge OEM generate more revenue for my company?
Q.	Would it not cause confusion if Merge OEM sold our technologies while we are doing so as well?
Q.	Why should my company consider licensing medical imaging technologies and applications from Merge OEM?
Q.	But why should our company use Merge OEM if it already has a software R&D department?
Q.	But what if our company’s software R and D department has a “Not Invented Here” mentality?
Q.	But how can licensing technology from Merge OEM be cheaper than building it ourselves?
Q.	But if we licensed Merge OEM technology, how would we be able to differentiate our company’s offerings in the market?
Q.	But if we licensed Merge OEM technology, wouldn’t we have to pay a royalty which would increase our product’s cost-of-goods-sold?
Q.	But if we licensed Merge OEM technology, wouldn’t we be creating a technology dependency on a third party that may not be in our company’s long-term interests?

Q.	How can Merge OEM generate more revenue for my company?
A.	Merge OEM can generate additional revenue for you in two ways: By selling your existing medical imaging technologies and applications to our global distribution channel. By licensing you additional medical imaging technologies and applications for your company to sell through your own sales force.

Q.	Would it not cause confusion if Merge OEM sold our technologies while we are doing so as well?
A.	Not necessarily. We can augment your sales efforts by selling into territories you currently sell into or by concentrating on countries you currently don’t do business in. You decide.

Q.	Why should my company consider licensing medical imaging technologies and applications from Merge OEM?
A.	To sell more products to your customers and increase revenues.

Q.	But why should our company use Merge OEM if it already has a software R&D department?
A.	Each of our customers have different reasons for using our technology. Some of the common responses that we have previously encountered include: Your company may not have the time to wait for your engineers to build the technology from scratch because you need to: accelerate your time-to-market and earn revenue now not lose your customers to a competitor who is already introducing the particular technology feature or new application leap-frog over your competition Your engineers may be busy working on another project. Your engineers may not have sufficient expertise in a specific area of technology you need. It may be cheaper to “buy” versus “build”. You might wish to keep your precious capital on your balance sheet or deploy it for marketing rather than technology development purposes. It may be safer for company to not take the risk of building a technology that may fail or have serious cost and deadline overruns.

Q.	But what if our company’s software R and D department has a “Not Invented Here” mentality?
A.	This is a real challenge for all good software R&D departments including even our own. At the end of the day though, every company needs to make an objective, rational “Build vs. Buy” decision. In fact, some of our partners prefer dealing with our engineers rather than their own, for that very reason.

Q.	But how can licensing technology from Merge OEM be cheaper than building it ourselves?
A.	There is only one way to find out – speak to us and see. We think you’ll be pleasantly surprised.

Q.	But if we licensed Merge OEM technology, how would we be able to differentiate our company’s offerings in the market?
A.	All our customers have the need for product-specific differentiators. They either hire Merge OEM engineers to confidentially develop them or they use their own engineers to customize a licensed technology rather than “reinvent an existing wheel” from scratch. We also actively listen to our customer’s input when we design roadmaps so our customers get the full benefit of both their own needs, as well as non-proprietary input from other business partners.

Q.	But if we licensed Merge OEM technology, wouldn’t we have to pay a royalty which would increase our product’s cost-of-goods-sold?
A.	Perhaps but not necessarily. It depends on the type of deal we structure. Some of our customers prefer to pay a low royalty every time they sell a product. Others prefer to negotiate a volume purchase at a lower cost. Still others prefer to negotiate a one-time payment so as to eliminate the costs-of-goods issue entirely. Our customers are genuinely surprised to learn how flexible Merge OEM is with its deal structures.

Q.	But if we licensed Merge OEM technology, wouldn’t we be creating a technology dependency on a third party that may not be in our company’s long-term interests?
A.	Once again, not necessarily. It really depends on the type of deal we structure. Some of our customers are happy to have Merge OEM contractually obligated to provide ongoing release upgrades and updates as well as ongoing customization services. Other customers prefer to bring the technology in-house. Again, our customers are genuinely surprised to learn how flexible Merge OEM is with its deal structures including the willingness to license source code and provide technology-transfer education services. We are willing to help our customers to eventually write us out!

FAQ's

Q.

How can Merge OEM generate more revenue for my company?

Q.

Would it not cause confusion if Merge OEM sold our technologies while we are doing so as well?

Q.

Why should my company consider licensing medical imaging technologies and applications from Merge OEM?

Q.

But why should our company use Merge OEM if it already has a software R&D department?

Q.

But what if our company’s software R and D department has a “Not Invented Here” mentality?

Q.

But how can licensing technology from Merge OEM be cheaper than building it ourselves?

Q.

But if we licensed Merge OEM technology, how would we be able to differentiate our company’s offerings in the market?

Q.

But if we licensed Merge OEM technology, wouldn’t we have to pay a royalty which would increase our product’s cost-of-goods-sold?

Q.

But if we licensed Merge OEM technology, wouldn’t we be creating a technology dependency on a third party that may not be in our company’s long-term interests?

A.