I'll critique your landing page for you (rebooted)

https://medium.com/artisana/postpilot-8ba6ffa3030b

Hope this helps.

I've closed this thread but this reply to another comment may be of help. I'll do this again next month. It'd be great if you asked again then.

I've closed this thread. Will do another one next month. Can you ask again then?

Will do another one next month! Hope to see you then.

I don't know enough about design to comment on that aspect but I will say I don't disagree with the comments.

How to put it...? Your design is very ascetic and severe, almost hospital like. Homes are supposed to be warm and welcoming. Maybe you could throw in some vector images to reduce the seriousness of your site?

https://medium.com/artisana/mentorcruise-6db4973ac234

Hope this helps. Maybe I can find a mentor to help me critique web copy better?

The heading We Tell Your Stories doesn't seem to match the actual service you provide which is of video editing. A better heading would be "Make your videos pop".

I like how visual your website is as it should be for a video editing service. Can you add some samples of your work annotated with your contributions to the final product? I saw an example video by Oliver Bink but I couldn't tell what value your team added.

Other than that, your copy looks ok.

https://medium.com/artisana/slickaccount-da4335d3b5cd

I can't quite figure out the problem you are trying to solve. Are you trying to help people who are too busy to send reminders to their counterparts asking for documents OR are something else? I'd try to answer this question more clearly.

Maybe it's just me but I couldn't understand what this line meant - notify your client with invalid documents. Are you planning to notify clients who sent you invalid documents or are you planning to notify clients by sending them invalid documents? I know the second option makes no sense - who'd ever send someone invalid documents as a notification? - but I'd still ask you to rephrase that sentence.

Lastly, you still haven't explained why I'd need Filerequest. I'd replace Automated data collection with a heading derived from a customer pain.

Say people have been telling you they're tired of sending reminders - your heading could be Tired of asking for documents?.

If they say that they often forget to send reminders for documents, your heading could be - Never wait on a document ever again or something like that.

The heading is great but the main copy is very light on details. You add more information about Albert later but maybe you could incorporate some of those details in the main copy?

Oh, I get why you picked that particular image. It's supposed to evoke Albert Einstein? If so, I'd heavily play up the Einstein angle in the copy.

Also, there's a typo in gitft.

With code refactoring, are people willing to wait for experts to give their feedback which could take hours or days to stabilize?

You know there are going to be a dozen different opinions about your code refactoring and it is going to take time before the best way to refactor your code surfaces.

Someone like me would appreciate timely feedback because I'm rarely in a position to delay pushing out my code. Can you promise a minimum SLA for feedback?

Other than that, your copy looks fine.

LOVE IT.

To the point, consistent in tone, targeting a specific pain point, irreverent, unapologetic - it's great!

The next question is how you plan to find potential users. You're targeting a really really small market of people who are (a) aware they're procrastinators (b) but have the willpower to consistently work for a year (c) and willing to lose 650$ (d) right now (e) and trust some hustler on the web who's telling them they might lose money with him.

Can't imagine this is a very big number.

Hmm, does there need to be a huge login box stretched across the top of the page above the fold?

Your tagline - Duolingo but for math - is actually quite good. The rest of the content about Quantum Mechanics and payment does not add to your USP of being a math learning tool.

I'd demote the "Counting to calculus to QM" somewhere below the fold and drop all justification for pricing. You aren't going to convince anyone to pay for an app they don't need because the app doesn't show ads. Calling it out doesn't add any value.

https://medium.com/artisana/fireadmin-a3bb60d096c6

Hope this helps.

Your signup input field is waaaayyy below the field and is obscured by your cookies policy disclaimer. First, do you really need such a massive cookie policy toast? Can you make it more discreet? Second, can you move your CTA above the fold?

About your copy -

Your copy is unfocused. It highlights a feature - location based notifications - and an opinion - right reminders in the right place - but does not tie it back to a specific user archetype and a specific business problem it is trying to solve. Even if I were looking for a location based notification system, I wouldn't realize you guys may have a solution to my problem.

Also, what's up with using text inside images? Do you want to avoid getting crawled by search engines?

I'm not sure how to sell this product.

If you are targeting serious developers who make complicated backends talking to multiple endpoints or use a DB store, I'm not sure how a visual interface is going to suffice because such developers tend to know the hard limits of having a one-size-fits-all visual interface to create products. The 'glue' code your visual interface creates for them is actually the easy part of creating backends.

