Build a Pricing Calculator for Your Services

You'll end up with: A working Google Sheet calculator (inputs → quote) plus a short client-facing explanation of how your pricing works

Overview
25–35 min
Intermediate
Free
2 tools
Cost breakdown
ClaudeFree
Google SheetsFree
TotalFree
Common mistake

Building formulas before locking a pricing philosophy (hourly vs package vs value bands). You get a pretty spreadsheet that still panics under negotiation because the "why" and the floor were never explicit. Fix: Steps 1–2 force a written model + floor before any Sheet structure; Step 4 stress-tests with fictional clients so caps and rush rules survive reality.

Before you start
  • Rough sense of your loaded hourly cost (or willingness to compute it from monthly burn ÷ billable hours)
  • One flagship offer you sell most often (name + typical scope)
  • Whether you mostly sell time, fixed packages, or both
  • A Google account and Claude open in two tabs
1

Name the offer, inputs, and your hard floor

Turn a messy service into explicit calculator inputs and a minimum price you will not go below.

ClaudeFreeOpen Claude
Exact action

1. Open https://claude.ai and start a **new chat** (stay in this thread through Order 2; you will return for Orders 4–5 after you work in Sheets). 2. Paste this block and replace every bracket: "I'm building a Google Sheets pricing calculator for one flagship offer. Do NOT write spreadsheet formulas or cell references yet — only structure and math logic in words. Offer name: [...] Who it's for (1–2 sentences): [...] Typical deliverables / scope (bullets): [...] My monthly minimum income (or gross target): $[...] Billable hours I realistically sell per month: [...] Loaded hourly cost if I know it (or write "compute from burn ÷ hours"): $[...] Current gut price I usually quote: $[...] Biggest fear: [too expensive / too cheap / both] Return ONLY these four sections: (1) A numbered list of the **inputs** the calculator must expose (max 8 line items). (2) A **floor price** in dollars with a **one-sentence arithmetic trace** tying it to my numbers. (3) **Non-negotiables** to bake in (rush rule, meeting cap, revision cap, payment split if any). (4) A short list of **what NOT to automate** (scope-creep items that should stay custom / discovery)." 3. If Claude outputs slick final prices without showing how the floor was derived, reply: "Show the floor calculation explicitly in one sentence, then restate the input list — still no formulas." 4. Keep this chat open; you will reference it in the next step.

You have a numbered list of ≤8 inputs, a stated floor with a visible arithmetic path in plain English, and Claude has not written any spreadsheet formulas.
Claude jumped to formulas or client-ready quotes without exposing the floor logic — reset with the line: "Do not write spreadsheet formulas yet" and ask again for sections (1)–(4) only.
2

Pick one pricing model and lock the rules

Choose one primary model (packages, hourly + minimum, or scope sliders) and write the business rules before you touch formulas.

ClaudeFreeOpen Claude
Exact action

1. In the **same Claude chat**, paste: "Using ONLY my prior message in this thread, compare **two** pricing models that could fit this offer (examples: tiered packages vs hourly + minimum engagement vs scope sliders with caps). Pick **one** primary model for the calculator. Output: - Model name (one line) - 3 bullets: why it fits **solo buyers** for this offer - **When this model fails** (be blunt) - Rush rule: multiplier OR flat fee OR "none" (pick one) - Revision cap (number + what counts as a revision) - Optional payment split (e.g. 50/50) or write "not in v1" - A 5-line **policy** I could paste to a client (plain language) If you say 'it depends,' still pick a **default** for first-time buyers and move edge cases to a footnote, not the calculator." 2. Read the policy out loud. If it promises unlimited meetings or unlimited revisions, reply: "Tighten caps to match my non-negotiables from step 1 — no unlimited language." 3. If the rush rule would ever push quotes **below** the floor from step 1, reply: "Revise rush so the effective quote can never finish below my floor without an explicit exception I approve."

You can name the chosen model, state one clear failure mode, and you have exactly one rush rule you would actually enforce.
Claude stays vague ('it depends') without a default — re-prompt: "Pick a default for solo buyers; edge cases go in a footnote, not the calculator."
3

Scaffold the Sheet: inputs, math, one Quote output

Build a clean Google Sheet: yellow input cells, optional gray assumptions, one bold **Quote** cell fed by formulas only.

