-
Website
http://www.instigatorblog.com/ -
Original page
http://www.instigatorblog.com/how-to-price-your-software-product/2008/11/11/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
AndyBeard
27 comments · 4 points
-
paulmcenany
8 comments · 1 points
-
webomatica
4 comments · 5 points
-
Michael Lankton
8 comments · 1 points
-
Jim "Genuine" Turner
15 comments · 2 points
-
-
Popular Threads
-
Why are Customer Development and Lean Startup Principles So Popular?
2 days ago · 4 comments
-
Where’s the WOW! in Retail Stores?
1 week ago · 17 comments
-
Firing People Quickly is the Best Way
6 days ago · 10 comments
-
Don’t Try to Get Funding Before You Know How It’s Done
1 week ago · 8 comments
-
What are the Social Media Roadblocks for Companies?
5 days ago · 4 comments
-
Why are Customer Development and Lean Startup Principles So Popular?
Really interesting posting, thanks! From the other side of the fence, when buying software some of the things that are really important:
- attitude of the vendor - do they know the RFP
- how much money with this software save / generate?
- is it cheaper to buy or to build
- how can the charges be capitalised and over what time period
- how flexible is the vendor
- will they implement the additional functionality requested?
A lot of these points can also help with pricing and sales arguments. I think the big one is trying to understand and put a figure on the value your product can bring to a company because in theory that's logically their purchase limit. It's a hard one to calculate though.
One trap to avoid is accepting to build customisations / adaptions and not pricing them correctly. I've worked with vendors that make a loss on their customisations, some of which the customer has just requested on a whim. It's not a good position for a start-up to be in.
Some big companies like to spread the charges over different periods as it's good for their financial statements. So it may be that they take a one-off purchasing model, but spread the payments.
Currently we do OK on the larger projects but were at a stage in our development where big projects come in now and again and make us a descent profit but we still have to rely on very small projects for the bulk of our work.
We often find on these smaller projects when speaking to clients that they have had quotes from project websites on the Internet or have approached outsourcing partners directly. This has had a big impact meaning on a lot of projects we just can't compete on price. Some of these clients that have gone for cheap outsourcing options though have got back in touch again after having their hands burnt.
I guess the key point is to make sure you sell your costs. You have to justify them to the client and help make them make the right decision.
Most people these days are putting out quality software for free. They needed it, designed it themselves, and released it to the public.
In fact, I have been using Adobe Photoshop for 10 years, and currently my employer provides me with a license, but if their asking price had to come out of my pocket, I would not pay it, and would accept my entrance barrier and peruse a different trade. But I would pay $50 dollars for it.
For some reason, non material tools do not win my monetary vote.
Hudson
Pricing software is a very difficult art and in cases like microsoft can cost millions, there is lots of research on competitors to do then beat there prices and CUSTOMER SERVICES.
Daivd
from
Product Sourcing
By the way, seems like we have a little CSS issue here: http://jobs.standoutjobs.com/people
We increased the price of our product from $27 to $47 ant we got more sales.
Sometimes if you want to give to much for a small price people may think it's a scam.
First, I plot my client's position on the chart and then add those of chief competitors (most useful to include price points higher and lower) according to what they do/don't include in their offering. It's a good way of visually evaluating whether a price is competitive and also for identifying "premium" features competitors charge extra for.