<?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>Technology Bits and Bytes &#187; Business Development</title>
	<atom:link href="http://blogs.circlesource.com/category/business-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.circlesource.com</link>
	<description>CircleSource Technical Talent ShowCase</description>
	<lastBuildDate>Thu, 10 Dec 2009 20:01:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Tips to create an effective proposal</title>
		<link>http://blogs.circlesource.com/2009/04/12/tips-to-create-an-effective-proposal/</link>
		<comments>http://blogs.circlesource.com/2009/04/12/tips-to-create-an-effective-proposal/#comments</comments>
		<pubDate>Sun, 12 Apr 2009 17:12:42 +0000</pubDate>
		<dc:creator>Sanchit Jain</dc:creator>
				<category><![CDATA[Business Development]]></category>
		<category><![CDATA[comunication]]></category>
		<category><![CDATA[proposal]]></category>
		<category><![CDATA[sales]]></category>

		<guid isPermaLink="false">http://blogs.circlesource.com/?p=380</guid>
		<description><![CDATA[1.    While writing the proposal keep in mind who is the audience. Is it a technical person, an end user, a finance guy or maybe a combination? Tailor it to suit their needs. This basic rule holds good for any document for that matter, always keep in mind who will read it.
2.    A good introduction [...]]]></description>
			<content:encoded><![CDATA[<p>1.    While writing the proposal keep in mind who is the audience. Is it a technical person, an end user, a finance guy or maybe a combination? Tailor it to suit their needs. This basic rule holds good for any document for that matter, always keep in mind who will read it.</p>
<p>2.    A good introduction goes a long way in setting the tone of the proposal. The introduction should tell about the problem and the solution that your proposal intends to solve. It should also tell what to expect from the proposal.</p>
<p>3.    Important points in the proposal should be bulleted, highlighted, colored or whatever it takes to make them jump out of the pages. Don’t make it look like a credit card’s hidden terms and conditions.</p>
<p>4.    Keep it short. If the buyer has received ten proposals, probably she’ll pick up the shortest one first.</p>
<p>5.    Leave the finances for the later sections, if money is not your selling point. If you can convince you have understood and can solve a problem effectively, the buyer shouldn’t bother much about it.</p>
<p>6.    Your company’s profile should not appear in the first few pages. The buyer probably knows about that if she asked you to submit a proposal. It can be a part of the appendix at best.</p>
<p>7.    Do a spelling and grammar check. Do not submit a proposal without a table of content.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.circlesource.com/2009/04/12/tips-to-create-an-effective-proposal/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
