Define the delivery represented by the price
Before calculating a price, describe what the customer receives and the conditions under which work will be performed. Include preparation, execution, revisions and relevant dependencies. Scope gives meaning to the quoted amount and enables comparison without assuming that two services with the same name require equal effort or address exactly the same need for the buyer.
An implementation may cover configuration alone or also diagnosis, information migration and team preparation. If these differences remain implicit, customers compare prices for different deliveries and operations inherits expectations missing from the estimate. The proposal should make those choices visible, including anything that will require an additional decision before it can be included.
Record what the customer must provide and when. Late or incomplete information may change sequencing and coordination effort. Defining these conditions supports a realistic estimate and a clear discussion when changes arise. Your positioning and value proposition should remain recognisable in this concrete delivery description, connecting the promise that attracted the customer with the work being priced.
Estimate effort including less visible work
Service effort includes more than the production hours visible in the final result. Meetings, preparation, reviews, coordination and resolving questions also consume capacity. Estimate these components separately and state where assumptions came from, so you can later identify which parts of execution matched or departed from the scenario used to establish the price of the service.
Where comparable previous projects exist, use their records while considering differences in scope. Where they do not, present the estimate as a hypothesis and identify the most uncertain activities. An unexplained time allowance can conceal missing information; it is more useful to know which part of the work still requires confirmation.
Include the founder's time when they participate in delivery. The absence of an additional payment for each hour does not make that capacity unlimited or irrelevant to the decision. Preserve the distinction between an internal capacity allocation and an actual additional expense caused by the project. Keeping these categories separate avoids counting the same expense twice in the analysis.
Distinguish direct costs, overheads and business results
To analyse an offer, separate costs attributed to delivery from the overheads the business supports. The amount remaining after the project's selected costs must be interpreted according to that scope. Only a complete view of revenue and expenses allows assessment of the overall result, including costs that have not been allocated to each individual service or project.
Specific software, external work and materials may be directly associated with a delivery. Other resources are shared between projects and need a consistent allocation method when included in the analysis. Explain that method in the worksheet so comparisons between services do not change merely because expenses have been classified differently.
Avoid calling an amount net profit when it still needs to cover overheads, other charges or taxes. Do not confuse cash received with revenue expected under a contract. An internal estimate can support capacity decisions; financial accounts require the records and accounting treatment appropriate to the business. Clarify the question before selecting the number that is supposed to answer it.
Build a worksheet with visible assumptions
An analysis worksheet should let you change price, effort and costs without hiding how the result is calculated. Keep assumptions separate from formulas and identify each field's unit. The following example is entirely hypothetical and only demonstrates how an operational estimate changes when the work required differs from what was originally expected for the service being delivered.
| Field | Hypothetical example | Interpretation |
|---|---|---|
| Service price | €2,000 | Amount excluding taxes on the sale |
| Estimated effort | 30 hours | Total time attributed to delivery |
| Internal hourly cost | €30 | Assumption for allocating capacity |
| External work | €200 | Additional cost of this project |
| Specific tool | €100 | Additional cost not included above |
| Modelled cost | €1,200 | 30 × 30 + 200 + 100 |
| Balance after modelled costs | €800 | 2,000 − 1,200, before remaining costs |
This balance is neither net profit nor a typical industry margin. If effort rises to 40 hours while other assumptions remain unchanged, modelled cost rises to €1,500 and the balance falls to €500. The comparison shows why tracking effort and controlling scope can change the interpretation of a price that initially appeared appropriate for the project.
Consider price and capacity together
A service also needs assessment through the capacity it occupies and the commitments it prevents you from accepting. Observe duration, intensity, dependence on particular people and coordination requirements. Two offers with the same estimated balance may demand very different schedules, so commercial choices should consider how each one fits into the operation and commitments that already exist.
A delivery concentrated on one person can limit the number of active customers even when other functions have availability. A project with long waiting periods may consume little production time but require ongoing coordination. Representing these differences avoids decisions based only on total price or average hours that hide important operational dependencies.
The agreed sequence of receipts and payments matters too. A project can look attractive in an estimate while requiring resources before the customer pays. Include that need in operational planning without confusing cash timing with economic results. Managing a service business requires connecting demand, estimated margins and the capacity to deliver work under the conditions being offered.
Review scope and changes during execution
Price management continues after proposal acceptance because delivery may change during a project. Define how additional requests will be identified, their impact assessed and agreement obtained before execution. This procedure makes changes understandable to customers and prevents accumulated small decisions from altering the service without an explicit review of the commitment and resources required to fulfil it.
Not every question requires a new proposal. Distinguish clarification within scope from work that adds deliverables, revisions or responsibilities. Record the request, its effect on execution and the decision taken. A concrete explanation of effort and consequences is usually more useful than invoking a limit without connecting it to the delivery originally agreed.
When you choose to absorb a change, record that choice and its reason. It may make sense in a particular situation, but should not disappear from later analysis as though the work never happened. That history helps identify whether the offer needs different boundaries, better diagnosis or another price to remain sustainable under similar circumstances.
Learn from completed projects before changing prices
Review estimates against execution to understand differences in effort, costs, scope and perceived value. Use several cases where available and preserve each one's context. This analysis helps decide whether to adjust pricing, improve processes, redefine the offer or qualify enquiries more effectively, instead of attributing every difficulty to the amount charged for a service or project.
A project requiring more effort than expected may reveal an exception or a recurring weakness in the proposal. A difficult sale may reflect unclear delivery, an unsuitable audience or comparison with a different solution. Commercial and operational review distinguishes these situations and helps select a change that addresses the problem actually observed.
To review pricing in relation to operations, send the context through the individual mentoring form. Describe the service, usual scope, approach to effort estimates and difficulties encountered. We can organise assumptions and management questions using your business information, without treating a hypothetical calculation as a universal recommendation for what you should charge.