Much prefer is on boarding is baked into the design of the app. So literally hide / alter the page based on where they are in the setup / learning process.
Because I'm dumb and short of time, I could only take it at face value.
I sort of want to come away lusting to have the feature on my site.
Be great to see some of the possibilities demo'd on the page in the future !
Pricing is linked to in the footer: https://www.getonboarded.com/pricing
I do not want pricing to be an open conversation. That sounds horrible to me.
To take a wild guess - maybe you think that an open conversation is good for the customer because it represents flexibility? To me it doesn't. To me it screams "UNCERTAINTY!" and the less of that I have the better.
I'm at the tail end of roughing out the high level design of a pretty large (as in complexity, not number of users yet), Enterprise SaaS thing.
In any case, I've had to probably glance at 5,000 things and of those, look at 2,500 things, and of those play with 1200 things, evaluation 700 things to end up with about 300 things (currently) that will turn into probably less than 150 things in production.
At the front end of this process, I probably unfairly dismissed some possibly viable candidates for technologies or services. Which is unfortunate and ultimate unfair to the vendor.
The two top things that made me go away (unless HN or somebody pointed me back) was:
- The front page, the about page, and the top blog post don't really tell me what the company is or the product is. IF I get pointed back to look, I'll poke around github to see if some brilliant marketing maneuver made them put their "about page" from their website into the github Readme.md. (I'm looking at your, Weave)
- I can't find a way to put the right number of zeros behind the price in my estimates. Now. 6 Months. 12 Months. 24 Months. 36 Months. It has to be easy-to-understand (because I am very simple), and look thought-through and stable.
N.B. 1) Our use case probably isn't in your sweet spot, but who knows, you may shift.
N.B. 2) Not trying to be harsh, but I was up to my ass in alligators 2~3 months ago, and I would have tossed the link and not looked back.
I am never interested in building a social profile or entering preferences to some app I'm unfamiliar with. Like others comment, I'd like to get to using the product ASAP.
Signing up is already a hassle that should have been kept to a minimum.
Making me fill out, really anything, before I can drive the app around at all is a sure way to make me "nope" right out of there. Now, I understand that you said "don't have to", but a big screen of form(s) is an intimidating clue that you will want more from me than I suspect I am willing to give. I don't even know who you are yet.
Incrementally adding information during the use of the application to make operation/data/context more relevant or useful is fine. Not filling out a list of interests, for gods sake. And not 20 things, mind.
So this isn't for the user's benefit.
If something is increasing retention; and creating more satisfied customers (so much so they are telling other people about you)... then it is benefiting the user. Actions clearly indicate it's benefiting the user.
I think it is. You're understanding what problems they need solved so you can do that for them (and thus increase retention and conversions).