PRODUCT LED TRANSITION

Concept Note for Founder Decision

Version: 1.0 Date: 5 August 2026 Prepared by: Prof. NOTA Status: Proposed Phase-2 direction — not yet approved

1. Proposal

BGC × iBLOOMING should transition from a project centered on tokenizing existing rewards into a program centered on:

• products;

• customers;

• commerce;

• distribution;

• access;

• ownership;

• authenticity;

• measurable usage;

• repeat demand.

Blockchain and AI should be used selectively to strengthen those systems.

Proposed program name:

Practical Blockchain and AI Integration for Product, Commerce, Access, Distribution, and Trust

The current project has shown that:

• BGC recorded cash-in is dominated by affiliate-entry activity;

• iBLOOMING direct product revenue is much smaller;

• existing-system tokenization could duplicate rights and obligations;

The next strategic problem is therefore not:

“How can we create a token?”

It is:

“How can we make more people genuinely want to buy, use, trust, and return to BGC × iBLOOMING products?”

No token should be created merely to search for utility later.

Correct order:

Use normal databases, APIs, ecommerce systems, and cloud infrastructure when they are sufficient.

Use blockchain where it improves:

• ownership;

• portability;

• provenance;

• authenticity;

Use AI where it improves:

• product recommendation;

• customer support;

• creator productivity;

• content matching;

The program must not:

• promise yield;

• create deposit products;

• create a DEX or CEX;

• use token emissions as fake revenue;

No accountable owner means:

Not resourced — not executable.

Measure purchases that occur without affiliate-income motivation.

Improve catalogue, checkout, inventory, fulfillment, retailer, distributor, and after-sales systems.

Create authenticity, warranty, ownership, and traceability systems where useful.

Create clear and portable access to content, courses, subscriptions, and credentials.

Complete the approved Web3 Login architecture.

Improve products and operations, not merely marketing claims.

Measure conversion, repeat use, margin, retention, cost, and user value.

Scope:

• existing account login;

• wallet setup;

• embedded or connected EOA;

• Smart Account;

Owner:

• Yuku and engineering.

Prof. NOTA role:

• architecture and integration support.

Scope:

• customer segmentation;

• reward-led versus product-led campaign comparison;

• direct-sale funnel;

• repeat purchase;

Scope:

• product catalogue;

• SKU;

• batch;

• pricing;

Scope:

• proof of authenticity;

• product passport;

• product ownership;

• warranty;

Scope:

• GiM;

• iLearn;

• iMATRIX;

• Channel Provider content;

Scope:

• recommendations;

• support assistant;

• creator assistant;

• content localization;

Scope:

• KPI definitions;

• data dictionary;

• decision log;

• privacy;

This track:

• is not part of core execution;

• has no launch date;

• is separate from affiliate rewards;

• begins only through a separate founder resolution.

A wallet-linked product credential can improve authenticity, ownership, warranty, and after-sales experience.

The credential is not created for speculation.

• activation rate;

• warranty usage;

• support reduction;

• authenticity checks;

A wallet-linked access credential can improve cross-application access and make digital entitlement more portable and auditable.

• activation;

• content usage;

• completion;

• retention;

Combine:

• physical product;

• content;

• onboarding;

• warranty;

This creates BGC × iBLOOMING integration through product utility.

Verify:

• authorized retailer;

• authorized distributor;

• product category;

• region;

• non-affiliate customer;

• affiliate customer;

• buyer paying new fiat;

• PC redeemer;

• independent product buyers;

• conversion rate;

• repeat purchase;

• subscription retention;

Current-style communication emphasizing income opportunity and network benefits.

Communication emphasizing product problem, function, value, quality, use, delivery, and support.

Compare:

• purchase conversion;

• retention;

• repeat purchase;

• refund;

• translate business problems into technology systems;

• evaluate blockchain suitability;

• evaluate AI suitability;

• design product and commerce architecture;

• development;

• Web3;

• physical-product sourcing;

• spare-parts trade;

• legal opinion;

• tax opinion;

• financial audit;

• accounting certification;

• issue founder meeting record;

• appoint owners;

• begin Web3 Login technical verification;

• define product-demand baseline;

• develop limited Web3 Login proof;

• prepare product data;

• launch product-first campaign test;

• build first product or access credential;

• compare Product-Led and reward-led outcomes;

• evaluate conventional versus Web3 implementation;

• decide whether to scale, change, or stop;

1. Approve or reject the Product-Led transition.

2. Appoint a Product owner.

3. Appoint a Marketing and Demand owner.

4. Appoint an Engineering owner.

The program is successful when it produces evidence that:

• more people buy products for their product value;

• product usage and repeat purchase improve;

• commerce and distribution become more reliable;

A pilot should stop when:

• users do not value the feature;

• Web3 adds cost without measurable benefit;

• legal or privacy risk is unacceptable;

• the pilot depends on recruitment;

Stopping a weak pilot is a valid success of the evidence process.

BGC × iBLOOMING should use the next year to become more Product-Led, not more token-dependent.

Web3 Login should create the identity and wallet foundation.

Blockchain should be tested through small product, access, ownership, authenticity, and distribution use cases.

AI should improve products and operations.

Any public-token research should remain separate, optional, and inactive until real product demand and institutional readiness are proven.

P.S. Read this document freely for information and guidance. Do not redistribute or restate—no quotes, summaries, paraphrases, or derivatives—without prior written permission from . Sharing the link is allowed. So, share the link, not the text. Do not discuss or re-tell the contents in any form—written, spoken, or recorded—without prior written permission.