← All work
platform

GoodPair 錦好沛

A platform connecting senior-learning instructors and course organizations through profiles, credentials, cases and matching.

Project brief

15 / 20
Client
GoodPair
Type
Platforms and systems
Period
2026
Status
Live
Collaboration
UI/UX and visual design supplied by an external designer
Scope
System build, UX implementation advice, REST APIs, memberships and administration
GoodPair public website homepage
The public homepage presents instructors, course demand and the two member entry points in one service structure.

Project overview

GoodPair connects senior-learning instructors with organizations seeking courses.

Organizations post cases or invite instructors, while instructors build profiles, document credentials and apply. We developed the system architecture, frontend, backend and REST API.

Key outcomes

01Dedicated member centers for two roles
02Profiles, credentials and KYC
03Cases, applications and invitations
04Operations admin and REST API

Working flow

Matching starts after both sides have prepared the right information.

  1. 01
    Build profiles

    Clients publish a brief while instructors prepare profile, work samples and KYC.

  2. 02
    Match

    Either an application or an invitation can begin the two-sided process.

  3. 03
    Confirm

    Contact information unlocks only after both parties confirm the match.

01 01

Matching course needs with the right instructor

Organizations can post cases or invite instructors; instructors present expertise, credentials, work and availability before applying. Both routes share one clear matching state.

02 02

Contact details unlock only after a match

Phone, email and other private details remain hidden before confirmation. Once both sides accept the match, contact information unlocks for that case; the platform scope ends at matching.

03 03

Two roles need two complete workspaces.

Clients manage briefs and invitations. Instructors manage their profile, work samples, credentials and KYC. The system does not compress these distinct tasks into a single generic account screen.

04 04

One state model connects the public site, member areas and administration.

REST APIs define instructor profiles, briefs, applications, invitations, confirmations and the condition for revealing contact details. Both sides therefore see the same progress instead of one account remaining in a waiting state after the other has confirmed.

Next case

Dominifriend 多明麗 →
Working on something similar? Let’s talk →