So let's quickly look at technical versus non technical, white papers. And why you would choose one over the other. So number one, consider the product and consider how technical the product is, are we looking for users to use a product? Or do the users really need to understand the nuts and bolts of it? Who's gonna be the investors? Who's going to be the guy who's actually going to look at this thing?

So consider the audience who's going to read this white paper? Who's going to skim over the white paper? Who's actually going to use the product? So you got to consider both the both the investor and the user, but also consider how technical savvy technically savvy they are, and do you need to produce a technical white paper and a non technical white paper? Or do you need to fuse them both together? Also, consider what's believable.

Some examples of Ico projects or, you know, dating apps, message apps, exchanges, trading platforms, coin creators, analytics platforms, investment platforms. So let's say it's an analytics cloud. For him, he may want to speak to the mind of your core customer, which may be advertising or anyone or other business owners, or you may want to speak to people who already understand. So it just depends on what you're doing investment platforms, you can get a little bit more technical than you can with the dating app, right? Also that compared to an exchange, now, if you're touting that this exchange is going to do something more tech, something different on the technical side, you may want to go a little bit more technical. So you know, so you have to think about what you're trying to do and what makes sense in that light.

I hope this, this helps. You know, because ultimately you want returns right? You want more readers, you want more subscribers, and you want to get do what's going to get the returns. So let me know if this helps. If it doesn't, I'll produce another video and clarify further