<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://72.14.177.54/skins/common/feed.css?207"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>Alice Ghostley - Revision history</title>
		<link>http://72.14.177.54/Oklahoma/?title=Alice_Ghostley&amp;action=history</link>
		<description>Revision history for this page on the wiki</description>
		<language>en</language>
		<generator>MediaWiki 1.15.1</generator>
		<lastBuildDate>Tue, 30 Jun 2026 02:01:39 GMT</lastBuildDate>
		<item>
			<title>67.203.136.195:&amp;#32;CsQzzOJVEdSWNnlg</title>
			<link>http://72.14.177.54/Oklahoma/?title=Alice_Ghostley&amp;diff=2026&amp;oldid=prev</link>
			<description>&lt;p&gt;CsQzzOJVEdSWNnlg&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Thanks, Sarah. Listing prices makes total sense to me.But What if I don't know how much my stuff costs? I won't truly know until I rlleay understand my client's issue and ascertain how long it may take to actually help fix the issue and get a handle on scope. Or is this just me complicating matters? Are packages the best way to sell my services?  Is it ok to list prices for some things (with clear, well-defined expectations and scope) and leave open others? For some reason that seems like a bad idea. Like it could give a potential client the wrong idea of how much the stuff will cost.OK, well that was a lot of questions, maybe I should just hire you.&lt;/div&gt;</description>
			<pubDate>Sat, 20 Oct 2012 10:12:08 GMT</pubDate>			<dc:creator>67.203.136.195</dc:creator>			<comments>http://72.14.177.54/Oklahoma/Talk:Alice_Ghostley</comments>		</item>
	</channel>
</rss>