Pricing Services: Beyond Hours x Rate

Build the mental model

Pricing a service as simply hours multiplied by an hourly rate ignores most of what actually determines what a client will pay and what a business needs to survive. Real pricing accounts for the value created, the scope and complexity of the work, the risk taken on, the provider's experience and reputation, current market rates, urgency, the level of support included, and the underlying cost of running the business at all.

That pricing floor must account for labor, software, cloud and API costs, contractors, applicable taxes and fees, support time, risk, and profit. Exact tax treatment varies by jurisdiction and business structure, so treat this course as a framework for thinking, not as jurisdiction-specific tax or legal advice.

PRICING MODELS LANDSCAPE
------------------------
Hourly      -> optimizes for: flexibility on uncertain scope
Project     -> optimizes for: a fixed, defined outcome
Retainer    -> optimizes for: ongoing recurring access
Value-Based -> optimizes for: the client's economic value
Cost-Plus   -> optimizes for: a guaranteed minimum margin

Connect it to a real scenario

Before quoting any price, calculate your pricing floor first, using real numbers rather than round guesses. List every cost the engagement actually creates: your labor at a realistic rate, software subscriptions, API or cloud usage, any contractor cost, support time, and a margin that reflects real business risk -- not just enough to break even. The function below turns those inputs into a minimum sustainable price.

Once you know the floor, choose a pricing model deliberately instead of defaulting to hourly out of habit. If scope is well-defined, project pricing protects your time better than hourly. If the relationship is ongoing, a retainer creates predictable revenue. If you can point to a specific, verifiable business outcome the client cares about, value-based pricing may fit -- but only if you can actually show your reasoning, not just assert a bigger number.

Never present a price you cannot explain in plain terms if the client asks how you arrived at it.

• Pricing depends on value, scope, risk, experience, market, urgency, and support -- not hours times a rate alone.
• Each of the five pricing models -- hourly, project, retainer, value-based, cost-plus -- fits a different situation and carries different tradeoffs.
• Calculate a real pricing floor from actual costs and margin before quoting, and never charge below it without knowing you are doing so.

Try the working example

function calculatePricingFloor({ laborCost, softwareCost, apiCost, supportCost, desiredMargin }) {
  const totalCost = laborCost + softwareCost + apiCost + supportCost;
  const marginAmount = totalCost * (desiredMargin / 100);
  const minimumPrice = totalCost + marginAmount;

  return {
    totalCost,
    marginAmount: Math.round(marginAmount),
    minimumSustainablePrice: Math.round(minimumPrice),
  };
}

const example = calculatePricingFloor({
  laborCost: 1800,
  softwareCost: 120,
  apiCost: 60,
  supportCost: 100,
  desiredMargin: 25,
});

console.log(example);

Given laborCost 1800, softwareCost 120, apiCost 60, supportCost 100, and desiredMargin 25, calculatePricingFloor returns totalCost 2080, marginAmount 520, and minimumSustainablePrice 2600 -- the lowest price that covers cost plus a genuine 25% margin.

Value-based pricing — Wikipedia — Digital Business