How to add a token utility using a subscription to a Web3 application

Do you have a working product and are thinking about monetization and increasing the utility of your token?

If this sounds familiar, then this article is for you!

Let's say you have a B2C product in Web3.0 with a freemium monetization model based on periodic subscriptions or access to functionality. You need to accept payments, and it would be nice to organize subscriptions through your own token.

What should you do?

Refuse to monetize or utilize the token?

Not charge users anything until your product reaches a critical mass of users?

Of course, you want everything at once, BUT you have to choose!

OR

Is it possible to offer the user any option at their discretion in order to:

maintain a wide sales funnel?

maintain the ability to verify product value through payment?

offer a discounted rate to those who are still undecided?

In fact, you need a system of smart contracts with an interface that can be placed in front of your product as a payment gateway.

Most solutions are not suitable, and independent implementation of such functionality would require several months of development and a budget of $30k.

There is an approach to organizing subscriptions that allows you to retain any user without losses in unit economics.

How Subscription Service works

Envelop Subscription offers the market a new concept called “Service Farming.”

While usual farming helps maintain the price of a project's token WITHOUT a product, Service Farming helps projects with an existing product increase the utility of the token and organize monetization with discounted rates.

Envelop Subscription is a module consisting of smart contracts and a front end.

There are two types of subscriptions:

1) “Payment” for the dApp with tokens.

2) “Deposit” of project tokens or “Service Farming” with tokens locked for a certain period.

Both options are flexible in terms of usage time or number of transactions.

The user's path is as follows:

1. user selects the wallet to which the subscription will be issued, this can be the user’s wallet or any other wallet, i.e., you can issue a subscription to someone as a gift or to a wallet with a zero balance

2. user selects the payment type:

subscription payment: funds will be charged from the user's balance in favor of the project

deposit: the user adds tokens to the deposit for a certain period, during which they can’t withdraw these tokens. The deposit time should be higher than the subscription age.

3. user selects the subscription type: the period or number of times the product can be used. It's like a ticket for 10 trips, or a pass for 1 month without restrictions

4. user selects a token for payment (stablecoins, native coins, or project tokens).

Why you should order Subscription module

you save tens of thousands of dollars and several months of teamwork

unique subscription model based on token locking. Users don’t spend tokens or sell them. The project reduces selling pressure and increases token utility.

user decides on the payment method, price plan, and payment token

free trial plan support

individual terms with each affiliate and future profit sharing

recurring payments on demand