If you are targeting non-technical folks, your language is very technical starting from the indiscriminate use of REST APIs and backends in your copy. Such folks will need a LOT more handholding by way of gifs, blogs, and tutorial videos to start trusting Pipegears.

Think of IFTTT - even their name evokes the exact phrase a person says to themselves when they imagine a workflow. Their entire website is chock full of 'recipes' - another evocative word - describing workflows people can easily understand.

Your copy will need to be like IFTTT's, imho.

We can talk offline if you want. I feel you need to think through your product offering and target customers. Hope this helps.

Here's what I look for while reviewing copy -

0. Do I Name things (link to an earlier post on the hidden power of naming things on Medium)? Name the customer pain you solve, name the supported architectures, name the blog engines, name channel partners...name everything you can. You're absorbing some of their credibility when your product can confidently state that, for instance, it integrates with WordPress OR generates JSON etc.

If you take nothing else away from this list, I'd ask you to start naming things.

1. Is the headline and subheading addressing a customer pain point or simply listing out product features? Very often, I find that the content right below the fold is actually better suited in the headline/subheading.

2. Is the headline an imperative? If not, start your headline with a verb. E.g., consider the sentence Start your headline with a verb. It's an imperative statement. You want your users to believe that you have a roadmap which will help them achieve their desired end goal. If I had written It is better to start your headline with a verb, you'd skip right past this suggestion as a nice-to-have, right?

3. Deeply understand your primary customer archetype and address your copy at their pain. E.g., if you're selling box subscriptions for vegetarian dog food, your copy should reflect concerns of people who'd go looking for vegetarian dog food and subscription boxes.

4. Focus on UX writing. E.g., it is the difference between hotel booking websites inviting you to Check Availability versus telling you to Book Now!. You want to make sure your copy matches the typical user's state of mind when they are interacting with your website/app.

5. Don't be afraid to adopt a tone or an attitude.

6. I'm not a designer per se but I'll definitely say that your fonts matter. A cursory search will show you effective font pairing. Likewise with font size - make it big. As such, small font size don't hurt but huge, clear font sizes definitely help.

I can do Hindi and probably Marathi because the script is similar and my wife speaks Marathi. If it's some other language, I can try to help using Google Translate but my grasp of idiom will be poor.

I could summarize what I look for while critiquing web sites. You could apply those rules on your site?

https://medium.com/artisana/gif-com-ai-1121f9016945

Longish feedback. Hope it helps.

Will do!

If things are already working and you're getting inquiries via the website, I'd be wary of changing things.

I'd change a few little things - maybe have a soccer player's silhouette in the dashboard to evoke the joy of playing high quality soccer. Right now the dashboard could be for any generic service.

I love the How it works section. It's very crisp.

Love this. Can I ping you offline for a testimonial?

The value prop and language seems clear to me.

I might want to

1. add a few exhortations like 'No coding required'

2. include name and logos of major blogging platforms like WP, Blogspot, and Ghost that your widget supports.

I understand that your widget is (probably) an embedded js snippet but the average blogger will be looking for familiar names to help them feel comfortable about using your widget.

Anything that makes your prospective users feel at ease with your product is a good thing.

What BackendLab can do is clear but what isn't clear is why I (the developer) need it.

Does it save time? Scale better? Allow users to do interesting things with minimal effort? How much work will I have to do to finetune your autogenerated API? Is it worth the little amount of time I'll save by using BackendLab? Is there a well known API re-implemented using BackendLab?

If your copy doesn't answer those questions, you're going to lose prospects.

https://medium.com/artisana/autenti-ca-afc16d7479db

Hope this feedback helps.

How can I help you out?

I'm not sure what you meant by this. Feel free to jump in and give feedback if you feel you have something to share.

https://medium.com/artisana/cloudsprt-5484449c45b7

Thank you! Hope the feedback helps.

https://medium.com/artisana/hivis-io-f616b6daadfb

1. I updated the headline and the subtitle to focus on what exactly your product can do for the user.

2. And moved the section where users can enter their own keywords above the fold. People love to try stuff even if they’re never going to buy your stuff.

3. I would do away with the code snippet. It adds nothing to 99% of your audience. I’d use that space to explain where picking the first Unsplash image for a keyword might be sufficient for a user.

Your business case is a little iffy — I can’t think of any user demographic which would be interested in trusting an API to insert random images into their collateral. Maybe I’m not seeing it the right way...