Gustav Söderström

It's old school engineering, exposing all this data that we have so that you can have a reasoning engine reason for you as a product person or actually for me as a consumer potential over my own data in real time. So I think that's what's happening.

It's old school engineering, exposing all this data that we have so that you can have a reasoning engine reason for you as a product person or actually for me as a consumer potential over my own data in real time. So I think that's what's happening.

So the combination of now there's a standard MCPs that you can wrap these APIs in, and many of these companies, at least us, trying to expose all of this data means that a business person, a lawyer, a product person, a designer will be able to use Cursor without having to code. And they can actually at least prototype or talk to real services. That, I think, is the journey that we're on.

So the combination of now there's a standard MCPs that you can wrap these APIs in, and many of these companies, at least us, trying to expose all of this data means that a business person, a lawyer, a product person, a designer will be able to use Cursor without having to code. And they can actually at least prototype or talk to real services. That, I think, is the journey that we're on.

It started with developers. But I think as you expose the infrastructure and wrap it in APIs, I think it's going to have to go outside.

It started with developers. But I think as you expose the infrastructure and wrap it in APIs, I think it's going to have to go outside.

Is a way to say that and lose a lot, but summarize it, that what we've seen happen with developers is going to happen. I'm surprised that it's Cursor that they're using. That's quite interesting. But with other similar tools.

Is a way to say that and lose a lot, but summarize it, that what we've seen happen with developers is going to happen. I'm surprised that it's Cursor that they're using. That's quite interesting. But with other similar tools.

And that just more of our work is going to feel like we're working with a team, speaking to a team, using natural language to prototype things, to try things. And that will diffuse slowly through the entire, not only just the hours of the software developer, but the hours of each of the other functional areas.

And that just more of our work is going to feel like we're working with a team, speaking to a team, using natural language to prototype things, to try things. And that will diffuse slowly through the entire, not only just the hours of the software developer, but the hours of each of the other functional areas.

Yeah, I think so. It's hard to see where it's going to land because you're somewhere right now, but we're pretty certain that that somewhere is on this curve. So you can be pretty certain that... The workflows you see right now are not going to be the same. And that's actually one of the problems. How much are we going to build for what we see right now?

Yeah, I think so. It's hard to see where it's going to land because you're somewhere right now, but we're pretty certain that that somewhere is on this curve. So you can be pretty certain that... The workflows you see right now are not going to be the same. And that's actually one of the problems. How much are we going to build for what we see right now?

When you know the models are going to be more capable, there are going to be different tooling very soon. So you don't want to overfit too much to the moment. A reasonable...

When you know the models are going to be more capable, there are going to be different tooling very soon. So you don't want to overfit too much to the moment. A reasonable...

view of a modern company is that all of its data is exposed in real time and you have some tool on top like cursor or something else maybe different tools for different skills maybe a tool more the licensing team at spotify may have a different tool to reason over all the contracts and quickly say do we think we can do this in that market and what do we need to license to do this but also the product team could ask that

view of a modern company is that all of its data is exposed in real time and you have some tool on top like cursor or something else maybe different tools for different skills maybe a tool more the licensing team at spotify may have a different tool to reason over all the contracts and quickly say do we think we can do this in that market and what do we need to license to do this but also the product team could ask that

licensing engine. We have 15 years of contracts, both current and previous. So this AI has a lot of insight into what music licensing looks like, more than any single person in Spotify, if you train it that way. There will probably be slightly custom interfaces for different skills. I'm not sure which is going to win out. But I think it's going to look something like that.

licensing engine. We have 15 years of contracts, both current and previous. So this AI has a lot of insight into what music licensing looks like, more than any single person in Spotify, if you train it that way. There will probably be slightly custom interfaces for different skills. I'm not sure which is going to win out. But I think it's going to look something like that.

Right now, what we see people doing is they're sharing examples of prompts they used for the workflows and then prototypes that they've used. And that feels like very much a point in time. It's kind of hacky and different things.

Right now, what we see people doing is they're sharing examples of prompts they used for the workflows and then prototypes that they've used. And that feels like very much a point in time. It's kind of hacky and different things.