Signal Sources (v8 Triple Source)

Trigger

중소기업 멀티클라우드 비용 최적화 SaaS

Market

G2 FinOps 카테고리 YoY 47% 성장, SMB 타겟 도구 공백

Workflow

Reddit r/devops: 매일 아침 3개 클라우드 콘솔 빌링 페이지 돌며 이상 체크하는데 30분

Problem

DevOps engineers at companies with 50-200 employees using a mix of AWS, Azure, and GCP spend over 30 minutes each morning checking billing pages across three cloud consoles for cost anomalies. Missing spikes due to price changes or regional issues leads to repeated month-end bill shocks.

Solution

Connecting the three major CSP APIs automatically sends a daily morning Slack digest with the previous day's cost summary, anomalies, and month-over-month changes. Setting team-specific cost thresholds triggers instant alerts when exceeded. As usage history accumulates, the system learns the organization's normal cost patterns to reduce false positives.

Target: SMEs (50-200 employees) using AWS+Azure or AWS+GCP — DevOps engineers, infrastructure team leads

Revenue Model: Monthly $49 base (up to 3 cloud accounts) + $19 per additional account — 20% discount on annual contracts

Ecosystem Role: -

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

2.0/5

U Urgency

5.0/5

M Market

4.0/5

R Realizability

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

N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (81%)

Tech Complexity

40.0/40

Data Availability

21.2/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 (57/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

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