Please roast our landing page 🔥

Hey Nilesh,

Thanks for sharing your project! I've recorded my initial impressions and there are far too many points for me to properly summarise in this comment

Here are some of the main feedback items

Value prop

• It felt like the value proposition wasn't obviously highlighted
• Personally I thought it could be the reporting and insights which was listed as the last item under "Key Offerings", consider moving this towards the top of the page

Who is our audience?

• It seems like companies who can afford to hire on-call staff and are considering purchasing tooling for them would be enterprise level clients
• If this is the case; is the intention to target C suite level decision makers or the engineers themselves?
• If you target the engineers you'll likely need to prioritise documentation, tech details, free trials and tangible metrics they can relate to
• If your audience is execs you'll likely need to prioritise business outcomes, ROI, reporting and social proof.
• Devs often choose tools based on technical functionality while managers choose tools based on business outcomes. Devs can understand platform risk from technical details while managers may need social proof because their risk concerns are more reputational eg. "if I buy this product will it make me look good?"
• There were many points that focused on how existing on-call teams are "bad" or "suck" or create "stress". Try to focus on enhancing your customers rather than pointing out all their potential flaws. If your competition talks about all the upside while your company focuses on all the existing downside, which would leave a more positive feeling within your potential customers?

Where are the docs and FAQs?

• If you're building a tool for technical people they will probably navigate your website like this

Homepage (skimmed) > Pricing > FAQs for pricing definitions if unclear > Documentation or Github

• Personally I wouldn't feel confident making a purchasing decision on a technical product unless I fully understood how it works and its potential limitations.
• I don't know what a Service is or whether my architecture would exceed the 10 Services limit

Execution details

• I can see this is a wix template and this is an early stage project so please don't worry too much about these details just yet. The core business is more important first
• There are some elements of the template that are obviously left there like the social icons that lead to wix or the pricing page placeholder text
• The footer should have a CTA to buy the product not join the newsletter

I know I was quite critical in this review but please don't be disheartened. You've made a good start and there's potential if we can highlight the strengths of your product and make the customer feel excited that their own customer's will have better experiences with uptime and on-call support staff.

Please feel free to ask me any questions or reach out if you'd like me to take another look in the future.

Hi, Nilesh.
Tbh, I don't know what an 'on-call' is but I'd like to answer the third question...

• Your landing page loads fast which is obviously a good thing
• It's surprisingly easy to navigate despite the images. The images don't slow down the page and they load smoothly with the text.
• In terms of content, the copy is straightforward and tells the prospect how your service solves a solution.

I hope this helps.
Well done!