A little feedback: blog posts about how to use small interesting features can help prospective users form a simple mental model of how Hirundin works. That can help the big concepts presented in the site to stick to something the user already sees some practical value in.
Or: maybe work with a persona for a drive-by visitor who could really use Hirundin but doesn't have a lot of time to read about it or try the demo. Maybe do A/B tests of showing a simple task how to ("how to setup an A/B test and goals with Hirudin"?) and see if it improves the time users spend on the site/demo.
Edited to add: looks really interesting and likely to have big positive impacts for many teams.
The plan was for the next month to be building out a library of how-to feature/benefit pieces, and all the documentation, so that fits with our roadmap nicely. Nice to hear we're probably on the right track there!
Or: maybe work with a persona for a drive-by visitor who could really use Hirundin but doesn't have a lot of time to read about it or try the demo. Maybe do A/B tests of showing a simple task how to ("how to setup an A/B test and goals with Hirudin"?) and see if it improves the time users spend on the site/demo.
Edited to add: looks really interesting and likely to have big positive impacts for many teams.