The Executive Summary
Agency founders at $60–$150K/month spend 9 hours per month rebuilding a pricing decision they’ve already made—costing $8,100/year in deliberation time alone.
Who this is for: Service agency founders at $60–$150K/month producing 3+ proposals per month with inconsistent delivery margins
The pricing problem:At 6 proposals a month, pricing deliberation costs $675/month in founder time. Add an estimated $750/month in missed margin from 2 underquoted projects, and the modeled annual cost reaches $17,100.
What you’ll learn: The Pricing Protocol — Scope-to-Cost Calculator, Margin-to-Price Formula, Complexity Modifier Scorecard, Price Presentation Format
What changes if you apply it: Proposal pricing moves from real-time judgment under client pressure to a 15-minute structured calculation completed before the document opens
Time to implement: 3–4 hours to build once; under 15 minutes per proposal from day one
Written by Nour Boustani for service agency founders at $60–$150K/month who want consistent delivery margins without rebuilding the same pricing decision on every proposal.
› Library Navigation: Quick Navigation · Service Agencies
How to Price Every Proposal Without the 90-Minute Deliberation
You’re producing 3+ proposals per month. You’ve been running this agency long enough to know roughly what things cost. And yet every time a new proposal needs a number, you open a blank document and start the same deliberation: What did I charge for something similar last time?
Did I make money on that? Should I go higher? What if they push back?
The deliberation runs 90 minutes on average. Sometimes longer. Sometimes you still send a number you’re not confident in.
At 6 proposals per month, that is 9 hours of founder time consumed every single month by a decision you’ve already made dozens of times - just never documented.
The failure isn’t lack of experience. It’s that the pricing logic lives in your head, unstructured, rebuilt from scratch each time under the pressure of a specific client, a specific scope, and a deadline.
That’s the constraint. And it has a documented cost.
The Real Cost of Pricing From Memory
Pricing from memory produces inconsistent outcomes because memory reconstructs rather than reproduces.
For the six proposals below, pricing deliberation takes 9 hours a month. At an effective rate of $75/hour, that is $675/month, or $8,100/year, in time spent pricing. A documented protocol reduces that work to 1 hour a month, recovering 8 hours. Those figures cover time only, not the cost of inconsistent quotes.
Why Agency Pricing Changes From Proposal to Proposal
An agency in the Scaling band ($60–$150K/month) sends proposals often enough for pricing inconsistency to compound. Without a documented system, each proposal becomes a separate pricing decision. The founder recalls past projects, estimates the client’s budget, considers team capacity, and settles on a number through judgment rather than calculation.
Judgment changes with circumstances. A founder behind on revenue may quote differently than they would after a strong month. A client who pushes back on website copy may receive a different quote than one who arrives through a referral.
This is not a discipline failure. Without a documented model, there is no consistent method for reaching a price.
Calculate the Time Lost by Project Type
Performance Marketing, 3 proposals/month:
Without a protocol: 90 min × 3 = 270 min/month
With a protocol: 10 min × 3 = 30 min/month
Time recovered: 240 min/month
Content + SEO, 2 proposals/month:
Without a protocol: 90 min × 2 = 180 min/month
With a protocol: 10 min × 2 = 20 min/month
Time recovered: 160 min/month
Web, 1 proposal/month:
Without a protocol: 90 min/month
With a protocol: 10 min/month
Time recovered: 80 min/month
Across all six proposals, deliberation falls from 540 minutes (9 hours) to 60 minutes (1 hour) per month. That recovers 480 minutes, or 8 hours. At $75/hour, the recovered time is worth $600/month, or $7,200/year.
Why Pricing Advice Does Not Produce a Quote
“Know your worth” and “charge based on value, not hours” are useful principles. Neither tells you what number to put in Tuesday’s proposal when its scope differs from your last three projects.
That gap between principle and execution is where the 90-minute deliberation happens. Without a calculation that puts value-based pricing into practice, founders are still guessing. The number comes from the calculation, not the principle alone.
When This Pricing Protocol Fits: Scaling Band ($60–$150K/Month)
This protocol is built for agencies in the Scaling band. At this stage, the constraint is not knowing whether to charge more. It is pricing without a documented model, which creates two problems:
Inconsistent margins. Underquoted projects may not become obvious until delivery is complete and the hours are spent.
Proposal friction. Pricing consumes founder time that could go toward revenue, delivery, or closing the next client.
The setup investment is easiest to justify at 3 or more proposals per month. Below that threshold, the protocol is useful but less urgent.
How to Reset Inconsistent Agency Pricing
If you are already pricing inconsistently across engagements, compare the cost of a reset with the modeled cost of continuing.
Reset now: Building the protocol takes an estimated 3–4 hours. At $75/hour, that is $225–$300 in founder time. The target is to reduce pricing work from 90 minutes to under 15 minutes per proposal.
Continue for 12 months: At 9 hours of deliberation per month and $75/hour, the modeled time cost is $8,100. Add an estimated $9,000 in suppressed complexity premiums, based on 2 underquoted complex engagements per month, and the combined modeled cost is $17,100. This excludes margin already lost on proposals sent.
On those assumptions, each month without the protocol carries $675 in deliberation time and an estimated $750 in suppressed complexity premiums: $1,425 combined. That is a modeled exposure, not a guaranteed saving. At $75/hour, the time recovered on a single proposal does not by itself repay the $225–$300 setup cost.
Reset the protocol step by step:
Audit the last 5 proposals (45 min). Pull each scope and quoted price. Calculate actual delivery cost as hours spent × team member rate, then calculate each margin and identify the range.
Build the scope menu (60 min). List every deliverable type quoted in the last 6 months. Assign estimated hours and a team member rate to each. This becomes the input layer for the Scope-to-Cost Calculator.
Set the margin target (15 min). Use the cited Parakeeto agency benchmark of delivery margin above 50% at the agency level as the floor. The Margin-to-Price Formula converts cost to price.
Apply the Complexity Modifiers. Starting with the next proposal, run the 6-factor scorecard before quoting. Include the appropriate premium for a complex engagement before writing down the price.
The first three steps account for 2 hours. Allow the remaining setup time within the 3–4-hour estimate to configure and test the modifiers.
Keep past scope items, time estimates, and rates charged. They are the raw material for the protocol. Stop setting prices through intuition under client-specific pressure; use intuition as a final check on the number the model produces.
What Delaying the Pricing Protocol Costs
Within 30 days: If you build the protocol, the next complex proposal can use it. The target is to cut pricing time from 90 minutes to under 15 and make the proposed delivery margin visible before you send the quote.
After 30–90 days without it: Another 3–6 proposals may be priced from memory. At the modeled $675/month in deliberation time, plus unknown margin leakage, the cost continues. Once installed, the protocol can repay its setup time within its first month of use at the assumed proposal volume.
After 90 days without it: The 90-minute pricing decision may feel like normal proposal work. Audit the last 12 months of project margins to look for a pattern that a revenue dashboard will not show: delivery margin falling short of the 50% target.
The time cost is easy to miss because deliberation looks like work. At the modeled volume and $75/hour effective rate, it adds up to $8,100/year spent repeatedly rebuilding a pricing decision.
Gate Check: Are You Ready to Build the Protocol?
You have at least 10 completed client projects to draw scope data from.
You have delivery records, such as time logs, invoices, or PM exports, to audit.
Your current proposals take more than 30 minutes to price.
Pass: All 3 criteria are met. Build the protocol.
Fail: Do not build the calculator from guesses.
If criteria 1 or 2 are missing, run 3 more engagements with basic time logging, then reassess whether you have enough completed projects and usable records to build the scope menu.
If criterion 3 is missing, the protocol may still be useful, but it is less urgent. Revisit it at 3 or more proposals per month.
The constraint is not that you do not know how to price. It is that your pricing logic is not documented where you can use it for the next proposal.
How to Price Agency Services Consistently With a Pricing Protocol
A pricing system gives you a number before you start negotiating with yourself.
The Pricing Protocol has four components. Each uses the output of the one before it:
The Scope-to-Cost Calculator calculates delivery cost at current team rates.
The Margin-to-Price Formula turns that cost into a quote at your target margin.
The Complexity Modifiers adjust the quote for scope factors that increase risk.
The Price Presentation Format determines how you present the number to the client.
Scope-to-Cost Calculator
The Scope-to-Cost Calculator is a documented cost model for each service the agency delivers. Given a specific scope, it produces the delivery cost at current team rates.
Build its scope menu from the last 10–15 completed projects. Each recurring deliverable needs three inputs:
Scope element: The specific deliverable, such as “10 social posts/month,” “monthly paid media management,” or “4-page website build.”
Hours per element: Actual hours from delivery records, not the proposal estimate.
Team rate per element: The rate of the person doing the work, not a blended agency rate.
Actual delivery hours matter because proposal estimates may not reflect what the work took. For the next quote, select the relevant menu items and calculate their combined cost instead of starting from a blank document. The target is to produce that cost number in under 10 minutes.
Performance Marketing Retainer: Example Calculation
- Ad account setup: 4 hours × $75 = $300 (one-time)
- Campaign management: 8 hours × $75 = $600/month
- Reporting (2×/month): 3 hours × $50 = $150/month
- Client calls (2×/month): 2 hours × $75 = $150/month
- First-month delivery cost: $1,200
- Ongoing monthly delivery cost without setup: $900Scope variants:
- Add creative briefs: 4 hours × $65 = +$260
- Add landing page: 6 hours × $75 = +$450
- Remove reporting: 3 hours × $50 = −$150/monthWhat a Working Scope-to-Cost Calculator Produces
One page per service type, listing every scope element and its hours from actual delivery history.
A total cost that updates when scope elements are added or removed.
A calculation a team member can run for any proposal without asking the founder to supply missing inputs.
If the hours are guesses, the calculator may look precise while producing the wrong cost. Pull delivery records from the last 10 engagements and use the time logged for each scope element. If those records do not exist, track actual time on the next 3 engagements before building the calculator.
Component 2: Convert Delivery Cost Into a Quote
The Scope-to-Cost Calculator produces the delivery cost. The Margin-to-Price Formula converts that cost into a quoted price.
Use three inputs:
Delivery cost from the Scope-to-Cost Calculator.
Target gross margin, with 50% as the stated floor.
Market benchmark for comparable scope, used as a sanity check rather than a starting price.
Calculate conservative, standard, and premium margin scenarios before choosing a quote. The price delivers the selected margin only if the work is completed at the cost used in the calculation. As the True Cost of Service Protocol and Cost-to-Cash Pricing Method emphasize, use actual delivery costs to assess realized margin. Without a reliable cost figure, the quoted margin is an assumption.
Margin-to-Price Formula: Worked Example
Delivery cost: $1,200/month
Price = Delivery cost ÷ (1 − target margin)
- Conservative (45%): $1,200 ÷ 0.55 = $2,182/month
- Standard (50%): $1,200 ÷ 0.50 = $2,400/month
- Premium (55%): $1,200 ÷ 0.45 = $2,667/monthThe 45% scenario shows the price at that margin, but it falls below the stated 50% floor.
Market Benchmark Check
- Comparable performance marketing retainer: $2,000–$3,500/month
- Standard scenario: $2,400/month
- Result: Within the benchmark range; proceed to the Complexity Modifiers.In the earlier retainer example, the $1,200 cost included a one-time $300 ad account setup. If setup does not recur, do not carry $1,200 forward as the ongoing monthly cost. Use $1,200 for the first month and $900 for ongoing months, then calculate the corresponding prices separately.
The three scenarios give the founder a calculated range rather than a number chosen by feel. The standard 50% margin scenario is the default.
The 45% conservative scenario shows where the engagement becomes thinner, but it sits below the stated 50% target and needs an explicit exception.
The premium scenario shows the price at 55%; check it against the market benchmark rather than assuming it is the market ceiling.
A working Margin-to-Price template fits on one page per service type. It shows delivery cost, all three prices with their margins labeled, and the comparable market range. Once the Scope-to-Cost Calculator has produced the cost, the target is to reach a base quoted price in under 5 minutes.
Component 3: Adjust the Base Price for Complexity
The Scope-to-Cost Calculator and Margin-to-Price Formula produce a base price for a standard engagement. The Complexity Modifier Scorecard adjusts it for factors that increase delivery risk:
Tight timeline: Delivery is required faster than the standard schedule. Add 15%.
Unusual requirements: The scope includes work outside the standard menu. Add 10%.
First-time service type: The agency has not delivered this exact scope before. Add 20%.
Difficult client history: A previous engagement required more founder involvement than scoped. Add 15%.
High-stakes delivery: The client’s business outcome depends directly on the engagement. Add 10%.
Competitive sensitivity: The client has fired a previous agency for similar work. Add 10%.
Run the scorecard before writing the final proposal price. The target is 3 minutes. Add the percentages for factors that apply, then apply the combined modifier once to the base price. The premium accounts for the additional oversight, communication, and risk management expected in a non-standard engagement.
Complexity Modifier: Worked Example
Base price from the Margin-to-Price Formula: $2,400/month
- Tight timeline: Yes, +15%
- Unusual requirements: No, +0%
- First-time service type: No, +0%
- Difficult client history: No, +0%
- High-stakes delivery: Yes, +10%
- Competitive sensitivity: No, +0%
Total modifier: 25%
Adjusted price: $2,400 × 1.25 = $3,000/monthWithout the scorecard, the founder might quote the $2,400 base price despite the timeline pressure and client anxiety. The example assumes that managing those demands takes 3× the planned hours and brings the effective margin down to 28%, rather than the planned 50%. That margin is a scenario outcome, not something the scorecard alone calculates.
The Complexity Modifier Scorecard prevents a common underquoting mistake: pricing the listed scope correctly while overlooking the overhead of delivering it under non-standard conditions.
A first-time service type brings learning costs that can reduce the planned margin.
A tight timeline may require overtime or reprioritization that standard pricing does not cover.
The modifier makes those demands part of the quote before delivery begins.
Component 4: Present the Price After the Outcome
The first three components produce the number. The Price Presentation Format determines how the client sees it. Its rule is simple: state the value before stating the price.
As described in the Foundational Pricing Strategy, the context immediately before a price shapes how the client assesses it. A fee placed after a task list invites a task-by-task comparison. A fee placed after a specific outcome gives the client a result to evaluate against the investment. Quantify that outcome only when you have a defensible basis for doing so.
Use this sequence:
Outcome statement: State the specific result the client is buying in one concrete sentence.
Scope summary: Define what is included and excluded, rather than listing every task.
Investment: State the price once, clearly. Avoid hedges such as “I was thinking around…”
Next step: Give the client one specific action to take.
Use the same direct format for a $1,500 quote and a $15,000 quote. The documented calculation gives the founder a basis for stating either number without renegotiating it internally while writing the proposal.
Separate the Pricing Decision From the Client Conversation
The Pricing Protocol does more than organize a spreadsheet. It moves the pricing decision out of the proposal-writing moment.
Run the Scope-to-Cost Calculator, Margin-to-Price Formula, and Complexity Modifier Scorecard before opening the proposal document. Then use the Price Presentation Format to discuss the outcome, scope, investment, and next step. The founder enters that conversation with a calculated number instead of starting another round of deliberation.
The intended shift is from 90 minutes of pricing from memory to under 15 minutes of structured calculation.
Why the Pricing Protocol Reduces Deliberation
At the Scaling band, the founder generally knows the work and has experience estimating its cost. The friction comes from having to reconstruct that knowledge for every proposal. The protocol stores the inputs and decision rules so they can be reused.
Existing frameworks support different points in that process:
The Project-Level P&L supplies delivery-cost data for the Scope-to-Cost Calculator.
Margin-First Pricing supplies the margin logic used by the Margin-to-Price Formula.
The Price Architecture Framework supplies the market-positioning context for the benchmark check.
The Pricing Protocol is the execution layer. It turns “price at a 50% delivery margin, then account for complexity” into a repeatable proposal process:
Assemble the scope from the menu in about 5 minutes and calculate cost at the relevant team rates.
Calculate three margin scenarios and select the base price.
Apply the Complexity Modifier Scorecard in about 3 minutes.
Present the outcome, scope, investment, and next step.
The target is under 15 minutes per proposal. Without the protocol, the modeled alternative is 90 minutes of deliberation, inconsistent margins, and no clear record of how each price was reached.
Build a Scope Menu With AI Assistance
Manually building the Scope-to-Cost Calculator can take 3–4 hours: gather past project files, extract hours by deliverable, and organize the results into a scope menu. If delivery records are incomplete, reconstructing the work from invoices and emails takes additional time.
An AI-assisted first draft can shorten the setup to an estimated 60–90 minutes, including 20–30 minutes to review and calibrate the output. Paste plain-language summaries of 8 completed projects into Claude, ChatGPT, or another conversational AI tool using this prompt:
I will paste summaries of 8 completed client projects. Each summary includes the scope, hours spent, and deliverables.
Using only the information I provide:
1. Identify the discrete deliverables in each project.
2. Group equivalent deliverables across the 8 projects.
3. Include items that appear in at least 5 of the 8 projects.
4. For each recurring item, report its name, a typical hours range supported by the records, and the required skill level (senior, mid, or junior).
Format the result as a scope menu for future proposals. Flag missing hours, ambiguous deliverables, or skill levels the records do not establish. Do not invent inputs.Review the draft against the underlying records before using it to price a proposal. This 8-project exercise creates a draft scope menu; it does not replace the protocol’s gate check of at least 10 completed projects and usable delivery records. Add and verify the remaining project data before treating the calculator as ready.
The cost of deferring setup is clearer at 6 proposals per month. Over 3–4 months, an agency pricing from memory would send 18–24 proposals before installing the protocol.
At 90 minutes per proposal and an effective rate of $75/hour, that is $675 per month in pricing deliberation, before any unknown margin leakage. Those proposals cannot be repriced after they have been sent.
Steal This:
“The price that produces the argument is usually the price you weren’t sure about. The price you calculated is the price you can defend.”
I built the first version of this protocol after the fourth consecutive proposal where I quoted a number, second-guessed it immediately after sending, and spent the following 48 hours waiting to see whether the client would push back.
The calculator didn’t make me charge more. It made me stop negotiating against myself before the client had said a word.
Premium Toolkit available for members
The Pricing Protocol System includes:
Scope-to-Cost Calculator — generate accurate delivery costs for any scope combination in under five minutes
Margin-to-Price Formula Template — produce a defensible price range that protects target delivery margins
Complexity Modifier Scorecard — prevent underquoting when timelines, risk, or non-standard requirements increase delivery cost
Plug-and-play AI diagnosis sessions — drop into Claude, Gemini or ChatGPT, answer a few questions, save hours of guessing, get your exact next move
Audio key points — concentrated frameworks you can absorb in minutes, implement while you move
Unlock 750+ ready-to-use constraint toolkits — built to solve every business problem operators actually face.
Prevent $675/month in pricing deliberation loss and margin leakage from underquoted complex proposals.
Cancel anytime. Every download you’ve accessed stays with you.
This system is built for Scaling-band agency founders producing three or more proposals monthly.
If proposals are sent before qualification is complete, install If I’m Not on the Sales Call We Don’t Close - The Sales Governance Engine first.
The first working version is one session. The Scope-to-Cost Calculator requires 60-90 minutes to build from delivery records. Every proposal that follows runs in under 15 minutes.
One thing from this section:
A pricing system doesn’t require more information than you already have - it requires that the information you already have is stored in a format a proposal can retrieve.
The model is built. The next question is how to install it so it holds across every proposal type, every team member, and every client pressure scenario.
Install Your Agency Pricing Protocol in One Session
The protocol takes approximately 3 hours to install. After that, the target is under 15 minutes per proposal.
Step 1: Build the Scope Menu (60–90 Minutes)
Pull the last 10–15 completed client projects. Use time logs, project management exports, or invoice line items to identify each deliverable and its actual hours. Do not reconstruct hours from memory.
What to record
For each deliverable type that appears in at least 3 projects, record:
Deliverable name and what it includes.
Actual hours range, from low to high.
Team member who delivered it and their rate.
How to build it
Use a spreadsheet, text document, or the Scope-to-Cost Calculator in Toolkit 1 - PDF. To speed up extraction, use the prompt in Build a Scope Menu With AI Assistance and check its output against the records.
Total time for this step: 60–90 minutes.
AI-assisted extraction and review: 30–45 minutes within that time.
Target output: 8–20 line items that cover standard proposals.
The AI prompt’s 5-of-8 rule identifies a narrow first draft. Use the at-least-3-projects rule when building the full menu from 10–15 completed projects.
If records are incomplete
If you cannot finish within 90 minutes because actual hours are missing, stop reconstructing. Track time with a simple task log on the next 3 engagements, then return to the menu. Guessed hours will produce an unreliable cost.
Check the output
Give a team member a client scope and ask them to calculate delivery cost using only the menu. If they need to ask what an item includes or which rate applies, make that line item more specific.
Step 2: Configure the Margin Formula (30 Minutes)
Set the target margin and complete the Margin-to-Price Formula Template in Toolkit 2 - PDF for your 2–3 most common service types.
Standard scenario: 50% delivery margin, using the stated Parakeeto benchmark.
If current margins are below 50%: Record 45% as an interim floor and 50% as the 90-day target.
Market check: Use a current agency pricing survey or prices accepted in your client portfolio. Accepted prices are evidence of what those clients paid, not proof of the highest price the market will bear.
Run the formula against your last 5 proposals. Compare the calculated prices with what you quoted and what clients paid. Complete this retrospective check within the 30-minute setup step.
If the 50% margin price is higher than past accepted prices, you have a gap to resolve. Do not assume those past prices establish a market ceiling. Choose a response:
Raise prices to the target on new engagements.
Reduce delivery cost by restructuring the scope.
Accept a below-target margin for this service type and plan for higher margins elsewhere.
The output is a one-page formula document for each core service type, with all inputs and three labeled price scenarios.
Step 3: Run the Complexity Modifier (3 Minutes per Proposal)
Before finalizing a price, use the 6-factor Complexity Modifier Scorecard in Toolkit 3 - PDF.
Mark each factor present or absent.
Add the premiums for the factors present.
Apply the total modifier to the base price from Step 2: Configure the Margin Formula.
If a factor is borderline, mark it present under the protocol’s default rule. Record why it applies so the decision can be reviewed rather than reconstructed later.
The output is a proposed price with a documented rationale. If the client questions the number, you can explain the scope and delivery conditions behind it without inventing a justification after the fact.
Install the Pricing Protocol in Order
Step 1: Build the Scope Menu. Allow 60–90 minutes; produce 8–20 documented items.
Step 2: Configure the Margin Formula. Allow 30 minutes; produce a completed formula document for each core service type.
Step 3: Run the Complexity Modifier. Allow 3 minutes on each proposal; produce a documented final price.
The first proposal using the protocol can go out in week one if the records and setup are ready. The target thereafter is under 15 minutes per proposal because the underlying pricing rules have already been documented.
Gate Check: Is the Protocol Ready to Use?
The scope menu uses actual delivery records, not guessed hours.
The margin formula shows a 50% target for each core service type, including any documented 45% interim floor.
The Complexity Modifier Scorecard is available and the person pricing proposals knows how to use it.
Pass: All 3 criteria are met. Use the protocol on the next proposal.
Fail: Stop and fix the missing input. If scope-menu hours are estimates, track actual time on the next 3 engagements before relying on the calculator.
What the Pricing Protocol Changes at the Scaling Band
The protocol makes the planned delivery cost and margin visible before a quote goes out. Actual profitability still depends on the hours and costs recorded during delivery; it cannot be confirmed from the proposal alone.
Your Pricing Protocol Cost Calculator
This example models a Scaling-band agency with $80,000/month in revenue and 6 proposals per month. It uses a $75/hour effective founder rate and assumes 2 complex engagements per month.
Without the protocol
- Pricing time: 90 minutes × 6 proposals = 9 hours/month
- Deliberation cost: 9 hours × $75 = $675/month, or $8,100/year
- Planned delivery margin: Not documented at proposal timeConsider a $3,000/month retainer priced for a 50% delivery margin. Its planned delivery cost is $1,500. If a tight timeline raises that cost by 25%, the cost becomes $1,875 and the realized margin falls to 37.5%.
- Planned margin dollars: $3,000 − $1,500 = $1,500/month
- Margin dollars after added overhead: $3,000 − $1,875 = $1,125/month
- Difference: $375/month per underquoted engagement
- At 2 such engagements: $750/month, or $9,000/year
- Modeled deliberation cost plus margin shortfall: $17,100/yearThe $375 is the margin lost relative to the original cost plan. It is not the amount a 25% price modifier would add.
With the protocol
- Pricing time: 15 minutes × 6 proposals = 1.5 hours/month
- Time recovered: 7.5 hours/month × $75 = $562.50/month
- Annual value of recovered time: $6,750
- Planned delivery cost and target margin: Documented before each quoteA 25% modifier on a $3,000 base price adds $750 per engagement. For 2 engagements, that is $1,500/month in additional quoted revenue, assuming both quotes are accepted and delivery costs stay as modeled. Combined with the value of recovered time, the modeled effect is $2,062.50/month, or $24,750/year.
The lower $1,312.50/month, or $15,750/year, figure uses only the $750/month margin shortfall across the 2 engagements, plus $562.50/month in recovered time. It measures closing that shortfall, not the full revenue effect of applying a 25% price modifier. Neither outcome is guaranteed; both depend on the assumed costs, accepted prices, and proposal volume.
Run a Pricing Simulation Before You Build
A Scaling-band founder at $95,000/month in revenue is preparing a performance marketing proposal. The scope includes ad account management, campaign setup, reporting twice a month, and 2 client calls per month. The client needs campaigns live in 3 weeks, making this a tight-timeline engagement.
Without the protocol
The founder recalls a similar client quoted at $2,800/month, weighs this client’s apparent budget flexibility and current team capacity, and quotes $2,800/month after 85 minutes.
No timeline modifier is applied. Delivery requires reprioritizing two other client projects and adds 6 hours of founder oversight.
Modeled delivery cost is $1,960/month: $1,200 base cost plus $760 in overtime and reprioritization.
Effective margin is 30%: ($2,800 − $1,960) ÷ $2,800. The target was 50%.
With the protocol
Assemble the scope from the menu in 5 minutes. Modeled base delivery cost is $1,200/month, producing a $2,400/month base price at a 50% target margin.
Apply the scenario’s modifiers: tight timeline (+15%) and high-stakes delivery (+10%). The combined 25% modifier brings the proposed price to $3,000/month.
Present the outcome before the price. In this simulation, the client accepts. Time to calculate the proposal number is 13 minutes.
If delivery still costs $1,960/month, the realized margin at $3,000 is about 34.7%, not 50%. The modifier improves the result, but it does not fully cover the modeled $760 in additional cost. At that delivery cost, a 50% margin would require a $3,920 price.
Compare the Next 90 Days
Without the protocol
The founder continues sending 6 proposals per month, spending 90 minutes deliberating over each.
In this scenario, 3 complex engagements are underquoted by an average of 20% because complexity modifiers are not applied.
At month-end, a review shows delivery margins 8–10 percentage points below target. Without project-level cost data, the founder attributes the gap to “busy delivery” rather than testing for systematic underpricing.
With the protocol
The first proposal takes 20 minutes while the founder learns the process. The second takes 14 minutes. By the third week, the sequence runs in under 15 minutes per proposal.
Two complex engagements in the first month receive modifiers. The scenario models $1,500 in combined additional quoted revenue, assuming clients accept both prices; the amount retained as margin depends on actual delivery costs.
Each new proposal starts with a documented cost and target margin. Actual margin becomes known as delivery costs are recorded, not on day one.
In this scenario, the founder observes less price pushback when the proposal states the outcome before the number. That observation does not establish that the format alone caused the change.
Check Progress at Day 14, Week 4, and Week 8
Day 14
Build the scope menu.
Test it against one live proposal.
Complete the margin formula for the 2 most common service types.
Run the Complexity Modifier Scorecard on every new proposal.
Week 4
Use the protocol on 3–4 proposals.
Track pricing time. Aim for 20 minutes or less per proposal during the first-month learning curve.
Check whether the scorecard caught at least one non-standard factor before a proposal went out.
Week 8
Aim for under 15 minutes per proposal.
Review the previous 2 months of proposals. Planned margins should be moving toward a range within 5 percentage points of the target.
Track delivery costs as work happens. Compare actual margins with the margins planned in each proposal.
If margins still vary at Week 8, look for deliverables missing from the scope menu. Add them, then repeat the retrospective check at Week 12.
Rollback and Retest an Inaccurate Calculator
If the calculator’s costs look consistently too high or too low, check its inputs before changing the margin target.
Set a judgment price for the next 2 proposals. Record the price and your reasoning.
Run the calculator on those same scopes. Compare its output with each judgment price.
Find the source of the gap. Check the hours assigned to each deliverable and the team member rate.
Correct one input at a time using delivery records. Do not adjust the margin target to make the price feel familiar.
Run the next proposal through the revised calculator. If its price is within 15% of your judgment price, the initial calibration check passes.
Spot Pricing Risks During Discovery
The Complexity Modifier Scorecard helps you capture delivery risks mentioned before the proposal is written.
Tight timeline: A prospect repeatedly says the work must move faster than your standard schedule. Check whether the +15% modifier applies.
Previous agency failures: A prospect says they fired two agencies for similar work. Check whether the +10% competitive-sensitivity modifier applies.
Without the scorecard, those details can be lost between discovery and pricing. With it, each is assessed before the quote goes out.
Early Signal 1: The prospect negotiates before seeing the proposal
Hold the calculated price for the agreed scope. If the budget differs, discuss changing the scope rather than discounting the same work.
“The price reflects the scope and timeline we’ve discussed. If the budget is different, we can discuss adjusting the scope.”
Early Signal 2: A proposal takes more than 20 minutes
Check whether it contains work missing from the scope menu. Add the item with a provisional hours range, complete the proposal, and replace the estimate with actual hours after delivery. Mark the input as provisional so it is not mistaken for verified cost data.
A proposal can show planned margin before work begins. Actual margin becomes measurable as delivery costs are recorded; revenue alone does not show the difference between the quote and the cost of fulfilling it.
Gate Check: Is the Protocol Validated?
Pricing took under 20 minutes on each of the last 3 proposals.
At least one complexity modifier was applied in the last 30 days.
Actual delivery margin on the last 2 new engagements exceeded the 45% interim floor.
Pass: All 3 criteria are met. Continue to What Breaks the Pricing Protocol.
Fail: Identify and address the missing condition.
Over 20 minutes: Check for scope-menu gaps and add the missing items.
No modifier applied: Review all 6 factors before the next proposal. Do not add a premium if none applies.
Margin below 45%: Review the last 5 proposals using the margin formula and compare planned costs with actual delivery costs to locate the gap.
What Breaks the Pricing Protocol
The calculator cannot protect a price the founder has already undercut in conversation. The main failure point is giving a verbal ballpark before running the protocol.
A prospect asks, “Roughly what are we looking at?” The founder offers a number to keep the conversation moving. Later, the calculated proposal price is higher, and the client refers back to the ballpark.
The client has not misunderstood. The founder anchored the price before calculating it.
Use a three-word response instead: “Let me calculate.” It keeps the number tied to the scope and the pricing process rather than a guess made during discovery.
When the founder still second-guesses the number
An early signal is running the calculator, then spending another 20 minutes comparing its result with a different past client.
Run the protocol retrospectively on the last 5 proposals.
Compare its calculated price with each proposal’s actual delivery cost and margin.
Check whether incorrect hours, rates, or missing complexity factors explain any gap.
Continue the comparison over 2–3 weeks of live protocol use.
The aim is to verify the calculator against delivery data, not to trust it simply because it produces a number.
How Underpricing Compounds Over Six Months
Month 1 without the protocol
In this scenario, 6 proposals go out at judgment prices.
Two complex engagements are underquoted.
Their delivery margins track 15–20% below target, though the gap may not yet be visible.
Month 3 without the protocol
The underquoted engagements have completed delivery.
A post-project margin review, if one is run, shows the shortfall.
The founder attributes it to scope expansion. That may have added cost, but the initial price may also have omitted a complexity premium.
Month 6 without the protocol
In this scenario, portfolio delivery margin trends below the 50% target despite healthy revenue.
A Project-Level P&L can reveal which engagements missed their margins. It diagnoses the pattern after delivery; the Pricing Protocol is intended to account for complexity before the next quote is sent.
Keep the Pricing Protocol Current Under Pressure
The protocol holds up only if its inputs stay current and the founder checks whether quoted margins match the model.
Update the scope menu: Add a new service type within 30 days of quoting it for the first time. Otherwise, that service remains priced from memory.
Review the price anchor monthly: Check 3 recent proposals against the protocol. You cannot change quotes already sent, but you can correct a recurring gap before the next one.
The Margin-to-Price Formula also makes exceptions visible. If you quote below its conservative scenario, record the expected margin and the reason for accepting it. Where 45% is the documented interim floor, a quote below 45% is below that floor; the standard target remains 50%.
Stress Test 1: Revenue Falls 30% in 60 Days
Revenue pressure may tempt the founder to lower prices without changing the work. The formula shows the margin impact before the quote goes out.
At a $4,000 retainer price:
A 35% margin allows $2,600 in delivery cost.
A 50% margin allows $2,000 in delivery cost.
The difference is $600/month in delivery cost at the same price.
If the scope costs $2,600 to deliver, quoting $4,000 does not produce a 50% margin. To offer a lower price while protecting the 50% target, reduce the scope and recalculate its delivery cost first. If you keep the scope and accept a lower margin, make that an explicit decision.
Stress Test 2: A Key Team Member Leaves
A departure can change the cost of work already sold. The replacement or founder may deliver it at a higher rate than the person used in the original calculation.
Store menu rates by role, such as senior, mid, or junior, rather than relying only on an individual’s rate.
Update the relevant role rate to reflect replacement cost before sending new proposals.
Recalculate the internal expected margin on proposals already sent but not yet delivered.
The client’s agreed price does not change. Internal margin tracking does, so the additional delivery cost remains visible.
Install the First Working Version
Target one 3-hour setup session:
Build the scope menu from delivery records.
Populate the margin formula for 2 core service types.
Have the Complexity Modifier Scorecard ready for use.
If a proposal is due, use the protocol on Day 1 after setup. Otherwise, target the first live proposal by Day 7.
Fix the Blockers Before Pricing From the Menu
No delivery records
Track actual hours on the next 3 engagements with a simple task log.
Allow an estimated 3–4 weeks before returning to setup.
Check that you have enough completed projects and usable records before treating the calculator as ready.
Too many service types
Build the menu for the 2 highest-volume service types first.
Continue using judgment for other services while you document them, but record how each price was reached. Do not present those quotes as calculated prices.
Only a blended team rate
Assign provisional rates by role: senior, mid, and junior.
Mark those rates as estimates. Replace them with documented delivery costs as records become available.
Use AI to Draft the Scope Menu
Paste the scope descriptions and actual hours from your last 12 completed engagements into a conversational AI tool with this prompt:
I run a [type] agency. I will paste scope descriptions and actual hours from my last 12 completed engagements.
Using only the records I provide:
1. Extract the discrete deliverables and hours from each engagement.
2. Group identical or near-identical deliverables across engagements.
3. For each group, provide a standardized deliverable name, the observed hours range from low to high, and whether the work requires a senior or junior team member.
4. Flag missing hours, unclear deliverables, and role assignments the records do not support.
Format the output as a plain-text scope menu with one item per line, not a table. Do not invent hours or rates.Treat the output as a first draft. Review each item against the original records before using it to quote. The setup target is approximately 30 minutes with AI assistance rather than 90 minutes of manual extraction; the actual time depends on the quality of your records.
The most important safeguard remains outside the calculator: do not give a verbal price estimate before running it.
Running the Pricing Protocol in Your Current Condition
Contraction: Revenue is declining or inconsistent
Keep the Scope-to-Cost Calculator and Complexity Modifier Scorecard in use. The 50% standard margin scenario becomes a decision reference: calculate the margin a proposed price would produce before choosing whether to quote below target.
If the last 5 proposals were below the 45% conservative floor, the protocol is recording underpricing rather than preventing it.
Check which services have a gap between delivery cost and accepted price. Restructure the scope, reduce its cost, or raise the quote.
Watch win rate alongside delivery margin. More wins with thinner margins do not, by themselves, signal a recovery.
Do not quietly remove complexity premiums to win tight-timeline or high-risk projects. Record any exception and its expected margin.
Stability: Revenue is consistent but not growing
Use this period to build the scope menu across more project types using actual delivery records. Review the last 6 months of proposals with the margin formula, then extend the retrospective to 12 months of completed projects where records allow.
For each completed project, compare its actual margin with the margin the protocol would have targeted using the scope and cost information available at quoting.
Calculate the modeled dollar gap. Treat it as a retrospective estimate, not revenue the agency could necessarily have captured.
Review 3 recent proposals against the protocol each month.
If pricing regularly takes more than 20 minutes per proposal, check for new scope items missing from the menu.
Expansion: Revenue is growing and engagements are more complex
The scope menu can fall behind as new services appear. The margin formula may still work for documented items while 30–40% of a proposal’s value, in this scenario, comes from items priced by judgment.
Add any new scope item quoted twice to the menu within 7 days of the second proposal. Mark its hours as provisional until delivery records can verify them.
If the complexity premium reaches 20% or more on over half of proposals, review the base scope. Work once treated as an exception may now be standard.
Rebuild the baseline when the agency’s typical engagement changes. What was complex at $80K/month may be standard at $120K/month.
The Pricing Protocol in the Agency Operating System
Revenue Is Up But My Bank Account Isn’t - The Project-Level P&L supplies actual delivery-cost data for accurate scope pricing. Use this when proposal costs are based on estimates.
We’re Doing More Work Than Ever but Our Margin Is Shrinking - Margin-First Pricing sets the margin target the protocol applies to every proposal. Use this when you need a defensible pricing floor.
If I’m Not on the Sales Call We Don’t Close - The Sales Governance Engine qualifies prospects before the pricing protocol scopes their work. Use this when proposals reach poorly qualified prospects.
Foundational Pricing Strategy provides the anchoring logic for presenting protocol-generated prices confidently. Use this when prospects push back on price.
It’s Hard to Close $5k+ Deals Without a Guarantee - The Performance Guarantee Architecture adds risk reduction to high-ticket proposals without undermining the margin floor. Use this when qualified buyers hesitate on commitment.
Death by a Thousand ‘Can You Just’ Requests - The Scope Creep Guardrails protects priced scope and delivery margin after the proposal is signed. Use this when client requests expand beyond agreement.
Stop Guessing Your Rates: The Cost-to-Cash Pricing Method connects pricing decisions to the cash system supporting margin targets. Use this when rates lack cash-flow context.
The Delivery Cost You Never Calculated: The True Cost of Service Protocol calculates the full cost base behind sustainable service pricing. Use this when delivery costs remain incomplete.
Choose the Next System to Install
Proposals go out without sales qualification: Install the Sales Governance Engine first. The Pricing Protocol is for qualified proposals.
Scope changes after signing erode the planned margin: Install the Scope Creep Guardrails next.
Project delivery margins meet target, but overall agency margin is still thin: Use the Project-Level P&L to find where the gap occurs.
Your Pricing Fix Starts Now
At Week 8, you’ll be able to say:
“I can produce a defensible proposal price in under 15 minutes for any scope combination assembled from our service menu. The number comes from the calculator, not from my memory of the last comparable project.”
“Every complex engagement - tight timeline, first-time service type, difficult client history - has the appropriate premium applied before the proposal goes out. I haven’t quoted a complex engagement at standard rates since the modifier was installed.”
“My delivery margin on new engagements is visible on day one of the project, not day 60. I know what each project needs to produce in margin before a single hour of delivery has been spent.”
Three time-boxed actions:
In the next 30 minutes, review your last 5 proposals.
Record the quoted price for each.
Estimate delivery cost from hours worked × the relevant team rates, then calculate the delivery margin.
Note the margin range. It shows the variation the protocol is meant to reduce.
This week, build a first-version scope menu from the last 10–15 completed projects.
Use actual delivery records to create 8–15 line items.
Use the prompt in Build a Scope Menu With AI Assistance to organize available records, not to fill in missing hours.
If records are too incomplete, track actual time on the next 3 engagements before relying on the menu.
Before next month, run the full protocol on your next 3 proposals.
Time each pricing decision.
Compare those times with your historical deliberation time.
Use the difference to estimate monthly time recovered at your actual proposal volume; keep measuring as your scope and workload change.
Pricing Protocol Progress Milestones:
Milestone 1: Scope menu built from actual delivery records. Minimum 8 line items with hours ranges and team rates. One team member other than the founder can assemble a delivery cost from the menu without asking a question.
Milestone 2: Margin formula populated for 2 core service types. Retrospective check on last 5 proposals confirms formula would have produced a defensible number on each.
Milestone 3: Complexity modifier run on 3 consecutive proposals. At least one modifier application that added a premium not previously applied.
Milestone 4: Protocol time below 20 minutes per proposal (month-one target). Time tracked and recorded for 5 consecutive proposals.
Milestone 5: Delivery margin on all new engagements above 45% (conservative floor) for 3 consecutive months. Monthly price anchor practice in place - 3 proposals reviewed against protocol monthly.
If you take one thing from each section:
The 90-minute proposal deliberation isn’t experienced as a cost because it registers as normal work - but $8,100/year in founder time is being spent rebuilding a decision that a documented model makes once.
A pricing system doesn’t require more information than you already have - it requires that the information you already have is stored in a format a proposal can retrieve.
The protocol requires one setup session. Every proposal after that is 15 minutes - not because the thinking is faster, but because the thinking already happened.
Margin isn’t visible on the revenue dashboard - it’s visible in the gap between what you quoted and what delivery actually cost. The protocol makes that gap measurable before the project starts.
The protocol breaks when the founder gives a verbal price estimate before the calculator runs - which is the same pattern the protocol was built to replace.
But if you remember only one thing:
The Pricing Protocol converts the most expensive habit in a Scaling-band agency - pricing every proposal from memory under client-specific pressure - into a 15-minute calculation that produces a defensible number before the first word of the proposal is written. The founder who installs it stops paying $675/month to make a decision the model already made.
Pricing Protocol Checklist
Reference this before sending any proposal to eliminate deliberation and protect margin.
☐ Scope assembled from the scope menu — no blank-document starts
☐ Delivery cost calculated at actual team rates, not blended rate
☐ Margin-to-Price Formula run at 50% target with all three scenarios
☐ Complexity Modifier Scorecard completed — all 6 factors checked
☐ Price presented with outcome statement before the number appears
Every proposal priced this way produces a documented, defensible number in under 15 minutes — and a margin record visible before delivery begins.
FAQ: The Pricing Protocol
Q: How long does it actually take to build the Pricing Protocol from scratch?
A: Three to four hours in a single session covers the full build — 60 to 90 minutes for the scope menu, 30 minutes for the margin formula, and 15 minutes for the complexity scorecard. AI-assisted scope menu extraction using actual delivery records cuts that to roughly 90 minutes total.
Q: What if I don’t have clean delivery records to build the scope menu from?
A: Build the scope menu only from data that exists. Pull time logs, invoice line items, or project management exports from the last 10 to 15 completed projects. If detailed records are genuinely missing, track the next three engagements with a simple task log before building the menu.
Q: My proposals vary a lot — can a standardized scope menu cover enough combinations?
A: The scope menu is not a fixed package list. It is a library of individual deliverable items each assigned hours and a team rate. Any proposal scope is assembled by selecting and combining relevant items from the menu. The example in the article shows adding, removing, and swapping scope elements in under five minutes.
Q: What is the Complexity Modifier Scorecard and when do I use it?
A: The Complexity Modifier Scorecard is a six-factor checklist run in three minutes before the final price is written. Each factor — tight timeline, unusual requirements, first-time service type, difficult client history, high-stakes delivery, and competitive sensitivity — adds a defined percentage premium when present.
Q: What delivery margin should I be targeting, and why 50%?
A: The Parakeeto agency benchmark sets 50% delivery margin as the floor for a structurally healthy agency. Delivery margin is calculated from actual delivery cost — hours spent multiplied by team member rate — not from estimated cost or blended rate.
Q: What happens if a client pushes back on the price the protocol produces?
A: The price produced by the protocol is not a starting bid — it is the calculated number for the scope discussed. The article prescribes a specific response when clients push back before the proposal arrives: hold the price and offer scope reduction instead.
Q: Can a team member other than me run the Pricing Protocol on proposals?
A: That is the design goal. A correctly built scope menu means any team member can assemble the delivery cost for any proposed scope without asking the founder a question. The Margin-to-Price Formula and Complexity Modifier Scorecard are one-page documents with no judgment calls embedded.
Q: What is verbal price anchoring and why does it break the protocol?
A: Verbal price anchoring happens when a founder gives a ballpark number during the discovery call before running the protocol. If that ballpark is lower than the calculated price, the proposal arrives at a higher number than the prospect expects. The client references the verbal figure.
Q: How do I know the scope menu needs updating?
A: Two signals indicate the scope menu has gaps. First, deliberation time on a proposal creeps above 20 minutes even with the protocol in use — items being priced are outside the menu. Second, the monthly price anchor review shows systematic variance between protocol output and actual margins.
Q: What does the protocol look like once it is fully running?
A: By week eight, deliberation time is below 15 minutes per proposal, delivery margin on all new engagements is visible on day one, and margin variance across proposals is within a five-percentage-point range of the 50% target.
⚑ Found a Mistake or Broken Flow?
Spotted a math error, unclear framework, or broken link? Use this form to flag it — helps me keep the articles accurate and useful. Report a problem →
› More to Explore: Quick Navigation · Service Agencies
➜ Help Another Founder, Earn a Free Month
If the Pricing Protocol just showed you how much the 90-minute proposal deliberation was actually costing you, share it with one founder stuck in the same pricing loop.
When you refer 2 people using your personal link, you’ll automatically get 1 free month of premium as a thank-you.
Get your personal referral link and see your progress here: Referrals
Get The Pricing Protocol Toolkit
You’ve read the system. Now implement it.
Premium gives you:
Ready-to-use PDF toolkit—every template, diagnostic, and formula pre-filled, zero setup, immediate use
Plug-and-play AI diagnosis sessions—drop into Claude, Gemini or ChatGPT, answer a few questions, save hours of guessing, get your exact next move
Audio key points—concentrated frameworks you can absorb in minutes, implement while you move
Unrestricted access to the complete library—every system, every update
What this prevents: Agencies at $60–$150K/month losing $17,100/year to deliberation and unpriced complexity.
What this costs: $12/month.
Download everything today. Implement this week. Cancel anytime, keep the downloads.
Already upgraded? Scroll down to download the PDF, audio, and your AI session.
