A service can look profitable while the founder supplies unpaid research, account recovery, client reporting, and late-night reply handling. Sent-message pricing hides those costs until volume grows.
A useful model follows the work from source research to managed reply and allocates the capacity each client consumes.
Commercial answer
Calculate Telegram outreach unit economics per managed client and per qualified conversation. Include research and review labor, account and proxy inventory, campaign setup, reply handling, supervision, incidents, reporting, software, and rework. Revenue minus these variable and allocated service costs gives contribution margin. Do not price from sent-message volume because it ignores the work and risk that create quality.
Inputs for the model
- A complete cost model.
- Unit choices for retainers and delivery.
- Contribution-margin and capacity calculations.
- A method for exposing unpriced rework.
Choose two units
Avoid cost per sent message as the primary unit. A larger queue can lower that number while increasing unwanted contact, reply backlog, and account incidents.
| Unit | Why use it |
|---|---|
| Managed client-month | Pricing, staffing, and account inventory |
| Qualified, owned conversation | Delivery efficiency and source quality |
Inventory all service costs
| Cost group | Examples |
|---|---|
| Research | Community discovery, source scoring, profile review |
| Account operations | Account sourcing where lawful, proxies, inventory, authorization, monitoring |
| Campaign | Brief, copy, list QA, approval, queue supervision |
| Replies | Classification, response, qualification, follow-up, tickets |
| Quality and compliance | Suppression, audits, client isolation, incident review |
| Client service | Onboarding, meetings, reporting, revisions |
| Tools and infrastructure | CRM, data, communications, storage, backups |
| Rework | Wrong source, bad brief, duplicate data, missed handoff, recovery |
Calculate contribution
Track founder time at a market replacement cost even before drawing a salary. Otherwise the model rewards work that cannot be delegated profitably.
- Service revenue: retainer plus approved variable fees.
- Direct labor: actual time by role multiplied by loaded hourly cost.
- Direct account cost: proxies and client-specific inventory.
- Allocated platform cost: software and infrastructure share.
- Expected rework and incident cost: historical average or explicit buffer.
- Contribution margin: revenue minus all costs above.
Find the constraint
| Constraint | Business symptom | Improvement |
|---|---|---|
| Research | Large exports, low eligibility | Better source score and filters |
| Accounts | Frequent manual intervention | Inventory, isolation, and controlled queues |
| Replies | Backlog after successful campaigns | Capacity planning and handoff |
| Client revisions | Repeated changes after launch | Stronger brief and approval |
| Incidents | Unpriced recovery work | Stop rules and runbooks |
Price the system you can operate
- Set a base retainer for research, account, campaign, inbox, and reporting readiness.
- Limit included capacity with explicit account, campaign, or reviewed-audience bounds.
- Use change orders for new markets, clients, or account inventory.
- Avoid guaranteed outcome pricing when factors remain outside your control.
- Review margin by client and close the causes of rework.
Minimum model: monthly revenue minus research, account, campaign, reply, client-service, tooling, and expected rework cost. If any line is zero because the founder handles it, the model is incomplete.
Research note
This is a service-cost framework, not a market-rate claim or profitability guarantee. Local labor, account, legal, platform, and client requirements vary.
Pressure-test the economics
Time every activity for one client-month. The hidden cost will usually be reply handling, revision, or rework rather than delivery.
A sustainable service sells a controlled operating system, not an unlimited message count.
Reduce tool and handoff fragmentation: TeleBoost for agencies combines prospecting, campaigns, multi-account operations, replies, tickets, and teams in one workspace.
Continue the operating system
Related TeleBoost guides
Evidence base