>But the math never adds up to only $12,000, does it?

It could theoretically be less....from a pure software procurement
standpoint, not necessarily a development cost standpoint.

>If you want to deploy the Flex application in a load balanced environment,
>then it will require at least $24,000. If you want a separate
>development/QA server (you're using Flex for enterprise development with a
>team, right? You match the Flex project profile right?), then you'll be
>looking at least $36,000.
>

That depends on your setup. In our environment, yes we're clustered across 2
servers, but each box only has 1 CPU, so I only need one license. (As I've
mentioned before, you can split the CPU licenses across multiple boxes.) So
I'm still technically at $12K (and that's before our discounts and
negotiations kick in).

>Oh, let's not forget procuring a Gold support agreement, I imagine that
>$20,000 annually won't be unexpected, and by the way, all the prices
>discussed don't include subscription pricing, which is typically around 40%
>more. We want to protect our investment for the future yes? So for those 3
>licenses above, with subscription and Gold Support? $70,000
>

Well, the Gold support agreement is your call (not really sure how necessary
it is, quite frankly, seeing as there's a pretty responsive development
community for Flex even now, let alone what will arise over the coming
months). But I'm assuming by "subscription pricing" you mean annual
maintenance contracts, which are indeed standard nowadays. It clearly states
on the Flex pricing page:

"Flex presentation server pricing starts at $12,000 for two CPUs and
includes annual maintenance."

http://www.macromedia.com/software/flex/buy/

So your 40% goes out the window too.

>Also if I'm not mistaken, you have to provide an application server for it
>to run on. And by the way ColdFusion MX Standard does not count. ColdFusion
>Enterprise does, which is a cost of $5,999 per server (2 CPU License). I
>believe JRun may be the least expensive application server option (aside
>from freeware) and that's $899 or so.
>

*Technically,* you are mistaken. You don't need ColdFusion to run Flex, and
you can install this on Tomcat if you'd like. However, I say technically
because to do any amount of heavy lifting regarding database access, etc.,
your life is probably made much easier by having a middle tier such as
ColdFusion MX to handle it.

>Let's assume you don't have an application server and need to provide one,
>with of course some kind of software protection, we're up to $73,747 or so.
>

With the modifications above, we're nowhere near this number.

>This is a significant amount of investment to improve your presentation
>layer, and for larger shops, we can easily push into 100s of thousands of
>dollars.
>

I'm not in any way trying to suggest that Flex isn't a significant financial
investment (let's be honest, it is). However, I think you need to do a more
thorough cost analysis for your own system before writing it off as well.
Even if the total cost of procuring the software was $60K, if you have a
project where you know the potential ROI is above that, then all of a sudden
$60K isn't so bad.

>Let's not forget the unspoken elements. MXML is a distinct and completely
>new development language, with it's own constructs, syntax and
>idiosyncrasies that must be learned and mastered. In addition to the above
>costs, you have to consider training, and experimental efforts, people
>don't learn without doing, and typically don't do for free. I don't have a
>price tag for that one, that depends on your team.
>

Agreed. But this isn't in the realm of software procurement as much as it is
development costs.

>My current opinion is be very aware of potential hidden costs when it comes
>to Flex, not only do you have to be careful on advocating investing money
>in the technology, you also should be careful investing your time learning
>it, there are simply too many technologies to spend your time to improve
>your products and services in that don't require such a high financial
>investment from your clients or shareholders.
>

This is a valid statement, and it's a decision that is entirely based on
your team/environment. When you get in to development costs vs. software
procurement costs, there's a big difference. But many people seem to be
focusing on the software procurement costs as opposed to the development
costs when they write the product off before even playing around with it.

>I will be very curious to see hard numbers with success stories on ROI for
>this product.

Me too.

Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to