<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Can everyone be a software developer?</title>
	<atom:link href="http://beebole.com/blog/general/can-everyone-be-a-software-developer/feed/" rel="self" type="application/rss+xml" />
	<link>http://beebole.com/blog/general/can-everyone-be-a-software-developer/</link>
	<description>The News about the Easiest and Fastest Timesheet</description>
	<lastBuildDate>Sat, 18 Feb 2012 18:59:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Yves</title>
		<link>http://beebole.com/blog/general/can-everyone-be-a-software-developer/#comment-26</link>
		<dc:creator>Yves</dc:creator>
		<pubDate>Tue, 05 May 2009 09:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://beebole.com/blog/?p=23#comment-26</guid>
		<description>Hi Mo,
Our first ideas were balancing between a price per application strategy and a pay per use strategy.

The problem with the pay per use is that it’s not sexy.

If a future customer lands on your pricing page and has to fill in a form and think about how much timesheets, expenses, ... his company is doing every month, just to have an idea about how much he will have to pay... Well, I guess, it’s already a customer lost. (At least in the SMB industry).

We have also abandoned the price per application because it wasn’t flexible enough.

What we want to achieve is to give the maximum freedom to the customers.
If we decide to package the modules in applications, it means that we have decided for the users which modules are grouped.

Innovation comes from the possibility to rearrange modules in a way that nobody has ever though before.

Of course, we couldn’t go with a price per module. This would suffer the same problem than the pay per use. It’s just not sexy and too complex.
We finally went for a flat price for everything contained in the catalog.

It also makes sense when you compare that strategy with our development strategy, which is more to integrate existing applications and APIs in our platform than developing the applications ourselves.</description>
		<content:encoded><![CDATA[<p>Hi Mo,<br />
Our first ideas were balancing between a price per application strategy and a pay per use strategy.</p>
<p>The problem with the pay per use is that it’s not sexy.</p>
<p>If a future customer lands on your pricing page and has to fill in a form and think about how much timesheets, expenses, &#8230; his company is doing every month, just to have an idea about how much he will have to pay&#8230; Well, I guess, it’s already a customer lost. (At least in the SMB industry).</p>
<p>We have also abandoned the price per application because it wasn’t flexible enough.</p>
<p>What we want to achieve is to give the maximum freedom to the customers.<br />
If we decide to package the modules in applications, it means that we have decided for the users which modules are grouped.</p>
<p>Innovation comes from the possibility to rearrange modules in a way that nobody has ever though before.</p>
<p>Of course, we couldn’t go with a price per module. This would suffer the same problem than the pay per use. It’s just not sexy and too complex.<br />
We finally went for a flat price for everything contained in the catalog.</p>
<p>It also makes sense when you compare that strategy with our development strategy, which is more to integrate existing applications and APIs in our platform than developing the applications ourselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mo</title>
		<link>http://beebole.com/blog/general/can-everyone-be-a-software-developer/#comment-27</link>
		<dc:creator>Mo</dc:creator>
		<pubDate>Mon, 04 May 2009 14:25:49 +0000</pubDate>
		<guid isPermaLink="false">http://beebole.com/blog/?p=23#comment-27</guid>
		<description>If I understand well, you want to allow user to choose from a catalog of applications. Just wondering what would be the pricing strategy.
User pays for all selectable applications?: not fair if application is not used. Will you invoice if a user selects an application? Tracking this might be some kind of nightmare.</description>
		<content:encoded><![CDATA[<p>If I understand well, you want to allow user to choose from a catalog of applications. Just wondering what would be the pricing strategy.<br />
User pays for all selectable applications?: not fair if application is not used. Will you invoice if a user selects an application? Tracking this might be some kind of nightmare.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Celeroo &#124; What users want in their Web Software Development Tools</title>
		<link>http://beebole.com/blog/general/can-everyone-be-a-software-developer/#comment-25</link>
		<dc:creator>Celeroo &#124; What users want in their Web Software Development Tools</dc:creator>
		<pubDate>Mon, 06 Apr 2009 07:27:21 +0000</pubDate>
		<guid isPermaLink="false">http://beebole.com/blog/?p=23#comment-25</guid>
		<description>[...] Beebole, on the other hand, appears quite pessimistic about the ability of these tools to ever live up to their promise. According to it, Creating web applications is about 4 big steps: [...] </description>
		<content:encoded><![CDATA[<p>[...] Beebole, on the other hand, appears quite pessimistic about the ability of these tools to ever live up to their promise. According to it, Creating web applications is about 4 big steps: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

