New Landing Page - feedback much appreciated

Hey Colin,

I will share some thoughts but first I'd like to ask - who is your ideal customer?

I ask because some of the language is geared towards developers and some is geared toward business units.

Here are my thoughts overall (very long, sorry):

The headline feels a little stiff, jargony and could better call out benefits.

Here's why I say that:
"Design" is a little ambiguous even in the software world. That can be UI, that can be architecture. It can be confusing depending on your ideal customer. If they aren't software development folks, they may wonder what exactly design means in this context.

"Consolidate" also has more than one meaning. It could mean that you're fortifying something or that you're reducing multiple things into one or fewer. It's also a heavy word.

"without coding" - Coding can mean different things to different industries. There are medical codes, compliance codes, etc. To the software folks, coding means writing code. To others, it might not be as clear.

The current benefit is that you can build applications without writing code but that's it.

If you took a more conversational tone, you can draw out extra benefit with a little wordsmithing, like so:

"Create applications for your business without writing code"
"Build applications for your business without writing code"
"Create and connect applications for business without writing code."

"Create" or "build" is a little more conversational while keeping the same meaning.
"for your business" is a direct beneficiary. They're improving their business.
"without writing code" is a direct benefit.

This is long-winded:
"Enterprise-grade no-code platform empowering you to leverage customer, employee and operational data for better decision-making."

If you met me in line at a coffee shop, would you say that out loud as a way to describe your product?

If not, how might you say it in a more conversational way?

Your headline establishes that your product is no-code. You don't really need it in the subhead.

Your headline and your subhead should be treated like a continuation in one conversation. They don't need to be written as separate items.

Your headline should get the user's attention and establish the topic. Your subhead should support it and continue the reader down the path you want them to go.

Using a sample headline above, here's an example of headline to subhead.

"Create applications for your business without writing code"
"Turn your company's data into software that helps you make decisions, without having to bug your developers."

If I may be candid (not trying to be insulting), the rest of it reads like you made a list of topics you wanted to cover and wrote to satisfy that list. You outlined that in your post here and I think the landing page feels that same way.

It doesn't feel like a conversation with a potential customer.

For example, the callout heading "Why is corebapp unique as a no-code platform?" doesn't sound like a question that I might ask myself.

If I were wondering why corebapp is unique among no-code platforms, I might say to myself something along these lines:

"Another no-code platform? Why is this one any different?"

If you have any research on your ideal customers tone of voice and it's aligned with your own brand's tone of voice, write accordingly.

You could have a little fun with it:

"Another no-code platform? Yeah, we are, but we're different".

Then go into your six bullet points.

In those bullet points, you say "no-code" in 4 of them. It almost feels like the content is written to try to grab some SEO based on keywords.

Try to turn those into a conversation.

When I read through them, I pull out the following benefits:
Nothing to download - I can do everything in the browser.
I can build applications using reusable building blocks, templates or go from scratch.
I can build and deploy without going through the typical software development life cycle. (no developers, no waiting on deployments, no release schedules, etc)

"What problems do we solve?" - Again, feels like a bullet point rather than a conversation.

The points in this section are very wordy.

"What can you build within the..." - Icons in this section don't match the rest. Why the color change?

"How does corebapp platform work?" - Too wordy again. Boil it down the basics without jargony details. To me, the gist is:

Create a workspace > pick an application template OR start from scratch > connect a bunch of data > done.

You have 4 call to action buttons with 3 distinct calls to action.
"Join Beta"
"I want to try the platform"
"I want to build my business app"

Be consistent on the call to action buttons so that the user is very clear on what will happen if they add their email and click the button.

Also, your term for joining the beta is inconsistent:
"Ready to enter our beta?"
"Join beta"

Pick one word. Make it part of your ubiquitous language. If you were describing the overall goal to your internal team, would it be get customers to "Enter the beta" or "join the beta"?

Also, "Enter our beta" for some reason makes me think I'm entering The Thunderdome or some kind of competition.

Here are a couple of design considerations:
The footer background color is the only element with that color. If that is a brand color, use it on the page somewhere else to solidify that brand color. In this example, you could swap all of the icons to the use that same color.

The animations in the UI screenshots are inconsistent. It makes for an odd feel.
The login screen animates up from the bottom and then animates up before the transition
The second screen transitions in and then grows up from the center
The third and fourth screens transition in and then slide down from the top

None of those screenshots really sell what the product does.

For example, there is no reason to show the login screen. Every application has a login screen. Many have social login features, so that doesn't sell the value.

The second and third screen sort of give you a hint but without context, they just look like lists of data.

The fourth screen is empty with a drawer menu. It actually kinda looks like your product is not complete.

Finally, I would move the Blog and Public... links from the header to the footer. At least until they have lots of meaningful content.

I know that was a lot. I hope there are some insights in there to help.

Good Luck!

Hi Colin!

Currently, the landing page consists of a lot of text, and I don't see any screenshots/videos of the product. A video in the header or a couple of screenshots throughout the page would be a great addition. Personally, I won't sign-up for a product if I can't see anything of the product itself.

Also, when the HubSpot chat widget is open, you can't click on the social icons (when the viewport is smaller than 1900px).

hey, I have got something for you can we connect? @Colin@CBA