💡 Per-hive harvest yield intelligence with multi-product revenue analytics

[github-actions[bot]]

Summary

Track honey production, wax, propolis, pollen, and nucleus colony sales per hive with voice-commanded harvest logging during zero-tap inspections. AI correlates yield with colony health observations, treatment history, and environmental conditions to answer "why did this hive outperform?" Year-over-year comparison, per-apiary aggregation, and cost-per-colony profitability complete the colony economics picture.

Market Signal

Six-plus competitors (HiveFlow, HiveTracks, TerraAurelium, HiveBook, Beeing, Navfarm) already offer production tracking — this is table-stakes functionality. US honey yield per colony dropped 6% YoY to 51.7 lbs average (USDA 2024 data). Beekeeping profitability analysis cites "net yield per hive" as the #1 KPI, with a 2026 target of 60 lbs/hive. Financial clarity is essential for sideliner retention as total US managed colonies declined from 2.60M to 2.41M.

User Signal

No existing Broodly idea covers harvest or production tracking. Existing idea #479 covers treatment cost economics but not the revenue/yield side. Without yield tracking, the recommendation engine cannot close the loop from advice → outcomes → learning. Multi-product tracking (honey, wax, propolis, nucleus colonies, queen sales) serves the sideliner segment that derives meaningful income from their operation.

Technical Opportunity

Natural extension of the inspection data model — harvest entries are observations tied to hive + date. Voice entry integrates into the zero-tap flow: "Harvested thirty pounds from Hive 5, medium amber, wildflower source." TanStack Query cache supports offline harvest logging. Yield correlation analysis leverages the same Vertex AI pipeline planned for recommendations. GraphQL schema already supports extensible observation types per the architecture document.

Assessment

Dimension	Score	Rationale
Feasibility	high	Standard data model and UI. Voice grammar for harvest entries is straightforward. Builds on existing observation infrastructure.
Impact	high	Table-stakes feature gap vs competitors. Closes the advice→outcome loop for the recommendation engine. Essential for sideliner financial management.
Urgency	high	Competitors already ship this. Harvest season (late summer) is the highest-relevance window. Users evaluating Broodly will expect production tracking.

Adversarial Review

Strongest objection: Every competitor already has harvest tracking — Broodly is late to a commodity feature. Basic production logging isn't a differentiator.

Rebuttal: Basic production tracking is commodity, but no competitor integrates yield data with AI-powered decision support. Broodly's unique value is correlating yield with colony health, treatment history, and environmental conditions through the recommendation engine — answering "why did this hive produce 60 lbs while that one produced 20 lbs?" Voice-first harvest entry during zero-tap sessions is also differentiated. The gap must be closed regardless — users will not adopt an app that cannot track what their hives produce.

Suggested Next Step

Design the harvest observation data model and GraphQL schema extension. Define voice grammar for harvest entries (weight, color grade, floral source, product type). Prototype the yield dashboard with per-hive comparison charts and season-over-season trends.

---

Generated by weekly feature ideation scan — 2026-08-31