Google SheetsFreeOpen Google Sheets
Exact action

1. In Google Sheets, create a new spreadsheet named `Pricing — [Offer] — v1`. 2. Layout: - Column A: input **labels** (from Claude's step-1 list). - Column B: matching **empty value cells** for you to type numbers later (highlight these yellow). - Pick **one cell** (example `D2`) and label the row/column clearly as **Quote** — this cell will hold the final formula. - Optional: a small gray "Assumptions" block for constants (rush multiplier, floor, revision count) if you do not want them edited accidentally. 3. Return to your **Claude chat**. Paste: - The **exact input labels** and their **cell addresses** (e.g. `B3` = Estimated hours). - The **Quote** cell address you chose. - The **model + rules** from step 2. Ask Claude: "Give me **exact Google Sheets formulas** only, referencing those cell addresses (no named ranges required). The Quote cell must be the **only** public-facing output later. Do not put formulas inside my yellow input cells." 4. Paste Claude's formulas into the correct cells. Format currency on Quote and key inputs. 5. Sanity check: change one input — Quote should move. No formula should live inside a yellow input cell.

Changing one input changes the Quote cell; every formula lives outside the yellow input range; Quote is a single obvious cell.
Formulas are scattered with no single Quote cell — pause and refactor so **one** cell is the canonical output before moving on.
4

Add scenarios, caps, and stress-test three buyers

Model Base / Rush / edge cases, enforce min/max caps, and run three fictional buyers through the sheet with Claude.

Google Sheets & ClaudeFreeOpen Google Sheets & Claude
Exact action

1. In Sheets, add a small **scenario area** (duplicate key inputs OR use a dropdown / data validation) for at least **three** labeled scenarios — e.g. **Base**, **Rush**, **Scope-heavy** — matching the language from step 2. 2. If any multiplier could push Quote **below your floor**, wrap the core math with a floor guard, e.g. `MAX(yourRawQuoteCell, floorCell)` (create a cell for floor if needed). 3. Copy your current formulas + a screenshot OR typed sample values for each scenario into **Claude** (same chat). 4. Ask Claude: "Act as three fictional buyers for this offer: (a) skeptical on price, (b) rushed timeline, (c) tries to expand scope mid-stream. For each, say whether the sheet's quote **violates** my floor or revision/meeting caps from earlier. If any scenario fails, tell me **exactly** what to change (formula vs cap vs input)." 5. Apply the smallest change that makes all three pass. Re-run the numbers once by hand for confidence.

You have ≥3 labeled scenarios with quotes; Claude's stress test shows **pass** for each, or you adjusted caps/formulas until they do.
Rush (or another scenario) finishes **below** floor — add `MAX(..., floor)` or remove the discount until the math respects your walk-away.
5

Client copy, cell protection, and how you'll share

Write short client-facing language, protect formula cells, and decide view-only share vs PDF for proposals.

Claude & Google SheetsFreeOpen Claude & Google Sheets
Exact action

1. In **Claude** (same chat), paste: "Using this thread only, draft client-facing copy for my calculator: - **80–120 words** explaining how pricing works and which inputs **they** control. - **3 bullets**: what increases price. - **1 disclaimer line**: estimate / not a binding contract unless separately signed. Ban the phrase **unlimited** for meetings or revisions — use the caps from step 2." 2. Add a new tab in Sheets named `Client copy` and paste Claude's text there (or link out to Google Docs if you prefer — but keep the Sheet as source of truth for numbers). 3. In Sheets: **Data → Protected sheets and ranges** → protect **every non-input cell** (everything that is not yellow) so clients cannot break formulas if you share the file. 4. Decide your sharing mode for proposals: - **View-only link** to this Sheet (best for transparency), **or** - **File → Download → PDF** snapshot per quote (best if you do not want live edits). Write your choice in cell `A1` on the `Client copy` tab as a one-line note to Future You.

Client copy lives in the Sheet (or linked doc); formula/protection is on; you picked share vs PDF and noted it on the Client copy tab.
Client copy still promises unlimited revisions or open-ended scope — rewrite with the caps from step 2 until every promise matches the sheet.

All done!

You now have: A working Google Sheet calculator (inputs → quote) plus a short client-facing explanation of how your pricing works

Explore more guides

Want this workflow built for your business?

Book a free audit