💡 Integrated treatment economics and efficacy dashboard with cost-per-colony ROI

[github-actions[bot]]

Summary

Track treatment costs alongside efficacy outcomes (mite count reduction, colony survival) to calculate per-colony ROI and recommend the most cost-effective treatment strategies. Voice-enabled cost capture ("Hive 3 treatment: OA vaporization, cost four dollars") integrates seamlessly into the zero-tap inspection flow. Over time, build a treatment economics knowledge base that helps beekeepers make evidence-based spending decisions based on their own historical data.

Market Signal

BroodMinder's sensor ecosystem tracks biological metrics but not economics. HiveLog AI tracks treatment records but not costs. No beekeeping app connects treatment spending to measurable outcomes. Treatment costs are the #1 variable expense in beekeeping — Apivar strips cost $6-8/hive, oxalic acid vaporization costs $0.50-2/hive, with dramatically different efficacy profiles that vary by region and timing. Agricultural cost management tools exist for farming but none are beekeeping-specific. The economic dimension of treatment decisions is completely invisible in current tools.

User Signal

The PRD's Sideliner persona (Elena, 50+ hives) explicitly needs "economic-impact estimates for priority decisions." Existing idea #348 (automated treatment efficacy scoring) tracks efficacy but not cost. Idea #85 (treatment compliance and PHI alerts) tracks compliance but not economics. The gap is connecting SPENDING to OUTCOMES — enabling the recommendation engine to say: "OA vaporization recommended — 92% efficacy at $2.50/hive vs Apivar at 85% efficacy and $7/hive based on your historical data."

Technical Opportunity

Treatment records already exist in the architecture's observations table (JSONB structured_data). Adding a cost field to the treatment observation schema is a minimal schema change. The recommendation engine's confidence scoring framework can incorporate cost-effectiveness data as an additional signal for treatment recommendations. Voice capture in the zero-tap flow makes cost entry frictionless — one additional data point during an already-captured treatment observation. The recommendations table's action/rationale/confidence/fallback contract naturally accommodates cost-aware recommendations.

Assessment

Dimension	Score	Rationale
Feasibility	high	Minimal schema addition (cost field in JSONB). Voice capture already handles treatment records. Dashboard is a read-only aggregation view.
Impact	high	Enables evidence-based treatment spending decisions. Sideliners with 50+ hives can save hundreds of dollars per season by optimizing treatment strategies.
Urgency	med	Most valuable after 1-2 seasons of data accumulation. Design the schema and capture mechanism now; build the analytics dashboard when sufficient data exists.

Adversarial Review

Strongest objection: Beekeepers may not consistently track costs, leading to incomplete data. Treatment economics vary wildly by region, scale, and supplier — aggregate recommendations could be misleading.

Rebuttal: Cost tracking is optional and additive — the system works without it but improves with it. Default costs for common treatments (editable by the user) reduce entry friction. The recommendation engine uses PERSONAL historical data, not aggregate averages, so regional variation is captured naturally. Even partial cost data over 2-3 seasons reveals actionable patterns: "You spent $340 on treatments last year. Switching your Hive 5-12 regimen to OA could save $180 with comparable efficacy based on your own mite count data."

Suggested Next Step

Add an optional cost_cents field to the treatment observation JSONB schema. Build a treatment economics summary view showing per-treatment and per-colony cost breakdowns for the current season. Validate with 5 sideliner beekeepers whether cost visibility changes their treatment decisions.