StormTrust should maintain a separate margin model for every meaningful delivery class.
| Class | Example costs |
|---|---|
| Platform | Workers, D1, R2, Queues, and observability |
| Data | Property, contact, mapping, and licensed weather data |
| Implementation | Configuration, import, training, and project work |
| Integration | CRM mapping, reconciliation, and custom adapters |
| Review | Meteorological or other qualified human work |
| Support | Live-event coverage and customer operations |
Track these measures by offer and customer segment:
- Collected revenue
- Gross profit
- Acquisition cost
- Payback period
- Implementation hours
- Support hours
The initial strategy proposes an implementation fee plus a recurring operations subscription. It also proposes usage-based or contracted allowances for premium data and reviewed services.
These values are test inputs. Replace illustrative margin and payback examples with actual collected revenue and fully loaded delivery costs.
Do not scale paid acquisition until the offer has a plausible payback model and sufficient fulfillment capacity. Do not hide loss-making services inside high software margins.