Platform subscription
Plan, contact tier, sending volume, users, locations, and add-ons.
Build a realistic budget from software, list size, sending volume, design, staff time, data work, and optional integrations. Separate known invoices from planning assumptions.
A low subscription price does not describe the full operating cost. Record each item as a confirmed expense, a vendor quote, or an editable assumption.
Plan, contact tier, sending volume, users, locations, and add-ons.
Data cleanup, consent mapping, templates, authentication, integrations, and training.
Planning, writing, approvals, photography, design, QA, and scheduling.
Bounces, suppressions, preference changes, imports, exports, and access reviews.
Booking or order tracking, link tagging, reporting, and interpretation time.
Professional advice, privacy work, policy updates, and incident response when needed.
Every starting number below is an illustrative assumption, not an industry benchmark. Replace each value with the restaurant's own data.
Formula: attributed revenue × gross margin, minus software and labor. ROI equals estimated net contribution divided by software and labor cost. This does not prove causation and excludes taxes, discounts, refunds, capacity constraints, and other operating costs.
Attributed revenue is not automatically incremental revenue. Some recipients would have ordered without the email, some reservations may displace other demand, and discounts can reduce contribution. Compare the model with actual restaurant capacity, gross margin, cancellation behavior, and campaign costs.
After sending, replace assumptions with measured data. Keep the original assumptions so the team can see why the estimate changed. Do not publish the calculator output as an industry benchmark or guarantee.
Connect the budget to a strategy