This is truly unethical. Changing the original terms of use feels completely wrong to me, and frankly, quite deceptive on the part of the Pickaxe team. They attracted customers to purchase LTDs under false pretenses.
If you make a promise, you should keep it—your word holds significant value, potentially worth hundreds of thousands of dollars.
Had these limitations and usage policies been clearly stated from the beginning, people would have made informed decisions, and the backlash we’re seeing now from the Pickaxe community could have been avoided.
You may see your company growing, but your integrity is now in question.
At the very least, they should offer additional shares or compensation to early supporters for misleading them—especially if they have no intention of honoring the original agreement.
1 Like
Can you explain to me a real use case that this issue doesn’t have a viable work-around?
50 documents and/or links is a real limitation, but it’s not hard to consolidate multiple documents into a single document. That only becomes an issue if the compiled document is now larger than Pickaxe allows.
Rather than focus on how this makes Pickaxe function differently and is therefore now inferior — can someone spell out the specific cases for which no workaround exists?
1 Like
If you’re packing various genres of PICAXE tools into one studio, the limit is the bottleneck. For example, if you want to create a travel advisor in one country, if you want to create a professional assistant for each prefecture, you will create an advisor for each studio, not for each picaxe.
In other words, restrictions affect whether the studio has an expertise or PICAXE has a specialization.
As I write this, I want to create a TripAdvisor. ; )
If I want the studio to be specialized, I can use the documentation on the Pixel in the studio, so it shouldn’t be a problem.
I think most LTD buyers don’t really understand the possible outcomes when an app is being offered. This is basically gambling, and you’re placing a bet on Pickaxe to win when you bought from wherever you got it. Would you be happier if they failed and you couldn’t use it at all?
If winning means throttling back the POTENTIAL for you, because really, if you’re actually making money with it, then upgrading to PRO wouldn’t be an issue. If you think about it, Pickaxe was designed for it’s users to make money with AI, and also for Pickaxe to as well.
If it’s for personal use, then you still have a pretty awesome tool for a reasonable price, even if it means getting you’re own API key, which still makes it pretty reasonable for what you can do with it.
The only thing that irked me a little bit, besides the work to clean up the bots and studios after the UI update, was the Pickaxe Icon flash on the FAB embeds. Which, I don’t know, maybe @nathanielmhld or @admin_mike could let us buy our way out that like buying more documents and actions next time they decide to offer that.
Go make money with Pickaxe, and I guarantee you won’t be complaining about it.
3 Likes
Hi @paulfio I actually didn’t know about this issue! Could you send an email to info@pickaxeproject.com about it? We are not intentionally trying to flash our icon on embeds, if this is happening it’s a bug and we’ll fix it!
Hi Nate,
That is good news! I mean, that it’s not supposed to do that.
Thanks for responding, I appreciate it!