B

AI Token Usage Departmental Billing

3.20

Derivation Chain

Step 1 Chinese AI models surpass US in global token usage
→
Step 2 Explosive growth in enterprise AI API usage
→
Step 3 Service for allocating AI API costs by department/project
→
Step 4 AI budget optimization reports based on settlement data

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

The finance team of a mid-sized company (50-300 employees) that has adopted AI APIs spends 8-16 hours per month manually extracting usage from each vendor dashboard and allocating costs to departments/projects in Excel to settle monthly AI API costs of 5-30 million KRW (~$3,750-22,500). Unclear allocation criteria lead to quarterly cost disputes between departments, and missed cost optimization opportunities result in 15-30% overspending per month.

Solution

By integrating multi-vendor API keys (OpenAI, Anthropic, Chinese AI, etc.), it automatically tags token usage by department, project, and individual, and generates monthly settlement reports. Based on usage pattern analysis, it recommends cost-saving opportunities such as model downgrades, caching, and batch processing, and sends real-time alerts when budgets are exceeded.

Target: Finance and DevOps teams at mid-sized IT companies with monthly AI API costs of 5 million KRW (~$3,750) or more, team size 3-15 people
Revenue Model: SaaS: 99,000 KRW/month (~$74.25) for monthly API costs up to 30 million KRW (~$22,500), 199,000 KRW/month (~$149.25) for costs exceeding that, plus optional 10% performance fee on API cost savings.
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
3.0/5
U Urgency
4.0/5
M Market
3.0/5
R Realizability
3.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
Each dimension is scored 1-5 and weighted into grade S/A/B/C/D.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (70%)

Tech Complexity
29.3/40
Data Availability
20.8/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.
Total 100 points; below 50% is filtered out.

Market Validation (60/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
16.0/20
Revenue Signals
10.5/15
Pick-Axe Fit
12.0/15
Solo Buildability
7.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.
Total 100 points; below 50 is filtered out.

Technical Requirements

Backend [medium] Data Pipeline [medium] Frontend [low]
Dashboard