Support as a hidden cost: self-service, tickets or paid onboarding?
Support costs money even when few requests arrive. A worked example explains required hours, team costs and the differences between self-service, individual requests and paid setup.
18 articles in this category
Follow this category by RSSTurning an idea into a service raises questions about costs and day-to-day operation. How much is left per customer? What happens when usage grows? When does support become a bottleneck? Here I work through those relationships.
Topics include SaaS pricing, MRR, churn, infrastructure costs and capacity. The calculators let you change assumptions and compare scenarios. Results depend on your inputs; it is often useful to see which single assumption makes the biggest difference.
Tools to try
SaaS profitabilityCompare pricing modelsMRR & churnCash flow & runwayAI usage budgetCustomer acquisitionAutomation costsDigital productsSupport capacity
Support costs money even when few requests arrive. A worked example explains required hours, team costs and the differences between self-service, individual requests and paid setup.
Web interfaces, APIs and MCP through a document-checking example: understandable results, limited permissions and protection against duplicate jobs.
Local file processing can reduce server costs. The comparison explains when synchronization, independent backups and team features are also needed.
A customer AI key or usage included in the product price: who pays the AI bill, what support costs, and where keys and data are processed.
Setup help, a pause or a discount: matching the response to the cancellation reason and measuring revenue after extra costs.
A worked example explains AI attempt costs, retries and reserves. Averages help planning; actual budget boundaries require bounded jobs and a reservation before execution.
An annual subscription brings cash early but continues to incur costs later. Concrete examples show how monthly plans, annual plans and one-time deals affect MRR and available money.
Demos, paid pilots and free entry can be compared through actual use and payments. A step-by-step example explains acquisition cost per customer and how monthly contributions recover it.
Payment per page fetch, agreed usage rights or regularly delivered data: this comparison explains three offers that can be combined. Cloudflare’s private beta does not guarantee paying buyers.
A newsletter, affiliate site and SaaS can serve the same agencies. An example explains who pays, what work continues each month and why €800 in revenue does not mean equal profit.