Pricing Services

A service price is a promise about who does what, by when, with which inputs, risks, and exclusions, in exchange for money. It is not a number copied from a competitor or a personal worth score. Good pricing helps the right customer say yes, keeps the work fundable, and makes the cost of changes visible.

This guide builds on the customer and sales decisions in G06 and G07. It shows how to find a delivery floor, estimate customer value, structure a package, calculate contribution, price changes and risk, and review evidence after delivery. It also connects pricing to the cash, tax, capacity, and privacy boundaries covered later in the library.

A low price can be strategically useful for a clearly bounded pilot, but only when the learning or relationship value is explicit. A high price is not automatically credible. The test is whether the buyer can understand the result, the provider can deliver it responsibly, and the relationship can continue without hidden subsidy.

Opportunity and Customer

Pricing starts with the decision the buyer is making. A buyer comparing a 200 diagnostic with a week of internal effort is not using the same value logic as a buyer comparing a 20,000 implementation with a revenue-critical system replacement.

Define the unit of purchase

Choose one clear unit:

• One diagnostic.
• One fixed-scope project.
• One volume band of work.
• One monthly operating service.
• One retained advisory block.
• One implementation with a defined launch.

The unit should match how the customer experiences the result and how you measure delivery. "Consulting" is not a unit. "A 90-minute workflow review and a written exception list" is.

Identify the value driver

Ask what changes when the work is done well:

• Saved paid time.
• Faster payment or job completion.
• Fewer errors and less rework.
• Reduced delay or customer abandonment.
• Better evidence for a decision.
• Lower compliance exposure.
• More capacity during a peak.
• A better customer experience.

Do not claim a value you cannot measure. Use the buyer's estimate, label assumptions, and preserve uncertainty. If a task saves four hours per month, the value depends on what those hours can be used for and whether the time is actually paid or recoverable.

Segment by buying situation

The same service may require different packaging for:

• A solo operator who needs a fast start.
• A five-person team with an administrator.
• A regulated organization that requires review and documentation.
• A customer with high volume and stable inputs.
• A customer with low volume, urgent exceptions, and multiple approvers.

Different economics may justify different prices. Secretly charging one customer more for identical work can create fairness and communication problems. It is better to publish or explain the package logic: volume, turnaround, access requirements, risk, and support level.

Qualify before quoting

Before offering a price, know:

• The output and acceptance criteria.
• Volume and expected exceptions.
• Who supplies inputs.
• What systems and access are required.
• Turnaround and review rounds.
• Privacy and regulatory constraints.
• Who approves the purchase.
• What happens if scope changes.

An early indicative range can keep a conversation moving. A final price without these facts is a guess with a professional-looking font.

Fit and Skills

Pricing requires enough operational knowledge to estimate work and enough discipline to preserve the assumptions built into the quote.

Build estimating skill

Track every engagement in time bands:

• Customer setup.
• Input preparation and correction.
• Core delivery.
• Review.
• Communication.
• Rework.
• Administration and invoicing.
• Sales follow-up.

Use ranges rather than a single precise hour. A new workflow may take two to three times longer than the steady-state version. Mark uncertainty and add a contingency where the work is unfamiliar.

Separate your time from the customer's outcome

Hourly pricing can be useful for uncertain work or a time-based advisory block. It also rewards slow delivery and requires customers to audit hours. Fixed pricing is easier to approve and improve, but it transfers more delivery risk to you. Monthly or value-based pricing can create continuity when the service has recurring value, but it requires clear service levels and capacity.

Many small service businesses use a mixture:

• Fixed fee for a defined diagnostic.
• Fixed project price for a stable workflow.
• Monthly base for recurring coverage.
• Unit bands or change orders for volume and exceptions.

Learn to read delivery constraints

Price must account for:

• Your maximum sustainable hours.
• The number of reviews required.
• Customer response delay.
• Tool and data limits.
• Seasonal demand.
• The cost of maintaining quality.
• Time needed for sales, learning, and administration.

