(no title)
steveruizok | 5 months ago
I expect we’ll do extended trial licenses for teams that are serious but just getting started, or are pre-revenue pre-funding; and there’s a hobby license for non-commercial projects. Pricing… never ends.
steveruizok | 5 months ago
I expect we’ll do extended trial licenses for teams that are serious but just getting started, or are pre-revenue pre-funding; and there’s a hobby license for non-commercial projects. Pricing… never ends.
abxyz|5 months ago
There is a big difference between how startups buy and how enterprises buy, but it seems you’re treating them as equal in everything except budget.
Anyway, easy for me to say that, I have no stake. You know your customers… but as sales-aware observer, it seems very counterintuitive to make low budget people go through a sales process.
steveruizok|5 months ago
When I was doing pricing discovery and asking early adopters what they would pay for tldraw, almost all the teams I talked to either said "nothing because we don't have any money yet" or a number between $5,000 and $10,000, with a handful of outliers. In the end, my solution was just to put a price on the thing and then find ways to provide for everyone else, including PRPF commercial teams. In 3.x our solution was a watermark, which caused other problems for us; but this discussion made it pretty clear to me that we need to have a better answer for these teams in 4.x.
That said, we've at least got the startup sales _process_ as close to self-serve as we can. Someone still needs to validate the size of the company and send a Stripe link, but 20% of startup licensees were delivered in under 24 hours and more than half are done in under a week.
max1990|5 months ago
But the bigger issue is there's no clarity of what this will cost if the startup works out and grows. So you spend a bunch of dev time building something that uses TLdraw and then its completely unknown if you can keep using it in the future as the cost could be $1 or $1 billion.
Any startup would be crazy to depend on a service with unknown pricing.
Sure you can email them and get the pitch by a salesperson, and use a bunch of time to get some long legal agreement with pricing in it somewhere, but that's what you do for massive custom-built enterprise tools. Not for on SDK in your stack. I don't think the opaque pricing model is common or viable for this kind of SDK. Imagine if payments providers or authorization providers or hosting all just had blank pricing and a "talk to us" button.