Messaging Review of GoRattle.com

Let's start evaluating the homepage of Gorattle.com, fold by fold.

???? What does the headline mean?

• It’s ambiguous - what does taking a pulse mean? What information are you providing me that is not on SFDC/my CRM?
• The cycling of words on headline take too long to change; I don’t see most of them.
• I need clarification on what you offer now. 60% of visitor drop-off happens within the first fold.

?? The subheading is not ending…

• The subheading needs to be shorter and more inviting to read.
• After the opacity of the headline, I am hoping for clarity in the subheading - but - again, it’s a generic line claimed by all CRM accessories SaaS.
• Slack | Teams and the phrase bi-directional alert attract my attention in the second line and seem to be the only relevant words on the first fold.

?? Very overused imagery

• I initially thought the logos on top were customers, but as I scroll down, I see - that’s not the case.
• I see the typical flow of some marquee tools → stuff flowing through the SaaS offered→, ending in organized data. This representation is very dated, and as your product differentiation is not apparent (more on that later), it drives home that Rattle is not different. It’s more or less the same as its competitors.
• This needs to be more straightforward - why does the data need to go to both teams and Slack? It took me 15 secs to figure out it was an either-or situation.
• The dinosaur is super cute, however!
• I don’t see the video demo CTA at all at the bottom.

? Headline is generic

It again drives home that Rattle is just another automation, something visitors can build on Zapier.?

?? Subheading is - too big picture

Why can’t we simply say, 'Automate everything on CRM within your Slack and Teams'? Why does it need to be abstract/philosophical?

?? The three prominent numbers

• Now I realize these are your three selling propositions (after going through everything), but as a first-time visitor - I haven’t been told yet that these 3 are your main value props. So, the numbers don’t bring the same sense of ‘aha!’ as they should.

?? Subheading is - not helpful.

• Same thinking as before - what are human workflows? How do you specifically make RoI reach faster? Isn’t everything we do connect to reaching RoI faster??

?? The three steps

• They make sense, but I am still not satisfied - as you did explain, it’s easy to set up, but I don’t know yet - what I’m setting this up for!
• In the second box - challenge - what challenge? We get specific with the exact use case.
• The ‘playbook’ word is not very clear to a general user. No-code builder is causing me to get apprehensive as I assume something does need to be coded.

?? Headline and subheading

• Run smarter - too generic - a lot like transforming, digitizing, revamping
• The subheading is short and clear - but I am still unclear as the ‘grunt work’ is not precisely defined here or in the previous folds.

?? Productivity

• This part finally gets some clarity on what the tool does. But it could be shorter, and attention could be bought to the earlier call out to 4 hours/per week saved by Slintel sales reps.
• The GIF is super helpful.
• The information I’ve gained should have been the first thing that should have been apparent to me when I came to the first fold.

?? Clear now!

• These folds were helpful - the headline could be more crisp and precise.
• The copy of “Clean the room” is not very clear. Or maybe it’s something the TG uses, and I am unaware. But again, that makes it exclusionary.

?? Talking to your audience!

• This fold does a fabulous job of recognizing that different sales functions from their POVs will evaluate the software.
• Hence, it calls them out - with specific messaging.
• The CTA of 'Add to Slack' is also pretty powerful.

?? The rest of the folds (testimonials and ad-video) are good and serve the purpose.

?? Overall, what needs to be done?

• Explicit callout to actual functionalities of the product.
• The exact pain points and Rattle's solution to the TG needs to be frontloaded. We must be more specific in our solutions and benefits.
• A clear differentiation needs to be established with other RevOps automation tools.
• Rattle’s market positioning vis-a-vis its competitors is not precise. There needs to be a deliberate decision on that front.
• I’ve gone through the other pages, and they are pretty helpful. The challenge is to compress that essence into the homepage and still not be overwhelming.
• Better product-centric language (visual and written) needs to be employed.
• Customer advocacy needs to be centralized in the messaging.