5 ms·
I really want to use Algolia, but their pricing model just sucks. What's the point of a 14 day trial? If I'm going to spend a couple days hacking something usin
by hamhamed 11y ago
I really want to use Algolia, but their pricing model just sucks. What's the point of a 14 day trial? If I'm going to spend a couple days hacking something using Algolia, I wouldn't want it to end in 14 days. And it's extremely expensive..$49 a month for the starter package?
No thanks.
Their free plan can only store 1000 rows..that's really small. What they should do is at least 100k row for free (I'd even go to 1 million), but charge me the moment i surpass X amount of requests. That way I would be comfortable using Algolia from day 1 of my startup and stick with them forever.
- pbiggar 11y agoIf you're building a startup, you should consider $49/mo to be a trivial expense and just pay it. I'm aware that you'll need to use dozens of services and the cost may well achieve $1000/mo, even in the early days. Doesn't matter, just pay it. Startups are about growth. Paying for SaaS allows you to focus on your product and to grow much more quickly and aggressively than you would otherwise. It's silly and wasteful to even think about not spending $49/mo for the kind of leverage you'd get from Algolia.
- hamhamed 11y agoNobody said my startup is going to make it.. I need to test it out on the side, let it run a couple of months before I make a real move. And if it's limiting me on 1000 entries my startup won't be able to work on it's full potential
- biot 11y agoWith anything you're trading money for time. If you don't want to pay their more than fair asking price, then use your time to roll your own solution. It probably won't be as good but, as you say, your business may not succeed so why allocate resources towards the best solution before you've even proven your business model?
- hamhamed 11y agoBecause their solution is KEY to my early stage startup. Fast to iterate, and easy to scale and debug.
- teacup50 11y agoAs someone who bootstrapped a "startup", there are plenty -- PLENTY -- of non-SaaS solutions that: 1) are perpetually licensed. You don't have to worry that they'll disappear on you, or jack up their prices. 2) are cheaper. far, far cheaper. 3) are just as effective. 4) enable growth by: 4a) Being extensible (server-side code execution enables a lot). 4b) Being economical (SaaS chews up a runway like nobody's business). 4c) Building valuable (in the business agility sense) internal expertise. 5) don't incur the overhead of managing accounts for people across a different provider for every service. If you're growing fast, having a single account switch to flip makes a real difference to new-hire integration overhead and effectiveness. Hard dependencies on costly software subscriptions is rarely a net win for a startup.
- robot 11y agoSo in this case you favor installing and maintaining elastic search? I don't think so. It seems it would come with more than $50/month cost in terms of maintenance and hosting time, as well as the extra hassle. There is also the masters of search: https://www.google.com/work/search/products/gss.html#pricing_content https://www.google.com/work/search/products/gss.html#pricing... but looks like the price goes higher when you have a lot of queries. Also you probably can't customize the query result as neatly as algolia
- teacup50 11y agoYes, I'm in favor of installing and maintaing "elastic search". It's not rocket science. http://en.wikipedia.org/wiki/Elasticsearch#Users http://en.wikipedia.org/wiki/Elasticsearch#Users
- BadassFractal 11y agoOne thing they all have in common is that they're no longer 2 person shops. When you're at a single digit pre-PMF size, spending time on setting up your infrastructure and tooling is irresponsible. At some point the cost of the SaaS becomes greater than the cost of paying someone to maintain the tool, at which point you can do the switch.
- tptacek 11y agoTangent: Three problems in practice with the business model you propose: 1. Most free plan users will never convert to paid, but the company is still on the hook for supporting them; every dollar spent supporting non-converting users is a dollar not spent serving paying customers, so you have to believe you don't have a productive way to spend each free-plan dollar on real customers in order to have a free plan. 2. The free plan users are disproportionately going to be pathological. 3. Having the free plan is going to make it hard for paying customers to immediately opt-in to paid, rather than trudging through the free plan. But trudging through the free plan also makes a purchasing decision more complicated. If you have a product that creates enough value for paying customers that they would be willing to pay for it without a free plan, then having the free plan can actually make it harder to acquire those customers. Paying for something is a forcing function to integrating it and getting it working, rather than having it molder on a stack of todo cards in Trello.
- hamhamed 11y agoI don't see Asana having a problem with this. The moment the team needs to grow bigger than 10, they have to pay, and that's a good problem to have and I don't mind paying more than 49$ a month because it's too late to change and it'll cost even more if I did. If I ever happen to have lots of requests, then I too do not mind dishing out way more than their plan to get there.
- jonbishop 11y ago$49 is expensive? It's not worth an hour of your time each month to offload search to them?
- rip747 11y agoyou could implement them in a portion of your application and see how things work out. For instance, have them as the search provider for a couple of your more popular products categories or something and fall back to your current solution for everything else (a little A/B testing if you will). by doing so, you can avoid hitting the limits and see if your ROI increases before implementing or dumping them.