Perplexity Spaces

So yesterday I signed up for Perplexity Enterprise for my entire team and today I canceled it. I know a lot of you love perplexity, so I wanna talk about what made me sign up for it in the first place and why I don't think it's a good fit for me.

Hopefully this video will help other people decide if perplexity works for their case. So this started a week ago where I made a video about all the large language models.

And in it I said, I don't know why anyone uses perplexity anymore. And a bunch of people in the comments told me how perplexity is amazing.

And upon giving another look, I realised they added a bunch of new features. So if you don't know, perplexity is kind of like a large language model rapper, although they do have their own large language model and a bunch of cool features.

There were two features in particular that made me immediately think, yes, this is what I need and I'm switching right now. The first is that you can use most of the popular models inside of perplexity...

ar client and then we can use that project anytime we're creating content or developing strategy or brainstorming for that particular client. This process by far has been the biggest advantage I've seen from AI.

And the great thing about Perplexity Spaces is that we could share them across our team, which you can't do in Claude and Gemini. So everything just seems perfect, right?

That's why I bought enterprise. That's why I made the video yesterday about how excited I was about perplexity.

But over the last 24 hours, I spent a good amount of time with it and the output just wasn't hitting right. The first thing I noticed is that the brand ambassadors I made just weren't doing a good job representing the client.

They were still giving me generic output instead of output that sounded like it was made specifically for that client. So I did some research and I realized that Perplexity's context window is only 4,000 tokens by default...

es it really efficiently. After doing some research on perplexity, my understanding is that it is retrieving only the content that it thinks is relevant for your query.

And to save on money, it really skimps on how much it returns. Unfortunately, that alone makes it unusable for 90% of my use cases.

The second problem is that even though perplexity is calling these other models, it's calling it through the API. And so you're losing a lot of the infrastructure that's set up within the models themselves.

Now, I knew this was the case, but I didn't know how much of a difference it would make. Again, after doing some research, my understanding is that within Claude, for example, instead of just sending your prompt to the API, it's running additional prompts to check and reformat its response.

The most significant example, I found of this, I asked both the Cloud Platform and perplexity calling cloud to write headlines and descriptions for Google Ads...

hey're trying to learn something and that makes sense to me. I do think perplexity is probably a really good teacher, but if you need to create content or do anything where large context windows are important, for now, I think it's worthwhile to at least pay for Claude, if not all three platforms.