Skip to content
All prototypes

Life insurance

Employee Benefits Portal

Group plans are usually run by email and spreadsheets. This portal lets an HR manager add a joiner or remove a leaver in seconds, see the cost immediately, and receive an invoice built from the live employee list.

prototypes.nityo.com/demos/life/employer/members
Employee list with plans, monthly cost and joiners and leavers
Status
Interactive prototype
Updated
October 2026
Data
Fictional, browser-only
Built by
Nityo Infotech Indonesia

The short version

Watch the workflow before you open it.

Recorded from the running prototype — every screen in the film is one you can click through yourself.

Employee Benefits Portal · 0:20 · with sound

01 · The problem

Group plans run on spreadsheets and email.

HR teams email lists of joiners and leavers, wait for confirmation, then reconcile an invoice that never quite matches their records.

The prototype makes the employee list the single source of truth: change it, and cover dates and the next invoice follow.

02 · Use cases

Group benefits without the spreadsheet

For insurers and brokers running group health or life plans for companies of any size.

  1. 01Monthly joiners and leavers
    Who
    HR teams at companies with a group health plan.
    The situation
    HR emails lists of starters and leavers, waits for confirmation, and checks the result by hand.
    What changes
    Add or remove people directly; cover dates follow the company’s rules and the next invoice updates immediately.
  2. 02Bulk onboarding
    Who
    Growing companies hiring in batches.
    The situation
    A new site or intake means typing dozens of people into an insurer’s form.
    What changes
    Paste rows from the HR system; rows with mistakes are flagged before anything reaches the insurer.
  3. 03Invoice reconciliation
    Who
    Finance teams paying the monthly premium.
    The situation
    The invoice never quite matches the company’s own headcount.
    What changes
    The invoice is built from the employee list itself, with a downloadable breakdown per person.
  4. 04Plan usage and renewal conversations
    Who
    HR leads and brokers preparing for renewal.
    The situation
    Claims usage is only seen in a report at renewal time.
    What changes
    Claims against premium and the highest users are visible during the year, within the agreed privacy settings.

Fits

  • Group health and life insurers
  • Employee-benefits brokers
  • SMEs and large employers
  • Payroll and HR providers

Extends to

  • Flexible benefits choices
  • Employee self-service enrolment
  • Wellness programmes
  • Multi-entity companies

A production build connects to

  • HRIS and payroll systems
  • Group policy administration
  • Billing and payment
  • Single sign-on for HR users

03 · Interface previews

Captured from the running prototype

prototypes.nityo.com/demos/life/employer/members
Employee list with plans, monthly cost and joiners and leavers
Joiners and leavers, priced instantly
prototypes.nityo.com/demos/life/employer
Employer overview with covered employees, premium and claims
Employer overview

04 · Simulated versus live

What the demo simulates, and what a build would connect

CapabilityIn the concept demoIn a production build
Employee dataEntered by handHRIS integration or bulk upload
InvoicesCalculated estimatesBilling system and payment status
Claims dataTotals per employeeClaims system, with privacy controls

05 · Prototype limitations

What this demonstration is — and is not

  • The insurer, the partner bank and every customer, employee and policy are fictional.
  • Premiums, fund returns and underwriting rules are illustrative — not real tariffs or guaranteed values.
  • Data stays in this browser. No identity, health, document or payment data is collected.
  • No core policy, bank, payment, hospital or OJK reporting system is connected.

Try it

Open it and walk through the workflow.

  1. 1Add a new joiner — the plan follows their grade.
  2. 2Remove a leaver from next month.
  3. 3Open Billing: next month’s invoice already reflects both.