The Enterprise Mobility Forum

Viewing post 1 to 15 (16 total posts)

1 2 →

MEAP deployment: Contract structure/pricing? (16 posts)

← Group Discussion Discussion Directory

Josiah Filler said 2 years, 6 months ago:

Hi everyone,

I’m trying to gather some benchmark data points for the typical contract structure and costing of an enterprise-wide MEAP deployment with someone like Sybase, Syclo, etc. Specifically what kind of terms should I expect (high level) when engaging for the first time with these vendors?

Has anyone gone through this process that can share their experience?

Thanks!

#
MobileAdmin said 2 years, 3 months ago:

Almost all of them are per user per month type licensing. Very expensive for a large enterprise that wants to deploy Apps at a large scale.

#
Dr. Ch Subrahmanyam said 2 years, 2 months ago:

A ball park number is better than a policy statement on pricing. Especially, when some one is at the very initial stage.

#
Philippe Winthrop said 2 years, 1 month ago:

Good discussion here as well:

http://theemf.org/groups/enterprise-mobility-management/forum/topic/meap-vendor-comparison/

#
kumar said 2 years, 1 month ago:

#licensing, #support sla for prof services – devel,design,review,deploy, #scale and perf test data, #capacity planning and sizing guidelines,#solution management,#device support roadmap, #Gaps in out of the box backend adapters, #peer mdm friendliness…the list is huge..#, based on my experience I can tell this exercise pre project and @discovery differentiates the success of an enterprise mobility strategy. If we write it off thinking that all I need is a simple packaged app which has to realize a 2 level depth workflow only…even the roadmap gets a hit.

#
jwargo said 2 years ago:

Pyxis prices on a per server CPU, not a per user per month. Great entry point cost, scale up as needed based upon number of users x number of apps x number of transactions per day/hour.

Spring Wireless is typically a SAS solution, so as I understand it there’s a monthly platform fee, but not a per user fee.

#
Philippe Winthrop said 2 years ago:

Great info John. Do you think this creates a barrier to entry for users who could potentially be caught with “sticker shock” on the upfront costs?

#
jwargo said 2 years ago:

I know I’m going to get myself in trouble for saying this, but in general you’re going to have to expect a bit of sticker shock when you first look at MEAP. What most people miss is that in general, and Gartner reinforced this in their 2009 MEAP Magic Quadrant, MEAP is usually only cost effective when you’re doing three or more apps or three or more mobile device platforms. In my personal experience, since each mobile device beyond the first usually only adds 10% to 20% to the cost, an organization may not see the benefits until the 2nd or third app.
What happens is that companies compare the cost of MEAP against native development and if you’re only doing one platform (perhaps two) today, MEAP seems expensive. As soon as you start doing versions 1.1, 1.2 and so on then add a second or third app, MEAP becomes a much more interesting option. You therefore have to have the correct expectations, compare apples to apples as it were, to look at MEAP vs. native.

#
Philippe Winthrop said 1 year, 12 months ago:

So John – when you say Gartner “reinforced this,” are you saying they perpetuated the confusion?
An interesting side note is that I am seeing a lot more companies thinking about far more than just one or two apps….it’s turning into scores of apps. (amazing btw to see the change in two short years) Do you see that as well?

#
jwargo said 1 year, 12 months ago:

Perpetuates the confusion? No, they clearly address the confusion when they point out that the benefits of MEAP appear when you will be building three or more mobile applications or running on three or more mobile device platforms. To quote Gartner:

“MEAP vendors offering approaches that support mobile OS diversity have significant advantages over application suite or mobile OS platforms/tools in three situations: (1) when there are three or more applications; (2) when there are three or more targeted OSs or runtime platforms; and (3) when projects involve the integration of three or more back-end systems. Gartner further rates these vendors in “Critical Capabilities for Mobile Enterprise Application Platforms.”"

When you ignore that and try to use MEAP for only one app or only one mobile application platform, you’ll have issues with the price.

#
Kaare B Martinussen said 1 year, 12 months ago:

We see a clear trend that companies are looking for several applications, and at the same time are looking at ” how ” they can use their Smartphone’s for several new services for they workforce.
At the same time, we see that the companies that are making MEAP SW, have an unrealistic business model for solutions that only covers 1 – 4 Applications. We have also looked at several vendors, however the solutions that is out there today don’t support solutions for the SME market.
So pricing and license models / business models are the main issue for projects we are currently working on.

#
Dusan Babich said 1 year, 12 months ago:

Well we’re not a MEAP, but we do share some elements of them…I guess we’re more MaaS (http://www.devicemagic.com).

Our pricing is $10-$15/device/month. We’re a mobile data collection/forms building solution and the amount of forms/submissions is unlimited at this monthly fee.

Surely that still represents good value, even into the 000′s of devices?

#
John Magrino said 1 year, 11 months ago:

Great discussion here. Enterprise Mobility is here. Any company talking about one or two device specific or OS specific applications is a little late to the game. Pricing on a per user per month is a good way to go and it can be done in “bands” if the exact user base is not initially known. It looks to me that some of the posts may be confusing number of users with number of applications. A good, quality enterprise mobility platform will enable an enterprise to develop and create it’s own applications and these applications will be available to users based on user profiles. the same user may be accessing multiple applications. the enterprise should not be charged for each access. If the MEAP vendor is also a participant in application development, then there will be “one-time” fees associated with that engagement, however for the ongoing functionality of the plaform itself, number of users x rate is easy to calculate and track.

#
Philippe Winthrop said 1 year, 11 months ago:

John – so how does the MEAP co-exist with off the shelf mobile enterprise apps? Look at what Sybase/SAP is doing with the SUP platform. It makes me think the conversation needs to gravitate towards mobile application management.

#
jwargo said 1 year, 11 months ago:

MEAP apps are native apps, there’s really no way to tell the difference. So, they’d coexist just fine. No matter what you do, custom, MEAP or a combination of both, you’re still going to have to implement something to help you manage them.

#