<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Get Fully Funded Blog&#187; nonprofit newsletter</title>
	<atom:link href="http://getfullyfundedblog.com/tag/nonprofit-newsletter/feed/" rel="self" type="application/rss+xml" />
	<link>http://getfullyfundedblog.com</link>
	<description>Nonprofit Fundraising Articles &#38; Tips</description>
	<lastBuildDate>Thu, 13 Oct 2011 17:18:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Who wants to read your newsletter?</title>
		<link>http://getfullyfundedblog.com/2009/09/who-wants-to-read-your-newsletter/</link>
		<comments>http://getfullyfundedblog.com/2009/09/who-wants-to-read-your-newsletter/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 19:13:36 +0000</pubDate>
		<dc:creator>Sandy</dc:creator>
				<category><![CDATA[General Fundraising]]></category>
		<category><![CDATA[Newsletter]]></category>
		<category><![CDATA[donor newsletter]]></category>
		<category><![CDATA[fundraising]]></category>
		<category><![CDATA[nonprofit newsletter]]></category>

		<guid isPermaLink="false">http://getfullyfundedblog.com/?p=719</guid>
		<description><![CDATA[Maybe no one.  It all depends on the content. Unfortunately, MOST of the nonprofit newsletters out there are crap.  Sorry, but it&#8217;s true.  With tons of text, few or no photos, and loaded with jargon, donors are immediately turned off when they see your newsletter in the mailbox. If you want your newsletter to get [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgetfullyfundedblog.com%2F2009%2F09%2Fwho-wants-to-read-your-newsletter%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgetfullyfundedblog.com%2F2009%2F09%2Fwho-wants-to-read-your-newsletter%2F&amp;source=SandyRees&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Maybe no one.  It all depends on the content.</p>
<p>Unfortunately, MOST of the nonprofit newsletters out there are crap.  Sorry, but it&#8217;s true.  With tons of text, few or no photos, and loaded with jargon, donors are immediately turned off when they see your newsletter in the mailbox.</p>
<p>If you want your newsletter to get read, here&#8217;s what you do:  <strong>write what&#8217;s interesting to the donor</strong>, NOT what&#8217;s interesting to you.  That&#8217;s right, put your donor hat on and write what the donor wants to read.</p>
<p><strong>Write the stories of people whose lives are being changed by the work your organization does.</strong> Donors will read that.</p>
<p><strong>Write about how donors&#8217; gifts have been used in fulfilling your mission.</strong> Donors will read that.</p>
<p>Don&#8217;t write about the new janitor you just hired or some obscure award your organization won.  Remember that your average supporter knows little about the inner-workings of your organization.  Keep it simple for them.</p>
<p>Want more tips on creating donor-focused newsletters?   Here&#8217;s an article I wrote about common mistakes made in nonprofit newsletters. <a href="http://ezinearticles.com/?The-8-Most-Common-Mistakes-Made-in-Nonprofit-Newsletters&amp;id=2387768">http://ezinearticles.com/?The-8-Most-Common-Mistakes-Made-in-Nonprofit-Newsletters&amp;id=2387768</a></p>
<p>If you really want the scoop on nonprofit newsletters, read Tom Ahern&#8217;s book &#8220;The Mercifully Brief Real World Guide to Raising More Money With Newsletters Than You Ever Thought Possible.&#8221; Find it in my reading list: <a href="http://getfullyfunded.info/resources/bookstore">http://getfullyfunded.info/resources/bookstore</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://getfullyfundedblog.com/2009/09/who-wants-to-read-your-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips for a great nonprofit newsletter</title>
		<link>http://getfullyfundedblog.com/2009/07/tips-for-a-great-nonprofit-newsletter/</link>
		<comments>http://getfullyfundedblog.com/2009/07/tips-for-a-great-nonprofit-newsletter/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 02:17:21 +0000</pubDate>
		<dc:creator>Sandy</dc:creator>
				<category><![CDATA[Newsletter]]></category>
		<category><![CDATA[nonprofit newsletter]]></category>

		<guid isPermaLink="false">http://www.getfullyfundedblog.com/?p=623</guid>
		<description><![CDATA[It must be newsletter time.  I&#8217;ve fielded lots of questions recently about format and content &#8211; what to include, what not to include, what should be on the front page, etc.   So I thought I&#8217;d share a few pointers here for everyone. First, DO NOT put a letter from the Executive Director on the front [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgetfullyfundedblog.com%2F2009%2F07%2Ftips-for-a-great-nonprofit-newsletter%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgetfullyfundedblog.com%2F2009%2F07%2Ftips-for-a-great-nonprofit-newsletter%2F&amp;source=SandyRees&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>It must be newsletter time.  I&#8217;ve fielded lots of questions recently about format and content &#8211; what to include, what not to include, what should be on the front page, etc.   So I thought I&#8217;d share a few pointers here for everyone.</p>
<p>First, DO NOT put a letter from the Executive Director on the front page.  Donors don&#8217;t want to read this.  What they DO want to read is a story about a particular person whose life is being changed by your organization.</p>
<p>Don&#8217;t waste space on a table of contents.  Especially if your newsletter is only 4 pages.  And don&#8217;t continue a story on another page.  Make it fit in the space available.</p>
<p>Keep the special event info to a minimum &#8211; you don&#8217;t need to go on and on about upcoming or past events.  Stroke sponsors as needed, but don&#8217;t go overboard.</p>
<p>Realize that your newsletter is a great tool to build relationships with donors and educate them about what you&#8217;re doing.  Don&#8217;t waste space on things that aren&#8217;t interesting to your donors.</p>
<p>If you really want to learn more about nonprofit newsletters, check out Tom Ahern&#8217;s books and his website at <a href="http://www.aherncomm.com">www.aherncomm.com</a>.  You&#8217;ll find some great resources and tips.</p>
]]></content:encoded>
			<wfw:commentRss>http://getfullyfundedblog.com/2009/07/tips-for-a-great-nonprofit-newsletter/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>The Worst Newsletter Ever</title>
		<link>http://getfullyfundedblog.com/2008/12/the-worst-newsletter-ever/</link>
		<comments>http://getfullyfundedblog.com/2008/12/the-worst-newsletter-ever/#comments</comments>
		<pubDate>Mon, 22 Dec 2008 15:31:43 +0000</pubDate>
		<dc:creator>Sandy</dc:creator>
				<category><![CDATA[Newsletter]]></category>
		<category><![CDATA[nonprofit newsletter]]></category>

		<guid isPermaLink="false">http://www.getfullyfundedblog.com/?p=343</guid>
		<description><![CDATA[In the mail last week, I received the worst newsletter I&#8217;ve ever seen.  I&#8217;ve seen some bad ones over the years, but this one takes the cake. First, the front page was a long letter from the Executive Director.  This page was packed full of text with hardly any white space and no breaks for [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fgetfullyfundedblog.com%2F2008%2F12%2Fthe-worst-newsletter-ever%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fgetfullyfundedblog.com%2F2008%2F12%2Fthe-worst-newsletter-ever%2F&amp;source=SandyRees&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>In the mail last week, I received the worst newsletter I&#8217;ve ever seen.  I&#8217;ve seen some bad ones over the years, but this one takes the cake.</p>
<p>First, the front page was a long letter from the Executive Director.  This page was packed full of text with hardly any white space and no breaks for my eyes.  No photos, no headlines.  It was exhausting to look at.</p>
<p>On the inside, another long letter from the Board President.  Tons of text, no breaks &#8211; yuck.  The rest of the newsletter was more of the same &#8211; boring text-heavy pages with no photos, no stories, nothing to warm my heart or compel me to give.  There was a lot of &#8220;save the date&#8221; info about events coming up and events that happened months ago.  There was info about staff coming and going.  Nothing about the people the organization serves and how lives are being changed.  I know this organization has some powerful stories to tell (I&#8217;ve heard them before).  Why weren&#8217;t they in the newsletter?</p>
<p>The whole thing looked like a bad copy of a copy.  Am I as a donor not worthy of at least an original copy?</p>
<p>As I looked at this terrible excuse for a newsletter, it occured to me that it was written to be interesting to the writer &#8211; not interesting to me as the reader.</p>
<p>I share this with you in the hopes that you can learn from the mistakes of this organization and do a better job of your own newsletter.</p>
]]></content:encoded>
			<wfw:commentRss>http://getfullyfundedblog.com/2008/12/the-worst-newsletter-ever/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

