An outbound cost model should show what a proposed motion costs before you commit people, data, software, and operating time. Build it from cost drivers and compare each operating configuration with its own baseline. The expensive blind spot is the work around the send: most teams count only tool subscriptions when estimating outbound costs.1 Model the full outbound cost by including sending infrastructure, data and enrichment, automation, and, when relevant, fully loaded SDR compensation or agency retainers.2 That wider view changes the decision because a cheap stack can still carry expensive labor and overhead.
Set the boundary
Decide what the model must help you decide and which spend belongs inside it. A clear boundary keeps later comparisons from mixing unlike costs.
A cost model is a framework for calculating costs.3 Write down the costs it must capture: wages, expenses, and capital costs.4
If the model covers the sales budget, include the IT costs required to operate the sales organization, travel, sales personnel costs, and overhead allocated to sales.5 Keep traditionally defined marketing expenses outside that boundary when they belong to a separate campaign budget.6 If campaign production sits inside your outbound boundary, campaign costs can include design, copywriting, printing, postage, list rental or acquisition, data processing, and technology fees.7
Write the boundary at the top of the model. When someone proposes a new cost, you should be able to decide where it goes without changing the rules for existing rows.
List the cost drivers
Turn the boundary into rows that someone can price and update. Each row should describe the resource consumed, its rate or price, the period, and the activity it supports.
Relevant costing data comes from identifying the main cost drivers, determining component costs, and choosing a method for calculating the initiative's total cost.8 Use a loaded hourly cost when you want the estimate to include employer-paid taxes, benefits, equipment, and other compensation overhead.9
Include the work around meetings in the labor estimate. A direct labor estimate leaves out preparation, travel, note-taking, and follow-up work outside the scheduled meeting window.10 Add recurring credits and one-off list costs as separate rows so they remain visible when volume or targeting changes.11
Give time that has another productive use its own row. When outbound work displaces work elsewhere, the forgone contribution can affect the decision even if it never appears in the general ledger. Opportunity cost should be used when quoting or setting prices despite its absence from those accounts.12
Separate upfront, operating, and burden costs
Cost categories behave differently over time, so keep them separate before totaling the model. This makes it easier to see what changes when the program grows and what remains after a test ends.
Use CAPEX for capital expenditure, capital cost, investment cost, or upfront cost.13 Use OPEX for operating expenditure or operating cost.14 Put recurring software, data, labor, and operating work in the appropriate ongoing rows, while keeping an upfront setup cost visible on its own line.
Labor burden needs its own structure. Burden costs fall into two families that behave differently, which is why they need separate calculator fields.15 Per-hour burden can include vehicles, fuel, tools, protective equipment, devices, and paid nonbillable travel.16
Do not collapse every labor cost into a salary line. A rate that looks comparable on paper can carry a different amount of employer cost and nonbillable time.
Price each configuration
Once the drivers are listed, build a separate version of the model for each operating setup you might choose. Keep the rows consistent so the comparison shows a change in configuration, not a change in accounting.
Each parameter configuration has its own effective baseline, and costs should be calculated relative to that configuration-specific baseline.17 A model that calculates total cost for each system configuration can support more accurate estimates of resource requirements and return on investment.18
For every configuration, record the cost category, driver, unit, rate, period, expected activity, and resulting total. Use the same labor boundary, data boundary, and overhead treatment in every row. If one setup includes loaded labor and another includes salary alone, the comparison will favor the second setup before performance enters the discussion.
Keep assumptions beside the figures. When a rate changes, you should be able to see which total changes and which decisions depend on it.
Tie cost to volume and time
A total spend figure is useful only when you can see what activity it supports. Attach every configuration to the volume assumption that makes the budget meaningful.
A cost model should show the relationship between costs and the volume produced and sold.19 It should also allow a reasonably accurate calculation of cost and, from that, margin.20 Choose the output measure your budget decision uses, hold it constant across configurations, and show how the total changes as activity changes.
Keep time visible beside volume. A program can appear efficient when the model counts sends or meetings while leaving preparation, follow-up, and displaced work outside the calculation. The model should let you test the same activity with different labor, data, and operating assumptions.
Make the model maintainable
A cost model earns its place when someone can refresh it without rebuilding the logic. Keep the inputs simple enough that the person who owns each cost can supply an update.
A useful cost model is simple enough for the proper input data to be gathered and updated periodically.21 Accurate cost information improves the allocation of resources.22
Set a review point for rates, list costs, credits, labor assumptions, and activity volume. When an assumption changes, update the input row and preserve the prior configuration so the budget decision remains traceable.
What not to do
These mistakes make an outbound program look cheaper or more certain than it is.
- Do not present an outbound cost figure that leaves out SDR salaries, tooling, or management overhead.23
- Do not apply one company-wide multiplier to every type of work, because it can misprice different work in both directions.24
- Do not judge a system from its installation cost alone. Evaluating a service on installation cost instead of total cost of ownership is event costing.25