# Roadmap

#### KERC.io Go-To-Market Strategy (Lean, Subscription-Driven, Data-Centric)

**1. Immediate Monetisation Through Subscription-Based Health Records**

Objective: Convert existing clinic patients into paying subscribers for secure, long-term health data storage.

* Health Data Vault Subscription: Offer tiered monthly plans (e.g., $9.90, $19.90, $39.90) allowing patients to store, access, and share medical records across providers securely through the KERC app.
* Bundled with Clinical Visits: Include free 3–6 months’ subscription for patients of KERC-owned clinics as part of treatment packages, then upsell upon renewal.
* Family Accounts: Enable household-based plans for multi-patient data storage under one wallet — highly appealing for parents and elderly caregivers.

***

**2. Targeted User Onboarding in KERC Clinics**

Objective: Build the subscriber base from within the owned clinic ecosystem using patient interactions.

* Point-of-Care Upselling: Train front-desk staff and doctors to onboard patients into KERC’s health record system as part of intake or discharge.
* Post-Visit Value: Email/SMS follow-up offering one-click access to their visit summary + offer to store full history via subscription.
* Referral-Driven Growth: Launch patient referral rewards in KERC tokens or discounts for each successful new subscription.

***

**3. Partnerships with Employers and Schools**

Objective: Expand subscriptions at scale through B2B2C channels.

* SME Healthcare Subscriptions: Offer companies bundled checkups + digital record access for employees, focusing on white-collar SMEs with no structured wellness support.
* School Health Records: Pilot in private/international schools to digitize student health records with parental subscription as custodian — a strong compliance use case.

***

**4. Data Monetisation Layer**

Objective: Establish the long-term revenue stream from anonymised, user-consented data aggregation.

* Token-Incentivized Data Sharing: Allow users to opt-in to anonymised data usage and receive KERC tokens or subscription credits in return.
* Analytics for Pharma & Insurers: Offer anonymised real-time dashboards or research access for longitudinal insights on patient behavior, medication adherence, and chronic illness patterns.
* RWA-Linked Rewards: As clinics generate subscription revenue, flow a percentage back into the RWA pool for early token supporters — strengthening the circular economy.

***

**5. Cost-Efficient User Acquisition via Localized Outreach**

Objective: Drive subscriptions without burning capital.

* Clinic-Led Workshops: Monthly health talks on “owning your health data” with immediate onboarding.
* WhatsApp Health Tips Channel: Opt-in channel for patients that doubles as a subtle lead-gen for upselling subscriptions.
* Leverage Ministry-Approved Endorsements: Position KERC as aligned with Malaysia’s digital health blueprint for credibility.<br>

  ###

  | Timeline | Milestone                                               |
  | -------- | ------------------------------------------------------- |
  | Q2 2025  | MVP Rebuild, Clinic Onboarding, Smart Contract Relaunch |
  | Q3 2025  | Subscription Vault Launch, SME & School Health Plans    |
  | Q4 2025  | KERC Chain Testnet, Tokenized Data Monetization Begins  |
  | 2026     | Expansion to SG, IDN, PH – Clinic Network Scale-up      |

  ####


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kerc.gitbook.io/kerc/outlook/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.