I can see several use cases for this product.

The first use case, and the one being pushed by the company, is for developers and agencies. A developer will install some JS on the client's server and that will allow the client to log into Candu and change certain things up without screwing up the underlying code. It's a great use case, but the main thought in my mind is the install. Insertion relies on a CSS class/id and so it's not an ideal solution if the client wants to put a button here, a pop-up there, and 15 different things all over the place. Each of these requires separate JS statements (unless I'm mistaken). But for a client that has say 5 areas, they want to change up every now and then? Yes, then this is an excellent solution!

The second use case is for a developer that wants a way to dynamically change things up without the hassle of editing the underlying code. I could run a promotion, display a pop-up, target certain visitors for different things. At the moment, I think this use case isn't totally fleshed out. I would recommend the Candu team implement more leadgen features, such as funnels, lead capture forms, and multiple-step features.

As for everything else, I think this is a very impressive new product. It is clear that a LOT of development time went into its creation. It does take an hour or two to figure out everything, but it's incredibly well thought out. The WYSIWYG builder is top-notch and so are the templates.

Pros:
- Incredibly well thought out and well-designed application
- Awesome analytics and tracking data
- Loads of documentation and videos with great production value
- Amazing team
- Amazing deal value with no limit on views, domains, etc., only seats

Cons:
- Needs additional ways to display content. Candu can only display content immediately (unless I'm mistaken). It would be of immense value to display content after a time delay, page scroll, button click, etc.
- Adding new content items to a page is NOT user-friendly. Unless I am mistaken, each time a client wants to add a new item of content (distinguished from editing existing content), a developer has to insert a new javascript statement on the webpage and add a slug (identifying the content) and selector (identifying the CSS id/class). What is a better solution? A developer adds a single Candu script in the header and the end-user goes to the Candu website, creates the content, and links the content slug to the CSS class/id via the Candu website. I cannot fathom why it's not currently implemented this way.

Conclusion
I think this is a top-notch deal. If you're solo, get at least 1 code. If you're an agency, get as many codes as you can before your credit card is declined.