Next, we'll look at use cases. In some cases, it's fine to only use one use case, probably want to think of more than one because at minimal, you have a user and you have an investor. A lot of times you have multiple users or you have an ecosystem that has even up to three or four users. You can use the investors use case and that but that can be tricky sometimes, especially if you're looking at positioning your project as a utility more so than a security. You want to explain the uses for the product, the token within the product as well. Sometimes these are separate, expand on the user journey through the platform.

And by that I mean, how do they use this? How is it enhancing their journey through the platform? You can get these people's names, people names, or you can just use customer one, sometimes customer two. Sometimes they're different journeys and different uses and different sorts of value stores within the ecosystem and you want to question All that. Why is it that you're including this solution? And what does this do to add value or how it not having this prevent you from getting value through the tokenized system.

So you need to think this through, because this is really why people would adopt your coin, why your utility utility can grow and become valuable on an exchange? What is it that they get from this solution and show how like sort of how life is before and life after. And this can naturally in a paper go after presenting the solution. And sometimes it can be woven into the solution. I prefer to have it separate. So you can clearly see there clearly different valuable use cases.

Let's take a look at some examples. The use case section here so we'll go down to our use case section. Okay, here we have use cases. So show a screen of the app. This is good, you get an idea of what it looks like, potentially looks like your grass here and it's Talk about the patience here. Number one, you have the patience, what the patients will be able to do, combined scattered medical records, see a complete history.

See, it's a very clean overview of what you can do. And then they talk about the claims here, and the market for healthcare data. So that's a big topic there. And then they add on artificial intelligence and how that will play in to healthcare and data thing. He talked about the clinical trials here. And so this is a big one here too, as well as a lot of players here.

Trying to find a way to streamline and provide a single source of truth within the clinical space. And then you have tele telemedicine. So it's a very, very, very ambitious project here. And I think Finally, you get to the social media use case. So as you can see, they have a section section five, and then they do 5.1 through 5.7, and they clearly outline what they're going to do. So let's look at another here.

Let's look at clinics. So clinics has a business use case of friends river referral use case, as well as a developer use case. So let's take a look at all these here. So number one, they talk about the options for business here. And they talk about how, once again, like I mentioned in the slide, life before, and then life after. So integrating POS CRM systems, all that.

And then you go right into the direct business use case here. So you have a theoretical organization, how they'll use it, how they've last five years, how to retain customers and use referrals. And then they talk about how the system works. The days elapsed from providing a referral system to actually getting the customer. Okay, and then you have a theoretical use case for an even bigger company. So this is what really well done.

So noticing if you're doing b2b. You have small customers mom and pops and you Also have large enterprises. And those are different use cases. And so they have options for referrals that go very granular. And here's the friends and family. So these are everyday people, users.

People are going to download apps sign up for rewards, referrals and pass them around. And they talk about here, they have a generic guy, James, he logs in, he's counting, he passes his referral to a friend. And then they have the developer use case. So they have an introduction here to talk about why they're doing it. Then they go into how a developer can use the API, build upon the existing platform and also be given tokens when his platform his or her platform is used. So they do this really well.

Let's take a look at one more here. Let's look at protocol. And then we click through here now we have to go through. So that's a problem solution. The problems of the solution. And then we go into multiple use cases.

And so there's this little different you have a big quote here about what Provo allows you to do. You go down here, they talk about the natural benefits of creating infinite challenges and the use case for the noble cause. So this is general, this is a stretch here, but you can do this as well. That's the general society benefits from XYZ by XYZ. And they talk about that then they have a use case for fun and rewards. So as you see, you can have a specific user or use case for a result or benefit, and this is kind of what Provo duty does here.

So there's a funding reward and here's one from monetizing every active so very clear use case for fun use case for society use case for monetizing use case for the individual here, and this is token challenges, whatever. And here's a use case for businesses. You see, so they have bullet points and he clearly described how this leads to influence a marketing AI agent. All this stuff in any go into market so as you see there's a few different ways of doing it. I like all three examples, just you know you have to choose one and do it well