Hacker News new | ask | show | jobs
by mkilling 4054 days ago
I'd love to get an idea of the pricing before I sign up for a trial. I don't want to spend time trying out a product that will end up costing more than I'm willing to pay for it.
1 comments

Correction: Ahh I see what you're saying and agree. I wouldn't think about using a service that carried with it so much inherent uncertainty.

Pricing is linked to in the footer: https://www.getonboarded.com/pricing

The thing is, we're just focused on the free tier right now. When you've onboarded lots of people and decide you like the product, pricing is an open conversation.
> pricing is an open conversation

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.

Or even worse: "If you have to ask, you can't afford it."
First - apologies. There is a point to this. I apparently like taking the scenic route to get there.

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.
I am 12 months away from having to embed on-boarding into our project, and I will come back and see what you have at that time. But, please, for the love of getting anything past the CEO/CFO/Board ... let me rough out a guestimated cost (for us; pricing for you).

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.

Gonna agree with others that I don't like "pricing is an open conversation". Sounds like you just don't know what to price it at. Why not just start with something and then adjust up/down as needed?