Non-Code Work Tracker

4.00

Derivation Chain

Step 1 AI coding tool proliferation reduces code-writing share

→

Step 2 Dev team non-coding work visibility tool

→

Step 3 Non-coding work time auto-tagging SaaS

Problem

With the proliferation of AI coding tools, actual code-writing time has decreased, yet non-coding tasks—requirements definition, code review, deployment coordination, stakeholder communication—still account for 60-70% of total development time. This time goes unrecorded in Jira or Git, causing dev team productivity to be overestimated or PMs to misallocate resources.

Solution

A dashboard that integrates activity logs from existing tools (calendar, Slack, Notion, meeting notes) to automatically classify and aggregate non-coding work hours. Weekly reports visualize the 'code vs. non-code' time ratio and identify bottleneck tasks.

Target: CTOs and Engineering Managers at 10-50 person IT Startups, agency dev team leads

Revenue Model: SaaS Monthly Subscription at KRW 5,900 (~$4.40) per team member/month. Free Plan for 5 or fewer users. 15% discount on Annual Subscription

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

4.0/5

U Urgency

4.0/5

M Market

4.0/5

R Realizability

4.0/5

V Validation

4.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 (69%)

Tech Complexity

29.3/40

Data Availability

19.4/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 (58/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

16.0/20

Revenue Signals

10.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

7.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

Backend [medium] Frontend [medium] AI/ML [low]

Dashboard