If only ten hours per week are available for delivery, a full calendar of low-margin work is not growth. It is capacity exhaustion.

Practice explaining price without apology

Use a calm structure:

1. Restate the result and boundary.
2. Give the price.
3. Explain what it includes.
4. State the next step.
5. Allow silence for the buyer to think.

Avoid introducing a price with "I know this is expensive" or immediately offering a discount before the buyer responds. Confidence comes from a clear, testable economic case, not from claiming the price is cheap.

Startup Budget

Pricing decisions should include the cost of operating the business, not only the direct work.

Calculate a lean monthly floor

List:

• Personal essential spending that the business must help cover.
• Business tools and communication.
• Banking and payment fees.
• Insurance and professional advice.
• Registration, bookkeeping, and tax preparation reserve.
• Marketing and sales cost.
• Replacement or repair reserve.
• A small contingency.

Illustrative example: an owner needs 3,000 for personal essentials, estimates 350 in business tools and administration, 250 for insurance and professional support, 200 for sales and travel, and 200 for a reserve. The lean monthly cash target is 4,000 before income tax and debt repayment. The business does not need to earn that in the first week, but pricing cannot ignore it indefinitely.

These figures are illustrative and depend on jurisdiction and personal circumstances.

Keep setup costs proportional

Do not buy pricing software, a complicated accounting stack, or a brand package to produce a first quote. A spreadsheet, invoice template, and clear proposal are enough. Invest in advice when contracts, regulated data, taxes, insurance, or substantial customer concentration make the risk material.

Account for payment timing

If a 1,500 project costs 300 before delivery and the customer pays 30 days after acceptance, you may need cash to carry the work. A deposit, milestone payment, or shorter payment term can reduce that burden, subject to your market and local rules. Do not assume every customer accepts the same timing.

Track overhead per billable unit

If monthly operating overhead is 1,200 and you can responsibly deliver 40 service hours, the overhead allocation is 30 per hour before personal pay, tax, and profit. If your price is based on direct time only, that number is missing.

The arithmetic is not a recommendation to charge by the hour. It is a way to see whether current prices fund the business that supports delivery.

Skill Acquisition

Learn pricing by comparing estimates with actual records.

Estimate in ranges

For a new task, write:

• Best-case hours.
• Likely hours.
• Worst-case hours.
• The assumptions that create the range.
• The point at which you would stop and re-scope.

After delivery, compare actual time and cost with the range. Improve the questions you ask, not merely the hourly number.

Use a reference package

Build a fictional example:

"One workflow diagnostic for one team, one recent data set, and two live calls. Includes a process map, exception list, and 30-minute review. Starts after approved inputs. Fee 600. Additional workflows require a new scope."

Test the language with a peer. If they cannot identify the customer, output, and boundary, the package is not yet clear.

Learn contribution accounting

For each offer, calculate:

Contribution before overhead and owner pay = price - direct costs - rework reserve.

Then allocate sales cost, general overhead, tax reserve, and owner capacity. A service can show positive contribution and still fail because it consumes too much owner time or sales effort.

Review after every engagement

Hold a short post-delivery review:

• Quoted hours versus actual.
• Input quality.
• Number of review rounds.
• Change orders.
• Customer questions.
• Rework.
• Cash received.
• Whether the buyer would purchase again.

Change one part of the price model at a time: scope, input requirements, volume band, turnaround, or fee. Avoid changing all variables after one unusual project.

Setup

Pricing needs a small operating system so each quote reflects the same assumptions.

Create a price book

For each offer, record:

• Offer name.
• Customer type.
• Included output.
• Inputs and access.
• Volume range.
• Turnaround.
• Review rounds.
• Exclusions.
• Base price.
• Optional add-ons.
• Payment terms.
• Last reviewed date.

Keep internal cost assumptions separate from customer-facing material. A public price sheet may be appropriate for a standardized service. Complex or regulated work may require a quote after diagnosis.

