<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Xero &#8211; the product</title>
	<atom:link href="http://lancewiggs.com/2007/08/12/xero-the-product/feed/" rel="self" type="application/rss+xml" />
	<link>http://lancewiggs.com/2007/08/12/xero-the-product/</link>
	<description>NZ Internet, Media and Business</description>
	<lastBuildDate>Sun, 27 May 2012 02:05:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Glen Barnes</title>
		<link>http://lancewiggs.com/2007/08/12/xero-the-product/#comment-4110</link>
		<dc:creator><![CDATA[Glen Barnes]]></dc:creator>
		<pubDate>Sun, 12 Aug 2007 21:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://lancewiggs.com/2007/08/12/xero-the-product/#comment-4110</guid>
		<description><![CDATA[I don’t know how Rod &amp; Xero are designing their system, but since they are targeting to go global, perhaps it would be a good idea for them to explore the possible use of rule-based &amp; expert-system in the architectural design of their system.
AFAIK they are using a rule based system. At KiwiFoo this year when they presented they said they have designed the system from the ground up to be able to launch into new markets with different tax systems. From what they said they have spent a lot of time building the base architecture so adding new features will be a lot easier.
LANCE: They also mentioned that they will be building an API which will allow third parties to add features onto the product. Import/Export filters would be a prime example of this. My guess is you will see constant innovation on a 6 week/2month cycle with small improvements each time. In a years time the product will offer a lot more in terms of features while hopefully keeping it simple to understand for the small business owner (something that I don&#039;t think MYOB does at all).]]></description>
		<content:encoded><![CDATA[<p>I don’t know how Rod &amp; Xero are designing their system, but since they are targeting to go global, perhaps it would be a good idea for them to explore the possible use of rule-based &amp; expert-system in the architectural design of their system.<br />
AFAIK they are using a rule based system. At KiwiFoo this year when they presented they said they have designed the system from the ground up to be able to launch into new markets with different tax systems. From what they said they have spent a lot of time building the base architecture so adding new features will be a lot easier.<br />
LANCE: They also mentioned that they will be building an API which will allow third parties to add features onto the product. Import/Export filters would be a prime example of this. My guess is you will see constant innovation on a 6 week/2month cycle with small improvements each time. In a years time the product will offer a lot more in terms of features while hopefully keeping it simple to understand for the small business owner (something that I don&#8217;t think MYOB does at all).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Falafulu Fisi</title>
		<link>http://lancewiggs.com/2007/08/12/xero-the-product/#comment-3923</link>
		<dc:creator><![CDATA[Falafulu Fisi]]></dc:creator>
		<pubDate>Sun, 12 Aug 2007 02:39:33 +0000</pubDate>
		<guid isPermaLink="false">http://lancewiggs.com/2007/08/12/xero-the-product/#comment-3923</guid>
		<description><![CDATA[Bwooce said...
&lt;i&gt;I’d also have some concern that they’re going to hit i18n problems from the other direction; customising for local tax means you can make some decisions which are hard to generalise later.&lt;/i&gt;

I don&#039;t know how Rod &amp; Xero are designing their system, but since they are targeting to go global, perhaps it would be a good idea for them to explore the possible use of rule-based &amp; expert-system in the architectural design of their system. Expert-system  suits very well with applications that have different rules (ie, different taxation rules in different countries), that are changing frequently. When the rules changes, you don&#039;t need to re-write or re-compile any codes, all you need to do is re-edit the rules (addition of new rules or deletion of old rules that don&#039;t apply anymore) which are written in text-files. I am aware that taxation legislations are prone to frequent change, so in such an environment rule-based &amp; expert-system comes very handy and it has low costs of maintenance because there is no re-coding or re-compiling of codes whenever the rules change. Rule-based &amp; Expert-system are already popular in taxation-adviser software application of today. I might drop Rod an email about exploring rule-based &amp; expert-system scenario.]]></description>
		<content:encoded><![CDATA[<p>Bwooce said&#8230;<br />
<i>I’d also have some concern that they’re going to hit i18n problems from the other direction; customising for local tax means you can make some decisions which are hard to generalise later.</i></p>
<p>I don&#8217;t know how Rod &amp; Xero are designing their system, but since they are targeting to go global, perhaps it would be a good idea for them to explore the possible use of rule-based &amp; expert-system in the architectural design of their system. Expert-system  suits very well with applications that have different rules (ie, different taxation rules in different countries), that are changing frequently. When the rules changes, you don&#8217;t need to re-write or re-compile any codes, all you need to do is re-edit the rules (addition of new rules or deletion of old rules that don&#8217;t apply anymore) which are written in text-files. I am aware that taxation legislations are prone to frequent change, so in such an environment rule-based &amp; expert-system comes very handy and it has low costs of maintenance because there is no re-coding or re-compiling of codes whenever the rules change. Rule-based &amp; Expert-system are already popular in taxation-adviser software application of today. I might drop Rod an email about exploring rule-based &amp; expert-system scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bwooce</title>
		<link>http://lancewiggs.com/2007/08/12/xero-the-product/#comment-3907</link>
		<dc:creator><![CDATA[Bwooce]]></dc:creator>
		<pubDate>Sat, 11 Aug 2007 21:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://lancewiggs.com/2007/08/12/xero-the-product/#comment-3907</guid>
		<description><![CDATA[Hi Lance,

Nice review. I&#039;ve been trying to find a decent SaaS package, even just for estimates and invoices, that is usable in NZ. It is quite a challenge.

Xero would be quite good, even though it doesn&#039;t do estimates, but it is very expensive when compared with the competition. As I said in my mini-review on my blog I can&#039;t see what the target market is, the sweet-spot is quite small and they&#039;re either looking to get more blood from a stone (money from micro to NZ small businesses) or not charge enough from the NZ medium size enterprises. I&#039;d also have some concern that they&#039;re going to hit i18n problems from the other direction; customising for local tax means you can make some decisions which are hard to generalise later.

Xero does look very nice, but I&#039;m not much closer to finding even the basic estimate/invoicing option; a lot of i18n problems everywhere. The last suggestion (time59) won&#039;t let me put TAX INVOICE on the invoices...grrr...]]></description>
		<content:encoded><![CDATA[<p>Hi Lance,</p>
<p>Nice review. I&#8217;ve been trying to find a decent SaaS package, even just for estimates and invoices, that is usable in NZ. It is quite a challenge.</p>
<p>Xero would be quite good, even though it doesn&#8217;t do estimates, but it is very expensive when compared with the competition. As I said in my mini-review on my blog I can&#8217;t see what the target market is, the sweet-spot is quite small and they&#8217;re either looking to get more blood from a stone (money from micro to NZ small businesses) or not charge enough from the NZ medium size enterprises. I&#8217;d also have some concern that they&#8217;re going to hit i18n problems from the other direction; customising for local tax means you can make some decisions which are hard to generalise later.</p>
<p>Xero does look very nice, but I&#8217;m not much closer to finding even the basic estimate/invoicing option; a lot of i18n problems everywhere. The last suggestion (time59) won&#8217;t let me put TAX INVOICE on the invoices&#8230;grrr&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: so when should you buy XRO and BFW? &#171; Lance Wiggs</title>
		<link>http://lancewiggs.com/2007/08/12/xero-the-product/#comment-3890</link>
		<dc:creator><![CDATA[so when should you buy XRO and BFW? &#171; Lance Wiggs]]></dc:creator>
		<pubDate>Sat, 11 Aug 2007 15:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://lancewiggs.com/2007/08/12/xero-the-product/#comment-3890</guid>
		<description><![CDATA[[...] Contact&#160;Me          &#171; Xero - the&#160;product [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Contact&nbsp;Me          &laquo; Xero &#8211; the&nbsp;product [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

