GPone has formally entered its business preparation phase and begun preliminary work on the product structure, business processes and underlying technical architecture of its digital services platform.
Defining core user journeys
At this stage, the priority is to address the platform’s fundamental requirements rather than rapidly expand the number of products. These include how users will register and verify their identity, view product information, submit subscription requests, check order status, and subsequently access their account holdings and service records.
With these needs in mind, the team has reviewed the platform’s core business processes and identified account management, a product hub, order management, asset records, identity verification and customer support as the initial foundational modules.
Standardizing product information
GPone has also defined a consistent approach to presenting product information, including service terms, unit prices, issuance details, start and end dates, and order status. The aim is to reduce inconsistencies in how information is communicated across different pages.
Designing for mobile access
In parallel, the team has begun designing the platform around mobile use. As most future users may access the platform from their phones, the first phase of development will prioritize mobile apps and mobile web pages, with corresponding adjustments to page hierarchy, the presentation of key data and user flows.
Building the operational foundations
GPone remains in the process of building its foundational capabilities. The next phase of work will focus on developing core functions, strengthening account security, implementing identity verification and connecting order data with asset records across the platform.
For a platform at this early stage of development, clear product rules and stable business processes form the foundation for subsequently bringing its services to market.