Define change rules

A written change process should state:

• Who can request a change.
• What information the request must include.
• How impact on fee and schedule is decided.
• Whether work pauses until approved.
• How the new total is recorded.

This protects both sides. It also gives the customer a predictable way to expand without turning every conversation into an argument.

Establish payment and invoicing terms

Clarify:

• Currency.
• Tax treatment.
• Deposit or milestone schedule.
• Invoice delivery method.
• Due date.
• Late-payment process.
• Cancellation and refund terms.
• Costs caused by missing inputs or repeated access delays.

Local tax, invoice, consumer, and contract rules vary. Use a qualified local adviser for terms with meaningful legal or financial consequences.

Keep a capacity ledger

Before accepting a new project, record:

• Delivery hours committed.
• Review hours committed.
• Administrative load.
• Sales and onboarding time.
• Personal reserve.
• Remaining capacity by week.

The ledger turns "I think I can fit it" into a visible decision.

Set discount authority

Decide in advance when a discount is allowed:

• Early pilot with explicit learning value.
• Reduced scope.
• Prompt payment.
• A package that improves utilization without adding risk.
• A strategic relationship with a written boundary.

Record the reason and end date. Recurring discounts should become a revised offer, not an accidental permanent price.

Concrete Offer

Strong offers make the price easier to understand because the buyer can compare a result, not a pile of activities.

Three-tier design

A diagnostic tier:

• One workflow.
• One recent cycle.
• Map, findings, and review.
• Fixed lower price.

A pilot tier:

• One workflow and volume band.
• Defined queue or output.
• One review round.
• Fixed project fee.

A recurring tier:

• Defined coverage window.
• Volume band.
• Recurring reports and exception handling.
• Monthly price plus a change process.

The tiers should differ in responsibility and volume, not only in cosmetic extras. If the middle tier includes every useful part of the top tier, the structure is arbitrary.

Offer a useful range

When exact volume is unknown, present an indicative range with a condition:

"Projects with up to 100 approved source records and no more than two review rounds usually fall between 700 and 900. After the input review, I will confirm the fixed fee before work begins."

This is more honest than a false precise quote.

Price the risk

Add explicit fees or boundaries for:

• Rush turnaround.
• Multiple approvers.
• Legacy or inconsistent inputs.
• Sensitive data requiring extra controls.
• On-call availability.
• Extra review rounds.
• Weekend or holiday coverage.

A risk premium is not a punishment. It funds the extra attention needed to protect quality.

Explain what is not included

Excluded items may include:

• Legal, tax, accounting, or medical advice.
• Licences or certifications.
• Purchase and use of customer software.
• Chasing missing information beyond an agreed number of attempts.
• Unrestricted emergency response.
• Customer data cleanup before the scope begins.

State whether excluded work is unavailable or available through a separate quote.

Outreach

Pricing should be introduced as a decision aid, not hidden until the end of a long pitch.

Qualify the buying situation

In outreach, ask:

• Is this recurring or one-time?
• Who currently does the work?
• What volume is involved?
• Who approves a small paid test?

Do not lead with a price when you have not qualified. Do not lead with a discount either. Use a short range or entry point when it helps the buyer decide whether a conversation is relevant:

"The first diagnostic is a fixed 450 and covers one workflow. If the issue is broader, we can decide afterward whether a larger project is useful."

Use proposals to make tradeoffs visible

Offer two options only when both are genuinely appropriate:

• Diagnostic only.
• Diagnostic plus implementation.

Avoid adding a deliberately bad decoy option. Customers should be able to choose the level of responsibility they want without being manipulated.

Respond to price objections with diagnosis

When a buyer says the fee is too high, ask:

• Is the total above the available budget?
• Is the cash timing difficult?
• Is the result uncertain?
• Is the scope larger than needed?
• Is another provider using a different model?

Possible responses include a narrower scope, a phased start, a payment schedule, or a clear no. Do not immediately reduce the price while keeping every responsibility.

