Roast our landing page

Hey @ben_chrn, congratulations on your launch. I see how it's solving a big problem, but I'm not sure who it's for. Is this for developers? Sales Ops people? Salesforce administrators? Marketing people? Here are some suggestions.

1. One way to address this is to use language like this:

"If you're a developer who builds integrations with Salesforce, then you understand [problem description: e.g., how annoying it is to maintain processes across different apps ]."

2. Another way to address this is to use social proof, near the top of the page, from your target persona:

"4 out of 5 integration developers surveyed love our product."

3. Another way to address this is to compare yourself against an alternative that people know. For example:

"Unlike Zapier, we allow you to customize your workflows with more granularity." This implicitly communicates that if people are interested in Zapier, they should also choose your product.

@ben_chrn, if these suggestions were helpful to you, then I think you'll like my new website, SplashPad. SplashPad helps you write marketing emails that attract attention and sell your product by providing language suggestions as you write. As you compose your next message about your product, these tips and many more will be auto-recommended to you. I'd love to hear what you think: https://www.getsplashpad.com/.

Hey Benjamin, my 2 cents:

• hero section: what is the benefit of focusing on workflows (thinking along the lines of "Quickpipes: a solution for X that want Y, so that Z"
• hero section: that list of pain points is pretty amazing (I don't have to deal with that, and I'm cringing) -> you could try going with a problem-agitation-solution formula and rephrase your hero section around solving the pain, move the list of pain points up to agitate the pain to the point of "arggggh!", and then present your solution
• for all of the features -> answer "so what?" to really highlight the benefit of signing up
• for use cases -> I'd suggest breaking out those into separate categories + adding descriptions, so that page visitors that prefer to scan can still get the gist (again, focused on the benefits of each of the use cases)
• sign-up form "What do you plan to work on" question -> not obvious from the copy above that all of those ops are an option. Would your early adopters know what they want to work on even now? Can they select multiple options?
• wording around signups -> "I'm interested" -> depending on where exactly you are, it might make sense to manage expectations => are they going to be able to start using Quickpipes immediately, or are they joining a wait list? Same for "take part in building the solution you want and need" - I don't know how much friction this creates for your target audience, personally would be wondering whether it's worth sharing my email to help build something (vs solve my problem).

Hope this helps!

Best,
Ekaterina

Hey, some feedback with the provisor I may not be your target market.

• I get the broad concept from the landing page - something like Zapier for people who code?
• I think your target market is something like "Growth Marketers who can Code", this feels like a nice niche, but it is not clear from your content
• Not sure the problem you solve for these users, against existing solutions, and thus your USP is not clear
• Clear visual examples are useful to my understanding
• Copywriting feels overly complicated (example below)
• Personal taste, hate the orange gradient, drop shadow H1, with orange gradient buttons

I think you should review your copy generally e.g. "Automation hub for rational Sales & Marketing stacks"
What is an automation hub? Whats a rational stack? I would start with a simpler:
"Marketing Automation with a line of Code - Quickpipes helps growth marketers connect apps with simple code snippets."