Caregiving Shift Scheduler

3.30

Derivation Chain

Step 1 Parent caregiving coordination

→

Step 2 Role-sharing conflict among family members

→

Step 3 Lack of a tool to track actual caregiving after division agreements, leading to accumulated distrust among siblings

Problem

When 3-4 siblings in their 50s share caregiving duties for parents in their 80s — hospital accompaniment, meal preparation, administrative tasks — they verbally agree to divide responsibilities, but with no record of who did what and when, resentment over 'I'm the only one doing anything' erupts within 3-6 months. They communicate via KakaoTalk group chat, but past messages are unsearchable and visit counts cannot be quantified. This conflict escalates to sibling estrangement in 30% of Korean family dispute counseling cases.

Solution

On the web, register family members and assign caregiving activities (hospital accompaniment/meals/admin/overnight care) to a shared calendar by person and schedule. When an activity is completed, tapping 'Done' auto-records it. Monthly Reports quantify each member's activity count and hours for transparent sharing. Schedule changes trigger automatic notifications to find substitutes.

Target: Ages 48-58, families where 2-4 siblings share care of a parent aged 75+, eldest sons/daughters who have experienced or want to prevent caregiving division conflicts

Revenue Model: Up to 3 family members Free; 4+ members + monthly Report + activity statistics dashboard $3.60/month (per family)

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

2.0/5

U Urgency

4.0/5

M Market

3.0/5

R Realizability

4.0/5

V Validation

3.0/5

NUMR-V Scoring System

N Novelty	1-5	How uncommon the service is in market context.
U Urgency	1-5	How urgently users need this problem solved now.
M Market	1-5	Market size and growth potential from proxy indicators.
R Realizability	1-5	Buildability for a small team with realistic constraints.
V Validation	1-5	Validation signal quality from competition and demand data.

SaaS N=.15 U=.20 M=.15 R=.30 V=.20 Senior N=.25 U=.25 M=.05 R=.30 V=.15

Feasibility (74%)

Tech Complexity

29.3/40

Data Availability

25.0/25

MVP Timeline

20.0/20

API Bonus

0.0/15

Feasibility Breakdown

Tech Complexity	/ 40	Difficulty of core implementation stack.
Data Availability	/ 25	Practical availability and cost of required data.
MVP Timeline	/ 20	Expected time to ship a usable MVP.
API Bonus	/ 15	Bonus for viable public API leverage.

Market Validation (54/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

8.0/10

Validation Breakdown

Competition	/ 20	Signal quality from competitor landscape.
Market Demand	/ 20	Demand proxies from search and mention patterns.
Timing	/ 20	Fit with current shifts in tech, behavior, and regulation.
Revenue Signals	/ 15	Reference evidence for monetization viability.
Pick-Axe Fit	/ 15	How well the concept serves participants in a trend.
Solo Buildability	/ 10	Practicality for lean-team implementation.

Technical Requirements

Frontend [medium] Backend [medium] Infrastructure [low]

Dashboard