Make referrals coherent

If a partner recommends you, give them a short, accurate description of your starting offer and typical range. Do not ask them to promise a result or negotiate a secret commission without disclosure. Referral incentives may be regulated or inconsistent with the customer relationship.

Pricing and Unit Economics

This section turns the price into a repeatable financial test.

Fixed-project example

Illustrative pilot:

• Price: 1,200.
• Direct data or software cost: 50.
• Payment fee: 35.
• Delivery: 14 hours at 40 cost basis = 560.
• Administration and communication: 3 hours at 40 = 120.
• Expected rework: 80.
• Sales and proposal time: 2 hours at 40 = 80.

Contribution before general overhead and tax reserve is 275. If monthly overhead is 1,000, this project covers more than a quarter of it, but it is not pure profit. If it repeats without the same sales effort, the unit economics improve.

These are illustrative figures.

Monthly service example

• Price: 1,400 per month.
• Included volume: 80 requests.
• Planned delivery: 15 hours.
• Ongoing administration: 3 hours.
• Tools and payment: 60.
• Rework reserve: 100.
• No new acquisition cost after the first three months.

The owner should compare this recurring work with the capacity and contribution of one-time projects. A lower headline price can be superior if it uses predictable capacity and produces less sales effort.

Contribution margin

Contribution margin = contribution before overhead and owner pay / price.

If the 1,200 pilot produces 275 contribution, the margin is about 22.9 percent. Whether that is enough depends on overhead, utilization, and strategic value. Report the calculation rather than describing a small remainder as profit.

Break-even volume

If monthly business overhead is 1,500 and an average project produces 300 contribution, the business needs five projects per month before owner pay and tax reserve, assuming projects are otherwise identical. Real demand and costs vary. The calculation reveals the scale implied by the price.

Customer lifetime economics

Track repeat purchases separately:

• First purchase contribution.
• Repeat purchase contribution.
• Referrals generated.
• Support load.
• Retention period.

Do not assume every first customer becomes a multi-year client. A customer who returns because the result works is evidence. A customer who buys once because of an aggressive discount may not be.

Review price after delivery

Update a price when:

• Actual hours consistently exceed the quote.
• Input quality changes.
• Tool or compliance cost changes materially.
• The service becomes more standardized.
• Demand exceeds responsible capacity.
• The customer requests a different service level.

Communicate changes with notice and preserve existing agreements according to their terms and local requirements.

Delivery Example (Illustrative)

This is a composite example, not a real client case.

A former hotel revenue analyst offers a weekly report service to small independent guesthouses. The report organizes booking pace, cancellations, and channel mix from exports the owner already receives. The service does not access the booking system directly.

The first offer is a one-time 350 diagnostic. It maps the current report, identifies which fields are unreliable, and produces a fictional sample of the weekly summary. The buyer is the guesthouse owner. The buyer's part-time manager supplies the approved export files.

The guesthouse buys the diagnostic. The owner then asks for a weekly service. The analyst quotes 600 per month for up to four properties, four weekly reports, one revision per report, and a 24-hour response window on data questions. The fee excludes forecasting advice and emergency support outside the stated window.

After the first month, actual delivery takes nine hours instead of the estimated six because two property exports use inconsistent date formats. The analyst does not silently absorb the problem forever. She adds an input-standard checklist and offers a 150 one-time cleanup. For future months, the customer agrees to use the checklist before sending files. The monthly price remains 600 because the input process now fits the original assumption.

After three months, demand grows to six properties. The analyst offers a second band at 850, with additional volume and another review cycle. The owner can see why the fee changes. A second guesthouse asks for the same service, but it wants direct access to a sensitive booking account and same-hour emergency reports. The analyst quotes the first service separately and declines the account access because her privacy and security process does not support it. The refusal protects the price and the service.

Growth

Pricing supports growth when it funds quality and creates room for better work.

Raise price with a reason

Reasons can include:

