A Freelance Pricing Architecture: Floors, Targets, and Tradeoffs

A pricing architecture defines your floor, target, and strategic exceptions before negotiation. It turns pricing into a decision about scope, capacity, risk, and relationship value.

Pricing becomes more consistent when one number is not asked to do every job. A floor protects viability, a target reflects the value and operating model you want, and a documented exception explains why a particular engagement deserves different treatment. The architecture should inform judgment without pretending uncertainty can be priced away.

Define the boundaries of a sustainable price

Set a floor that accounts for delivery, administration, and business…

Set a floor that accounts for delivery, administration, and business viability. Apply this to one live opportunity or client decision, not to an abstract ideal. Write down the evidence you have, the assumption you are making, and the condition that would change your view. If the evidence is missing, resolve the smallest important uncertainty first. This keeps the guidance practical and prevents activity, confidence, or urgency from standing in for a reasoned decision.

Set a target for ordinary-fit work that reflects the type…

Set a target for ordinary-fit work that reflects the type of engagement you want to repeat. Compare the benefit with the operating cost: time, coordination, attention, cash-flow timing, and capacity that cannot be used elsewhere. Then ask whether the choice supports the offer and relationships you want to build. A choice can be sensible for short-term stability and still be wrong as a repeatable model. Naming that distinction makes a deliberate exception less likely to become the business default.

Define exceptions in advance, such as relevant proof, a relationship,…

Define exceptions in advance, such as relevant proof, a relationship, a bounded offer test, or gap coverage. Turn this into a visible boundary or next action. Identify who owns the decision, what must happen, and when you will review it. Where another party controls an input or approval, state the dependency instead of absorbing it silently. Clear boundaries are not a substitute for judgment; they preserve enough context for both sides to recognize when the situation has changed and a new decision is required.

Price the engagement as well as the hour: scope, timing,…

Price the engagement as well as the hour: scope, timing, decision access, revisions, payment, and ownership all matter. After the decision, record what actually happened. Note the source, the next step taken, the outcome, and any material difference between the original expectation and reality. Do not treat one result as a universal rule, but do not discard it either. Over time, this outcome history can reveal where your qualification is strong, where assumptions repeat, and which opportunities or relationships fit the business you intend to run.

Use the architecture before the proposal

Before sending the next proposal, record the floor, target, expected effort, risk, payment timing, and any exception in SmartBid. If the proposed price departs from the target, state the strategic reason and review it after delivery. Repeated exceptions are evidence that the architecture—or the pipeline—needs attention.

Pressure-test a price before sending it

Model the ordinary case and the difficult case

Estimate the engagement under two plausible scenarios. In the ordinary case, inputs arrive, decisions are timely, and revisions stay inside the brief. In the difficult case, coordination grows, dependencies slip, and uncertainty consumes more senior attention. You do not need to price for catastrophe, but you should know which assumptions make the price viable. Turn the most important assumptions into scope boundaries, milestones, client responsibilities, or change triggers.

Use records to replace intuition over time

The Internal Revenue Service says a business may use any recordkeeping system suited to it that clearly shows income and expenses, supported by underlying business documents. Tax compliance is not the only reason records matter. Actual delivery time, subcontractor costs, software, payment delays, and write-offs help you understand whether the floor and target reflect the real business. Keep the system proportionate, but capture enough to learn from completed engagements.

Negotiate the shape before the number

When a buyer cannot support the proposed price, ask which requirement is flexible. A later start, fewer deliverables, reduced access, a shorter commitment, faster decisions, or different ownership can change the economics. Discounting the same work without changing a condition transfers the entire compromise to you. A productive negotiation makes the trade visible and preserves the parts of the engagement that create the intended outcome.

Review the price after delivery

Compare the original assumptions with the actual engagement. Which work expanded? Which risk never appeared? Did the payment schedule support cash flow? Did the client relationship create proof, referrals, or repeat work—and at what operating cost? Do not retroactively declare every low-margin project a mistake or every profitable project perfectly priced. Update the architecture only when the evidence suggests a repeatable lesson.

Related reading

Balance utilization and capacity

Review whether to renew or offboard

Reference

Internal Revenue Service: What kind of records should I keep?