Earlier quoted context omitted.
Taco is free for now, but we expect and hope to charge $5-$10/month at some point - cheap enough be a fantastic value for anyone who uses it even occasionally, but also not a free service that you rightly don't want. We're still figuring out when we should flip the switch but in the meantime, you are right, we need to do a better job of explaining possible future pricing.
So the plan is to generate an initial spike in demand from a group of people marginally interested in something they can get for free, then alienate your core users, who would have been happy to pay from the outset, by introducing a fee, but only once the service is sufficiently overburdened supporting free users ? Well they say any plan is better than no plan... but.... Turn this upside down now, think about 100 use…
If you're going to have a free tier, I'd say limit it to N service integrations (3-5), but definitely make your core users paying close to the start.
If I had a need for something like this day to day, I'd definitely pay... Actually, I'd suffer for a while, then try it, then suffer again, then pay... but that's me and I'm kind of cheap/frugal. Most people will start paying once they see and feel the value.
Also, it's much easier to field requests from a few hundred paying users than thousands of non-paying ones. It's very hard to do conversion from free after the fact... many businesses have failed, burned, burned out, and left their best (paying) users in a lurch following this model.