Proposal for Optimizing Resource Usage and Subscription Model

[amad-amad]

---

1) Daily/Hourly Usage Limits

To manage server load during file downloads and online test usage, it is recommended to implement usage limits as follows:

• Daily: Up to 5 downloads or test attempts

• Hourly: Up to 3 downloads or test attempts

2) Subscription Model to Remove Limits

Users can remove these limits by purchasing a subscription. Suggested base prices:

Subscription Plan	Price
Monthly	$5
Quarterly	$12
Semi-annual	$21
Annual	$39

These prices serve as an initial baseline and can be adjusted later based on operational costs, new services, and market conditions. Pricing is structured so payment transfer fees remain reasonable.

3) Price Adjustment for Different Countries

To maintain affordability for users worldwide and prevent churn, the final subscription price should be multiplied by a Purchasing Power Parity (PPP) coefficient for each country.
Suggested pricing sheet:
https://docs.google.com/spreadsheets/d/1olzAGki2aqlXDVH7CKaew28c0WSovNRXa8tDWeN0ojk/edit?usp=sharing

4) Detecting User Location

User country can be identified through:

• IP address

• Previously downloaded files and account history

5) Coverage of the Subscription

• The subscription does not include paid files.

• Users must pay separately for premium files.

• However, subscribers may receive exclusive discounts on these items.

6) Payment Method

• All payments should be made using the Gamma token.

• Subscription pricing should remain pegged to fixed USD values for clarity and consistency.

7) Revenue Sharing Proposal

From subscription revenue, the following shares are suggested:

• 1% for the project designer

• 4% for the development team

---

[sanaderi]

To make the system more practical and ensure a smooth initial launch, I propose that in the first phase, we keep the subscription pricing the same for all countries, without applying PPP adjustments or country-based pricing.

1. Reduces Development Complexity

Implementing PPP, geo-pricing, and country detection requires additional logic and time. Removing these for now speeds up development.

2. No Need for Accurate Location Detection

We avoid depending on IP-based or account-based country identification until later phases.

3. Faster Launch for the Initial Version

A unified price model allows us to launch the subscription system quickly and start generating real user feedback.

4. Easier User Behavior Analysis

We can observe usage patterns, churn behavior, and willingness to pay before introducing more advanced pricing logic.

5. Simplified Financial Management

A single global price ensures stable and predictable revenue in the early stages.

[amad-amad]

Thank you for your input.
I fully agree that, for the first phase, it’s better to keep the pricing simple and uniform so we can move forward with development more quickly. The PPP idea was only introduced as a forward-looking option—something we could evaluate later if we have real user data and see a clear need to adjust prices for different countries.
For the current phase, I don’t think adding PPP would be necessary or helpful.

[naderiramin]

At this stage, applying broad subscription limits is not in the platform’s best interest and carries a high risk of user churn.
The optimal strategy is:

Keep the platform fully usable

Restrict only the download of docx and pptx formats

Require a subscription exclusively for these two premium formats

Reevaluate wider subscription mechanisms after the user base grows

This approach preserves user trust, supports platform growth, and introduces a sustainable, low-friction monetization model.

[naderiramin]

We must also evolve our existing services in a way that creates real added value, so that any paid model becomes justifiable and attractive for users. For each lesson note or blog post, we should gradually produce corresponding premium formats such as video content, PowerPoint slides, podcasts, infographics, and mind maps. These enriched content types can then be included in the premium subscription package.

[amad-amad]

"Your suggestion to keep the platform services open is completely reasonable, especially at this stage when the content volume is still limited. To activate a revenue model without causing user friction or putting pressure on the development team, I suggest focusing only on the files for now:

• Old files (more than 3 years old) → fully accessible
• Files from 1–3 years ago → light restrictions: maximum 20 downloads per day with a 10-download hourly limit
• New files (current year) → require a subscription

To provide additional incentives:

• Initial registration → 3 free downloads
• Wallet connection → 5 free downloads
• First token purchase → 7 free downloads

This model is low-risk, quick to implement, and creates a real revenue flow while providing the team with immediate energy and motivation."

[naderiramin]

As I mentioned earlier, the current daily download volume is not high enough to justify imposing usage limits. I don’t believe this approach would be effective, and I think it would be better to move away from this idea.

I suggest focusing instead on models that encourage user-generated content and active participation—especially mechanisms that motivate token holders to be more engaged on the platform.

In my view, increasing participation and engagement is the only sustainable way to pave the path for future growth.