• New measurable scope.
• Faster turnaround.
• Additional review.
• Expanded reporting.
• A higher-volume band.
• Increased compliance or security requirements.

Raising the same service's price because demand is high can be valid, but new customers should receive a clear current price and existing customers should receive appropriate notice under their agreement.

Standardize before adding tiers

If every quote requires a custom spreadsheet, the business cannot scale without more owner time. Turn repeated project elements into checklists, templates, and standard boundaries. Keep customization for cases where it creates real value.

Improve utilization without overbooking

Use demand data to see when capacity is idle or saturated. Add a package that fills predictable gaps if it does not reduce quality. Do not fill every hour with delivery; sales, administration, learning, and recovery are part of operating capacity.

Build a portfolio of offers

A healthy mix might include:

• A small diagnostic.
• One repeatable core project.
• A recurring service.
• An occasional high-review implementation.

Review the mix monthly. If the highest-revenue work also creates most of the risk and support load, the headline number is incomplete.

Make ownership visible

Pricing creates surplus when the business collects more contribution than it consumes. Decide in advance how surplus funds reserves, owner pay, tax, debt reduction, tools, and future assets. G15 develops that allocation process.

Risks

Underpricing from incomplete estimates

The most common hidden costs are input cleanup, customer communication, approvals, rework, and sales. A low price can look profitable when only direct delivery hours are counted.

Overpricing without proof

A high price requires a credible result, buyer, boundary, and evidence. If the buyer cannot understand why the package costs more, the offer needs clarity rather than a better closing script.

Scope creep

Free additions slowly turn a profitable offer into an unmeasured loss. Use change rules and record repeated requests as evidence for a new package.

Hourly-work traps

Hourly pricing can fit uncertain advisory work, but it may punish efficiency and make budgeting difficult. If using it, define the block, time record, expiration, and what counts as work.

Uncertain taxes and classification

Tax treatment, invoice requirements, refund rules, and service classification vary by jurisdiction. Price the offer before tax according to local practice, and reserve for obligations rather than treating gross revenue as owner income.

Payment risk

A large project with one customer can consume cash and capacity. Use deposits, milestones, customer approval points, and credit checks where appropriate and lawful.

Customer concentration

A buyer who represents most of the revenue gains substantial negotiating power. Price and capacity decisions should recognize that concentration risk. G14 develops resilience.

Hidden automation cost

AI and workflow tools can reduce effort, but subscriptions, verification, data handling, and exception work remain. Recalculate price after the automated workflow is stable rather than assuming the tool creates pure margin.

This guide is general education, not tax, accounting, legal, or regulatory advice. Confirm local obligations with a qualified adviser.

Privacy and AI Verification

Pricing often requires sensitive information about volume, customers, employees, and finances. Collect only what affects the price.

• Do not ask for full customer records to produce an estimate.
• Use counts, field lists, or sanitized samples first.
• Keep quotes and cost models access-controlled.
• Avoid pasting confidential data into public AI tools.
• Verify any AI-assisted cost estimate against actual invoices and time records.
• Do not let AI invent market rates or competitor prices.
• Record the assumptions behind each quote.
• Remove old pricing files according to your retention policy.

AI can help build a checklist, calculate formula results, or rewrite a scope description. A human must confirm the numbers, the offer boundary, and whether the pricing method is lawful and fair.

30-Day Action Plan

Days 1 to 3: Build the cost baseline

• List direct costs, overhead, tax reserve, and personal cash needs.
• Estimate available delivery, sales, and administration capacity.
• Set a minimum contribution target for the next month.
• Record every pricing assumption in one file.

Days 4 to 7: Define one offer unit

• Choose a diagnostic, fixed project, or recurring service.
• Write the output, inputs, volume, review, exclusions, and finish condition.
• Identify the buyer's value driver without overstating it.
• Create a fictional example with realistic exceptions.

Days 8 to 11: Estimate the work

