Cut your monthly TTB compliance work from 12 hours to under 2. A 6–10 week engagement that automates your Report of Wine Premises Operations (or DSP equivalent), excise tax returns, and COLA label pre-check — handed off to your ops team, not locked behind a platform.
Not every producer. This engagement pays back fastest for operations where compliance is a real monthly cost center — not a nuisance.
Filing TTB Form 5120.17 (Report of Wine Premises Operations, the “BROP”) and Form 5000.24 excise tax returns. Producing 10,000+ cases is where the math typically clears.
Filing TTB Form 5110.40 (Monthly Report of Processing Operations) and associated DSP reports. Craft distillers past ~2,000 proof-gallon production a month.
If your compliance manager has a second job (inventory, ops, HR) and TTB paperwork is always running late, the savings compound fast.
If the person who “knows compliance” is one person, and their departure would create a six-month training gap, you're running institutional risk the Autopilot resolves.
We've mapped the TTB workflow across dozens of wineries and distilleries. The failure modes are remarkably consistent.
Production data lives in InnoVint or Vintrace. Inventory lives in your WMS or a spreadsheet. Tasting-room removals come from the POS. Bulk transfers are buried in email threads. Every month, someone walks through all of it and types totals into the TTB form. There is no technical reason this should still be manual in 2026.
Proof gallons by brand and tax class, removals vs. returns, exemption tracking for exports and transfers in bond — it all has to balance against the BROP. A single miscategorized removal triggers hours of chasing.
A new label goes to TTB, and you wait 30–60 days to find out if it's rejected for a formatting issue that could have been caught in five seconds. Rejection means starting over. An LLM-based pre-check catches 80%+ of preventable issues before the submit button.
The tacit rules — which SKUs map to which tax class, how to handle blend returns, what counts as a “transfer in bond” — aren't written anywhere. When the compliance manager leaves, six months of your next hire's job is archaeology.
Every deliverable is yours at engagement end — source code, models, dashboards, and documentation. No platform lock-in.
Reads directly from your production and inventory systems, generates a pre-filled TTB Form 5120.17 (or 5110.40 for DSPs) every month. Your compliance manager reviews and signs, rather than assembles from scratch.
Computes proof gallons, tax class mapping, and removal categories from the same source data. Produces a review-ready F 5000.24 with full line-item traceability back to source transactions.
An LLM-powered label review that catches mandatory-statement issues, prohibited claims, class/type misalignment, and formatting problems before submission. Shortens COLA cycles from weeks of uncertainty to days of confidence.
A single pane of glass showing every number on every report, with one-click drill-down to source transactions. When TTB audits you — or when a new ops hire joins — the audit trail is the dashboard.
A written playbook for every monthly process, every edge case we encountered in your operation, and the team's role in each step. Your institutional knowledge, documented.
Two onsite training sessions for your ops team, plus 90 days of post-launch support for any edge cases or regulatory updates that surface after we hand off.
6–10 weeks, depending on the complexity of your production stack and the historical data cleanup required.
Fixed-price, scoped in the kickoff call. No hourly billing, no time-and-materials surprises.
All design, build, integration, and testing
Retro-validation against your last 3 months of filings
Two onsite training sessions for your ops team
Compliance runbook — written specifically for your operation
90 days of post-launch support included
All source code and documentation transferred to you
Final price within the range depends on production-system complexity and historical-data cleanup. Scoped precisely in the kickoff call before any work begins.
Legal interpretation of ambiguous TTB rules (keep your compliance counsel for that). Filing with TTB on your behalf — you sign and submit, we just prepare. State-level compliance and three-tier distribution reporting (separate scope if needed). Hardware, sensors, or physical-inventory rebuilds.
After the 90-day warranty, most clients retain us at $2K–$5K/month for quarterly model updates, new-form responses when TTB changes something, and priority support. Not required; the Autopilot runs without it.
Measured at the 90-day mark against your pre-engagement baseline.
On monthly compliance workload, measured in actual human-hours of ops-team time.
Fewer rejections, faster iteration, more new labels launched per quarter.
The compliance process is documented, reproducible, and runnable by anyone with a login.
Yes. We integrate with any system that offers an API or structured export, and we've worked with all the major winery and distillery production platforms. During the kickoff audit we confirm the exact integration path and flag anything unusual before contracting.
During the 90-day warranty, form updates are included. After that, they're covered by the optional retainer or billed as a short one-off engagement. TTB updates forms infrequently enough that most clients handle them via quarterly retainer.
Our commitments are laid out in full on our Data Principles page. Short version: your data is never used to train models, is stored in US-only infrastructure, is deleted at engagement end, and is covered by a mutual NDA signed before any working session.
Common, and built into the engagement. Week 1's system audit surfaces data quality issues and week 7's retro-validation catches the rest. If we uncover a fundamental data-integrity problem that requires more cleanup than scoped, we flag it early and either extend scope (with your approval) or narrow the Autopilot to what's cleanly automatable.
Yes — but their job changes. Instead of assembling reports, they review generated reports, handle exceptions, and manage TTB audits and new-license work. Most clients redeploy that capacity into higher-leverage work; some reduce the role to part-time.
Separate scope. The data pipeline we build for TTB can feed state compliance too, and we often scope a follow-on engagement for state reporting once the TTB Autopilot is running. It's a much cleaner build on top of the foundation.
A 30-minute scoping call is free. We'll look at your current compliance workflow, estimate your time savings, and give you a tight price within the range above.
Request a Scoping CallCovered by a mutual NDA before any data is shared.