Helper Match SG - Product Concept

Core Idea

The detailed product design of Helper Match SG — the transfer facilitation workflow, profile structure for both maids and employers, contract tooling, monetisation approach, and guidance for first-time employers.


State of Thinking

Transfer facilitation workflow

The platform guides users through the full transfer process, not just the matching step. This includes:

  • Contract template generation
  • Checklist of what to buy and set up
  • Insurance referrals (potential referral revenue stream)
  • Step-by-step guidance for first-time employers — real assistance through each step, not just a list

Maid profile

Key information:

  • Age, years of experience, marital status
  • Expected release date from existing contract

Working condition expectations:

  • Number of off days expected
  • Expected salary

Non-key but useful information:

  • Top 3 skills or activities (cooking, cleaning, childcare, etc.)
  • Photos of work — e.g. cooking photos

Employer profile

Key information:

  • Living arrangement for maid — shared room or individual room
  • Whether there is an existing helper or plans for more than one
  • Reason for hiring or main scope of work
  • Top 3 job scope priorities
  • Expected start date

Contract template

  • Profile information from both sides auto-populates the contract template
  • Multi-language support to be explored — contract in helper’s mother tongue may be needed to protect the maid, though not legally compulsory (needs verification)

Language verification

  • Simple in-browser language test to verify basic, intermediate, or advanced language ability
  • Reading can be tested through the website
  • Spoken/conversational ability would require human verification — out of scope for now

Monetisation

  • Referral fees from insurance partnerships
  • Employer token system — employers buy tokens to unlock gated content
    • Free tier: access ratings only
    • Paid tier: access full testimonials
  • Donation model — open for donations to support the platform

Thinking Trace

  • The transfer process has many steps that first-time employers do not know — just listing the steps is not enough, need to actually assist with each one
  • Profile fields serve double duty — they are both the matching signal and the input for the contract template, which makes auto-generation natural
  • Contract in the helper’s mother tongue came up as a protective measure for the maid — need to check if this is required or just good practice
  • Language testing through the website is tractable for reading; spoken is a different problem entirely
  • Token model for testimonials feels like a natural paywall — ratings are free, full context costs something
  • Insurance referrals are low friction as a revenue stream — users need insurance anyway

What changed?

— skip, v1 —


Why it changed?

— skip, v1 —


Evidence / Signals

  • First-time employer guidance is a real gap — the transfer process is genuinely opaque for new employers

Open Questions

  • Is a contract in the helper’s mother tongue legally required or just best practice?
  • How do we prevent the token model from feeling exploitative toward employers?
  • What is the right scope for the language test — which languages to support first?
  • How do we validate that profile information (especially skills and experience) is accurate?
  • At what point does the auto-generated contract need legal review?

Connections


Changelog

  • v1 — Initial node