• Time the workflow end to end using fictional data.
• Include setup, communication, checking, rework, and administration.
• Set best, likely, and worst-case ranges.
• Identify the assumptions that most affect the cost.

Days 12 to 15: Calculate price options

• Calculate contribution for a fixed fee.
• Calculate a recurring monthly version.
• Identify risk additions and scope reductions.
• Test break-even volume against realistic demand.

Days 16 to 19: Write the offer

• Create a one-page package description.
• State price, payment, validity, and change process.
• Prepare an indicative range for uncertain work.
• Ask a peer or experienced operator to find ambiguous language.

Days 20 to 23: Test with qualified buyers

• Present the offer in at least five diagnostic conversations.
• Explain price, then listen.
• Record questions, objections, and requested variations.
• Offer narrower scope instead of automatic discounts.

Days 24 to 27: Deliver one paid test if accepted

• Track delivery, administration, communication, and rework hours.
• Protect the quality checks included in the price.
• Record every scope request.
• Confirm acceptance before starting additional work.

Days 28 to 30: Compare and revise

• Compare actuals with the estimate.
• Calculate contribution and break-even.
• Change one assumption, scope item, or price band.
• Set the price for the next customer and review it after the next engagement.

Templates

Pricing assumptions sheet

• Offer:
• Customer and volume:
• Included output:
• Inputs and access:
• Delivery hours:
• Review rounds:
• Administration hours:
• Sales hours:
• Direct cost:
• Rework reserve:
• Overhead allocation:
• Tax reserve:
• Minimum contribution:
• Quoted price:

Contribution calculator

• Price:
• Direct tools or data:
• Payment fees:
• Delivery time cost:
• Administration time cost:
• Rework reserve:
• Sales time cost:
• Contribution before overhead and owner pay:
• Contribution margin:

Change-order request

"Requested change: [description]. Impact: [additional output, volume, risk, or schedule]. Revised fee: [amount]. Revised finish date: [date]. Please approve in writing before the changed work begins."

Price conversation opener

"The diagnostic is [price] and covers [scope] with [review]. It starts after [inputs] and ends with [acceptance condition]. Would you like to proceed on that basis, ask a question about the boundary, or leave it for now?"

Package description

• For:
• Problem:
• Result:
• Included:
• Not included:
• Customer provides:
• Timeline:
• Review:
• Price and payment:
• Change process:
• Next step:

Post-delivery price review

• Quoted hours and actual hours:
• Quoted direct cost and actual cost:
• Rework:
• Scope requests:
• Payment collected:
• Net contribution:
• Customer repeat signal:
• Price or scope change for next time:

Common Mistakes

Copying a competitor's price

The competitor may have different costs, volume, quality, risk, or customer segment. Use market context, then price your own unit.

Treating revenue as profit

Gross receipts must fund delivery, tools, sales, tax, overhead, and owner pay. Calculate contribution.

Offering unlimited revisions

Unlimited review transfers all uncertainty to the provider. Define review rounds and what counts as a new request.

Raising the price without improving clarity

The buyer needs to understand the result and responsibility. Better packaging can be more valuable than a higher number.

Discounting to avoid a difficult conversation

Ask what is behind the objection. The answer may be timing, scope, uncertainty, or no fit.

Ignoring payment timing

A profitable project can exhaust cash if inputs and expenses arrive before payment.

Pricing without capacity

Demand is not useful if accepting it damages quality, health, or other commitments. Capacity is part of the price model.

Key Takeaways

• Define a clear unit of purchase and the result the buyer receives.
• Estimate all work, not only the core delivery task.
• Set a price floor from cost, overhead, tax reserve, and capacity.
• Use buyer value as context, never as an invented savings claim.
• Include changes, risk, review rounds, and payment timing in the offer.
• Track quoted assumptions against actual delivery.
• Use discounts deliberately and change scope when responsibility changes.
• Keep pricing files and customer data protected.
• Use AI for bounded calculation support and verify every number.
• Review price and capacity together before accepting more work.