Launch HN: Mutiny (YC S18) – Website Personalization for B2B Companies

It appears you're already on the hitlists of ad-blockers. So is Segment: They seem to be surviving just fine, regardless.

A few questions (honestly, you don't have to answer them all, esp publicly, if you don't feel like it):

1. Wouldn't a deployment of this on the first-party severs be more effective since it'd bypass the content blockers (server-side sdk)? Is it in the works?

2. What else are the existing customers / prospective customers asking for in terms of features?

3. What's the key functionality you ought to build next?

4. What was the most surprising thing abt how customers used your product?

5. Does it play nicely with other frameworks like Optimizely, Fastly, React, and so on... out of the box? Is the mutiny js-sdk a simple drop and forget? What's the catch?

6. Why the emphasis on B2B? I can't imagine why it wouldn't work for B2C (low-income vs high-income societies, artics vs tropics, europeans vs africans and so on)?

I really like the logo, the colours, and the super neat landing page.

---

A few suggestions from the comfort of the armchair I'm sitting on at the altar of unsolicited feedback from a non-expert:

1. Are you using mutinyhq on mutinyhq.com? If not, you could do so, and link a demo that shows mutinyhq as it would appear to a SaaS employee to someone from the finance industry to someone from Vietnam? Like how you do currently for Brex, Segment, Amplitude, and Carta: I must point out that it take too many clicks to browse what those really powerful examples. I wonder if viewing those could be a tad more friction free like how Facebook lets you view your profile from different PoVs.

2. Above the fold one liner, Turn your website into your #1 growth channel doesn't convey enough: I wouldn't click on (CTA) request invite, tbh. I'd expect to learn more / see faq / view demo (a screencast / video, may be)?

3. Personally, to me, the section with "works with any tech stack", "B2B playbooks to up your game", "More leads, fewer dependencies", "Reclaim your website" is too handwavy without conveying much (except for, works with any tech stack). I think, you'd be better off highlighting the 30 playbooks instead. I went through the three playbooks linked from the front-page and they did far more than anything to convince me to sign-up.

4. I feel, because the final section ends with ...let our team walk you through tactics to increase your inbound leads by up to 50%, the CTA could be Schedule a meeting (with href-mailto / calendly link) and/or Talk to us now (directing to a whatsapp chat or some such for visitors from mobile web).

5. "User adds the Mutiny javascript to their website and defines their website conversion events in the Mutiny UI." This isn't anywhere on the landing page. I wish it was. Stripe.com is a good example which conveys how easy it is to accept payments. The same goes for the editor you've built. I'd, personally, be blown away if I could see a screencast of it in-use, than read a blob of text abt it.

---

What a great product! All the best.

Within the Mutiny product, you can use our website editor to select and update any element of your page without requiring any code changes. The changes you make are compiled into a unique JavaScript file that is distributed globally through our CDN, this ensures Mutiny loads from the location closest to the visitor, making it performant and reliable. Once the incoming visitor loads the website in the browser, the Mutiny JavaScript classifies them based on their information and updates the relevant HTML elements to reflect the personalization (for example, you may change your hero CTA to "Get a Demo" for enterprise companies).

We have worked with customers running client-side, single page applications (using React, Vue.js, Angular, and more) from day 1 and have built our software to handle these environments. We hook into the browser's paint lifecycle using APIs like `requestAnimationFrame` (https://developer.mozilla.org/en-US/docs/Web/API/window/requ...) to avoid seeing a flash of the original content when personalization is rendered. We subscribe to DOM manipulations using `MutationObserver`s (https://developer.mozilla.org/en-US/docs/Web/API/MutationObs...), allowing us to render correctly in a dynamic JavaScript environment.

I took a look at your website and tried it out in our editor - all the personalized changes render well!