<?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"
	>

<channel>
	<title>Corporate Blog</title>
	<atom:link href="http://www.evapt.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.evapt.com/blog</link>
	<description></description>
	<pubDate>Tue, 12 Jun 2012 09:33:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<language>en</language>
			<item>
		<title>On Demand Business Model</title>
		<link>http://www.evapt.com/blog/on-demand-business-model/</link>
		<comments>http://www.evapt.com/blog/on-demand-business-model/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 12:36:10 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Billing]]></category>

		<category><![CDATA[Billing System for On Demand Services]]></category>

		<category><![CDATA[Saas pricing]]></category>

		<category><![CDATA[Billing for On Demand Services]]></category>

		<category><![CDATA[Billing System for On Demand Business]]></category>

		<category><![CDATA[Billing System for SaaS]]></category>

		<category><![CDATA[Billing System for VoIP]]></category>

		<category><![CDATA[On Demand Billing System]]></category>

		<category><![CDATA[On Demand Business Model]]></category>

		<category><![CDATA[SaaS Billing]]></category>

		<category><![CDATA[VoIP Billing System]]></category>

		<guid isPermaLink="false">http://www.evapt.com/blog/?p=225</guid>
		<description><![CDATA[The beauty of On Demand Services is that, you can access and avail service any time you need, but for premium ones you need to pay for it.  There are also challenges in maintaining these kind of services, as a corporate if you have On Demand Services these should be accessible by your customers at [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal" style="text-align: left; ">The beauty of <strong><em>On Demand Services</em></strong> is that, you can access and avail service any time you need, but for premium ones you need to pay for it.  There are also challenges in maintaining these kind of services, as a corporate if you have <strong><em>On Demand Services</em></strong> these should be accessible by your customers at any time through internet and these customer can be from various region and from a region there might be different types of customers (Sex, Age, etc) accessing the service and so you need deliver the appropriate content based on parameters such as region, customer profile, etc. There are content Management systems (CMS) available which can index the content based on parameters and store it, qualify the request for content based on parameters such as region, customer profile, etc and provision the appropriate content.  So, Content Delivery is managed through these systems but on pricing part, <strong><em>On Demand Service Provider </em></strong>might come up with different prices for the same content in different region and also packaging of services using various combinations of services as promotional activity and further more invoicing and collecting the payments, before provisioning of the content. CMS are not capable of packaging &amp; pricing of the services, invoicing &amp; payments collection, this part can be handled by Billing Systems.</p>
<p class="MsoNormal" style="text-align: left; "><span>So, <strong><em>On Demand Service Providers </em></strong>can have good turn over in this model by having an efficient CMS<strong><em> </em></strong>and<strong><em> Billing Systems </em></strong>in place.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/on-demand-business-model/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Revenue Management &#038; Customer Retention in Subscription Management</title>
		<link>http://www.evapt.com/blog/revenue-management-customer-retention-in-subscription-business/</link>
		<comments>http://www.evapt.com/blog/revenue-management-customer-retention-in-subscription-business/#comments</comments>
		<pubDate>Mon, 26 Mar 2012 11:37:35 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Billing]]></category>

		<category><![CDATA[Cloud computing]]></category>

		<category><![CDATA[OSS]]></category>

		<category><![CDATA[Pricing]]></category>

		<category><![CDATA[SaaS]]></category>

		<category><![CDATA[SaaS Monetization]]></category>

		<category><![CDATA[Saas pricing]]></category>

		<category><![CDATA[billing system]]></category>

		<category><![CDATA[Cloud]]></category>

		<category><![CDATA[Cloud Billling]]></category>

		<category><![CDATA[customer care]]></category>

		<category><![CDATA[Customer Retention]]></category>

		<category><![CDATA[pricing management]]></category>

		<category><![CDATA[Recurring Billing System]]></category>

		<category><![CDATA[Revenue Management]]></category>

		<category><![CDATA[Revenue Maximization]]></category>

		<category><![CDATA[SaaS Billing]]></category>

		<category><![CDATA[Subscription Business Model]]></category>

		<category><![CDATA[subscription management]]></category>

		<guid isPermaLink="false">http://www.evapt.com/blog/?p=215</guid>
		<description><![CDATA[Principle of Subscription Management Business Model - “Transforming Onetime Revenue to Recurring Revenue”. This lured many corporate and even industries to shape, offer and buy their services on subscription basis by the customer. Many (companies) turned to subscription model to -(leverage on) the advantages embedded in the principle  such as business continuity (Financially), brand and [...]]]></description>
			<content:encoded><![CDATA[<p>Principle of<strong> <em>Subscription Management Business Model</em> </strong>- “Transforming Onetime Revenue to Recurring Revenue”. This lured many corporate and even industries to shape, offer and buy their services on subscription basis by the customer. Many (companies) turned to subscription model to -(leverage on) the advantages embedded in the principle  such as business continuity (Financially), brand and customer loyalty, up selling, revenues from subscription sale (value) greater than Onetime, etc. Customers prefer to buy product or service on subscription basis as it eases the payment for expensive items, saves time in case of frequently purchased items, etc. This Model fetches advantage for both the customer and service provider.</p>
<h4><strong>How customer retention results in revenue generation?</strong></h4>
<p>Service Provider receives payments from customer on periodic basis in subscription model, but one should be aware of the fact that losing a customer in middle of any subscription period might bring down sale value, instead which onetime sale would have bought him more money. So, retaining a customer in subscription model is a key for recurring revenue. Service providers need to efficiently and effectively handle the some / all of the below activities in order to retain a customer in subscription model</p>
<p><strong>Pricing and Packaging Management</strong>: Create and offer flexible price plans, offer discounts and promotions, etc to win a new customer and also for retaining the existing customers.</p>
<p><strong>Contract Management</strong> – Service providers need to efficiently store and manage the contract related transactions such as up gradation/down gradation/renewals) to maintain a continuous information of a customer. By knowing purchasing behavior of a customer on a continuous basis will facilitate a service provider to retain a customer.</p>
<p><strong>Billing</strong> – Number of invoices generated will be more in subscription model compared to onetime sale. Service providers should be able to generate invoices on periodic basis with different frequencies (monthly/quarterly/half yearly/Yearly) as per contract agreement.</p>
<p><strong>Customer Care</strong> – Need to provide 24/7 online help desk services, handle requests in time, and provide self-care portal with privileges to view their contract details, bills, raise tickets, etc for providing transparency.</p>
<p>Some service providers handle these operations manually, which might work for a business with a low customer base, but for higher ones there should be a system in place to take care of these operations.  In the case of a small company the billing process is handled manually and faces a critical challenge in scaling up their business. And a reasonably large company faces critical issues by managing their business in a manual fashion or by obsolete systems. Subscription centric billing systems like eVapt are fast replacing various traditional billing systems in many companies across the world. These billing systems come with a set of features that are increasingly becoming necessary rather than a option to run the business. These modern day billing systems come with various abilities like integration with CRMs, ERPs, Financial Accounting Systems, etc and ability address various organization specific billing requirements and supports data transformation / sharing<br />
These benefits are increasingly being adopted by various business houses across the world and are enabling them to scale up their business by completely automating their business process and supporting in faster time to market their services &amp; offerings.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/revenue-management-customer-retention-in-subscription-business/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Identification and successful mitigation of challenges in Partner Management: An IaaS Scenario</title>
		<link>http://www.evapt.com/blog/identification-and-successful-mitigation-of-challenges-in-partner-management-an-iaas-scenario/</link>
		<comments>http://www.evapt.com/blog/identification-and-successful-mitigation-of-challenges-in-partner-management-an-iaas-scenario/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 08:34:24 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Agile development]]></category>

		<category><![CDATA[Billing]]></category>

		<category><![CDATA[Cloud computing]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[eVapt]]></category>

		<category><![CDATA[eVapt Inc]]></category>

		<guid isPermaLink="false">http://www.evapt.com/blog/?p=205</guid>
		<description><![CDATA[ 
In the context of IaaS or data center (Cloud computing), Partners play an important role of business process. Be it as a technology partner who is enabling the service provider by providing technology support or a sales partner who is sells the products to the end customers. No matter what kind of a partner [...]]]></description>
			<content:encoded><![CDATA[<p><!--[if gte mso 9]><xml> <o:OfficeDocumentSettings> <o:RelyOnVML /> <o:AllowPNG /> </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--[if gte mso 10]> <mce:style><!<br />
/* Style Definitions */<br />
table.MsoNormalTable<br />
{mso-style-name:"Table Normal";<br />
mso-tstyle-rowband-size:0;<br />
mso-tstyle-colband-size:0;<br />
mso-style-noshow:yes;<br />
mso-style-priority:99;<br />
mso-style-qformat:yes;<br />
mso-style-parent:"";<br />
mso-padding-alt:0in 5.4pt 0in 5.4pt;<br />
mso-para-margin-top:0in;<br />
mso-para-margin-right:0in;<br />
mso-para-margin-bottom:10.0pt;<br />
mso-para-margin-left:0in;<br />
line-height:115%;<br />
mso-pagination:widow-orphan;<br />
font-size:11.0pt;<br />
font-family:"Calibri","sans-serif";<br />
mso-ascii-font-family:Calibri;<br />
mso-ascii-theme-font:minor-latin;<br />
mso-fareast-font-family:"Times New Roman";<br />
mso-fareast-theme-font:minor-fareast;<br />
mso-hansi-font-family:Calibri;<br />
mso-hansi-theme-font:minor-latin;<br />
mso-bidi-font-family:"Times New Roman";<br />
mso-bidi-theme-font:minor-bidi;}<br />
--> <!--[endif] --></p>
<p class="MsoNormal" style="text-align: justify;">In the context of IaaS or data center (Cloud computing), Partners play an important role of business process. Be it as a technology partner who is<span> </span>enabling the service provider by providing technology support or a sales partner who is sells the products to the end customers. No matter what kind of a partner one is, he is an important part of the value chain of a company and should be rewarded according to his contribution. Companies see to it that their partners get their benefit in terms of commissions, which are also called revenue sharing. Some of the examples of these partners are virtualization platforms, resellers, vendors, payment gateways, sales personnel to name a few. This business model of passing on the benefit to its partners can actually improve the presence of a company in the market, without actually spending directly towards the same. A strong market presence in the market using partners can be helpful for better market penetration, new product introduction, increasing the markets into new segments, reduce the efforts required to build a system, handle payments etc.</p>
<p class="MsoNormal" style="text-align: justify;">Partnership model of business, however has few challenges to address from a business process point of view. Partner agreements are different from one another as the agreements are made on the basis of each partner’s role in the business process. Hence the revenue settlement cannot be done on the basis of a single agreement. Companies without billing systems generally take care of the revenue settlement manually in a tedious process and this leads to reduction in revenue and increase in expenditure.</p>
<p class="MsoNormal" style="text-align: justify;">Billing systems like eVapt come with a revenue settlement module as revenue settlement is treated as an important part of revenue management. These systems come integrated with payment gateway and a FAS(Financial Accounting System). So once the receivables are received, the billing system will automatically credit the respective amount of money in the partners account in your accounting system based on the pre-defined settlement rule.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/identification-and-successful-mitigation-of-challenges-in-partner-management-an-iaas-scenario/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Agility and Flexibility in Rating and Billing</title>
		<link>http://www.evapt.com/blog/agility-and-flexibility-in-rating-and-billing/</link>
		<comments>http://www.evapt.com/blog/agility-and-flexibility-in-rating-and-billing/#comments</comments>
		<pubDate>Thu, 27 May 2010 09:57:32 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Billing]]></category>

		<category><![CDATA[Cloud computing]]></category>

		<category><![CDATA[Pricing]]></category>

		<category><![CDATA[Saas pricing]]></category>

		<category><![CDATA[Cloud]]></category>

		<category><![CDATA[Cloud Billling]]></category>

		<category><![CDATA[Rating]]></category>

		<category><![CDATA[Usage Rating]]></category>

		<guid isPermaLink="false">http://www.evapt.com/wordpress/?p=200</guid>
		<description><![CDATA[
Cloud service providers should be capable of billing automatically based on any billing cycle. But one must not ignore the pains of a cloud service provider in calculating the usage of each and every customer, applying a specified rate plan, and generating a bill. So there should be a proper mechanism in generating a statement [...]]]></description>
			<content:encoded><![CDATA[<p><!-- 		@page { margin: 2cm } 		P { margin-bottom: 0.21cm } --></p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Cloud service providers should be capable of billing automatically based on any billing cycle. But one must not ignore the pains of a cloud service provider in calculating the usage of each and every customer, applying a specified rate plan, and generating a bill. So there should be a proper mechanism in generating a statement of account or invoice/bill.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Now the challenge here is, cloud service provider has to have a continuous watch on the usage consumption of its customer(s) which may prevent from significant revenue loss. Solution towards this is a Metering component, which integrates with cloud service providers database servers / control panel /virtualization platform to collect the usage detailed records (UDRs). </p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Does this accurate usage collection details really facilitate in generating usage based invoices/bills? In order to do so, a flexible rating engine should be in place to rate each individual service usage.  Rating engine should allow service provider to comprehensively define different price rules and measure based on the usage. So rating engine should be extensible with no restriction on units of measurement, support flat and tiered (incremental) rating schemes and also support both the prepaid and post paid scenarios.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Following are the different rate plans a cloud service provider metering and rating system should support.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Volume based rate plan: Based on the total volume (e.g.: storage space) consumption, system should support incremental slab where price per unit varies. Depending on the total usage invoices are to be generated.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Time based rate plan: Any day of the week, day of the year and time of the day are considered in order to define different rate plans (Off peak, holidays, business hours etc). And based on these parameters the usage is been calculated and the bills are generated accordingly.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">Billing: Invoicing/billing process will use the charges generated from rating engine i.e. discounts and tax calculation and posting them into accounts. Billing engine should also be flexible to support prorate rules while calculating the final invoice/bill.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/agility-and-flexibility-in-rating-and-billing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Challenges of Usage Metering in Cloud Computing</title>
		<link>http://www.evapt.com/blog/challenges-of-usage-metering-in-cloud-computing/</link>
		<comments>http://www.evapt.com/blog/challenges-of-usage-metering-in-cloud-computing/#comments</comments>
		<pubDate>Fri, 12 Mar 2010 12:39:25 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Cloud computing]]></category>

		<category><![CDATA[Pricing]]></category>

		<category><![CDATA[SaaS]]></category>

		<category><![CDATA[SaaS Monetization]]></category>

		<category><![CDATA[Saas pricing]]></category>

		<guid isPermaLink="false">http://www.evapt.com/wordpress/?p=189</guid>
		<description><![CDATA[Whose challenge is this ? Marketing team is coming up with innovative price plans, Sales is aggressive in acquiring customers,  Technical team is provisioning services, Customer is availing every option of service  extensively but end of the month, usage metering , calculation and invoicing !&#8230;..How do we do this? Is this a concern [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-bottom: 0cm;" align="JUSTIFY">Whose challenge is this ? Marketing team is coming up with innovative price plans, Sales is aggressive in acquiring customers,  Technical team is provisioning services, Customer is availing every option of service  extensively but end of the month, usage metering , calculation and invoicing !&#8230;..How do we do this? Is this a concern for every cloud computing provider ?</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">
<p style="margin-bottom: 0cm;" align="JUSTIFY">To have competitive edge and sustain in the cloud market place, cloud service providers are flexible in terms of their <a href="http://www.evapt.com/products/" target="_blank">services, price plans or pricing</a> structure which introduced the concept of <a href="http://www.idc.com/getdoc.jsp?containerId=prUS22239610">Pay Per Use (PPU)</a>. But, one must not ignore the pains of a cloud service provider in tracking, collating and calculating the usage of each and every customer, applying respective rate plan, and generating a bill.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">
<p style="margin-bottom: 0cm;" align="JUSTIFY">In addition to the usage based pricing parameters such as storage space, bandwidth consumption, computing cycles, number of users, modules, services, instances, downloads, alerts, hours etc, every cloud service provider has its own vertical specific usage based pricing charges e.g. in SaaS HRM vertical , they charge based on number of employees, or per month per user, Now the challenge here is cloud service provider has to have a continuous watch on the usage consumption of its customer(s) which may prevent from significant revenue loss. Alerting and allowing a customer on the usage limit (threshold) is again one such crucial business process. Cloud service provider follow a manual process or they have a tool in house developed to track such things. This exercise involves  additional human resource  or efforts to their operations .</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">
<p style="margin-bottom: 0cm;" align="JUSTIFY">Manual usage tracking is not much of a painful process for start-ups with less customers. However usage tracking process would become a challenging and painful process for the service providers with Large customer base.  Hence cloud service provider should automate its usage tracking process and keep a weather eye on the individual customer&#8217;s usage consumption. This will reduce the revenue loss occurred in manual process.</p>
<p style="margin-bottom: 0cm;" align="JUSTIFY">
<p style="margin-bottom: 0cm;" align="JUSTIFY">eVapt has proven experience in collecting the usage records for cloud subscription service providers across the globe. eVapt has deployed its solution along with it’s Metering module which integrates with cloud service providers database servers / control panel /virtualization platform to collect the usage detailed records (UDRs). This will collect data that is in logfiles, databases or can run scripts written in Java to collect data. The Metering component in eVapt allows collections of multiple usage type and accurate processing of the same. This will plug the loss of revenues through accurate usage collection and processing.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/challenges-of-usage-metering-in-cloud-computing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Dynamics of Cloud service plans and pricing</title>
		<link>http://www.evapt.com/blog/dynamics-of-cloud-service-plans-and-pricing/</link>
		<comments>http://www.evapt.com/blog/dynamics-of-cloud-service-plans-and-pricing/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 05:28:30 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Billing]]></category>

		<category><![CDATA[Cloud computing]]></category>

		<category><![CDATA[Pricing]]></category>

		<category><![CDATA[SaaS]]></category>

		<category><![CDATA[SaaS Monetization]]></category>

		<category><![CDATA[Saas pricing]]></category>

		<guid isPermaLink="false">http://www.evapt.com/wordpress/?p=183</guid>
		<description><![CDATA[“Pick what you want” is the mantra that made cloud service providers to stay ahead in the competitive cloud arena. The “On-demand” services offered by cloud service providers are now more dynamically availed by customers. Based on the usage analytics, cloud service providers have to offer new exciting plans to keep customer happy and to [...]]]></description>
			<content:encoded><![CDATA[<p>“Pick what you want” is the mantra that made cloud service providers to stay ahead in the competitive cloud arena. The “On-demand” services offered by cloud service providers are now more dynamically availed by customers. Based on the usage analytics, cloud service providers have to offer new exciting plans to keep customer happy and to get <span lang="en-US">competitive advantage. </span> To meet such requirements of the market dynamics, cloud service  providers have to come-up with new promising plans that enhances customer stickiness, sign-up for long term contracts and engages them to avail services continuously.</p>
<p style="margin-bottom: 0cm;">
<p style="margin-bottom: 0cm;">
<p style="margin-bottom: 0cm;">Service providers are more competitive in offering  modular packages such as Bronze, Gold, Platinum with additional services topping on the higher packages and Pay as you go services  in order to suffice the market requirement. Though services are offered across the globe, they should  support local currencies or a single standard currency.</p>
<p style="margin-bottom: 0cm;">
<p style="margin-bottom: 0cm;">Service provider system should have the option to scale up and scale down the services with respect to the market. Flexible service plans such as region and customer specific packages, dynamic pricing, lower monthly fixed plus usage based charges, long term contracts exclude or include different tax rates and support based services  are few important factors  which enhances the customer acquisition rate.</p>
<p style="margin-bottom: 0cm;">
<p style="margin-bottom: 0cm;">A service provider system should be  flexible enough to allow  customer to avail the service, even after exceeding the usage limit and charge them on the overages rather than terminating the service. This results in less efforts in customer retention process and more concentration of customer acquisition .</p>
<p style="margin-bottom: 0cm;">
<p style="margin-bottom: 0cm;">Some more scenarios where service provider&#8217;s system should support.</p>
<ul>
<li>Automates in changing the customer 	package on a future date.</li>
<li>Override 	the existing price and define a new price for the same price plan.</li>
</ul>
<p style="margin-bottom: 0cm;">
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/dynamics-of-cloud-service-plans-and-pricing/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Cloud solution fitting into the jigsaw of the current IT eco-system</title>
		<link>http://www.evapt.com/blog/cloud-solution-fitting-into-the-jigsaw-of-the-current-it-eco-system/</link>
		<comments>http://www.evapt.com/blog/cloud-solution-fitting-into-the-jigsaw-of-the-current-it-eco-system/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 07:14:56 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Cloud computing]]></category>

		<category><![CDATA[Economy]]></category>

		<category><![CDATA[SaaS]]></category>

		<guid isPermaLink="false">http://www.evapt.com/wordpress/?p=177</guid>
		<description><![CDATA[We have seen a significant increase in cloud solution adaption during the financial crises period. Customers / users are now more cautious in evaluating the cloud solutions. In addition to the adaptability, user friendly and scalable criteria, organizations are now more concerned about any   third party system&#8217;s capability in interacting with the existing [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-bottom: 0cm;" align="justify">We have seen a significant increase in cloud solution adaption during the financial crises period. Customers / users are now more cautious in evaluating the cloud solutions. In addition to the adaptability, user friendly and scalable criteria, organizations are now more concerned about any   third party system&#8217;s capability in interacting with the existing solutions in the eco-system. Where as the eco-system may have few home grown solutions, standalone applications, third party systems, back office solutions etc.,</p>
<p style="margin-bottom: 0cm;" align="justify">
<p style="margin-bottom: 0cm;" align="justify">
<p style="margin-bottom: 0cm;" align="justify">Opting a cloud business application affects all the areas of an organization, from sales &amp; marketing,  technical, operational and till customer support. An integrated cloud system should ensure that there is no redundancy in data, yet without compromising on its security. So System should have a flexible architecture which ensures integration with external systems and internal systems of the organization. And the overall system should be tightly integrated resulting  in enriching the value of their offerings through the synergy of functionality brought together on these platforms.</p>
<p style="margin-bottom: 0cm;" align="justify">
<p style="margin-bottom: 0cm;" align="justify">
<p style="margin-bottom: 0cm;" align="justify">Though there are good number solution providers aware of this fact, still few of the solutions offered to Cloud Business are not fully geared up in delivering these promises or expectations to their customers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/cloud-solution-fitting-into-the-jigsaw-of-the-current-it-eco-system/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Customer acquisition process in cloud computing services</title>
		<link>http://www.evapt.com/blog/customer-acquisition-process-in-cloud-computing-services/</link>
		<comments>http://www.evapt.com/blog/customer-acquisition-process-in-cloud-computing-services/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 11:50:36 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[Cloud computing]]></category>

		<guid isPermaLink="false">http://www.evapt.com/wordpress/?p=168</guid>
		<description><![CDATA[
As we all are familiar that, Customer acquisition is one of the important phases in the business process. There are certain best practices to increase the customer acquisition rate and reduce churn. Streamlining customer acquisition process will boost the sales of any cloud service provider.
1. Trial Sign-up Process: 
Cloud computing enabled users or end customers [...]]]></description>
			<content:encoded><![CDATA[<p><!-- 	 	 --></p>
<p>As we all are familiar that, Customer acquisition is one of the important phases in the business process. There are certain best practices to increase the customer acquisition rate and reduce churn. Streamlining customer acquisition process will boost the sales of any cloud service provider.</p>
<p align="left"><strong>1. Trial Sign-up Process: </strong></p>
<p align="justify">Cloud computing enabled users or end customers with <em>Try &amp; Buy</em> model which gives an option to sign up for a Trial period, evaluate and go for commercial contract. Cloud service provider should have a  system in place which allows them to define a trial plan and activate their access. The system should automate the life-cycle of a Trial User such as trial plan activation, providing limited/controlled access to the service, deactivation of the trial services based on the trail period expiration.</p>
<p align="left"><strong>2. Effective follow-up :</strong></p>
<p align="justify">Cloud service provider should communicate to its <em>Trial Users </em>effectively in advance to convert them into <em>Paid Users . </em>Sending regular communications will help in keeping the trial users in engage and explore to the additional &amp; attractive services by opting for the paid subscription which will result in maximizing the cloud service provider&#8217;s revenue.</p>
<p align="justify">Cloud service provider should have a system which provide the list of  <em>Trial Users</em> whose access is about to expire . System should send regular communication on the account expiry date and other  promotional service offerings.</p>
<p align="justify"><strong>3. Contract sign-up &amp; tailor made plans</strong></p>
<p align="justify">It is very challenging activity for cloud service provider to sign-up a commercial contract with its customers. In addition to the plans or packages offered by cloud service provider, customers will have their own plans, service requirement and contract terms during contract negotiation. Cloud service provider  should meet their customer requirements by singing up tailor made contract. Cloud service provider system should be able to define flexible service packages, plans, pricing &amp; contract terms.</p>
<p><a name="DDE_LINK1"></a>Cloud Service providers should  provide customers, the choice to utilize their preferred services. Which not only reduces the churn rate substantially but also retains high value and profitable customers. With this, service provider can experience increase in overall organization profitability. Cloud service providers should have a Business Support System and Monetization platform, which streamlines the above discussed customer acquisition process.</p>
<p align="justify">eVapt, a customer management, metering &amp; billing solution for Cloud computing, SaaS, PaaS, IaaS,  and On-Demand businesses. This billing and monetization platform available on-demand and enables service providers to both automate their back office operations, as well as support more sophisticated pricing and billing models.  eVapt is revolutionizing the way Cloud businesses can run and manage billing.  In addition to dramatically simplifying a service provider&#8217;s billing, payments and subscription management capabilities, eVapt can also offer additional benefits to other parts of a service provider&#8217;s organization such as Marketing, Finance &amp; Accounting, Sales.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/customer-acquisition-process-in-cloud-computing-services/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Are we ready with the right strategy in capturing the market, as we are coming out of downturn tide</title>
		<link>http://www.evapt.com/blog/are-we-ready-with-the-right-strategy-in-capturing-the-market-as-we-are-coming-out-of-downturn-tide/</link>
		<comments>http://www.evapt.com/blog/are-we-ready-with-the-right-strategy-in-capturing-the-market-as-we-are-coming-out-of-downturn-tide/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 09:11:40 +0000</pubDate>
		<dc:creator>djandhya</dc:creator>
		
		<category><![CDATA[SaaS]]></category>

		<category><![CDATA[SaaS Transition]]></category>

		<guid isPermaLink="false">http://www.evapt.com/wordpress/?p=160</guid>
		<description><![CDATA[Slowdown has created business needs for high level optimizations, for generating more output with lesser inputs &#38; best utilization of existing resources(capital, assets &#38; skills). Inventing innovative methods of selling products or simply repackaging solutions and services to combat slowdown opens a window of opportunity for existing players. For instance, small operators in telecom &#38; [...]]]></description>
			<content:encoded><![CDATA[<p>Slowdown has created business needs for high level optimizations, for generating more output with lesser inputs &amp; best utilization of existing resources(capital, assets &amp; skills). Inventing innovative methods of selling products or simply repackaging solutions and services to combat slowdown opens a window of opportunity for existing players. For instance, small operators in telecom &amp; pay media industry can opt for co-sharing resources, saving on huge capital investments. Similarly, Enterprise software solution providers, started offering their solution on hosted multi-tenancy model. Today, there are ample opportunities for Infrastructure sharing (passive infrastructure), subscribing to hosted applications &amp; even outsourcing non-core functions. Another aspect is establishing long term, meaningful partnerships in business with vendors, suppliers &amp; customers. When economy is in recession, every business has to go through almost similar challenges. When the ecosystem is strong &amp; synergised, the impact is lesser.</p>
<p style="MARGIN-BOTTOM: 0in" align="justify">Though SaaS and On-Demand model allowed operators to manage the downturn with no Capex and lower Opex, but now its time for solution providers to concentrate on improved quality and further value add offering. Otherwise, competition may take extra edge and Operators / Users may again go back to enterprise solutions, by leaving SaaS as stopgap arrangement.</p>
<p style="MARGIN-BOTTOM: 0in" align="justify">
<p style="MARGIN-BOTTOM: 0in" align="justify">The key is to win relationships with quality service delivery and not just contracts.</p>
<p style="MARGIN-BOTTOM: 0in" align="justify">
]]></content:encoded>
			<wfw:commentRss>http://www.evapt.com/blog/are-we-ready-with-the-right-strategy-in-capturing-the-market-as-we-are-coming-out-of-downturn-tide/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
