The working prototype validated the product direction. We are now rebuilding Guidance for commercial release, with a pricing model intended to stay accessible to growing CPG brands.
Pricing
These are draft commercial tiers, not plans that can be purchased today. Final module availability, point allocations, and pricing will be set before launch.
Our current pricing design avoids feature gating across tiers. Final module availability, integrations, point allocations, and prices will be published before commercial release.
Explore the problems the planned modules are designed to address:
Why spreadsheet COGS tracking breaks Lot traceability and FSMA 204 Demand forecasting for food brands COGS calculation guideTarget Model
We are evaluating a point model tied to infrastructure activity such as compute, storage, and AI processing. The table below illustrates the proposed mechanics; it is not a current billing schedule.
Point weights, allocations, overage pricing, and change-notice protections are still being calibrated with design partners and will be published before launch.
| Action | What It Triggers | Weight |
|---|---|---|
| Incoming order received | DB write, inventory update, lot assignment | Low |
| Purchase order sent | DB write, supplier notification, cost snapshot | Low |
| Inventory sync (Shopify / Amazon) | API call, reconciliation, lot matching | Medium |
| Production run completed | Yield calculation, COGS finalization, traceability write | Medium |
| Compliance audit generated | AI processing, document assembly, multi-table read | High |
| Demand forecast run | Compute-heavy multi-SKU projection | High |
Proposed Customer Protections
The protections below are target commercial policies under review. They are not current contractual terms and may change before launch.
The proposed model would use a trailing three-month activity average so a temporary seasonal spike does not immediately change a tier. Credit mechanics remain under review.
The intended circuit-breaker policy would pause billable accumulation when an automated integration creates abnormal activity, while alerting the customer and preserving data flow where technically possible.
The target policy would make prompt retries free within a defined window when an AI output fails or requires immediate regeneration. The exact window and eligibility rules are not final.
The proposed policy would notify customers when sustained activity suggests a lower tier may fit better. Automatic credits and downgrade rules remain under review.
Target AI Transparency Layer
The proposed transparency layer would show where points were used and surface ways to reduce cost. The example below is an illustrative product concept, not a live customer invoice.
We are still building. When we launch, the people who signed up early will hear first, have direct input on what we build next, and will be the first customers we work with to get pricing right.
No credit card. No commitment. We will reach out personally when we are ready.
FAQ