Landing page feedback for newly launched headless CMS

Hi @mike183, congratulations on your launch. This looks like a useful product.

Some suggestions.

1. I don't know what "digital experiences" or "content experiences" or "content across any channel" means. Can you provide examples? Some suggestions are:

"LexasCMS helps you produce blog posts, marketing emails, emails, tweets, Facebook Ads, and more. LexusCMS makes it easy to write your content, produce variations for different channels, and schedule it for delivery across different channels."

2. Remove extra words.

I think you can remove words like "All in one place" and "centralized" because that is implied by your screenshots.

3. State the customer benefit from your features.

For example, why is a globally distributed CDN important? You could say something like: "Your readers will never experience lag while waiting for content to load because content is delivered through our blazing fast CDN."

Or for another example: "Never show readers content in a foreign language. With our localisation support, you can make sure that your readers see content in their preferred language."

@mike183, was this helpful?

If so, then you may like my website, SplashPad. SplashPad helps you write about your product in ways that attract attention and sell. Our current version focuses on marketing emails, but we plan to release feature for landing page copy soon. https://getsplashpad.com.

Hi Mike, here is my feedback - https://screencast-o-matic.com/watch/cY10YiCRNk. It's pretty honest and hope it helps

I think your audience doesn't really know what headless content management is.
Therefore they won't understand the need for one.

The text in the white section under the hero is too cramped.

• "A better way to manage content" is too unfocused.

• What is the problem that people in your vertical are trying to solve? use that instead.

• For example: Auto-pilot for content management - is already much better.

• Use images of your platform in the explanations.

You have a minor spelling issue: https://app.pagewatch.dev/1b11b899c2aaeb2f52d5e66ad1d51c2322f105c5/dashboard

I feel you are missing some screenshots / expectation of what the actual tool looks like. Do you have a wysiwyg editor? Content types? A screenshot or online demo should really help.