<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Concise differences between hubspot.com and WordPress hub plugin in Sales Integrations</title>
    <link>https://community.hubspot.com/t5/Sales-Integrations/Concise-differences-between-hubspot-com-and-WordPress-hub-plugin/m-p/397226#M2727</link>
    <description>&lt;P&gt;We seem to have a spirited discussion going on here, and there are some relevant points being made on both sides.&amp;nbsp; As someone who has used HubSpot Marketing for a decade, I would say that the main reason I have always remained on WordPress and never gone to the HubSpot CMS is really about flexibility.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have never had programmers on staff, but there are thousands of WordPress developers out there, many of whom do freelance work at reasonable rates.&amp;nbsp; I have always enjoyed the flexibility to work with my favorite freelance developers to build the functionality I need into my WordPress site - functionality that at times simply would not be possible in the HubSpot COS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For me, the content customization HubSpot offers has never been practical from a workload point of view.&amp;nbsp; I just don't have the staff I would need to create and manage all those variations.&amp;nbsp; As a result, that advantage&amp;nbsp; has never outweighed the flexibility of hosting my site on an open source platform with a wide variety of potential programming suppliers.&amp;nbsp; I certainly admit that it is a compelling benefit&amp;nbsp;for the right customer.&amp;nbsp; It just isn't me.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jan 2021 16:44:36 GMT</pubDate>
    <dc:creator>trevordjones</dc:creator>
    <dc:date>2021-01-06T16:44:36Z</dc:date>
  </channel>
</rss>

