<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Church Planting the Easy Way</title>
	<link>http://billeasum.com/20071107/church-planting-the-easy-way/</link>
	<description>The unmotivated are oblivious to the obvious</description>
	<pubDate>Tue, 06 Jan 2009 06:30:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Daniel</title>
		<link>http://billeasum.com/20071107/church-planting-the-easy-way/#comment-639</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Mon, 16 Jun 2008 09:29:07 +0000</pubDate>
		<guid>http://billeasum.com/20071107/church-planting-the-easy-way/#comment-639</guid>
		<description>I read similar article also named Church Planting the Easy Way, and it was completely different. Personally, I agree with you more, because this article makes a little bit more sense for me</description>
		<content:encoded><![CDATA[<p>I read similar article also named Church Planting the Easy Way, and it was completely different. Personally, I agree with you more, because this article makes a little bit more sense for me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Troxell</title>
		<link>http://billeasum.com/20071107/church-planting-the-easy-way/#comment-518</link>
		<dc:creator>Greg Troxell</dc:creator>
		<pubDate>Tue, 13 May 2008 11:44:06 +0000</pubDate>
		<guid>http://billeasum.com/20071107/church-planting-the-easy-way/#comment-518</guid>
		<description>Many other church planters are cultivating the organic opportunities that flow from beyond their local church into the larger Church. Just as in the now age old illustration in "Spiritual Redwoods" , these leaders are networking below the surface for back office support. One might offer the support system for evangelism another for discipleship. Younglife uses this model in their "Church Partnership Model" something that I strongly support. 

Perhaps a specific example is how multiple churches (or the church plants via the parent church) can share the same "Hosted CMS solution". This type of partnership can reduce the cost to each church (well below the $10/member average cost), maintain autonomy and privacy of all data, and provide access to more program/ software solutions than otherwise might be affordable to each church. 

There are other examples of this type of catalytic partnership that include fellowship, HR, accounting, missional, and software solutions. New business models are popping up across the USA to provide what independent churches have never had, and denominational offices have failed to provide satisfactorily for well over 30 years.</description>
		<content:encoded><![CDATA[<p>Many other church planters are cultivating the organic opportunities that flow from beyond their local church into the larger Church. Just as in the now age old illustration in &#8220;Spiritual Redwoods&#8221; , these leaders are networking below the surface for back office support. One might offer the support system for evangelism another for discipleship. Younglife uses this model in their &#8220;Church Partnership Model&#8221; something that I strongly support. </p>
<p>Perhaps a specific example is how multiple churches (or the church plants via the parent church) can share the same &#8220;Hosted CMS solution&#8221;. This type of partnership can reduce the cost to each church (well below the $10/member average cost), maintain autonomy and privacy of all data, and provide access to more program/ software solutions than otherwise might be affordable to each church. </p>
<p>There are other examples of this type of catalytic partnership that include fellowship, HR, accounting, missional, and software solutions. New business models are popping up across the USA to provide what independent churches have never had, and denominational offices have failed to provide satisfactorily for well over 30 years.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
