Events
Item added, used, expired, reordered, wasted, substituted, price paid, store, category.
BellPath Business Control
Customers • Licenses • Sales • Support • UpdatesBusiness control actions
Make BellPath measurable, manageable, and sellable.
This control layer organizes the business behind the apps: customer records, license ownership, revenue proof, support load, updates, product scoring, pantry/data-model strategy, and acquisition readiness.
Open CustomersReview SalesPlan Data ModelScore ProductsCustomer Control
Track leads, customers, products owned, lifetime value, support history, and the next action for each account.
| Name | Status | Products | LTV | Next action |
|---|
License / Unlock Control
Use this as the control plane for activation keys, product access, admin overrides, revoked keys, and upgrade eligibility.
| Key | Product | Status | Owner | Issued | Notes |
|---|
Sales Proof
Track monthly revenue by product and channel. This is the core evidence needed for profitability decisions and future buyers.
| Month | Product | Revenue | Orders | Refunds | Channel |
|---|
Support Load
Support volume tells you which products are scalable and which products need fixes before marketing harder.
| Ticket | Status | Priority | Topic | Next action |
|---|
Updates & Changelog
Every release should be tied to a version, product, status, and customer-facing summary.
| Version | Product | Status | Summary |
|---|
Product Decision Scores
Score each product on revenue, usage, support burden, growth, and acquisition value. Double down on what scores highest after real data arrives.
Acquisition Readiness
| Area | Status | Next step |
|---|
Buyer Package Checklist
- Monthly P&L and product revenue report
- Customer count, refund rate, and support load
- Source files, release notes, and IP ownership notes
- Demo videos for each core app
- Clear privacy/data policy and consent model
- Growth roadmap and product score history
Pantry/Data-Model Strategy
The future data layer should start with consented, aggregated, non-sensitive event patterns. Pantry is the most natural first data model because it creates repeat household inventory events.
Value
Demand forecasting, household waste trends, price sensitivity, shopping frequency, category gaps.
Guardrails
Consent first, anonymize, aggregate, export/delete controls, no sale of personal identity.
Scale threshold
Useful internal insight at 100 users. Interesting data asset at 100,000+ users. Serious acquisition value at larger scale.
Business control modules
Business layer now tracks the company, not just the apps.
Customers
Customer ID, purchases, owned products, support history, upgrade opportunities. Licenses
License keys, activation status, product access, revocation notes, owner override. Sales
Orders, bundles, revenue, refunds, conversion, and product performance. Support
Tickets, bug reports, lost-download requests, feature requests, response status. Updates
Current version, latest version, release notes, download channel, update urgency. Product Scores
Revenue score, usage score, support burden, growth potential, exit value. Acquisition Readiness
ARR/MRR, customer count, retention, IP docs, demo assets, buyer checklist.
Customer ID, purchases, owned products, support history, upgrade opportunities. Licenses
License keys, activation status, product access, revocation notes, owner override. Sales
Orders, bundles, revenue, refunds, conversion, and product performance. Support
Tickets, bug reports, lost-download requests, feature requests, response status. Updates
Current version, latest version, release notes, download channel, update urgency. Product Scores
Revenue score, usage score, support burden, growth potential, exit value. Acquisition Readiness
ARR/MRR, customer count, retention, IP docs, demo assets, buyer checklist.