A big decision early in the lifecycle of a B2B SaaS Company is the technology, domain, and infrastructure to host your website on.
Picking a CMS is pretty straightforward. I recommend one of 3 options:
If you have the luxury to pick one technology platform for both your website (CMS) and marketing automation, I recommend Hubspot. The integration of all the pieces, including many tools that you have to buy separately when using, for example, Wordpress, makes it a no brainer.
If you already use Marketing Automation tools other than Hubspot (Marketo, Pardot, Mailchimp) and have invested in those, a good alternative is Wordpress. While it has less out-of-the-box tools vs. Hubspot (you’ll have to use plugins for things like SEO optimization, landing page optimization, analytics, content planning, and online chat) you’ll still benefit from a mainstream platform with a wealth of capabilities, templates, and skills that are easy to hire.
A third option is a static CMS. While this requires more technical knowledge in your team, it has benefits to have 100% control over each page. You can optimize speed and experience to exactly match your audience and content needs, and if done well, can outrank every other CMS for SEO benefits. It takes more work though, and here are some “tools” to still have some traditional CMS benefits while using a static site.
Subdomain (blog.kalungi.com) or Subfolder (kalungi.com/blog) ?
The short answer is Subfolder.
Keeping all your content on one domain is ideal for SEO purposes (Google tries to weigh both options equally...but still don’t do a great job at that), it’s easier to manage/maintain and manage and potentially cheaper from a DNS perspective.
There is one exception to this advice. If you are able to manage a great static website (this requires engineering time and expertise) having a main site with a small number of great pages could be great for SEO, and in that case, you will have to get a subdomain for your more dynamic content (Blogs, Landing Pages) that your marketing team can maintain. More on this under the “Technology” section above.
There are many opinions on this topic, so feel free to find out where I got my input from:
When you pick your CMS, this can point you to certain hosting options (HubSpot CMS is hosted by HubSpot, and they run on Amazon Web Services, Wordpress comes integrated with vendors like GoDaddy and a static site can be run on for example AWS or Azure).
My recommendation is to follow the hosting environment that comes with your CMS, and not spend too many cycles on this decision.
Once traffic grows you can optimize performance with various caching solutions, and you can worry about that when that time comes. In reality, AWS and others already do this for you in most cases.