Local Projects,Real Work.

The cases describe projects delivered in our team’s experience. They show the local work involved in campaigns, developer education, community activity, events and partnership development. Each record should be read with its market, delivery role and reported result, rather than as a list of current contracts or a promise about a future engagement.

For a new assignment, the useful question is which past work helps explain the job ahead. A developer program, creator campaign and enterprise discussion have different participants and measures. The case gives the client a concrete reference for the approach; the new brief still needs its own product evidence, audience, responsibilities and budget.

A case can explain the original objective, the audience that needed to act and the delivery work used to reach them. It may also report a result for a particular market or period. Read those elements together. A number without its unit or context does not explain whether the activity would be relevant to another product or business need.

Use comparable work to shape the next conversation. Ask what materials, local relationships and operating conditions the project required, and which of those would be different for your own market entry or partnership assignment.

The selected cases in this presentation cover several types of local work:

• Bybit: Korea trader events and a dedicated VIP program
• Aptos: local events, creator relationships and community channels
• Polygon: developer education and Korean DeFi participation
• Sahara AI: launch events for developers and enterprises
• KuCoin: creator partnerships and paid distribution
• peaq: DePIN education and IoT or mobility partner development
• World: a peaq × World pop-up during KBW 2026

Explore more cases and original records.

Begin with the objective and the audience. Compare a participation program with another participation program, or a partnership brief with work aimed at a relevant business counterpart. Then examine the market, delivery role, period and available result. That sequence helps identify which experience is useful to your brief without treating unlike measures as equivalent.

Bring the case closest to your objective, then describe the product and market you have in mind:

1. Share the project at panasia.io/contact
2. Identify the audience and intended action
3. Agree the first scope, owners and budget

The resulting assignment may involve Asia GTM, strategic partnerships or both. The case informs the discussion; the actual deliverables are agreed for your own product and market.

No. This collection represents the team’s project experience. A case can describe historical paid work, a defined delivery contribution or a particular collaboration. The project name identifies the subject of that record. Read the scope and source before assuming that a company has an ongoing engagement or that the same team performed every part of its wider market activity.

The distinction matters when preparing a new brief. A past project can demonstrate relevant delivery experience, but current counterpart availability, product readiness and commercial terms need to be established for the next assignment. For the services and how a scope is defined, read our service overview.

A case documents historical work and the results reported for it. Research examines a broader question using sources, comparisons and sometimes explicit models. Both can inform a new assignment when the evidence is read in context:

• Objective: Identify the audience and the action the original work aimed to support
• Evidence: Keep the stated role, period, reported result and original source together
• Relevance: Compare the operating conditions with your own product and market
• Next step: Use what is comparable to shape the brief, then name the work, owners and checks required for the new assignment

Past work is most useful when it helps the client ask more precise questions about what should happen next.

Panasia Intelligence supports market and partnership decisions with research on local conditions, channels, product access and operating requirements. It complements historical team experience by examining the evidence relevant to the decision ahead.

The public collection includes market-entry frameworks and research on stablecoin payments, redemption and tokenized assets. Sources and model assumptions are available where published, so readers can inspect the basis and limits of a conclusion before applying it to a new context.

Past delivery informs the questions we ask; the new product and market determine the scope.

A case may show how a local workshop, creator campaign or partner conversation was organized. The next assignment still needs an intended audience, usable product action, local materials and accountable owners. We use the relevant experience to prepare that discussion, while identifying which conditions and requirements must be checked again.

No. The figures describe the reported outcome of a particular case, with its own activity, market and period. For example, liquidity, trading volume, community size and event attendance measure different things. They should not be combined into company revenue or used as a forecast for another project. The new assignment is assessed against its own objective and evidence.

Match the measure to the goal: audience response, product actions, relevant meetings or agreed next steps. Keep the period and context with each result.

Where an original case is published, the Panasia project page links to it. Read the scope and result together and check whether the source describes a completed activity or ongoing work.

Yes. Discuss either service separately or combine both in one scope, with the audience, workstreams, responsibilities and budget defined.