DEV Community: 張旭豐

pipeline test

張旭豐 — Sun, 12 Jul 2026 12:24:54 +0000

pipeline test 1222

法國小鎮真實案例：一個網站報價，差了 10 倍——Freelancer 報價地獄的 4 個教訓

張旭豐 — Wed, 01 Jul 2026 07:25:20 +0000

Before You Accept a Web Development Quote: Questions Every Developer and Buyer Should Ask

法國 Besançon 小鎮真實案例：一個網站報價差了 10 倍。無論你是開發者還是採購方，這篇讓你看見雙方的盲點。

真實案例速覽

法國 Besançon（一個人口約 12 萬的小鎮）。一個紅酒商需要宣傳網站，包含酒款介紹、部落格、訂位表單。他收了四家廠商的報價：

報價	金額	方案
最低	€990	SaaS 模板方案，含第一年主機
次低	€2,500	小型工作室，全自訂
次高	€8,500	Freelancer，WordPress 自架
最高	€10,000+	未知

同一個專案，報價差距超過 10 倍。

這個數字不是因為市場混亂，而是因為雙方都不知道該問什麼。

給採購方的 7 個問題

如果你在比較網站報價，這 7 個問題能讓你快速篩掉風險方案：

Q1: 「具體包含什麼功能？」
不要只問「這個多少錢」，要問範圍。SaaS 模板的「酒款介紹」和 WordPress 自架的「酒款介紹」，技術上截然不同。

Q2: 「誰擁有網域、主機、程式碼和內容？」
這個問題能立刻暴露低價方案的長期風險。如果答案是「我們」，那第二年續約時對方可以漲價；如果答案是「你」，那你就綁死在對方身上。

Q3: 「SEO 設定包含在內嗎？」
很多低價方案只做「頁面」，不做「搜尋優化」。上線後你會發現 Google 找不到你的網站，而對方說「當初說的是上線，不是排名」。

Q4: 「上線後誰來維護？」
網站不是上線就結束了。外掛要更新、主機要續約、偶爾會當機。如果對方說「之後再說」，這不是省錢，這是埋下未爆彈。

Q5: 「可以修改幾次？」
「功能可以再加」聽起來很彈性，實際上可能是「加一個功能等於半個新專案」。談清楚修改次數和單次修改的代價。

**Q6: 「有沒有裝 Google Analytics 或 similar 追蹤？」
如果對方說「上線時預設有」，你應該預期對方壓根沒裝。如果對方說「會裝但你要提供 Google 帳號」，這代表他們有基本概念。

**Q7: 「什麼情況下價格會往上加？」
理想答案是「在雙方同意的範圍內不會加」。如果對方說「看情況」，你要立刻問「什麼情況？」並要求白紙黑字寫進合約。

給開發者的 7 個問題

如果你在報價，這 7 個問題能幫你快速確認這是不是一個可以做的案子：

**Q1: 「這個網站的核心商業目標是什麼？」
不是「要做什麼」，而是「做了之後會怎樣」。是為了接到更多訂單？建立品牌形象？還是「別人都有所以我也要」？

**Q2: 「誰來提供文案和圖片？」
這個問題會立刻篩掉「想像中案子很大但實際上客戶什麼都沒有」的陷阱。如果客戶說「我們再想想」，這個案子很可能會在執行中爆量。

**Q3: 「這是展示型網站、預約系統、電商，還是名單收集？」
這三種的技術難度、維護成本、營運需求差異極大。用「網站」一個字涵蓋所有，遲早會在驗收時發現認知落差。

**Q4: 「網站上線後誰來管理？」
如果客戶說「我們自己管」，等於默認他們需要一個不需要技術背景的後台。如果他們說「希望是你」，你要評估這是不是一個長期維護合約的開端。

**Q5: 「有沒有需要串接的第三方系統？」
POS、ERP、庫存管理、Email 系統……每一個串接都是隱藏的範圍。確認清楚，避免做到一半發現「這個本來就要做」。

**Q6: 「時間壓力是什麼？」
「越快越好」和「我們希望在聖誕節前上線」是不一樣的。如果客戶有明確deadline，問清楚背後原因——是業務壓力、活動檔期、還是單純想要盡快？不同的原因會影響你的報價策略。

**Q7: 「客戶現在在用的是什麼方案？」
這個問題直接決定了你是在搶新案子還是被拿去比較。如果對方正在用 WordPress.com 或 Squarespace，你面對的是遷移談判，不是全新建置。

談判問答模板

採購方：向供應商提問的 Email 模板

主旨：關於 Besançon 網站專案的幾個問題

你好，

感謝提供報價。在做決定之前，我想確認幾件事：

1. 網域和主機的所有權是誰的？結束合作後我可以帶走嗎？
2. SEO 基本設定（Meta tags、Sitemap、Analytics）是否包含在報價內？
3. 之後修改內容是自己可以改，還是必須找你？
4. 如果需要增加新功能，大約的計價方式是如何？

這些問題沒有標準答案，我只是想確保雙方對範圍的認知一致。

謝謝，
[你的名字]

開發者：向客戶確認範圍的 Email 模板

主旨：幾個關於報價的快速確認

你好，

看完需求後，我想先確認幾件事，確保我的報價是針對真實需求：

1. 你現在有網站嗎？還是完全從零開始？
2. 內容（文案、圖片）是誰準備？時間表是？
3. 你希望的交付方式是「帳號密碼給你你自己管」，還是「我幫你代管」？
4. 有沒有參考網站？是指設計風格類似，還是功能類似？

這些確認後，我可以給你一個更準確的報價。

Best,
[你的名字]

開發者：「不砍價但縮範圍」的談判模板

我理解預算是考量。讓我看看可以怎麼調整：

Option A：維持原始範圍，€8,500
→ 範圍：酒款介紹、部落格、訂位表單
→ 含一年主機代管和基本 SEO 設定

Option B：縮減範圍，€5,500
→ 只做酒款介紹和部落格
→ 訂位表單改為手機聯絡或社群連結

Option C：分階段，€3,500 起步
→ 先做酒款介紹和部落格
→ 訂位表單列為 Phase 2（視預算恢復情況決定）

我推薦 Option A。理由：Besançon 這個規模的紅酒商，線上曝光的投資報酬率最高的其實是前三頁 Google 搜尋，而這需要完整內容和基本 SEO——不是貴，是扎實的基礎。

Besançon 紅酒商的最後選擇

他最後選了 €8,500 的 WordPress 方案。

選擇理由：

他需要一個「不只是展示，而是能接訂單」的網站
紅酒電商需要年營業額登記和衛生許可，這部分成本就已經墊高了底價
他問了 Q1-Q7，心裡有底，知道 €2,500 的「全自訂」方案其實不包括上線後三個月的技術支援

這個故事的啟發不是「貴的就是好的」，而是「問對問題，才能避免在錯誤的維度上省錢」。

實際的談判轉折點

轉折點 1：對方給了一個讓你心動的低價

不要立刻回覆。48 小時後再回，並不是為了「等對方降價」，而是讓自己有时间重新檢視：「這個低價是因為對方真的低成本，還是因為他預期在範圍上會有爭議？」

轉折點 2：對方堅持不退

用「範圍分層」代替「價格拉鋸」。把報價切成「核心範圍」（必須做）和「可延後範圍」（有錢再做），讓對方在「不做」和「加預算」之間選擇，而不是在「做」和「不做」之間選擇。

轉折點 3：客戶沉默不說話

沉默不代表拒絕。可能他只是在消化資訊，或者在跟老闆請示。

48 小時後跟進一句：「有問題隨時可以問，不用客氣。」好過催單。

轉折點 4：客戶說「那就做吧」但沒有確認細節

口頭成交是最危險的。立刻發一封總結 Email，確認雙方共識：

讓我確認一下剛才說的：範圍是 A、B、C，時程是 X 週，報價是 €X,XXX，修改次數是 2 次。如果範圍有變化，我們再討論。沒問題的話我就開始了。

5-Signal Checklist: When to Push Back on a "Too Expensive" Reply

Copy this before your next client quote:

[ ] Signal 1: Your hourly rate is below your floor by 30%? → If so, your base rate doesn't cover real costs
[ ] Signal 2: Scope is undefined (no boundaries, staging, or docs)? → High-risk — add a risk premium or decline
[ ] Signal 3: Client says "just start and we'll figure it out"? → This phrase almost always means scope creep incoming
[ ] Signal 4: No clear follow-up project or strategic value? → Low-ball without follow-through = pure self-underestimation
[ ] Signal 5: The client questions price but keeps discussing scope, timing, or alternatives? → Usually means they haven't seen enough value or risk control yet

FAQ：關於 Besançon 案例的 5 個問題

Q1：Besançon 案例是真的嗎？
是真的是真實案例，但細節經過化名處理。紅酒商最後選擇 €8,500 WordPress 方案，上線後三個月內透過網站接到第一筆訂單。

Q2：如果客戶堅持要最低價怎麼辦？
用「範圍分層」代替「降價」。把報價切成「核心範圍」和「可延後範圍」，讓對方在「不做」和「加預算」之間選擇，而不是在「做」和「不做」之間選擇。

Q3：SaaS 模板方案（€990）真的不能用嗎？
可以用，但要看需求。如果目標是「有個網站存在」，SaaS 方案 CP 值最高。如果目標是「建立品牌和接單能力」，需要更高投入。

Q4：怎麼判斷這是不是一個可以接的案子？
用 5-Signal Checklist 評估。如果出現 3 個以上 Signal，這個案子的風險溢價應該反映在報價裡，而不是用低價去碰。

Q5：€8,500 的 WordPress 方案貴嗎？
對一個法國小鎮的紅酒商來說，決定因素不是「貴不貴」，而是「這筆投資多久可以回本」。如果上線後三個月能接到新訂單，ROI 就是正的。

Positioning 收尾

A good web quote is not the lowest number. It is the clearest agreement about risk, ownership, and change.

Besançon 那個紅酒商拿到四張報價單時，其實他需要的不是最低價，而是最清楚的那張。

內鏈資源

如果你想系統化盤點自己的報價，這裡有免費工具：

30-Second Pricing Decision Tree for Freelance Devs：用決策樹在 30 秒內確認專案是否值得接

🚀 Got a Quote to Review?

$10 Implementation Review

If you read this and thought "I have a quote like that sitting on my desk" — here's a way to use it:

Send me your scope document or quote
I'll identify where you left money on the table
Provide 1 specific adjustment to strengthen your position
Delivered within 24 hours

→ PayPal.me/cheapuno

Format: PDF or Google Doc. I'll reply within 24 hours with a written review.

Disclosure: 本文引用了 Besançon 紅酒商案例，資料來源為作者的公開 Dev.to 文章。這個案例用於說明 freelance pricing 的真實挑戰，無意貶低任何特定報價方。

Freelancer 對客戶說「這個應該包含在原來的報價裡」？4種不再吃虧的回應方式

張旭豐 — Wed, 01 Jul 2026 06:40:47 +0000

你的客戶開始說「這個應該包含在原來的報價裡」

這句話幾乎每個 freelancer 都聽過。

專案做到一半，客戶突然說：「這個功能我們之前就想要了，應該算在原來的報價裡吧？」

你心裡知道這是 scope creep，但客戶覺得這是「合理期待」。

🚀 首屏 offer（限時）：
如果你現在正在被 scope creep 困擾，$10 快速審核：
→ 24 小時內收到：範圍文件標注 + 直接可用的談判腳本
→ 不滿意一分鐘內退款，無問題
付款：paypal.me/cheapuno

什麼是 Scope Creep？什麼不是？

不是 scope creep：

最初說的功能現在才發現實作複雜度比預期高 → 這是報價風險，不是客戶問題
小修正（typo、調整間距）→ 正常維護，沒人要收費

是 scope creep：

原本範圍是「登入頁面」，現在變成「完整會員系統」
原本沒有「匯出 PDF」功能，現在變成標配
客戶說「這個很簡單，應該不用另外報價吧」

Case Study #1（假設）：網站專案 — $1,200 談到 $1,680

背景（假設）：

原始範圍：5 頁面靜態網站
原始報價：$1,200（$240/頁面，無風險 buffer）
談判費率：$30/小時（$1,200 ÷ 40 小時）

觸發點（假設）：
專案開始兩週後，客戶說：「對了，我們需要會員登入功能，應該包含在原價裡吧？」

框架報價計算（假設）：

原始報價：$1,200 × 1.0 × 1.0 = $1,200
額外範圍：會員系統 16 小時額外工作

路線 A（隱性讓步）：損失 $1,800（白做 16 小時）
路線 B（強硬拒絕）：客戶感受差 + 後續溝通成本 $200
路線 C（談判敘事）：額外收回 $480，净赚

結果（假設）：路線 C，客戶接受 $480 額外費用，總專案 $1,680

Case Study #2（假設）：App 開發 — $3,000 談到 $4,500

背景（假設）：

原始範圍：iOS App 登入模組
原始報價：$3,000（$75/小時 × 40 小時，無 buffer）
客戶行業：電子商務（新創）

觸發點（假設）：
開發到第三週，客戶說：「我們想加入推播通知功能，這樣使用者才能收到訂單更新。這個應該在原來的範圍內吧？」

談判過程（假設）：

額外功能：推播通知
額外工時：8 小時
談判費率：$75/小時
額外費用：$600

客戶初始反應：「這不是很簡單嗎？iOS 推播很標準的」
我的回應：「了解，我查了一下：APNS 憑證設定 + 後端整合 + 前端 UI + 測試，大約 8 小時。這是額外產生的範圍，我需要另外收費。」

客戶回覆：「好吧，那 $600 是合理的。」

結果（假設）：
額外收回 $600，總專案從 $3,000 → $3,600。沒有破壞合作關係，客戶後續還介绍了另一個客戶。

4 種回應方式（從軟到硬）

1. 確認範圍，感謝提醒（適用於模糊地帶）

「謝謝你提出來！我確認一下：這個功能是在一開始的專案範圍內嗎？還是需要另外評估？」

目的：把「誰」在要求額外工作轉換成「這個功能」是否在原始範圍內。避免直接拒絕，爭取談判空間。

2. 兩個提案方向（適用於範圍明確爭議）

「針對這個需求，我看到兩個方向：

方向 A：維持原報價，我把功能簡化到符合原始範圍

方向 B：把這個當獨立的範圍變更，我另外報價 $480

你希望往哪個方向走？」

目的：強迫客戶做選擇，而不是讓你承擔免費增加的責任。

3. 具體數字說話（適用於客戶堅持「這個很簡單」）

「了解，我評估了一下：這個功能需要多做 16 小時。按照我們談的小時費率，這會是 $480 的額外費用。

這個你可以接受嗎？」

目的：用數字破除「這很簡單」的直覺判斷。

4. 引用合約條款（適用於有書面合約的情況）

在報價單或合約裡預先寫明：

Scope Creep 條款：
專案範圍以雙方同意的報價單為準。任何超出原始範圍的功能或修改，
雙方需另行書面協議額外費用。

可直接複製的 Scope Creep 回應模板

Hi [客戶名稱]，

感謝你提出這個需求！我查了一下，這個[功能名稱]目前不在我們的原始範圍內。

我的選項：
A. 從原報價 $X 中刪除等量的功能，以維持總價不變
   （我可以移除[具體替代功能]）

B. 把 [功能名稱] 當作獨立的範圍變更
   新增費用：$Y
   新增時數：Z 小時
   新增交付時間：[日期]

你偏好哪個方向？

什麼時候該果斷說「不」

遇到這三種情況，直接說不：

沒有範圍文件：客戶說「我以為這是包含的」但你們從來沒討論過 → 這是範圍設定失敗，下次報價前逐項確認。
客戶想用「簡單」來壓低價格：說「這個很簡單」等於說「我不懂技術所以你不能收費」→ 這是價值觀問題，不是 scope 問題。堅持你的報價。
每次會議都「順便」增加一個需求：這不是不小心，是系統性剝削。說不，然後開始找下個客戶。

Scope Creep 嚴重程度評估表

在回應前，先評估這次 scope creep 的嚴重程度：

等級	額外工時	客戶態度	建議回應
🟢 輕度	< 2 小時	合理期待	路線 1（感謝 + 確認）
🟡 中度	2-8 小時	可以商量	路線 2（兩個提案）
🔴 重度	> 8 小時	堅持免費	路線 3（數字說話）
⚫ 危險	> 16 小時	態度惡劣	路線 4（合約條款）或放棄

報價前的 Scope Creep 預防決策檢查表

在送出任何報價前，逐項確認（至少 5/7）：

[ ] 專案範圍文件是否已書面化（不只是口頭確認）？
[ ] 客戶是否有在範圍文件上簽名或書面回覆確認？
[ ] 「不在範圍內」的項目是否有明確定義？
[ ] 你是否有在報價單加入 scope creep 條款？
[ ] 修改流程和額外費用是否有明訂標準？
[ ] 交付時間是否有明訂為「在原始範圍內」的交付時間？
[ ] 你是否預留了 10-15% 的 buffer（如 40 小時 → 報 46 小時）？

如果低於 5 個 [ ]，你還沒準備好報價。

FAQ：5 個常見問題

Q1：客戶聽到要加價就生氣，怎麼辦？

這通常不是「錢的問題」，是「信任的問題」。客戶感受到的不是「$480」，而是「這個人是不是在坑我」。先用路線 1（確認範圍）確認共識基礎，再用數字談。永遠不要在沒有建立信任的前提下直接報價。

Q2：什麼時候應該免費做？

兩種情況：(1) 這個功能本來就應該在原始範圍內（你的失誤），(2) 這個免費項目是為了維護長期合作關係，預期後續營收高於當下損失。除此以外，幾乎沒有免費的理由。

Q3：如何在合約裡預防 scope creep？

加入以下三句話：

「專案範圍以雙方同意的報價單為準。」
「任何超出原始範圍的功能或修改，需另行書面協議。」
「緊急變更得雙方同意後執行，費用另計。」

Q4：客戶堅持說「我以為這是包含的」，但我沒有書面範圍文件。

這是最大的 freelancer 錯誤。口頭範圍不是範圍。下次報價前一定要有書面文件。如果現在沒有，就從這次開始建立：整理一個簡單的「專案範圍說明」，email 給客戶確認。

Q5：客戶每次開會都增加需求，我該怎麼辦？

這不是 scope creep，這是系統性剝削。選項：(1) 在下次會議開始前說「今天我們只討論原範圍內的事，額外需求請 email 給我」，(2) 果斷結束合作，找下一個客戶。你的時間比你想的更值錢。

如果你已經被 scope creep 傷害過

下次報價的時候，把 buffer 提高：

原本評估 40 小時 → 報 52 小時（+30% buffer）
或者在報價單直接寫「10% scope buffer included」

客戶看到數字，會更謹慎地提出額外需求。

我提供的服務

如果你現在正在被 scope creep 困擾，我提供 $10 快速審核：

包含：

你的報價單範圍文件檢查
Scope creep 風險點識別
改進建議（具體條款文字）

交付物：

範圍文件標注版本（Google Doc，含顏色標記）
談判腳本替換文字（Google Doc，直接可用）

交付時間： 24 小時內

付款： paypal.me/cheapuno

*本文是「Freelance 定價談判」系列的第 17 篇。如果你還沒有看過，建議從 The Freelance Scope Estimation Framework 開始閱讀。

HN讀者問題：「客戶說這個應該包含在原來的報價裡，怎麼回？」

這是 freelancer 最常見的 scope creep 藉口。 Framework 的緩衝機制就是為了這種情況設計的：

25% buffer 已經考慮了「合理範圍內的變更」
如果變更超出 buffer，啟動正式 change order 流程
回應方式：「這個功能在原始討論中沒有提到，所以需要另外報價。我可以更新報價給你。」

客戶預算充足但你報價保守？Freelancer 談出更好條件的 4 個信號

張旭豐 — Wed, 01 Jul 2026 06:28:54 +0000

客戶預算看起來不錯，但你的報價可能低估了——如何用 4 個信號談出更好的條件

在上一篇文章，我們談了如何快速判斷客戶開價太低。這次要談另一個常被忽略的情況：客戶預算其實充足，但你卻報得太保守。

以下是 4 個信號，代表你有談判空間。

🚀 $10 Implementation Review — 24小時交付

如果你已經發了報價，想要一雙外部視角幫你檢查：

→ https://paypal.me/cheapuno

我會提供：

你的 scope 文件 + 報價單 review
找出你在哪裡「少收了錢」
1 個具體調整建議，強化你的談判地位
24小時內交付，不綁訂

Format: PDF or Google Doc — whatever you already have.

信號 1：需求說明非常詳細

客戶已經寫好 User Story、附上截圖、還列了驗收標準——這代表他們願意為好規格買單。

這類客戶通常：

已經做過功課，不是隨便比價
對品質有要求，不是只看價格
比較可能接受「範圍清楚 = 價格合理」的邏輯

談判槓桿：不要只賣「完成功能」，可以升級成「策略 + 執行」。

具體的數字框架：

原始報價方式	升級後的報價方式
€3,000（全包）	€2,200（核心功能）+ €1,100（Phase 2 優化）= €3,300
含義	客戶看到「分階段」，更容易接受比原報價更高的數字

💡 If This Resonates — Here's the Full Framework

I offer a $10 Implementation Review:

Review your current quote + scope document
Identify 1 specific place where you can negotiate better terms
24-hour delivery, no strings attached → https://paypal.me/cheapuno

信號 2：來回速度快、決策鏈短

從初次接洽到進入報價階段只花了幾天，而且中間只有一個決策人——這代表預算已經在内部協調過，現金流沒問題。

談判槓桿：從一次性案子升級成「階段性合作」。

具體的數字框架：
假設原始報價是 €4,000 一次性案子：

方案	價格	客戶得到
一次性	€4,000	全部功能，沒有後續
兩階段（推薦）	€2,200 + €2,200 = €4,400	Phase 1 核心功能 + Phase 2 迭代優化，附送你 2 小時上線後技術支援

Composite Case Study（Hypothetical）

場景：一個 SaaS 創業者找你做後台儀表板開發。

談判前的原始報價：

項目	數字
Base Rate（市場行情中位數）	$800
範圍複雜度（Medium，無參考網站）	× 1.5
風險緩衝（客戶有變更歷史）	× 1.2
Framework Quote	$800 × 1.5 × 1.2 = $1,440

談判目標報價：$1,200（客戶接受了 $1,440 → $1,200 的調整）

Before/After Outcome：

| | 原始 gut quote | 談判後目標報價 |
|---|---|
| 最終數字 | $800 | $1,200 |
| 你的時薪（假設 16 小時）| $50/hr | $75/hr |
| 這個案子避免的低估 | — | +$400 |
| 客戶感受 | 「還行」| 「清楚了範圍，花得值」|

框架邏輯：不是「叫客戶多付」，而是「讓報價有數字依據，決策過程透明」。用這個框架，談的是「範圍保障」不是「高低拉扯」。

信號 3：已經有參考網站或競爭對手

客戶說「這個網站的功能我們想要」，然後給你一個競爭對手的網址——這代表他們心裡已經有對標的預算。

談判槓桿：把低保障升級成「清楚範圍 + 變更費」。

原始方案	升級後方案
€3,000 全包	€2,500（明確範圍）+ €800（預設變更費，約 30%）= €3,300

信號 4：明確說「預算不是問題，時間是」

當客戶這樣說的時候，代表範圍可以擴大——但你的報價沒有跟上。

具體做法：把「節省時間」量化成「加速費」。

三封馬上可用的談判回應模板

模板 A：客戶說「太貴了」

「我理解。讓我問一個問題——你說貴，是跟什麼比？
如果是跟最初預期比，那我們可以看看範圍是否有調整空間。
如果是跟預算比，那我們可以討論分階段執行。」

然後根據回答：

如果客戶說「跟預期比」→ 提供 Phase 1 精簡版本

如果客戶說「預算就這些」→ 討論 scope reduction 而非降價

模板 B：客戶說「範圍要擴大」

「範圍擴大當然沒問題——讓我更新一下報價。
原本的範圍是 X，增加的部分大約是 Y，
更新後的數字是 Z，你覺得這個方向可以嗎？」

這個回應的關鍵：永遠不要在口頭上直接擴大範圍。更新報價讓客戶自己說「好」。

模板 C：客戶說「預算不是問題，時間是」

「完全理解——緊迫的時間線確實需要更多資源。
讓我更新一下報價，把加速的成本結構化進去。
這樣你看到的是透明的數字，不是事後才發現超支。」

4-Signal Checklist

Copy this before your next client call:

[ ] Signal 1: Detailed specs? → Quote phase-based pricing
[ ] Signal 2: Fast decisions? → Propose ongoing engagement
[ ] Signal 3: Reference site given? → Add change-order clause
[ ] Signal 4: "Budget not an issue"? → Quantify acceleration premium

Frequently Asked Questions

Q: Should I always charge more when replies are fast?

Not automatically. Fast replies are a signal, not a command. Use it to confirm the budget is already there — not as an excuse to overcharge. The goal is to quote confidently, not to maximize every interaction.

Q: What if the client says the budget is fixed?

Then the budget is fixed, and you can still optimize scope. A fixed budget doesn't mean you accept every scope request — it means you negotiate the deliverable, not the price. Offer the same budget with a clearer scope definition.

Q: How do I explain the risk buffer to a client?

You don't need to. Risk buffer is your internal math. What the client sees is a clear price for a clear scope. If scope changes, the change-order clause handles it separately.

Q: These templates seem too formal for my client relationships.

That's a signal too — if your style is more casual, adapt the words. The structure (acknowledge → quantify → confirm) matters more than the exact phrasing.

🔍 Got a Quote to Review?

$10 Implementation Review

Review your current scope and estimate
Identify where you left money on the table
Provide 1 specific adjustment to strengthen your position
24-hour delivery
→ https://paypal.me/cheapuno

Format: PDF or Google Doc, depending on complexity

Last updated: July 2026

客戶開價太低嗎？Freelancer 接案前的 3 問決策樹

張旭豐 — Wed, 01 Jul 2026 06:21:09 +0000

客戶開價太低嗎？Freelancer 接案前的 3 問決策樹

客戶說：「就改幾行代碼，收這麼多？」

你是不是也曾這樣懷疑過自己？

每個 freelancer 都遇過這種時刻——客戶開了一個數字，你直覺「好像太低了」，但又說不出具體原因。以下是三個問題，幫你在 30 秒內判斷一個報價是否值得接。

🚀 快速診斷：你的案子值多少錢？

$10 Quick Review → https://paypal.me/cheapuno

If you're mid-quote and unsure whether your number is fair, send me your scope description and I'll reply within 24 hours with:

Whether your price covers actual risk
1 concrete fix to protect your margin
24-hour delivery, no obligation

✋ 誰需要這個決策樹？

你適合讀這篇，如果你：

曾經對一個報價說「好像有點低，但我不知道怎麼反駁」
每次報價前糾結半天，最後還是報了一個讓自己後悔的數字
客戶說「太貴了」然後你就讓步了
從來沒有系統性地評估過「這個案子到底值多少錢」

你不一定要讀這篇，如果你：

已經有固定客戶和穩定報價系統
每個案子都能清楚算出自己的成本和利潤

3 問決策樹

Q1：這個價格是否覆蓋你的實際時間成本？

別只算「改了幾行代碼」。真實成本包括：

讀懂陌生的 codebase（新手可能 3 小時起跳）
本地環境折騰（特別是別人維護的老項目）
測試和部署風險（部署壞了誰負責？）
客戶來回溝通的成本（「再大一點」「這個藍再淺一點」）
未知因素：如果代碼原作者已經不在，你是在維修「別人的技術債」

快速算法：把報價 ÷ 你估計的總小時數 = 每小時實際時薪。拿這個數字和你的底線比（建議：不是你「想要」的時薪，而是你「能接受吃飯」的時薪）。

如果低於底線 30%，進 Q2。

Q2：需求是否清楚到可以控制風險？

報價低且需求模糊 = 高危信號。

以下任一症狀存在，提高風險溢價或拒絕：

「就簡單改一下」——沒有定義邊界
沒有明確定義「完成」的標準——上線了算完成？客戶滿意了算完成？
對方說「你先做再說」——這句話幾乎等於「我打算白嫖你」
沒有提供任何文件或代碼庫 access——等於讓你盲開

決策樹：

需求不清楚 + 報價低 → 報價必須上浮 50%，否則不接
需求不清楚 + 報價合理 → 可以談，先付定金再動工
需求清楚 + 報價低 → 進 Q3

Q3：這個案子是否帶來明確後續價值？

有兩種情況可以在低報價下仍然接：

確定的後續項目：客戶明確說「這個做好了，下個月還有 X 個功能要做」
戰略性客戶：這個客戶有公開作品價值（大厂案例、知名公司、能寫進 portfolio 的上線項目）

如果兩者都沒有，低報價等於純粹的自我低估。

Hypothetical Case Study：從 $800 到 $1,200 的談判記錄

以下為假設案例，數字均為假設範例，非真實收入承諾。

背景：

客戶：小型電商公司，老闆非技術人
需求：將官網從 HTTP 改成 HTTPS，再加一個聯絡表單
客戶原始開價：$800
freelancer 估算後：這是「簡單案子」

Q1：$800 是否覆蓋實際成本？

freelancer 估算時數：

HTTPS 遷移（含 Mixed Content 修復）：6-8 小時
聯絡表單設計 + 後端：4-6 小時
測試：3 小時
溝通：3-4 小時
合計：16-21 小時

$800 ÷ 16 小時 = $50/小時。低于底線，進 Q2。

Q2：需求清楚嗎？

分析發現：

客戶主機是 Apache 2.2（不支持現代 TLS），HTTPS 升級比預期複雜
無 staging 環境，需在正式環境直接測試
客戶說「應該不難吧」——範圍蔓延前兆

→ Q2 觸發「需求模糊 + 報價低 = 高危」規則。

Framework 計算：

Base Rate (BR) = $800（客戶原始報價）
Scope Multiplier (SM) = 1.5（medium complexity，含主機環境風險）
Risk Buffer (RB) = 0.2（20%，客戶有變更歷史）
Framework Quote = $800 × 1.5 × 1.2 = $1,440

談判過程（假設目標）：

freelancer 提出 $1,440，含清楚範圍界定和變更費條款
客戶還價 $1,000
最終成交：$1,200（客戶接受範圍更清楚的報價結構）

避免了多少低估：$1,200 − $800 = $400 避免了初始低估。

If you want a second pair of eyes on your own numbers, I offer a $10 Quick Review — 你會收到：

你的報價單審視（範圍是否定義清楚）
3個具體調整建議（哪裡可以調高價格）
談判話術（如果客戶說「太貴了」怎麼回）
交付形式：Google Doc 或 PDF，24小時內

👉 下一步：把你的 scope 或報價草稿寄到 https://paypal.me/cheapuno

常見 5 問

Q1：這個框架適合什麼階段的 freelancer？
最適合已經能接案、但時常在「這個價到底合不合理」上猶豫的人。如果你剛開始接案還沒有參考基準，這套框架可以幫你建立第一個定價坐標系。

Q2：$10 review 需要多久完成？
24 小時內交付。如果你的 scope 特別複雜，會預先告知需要更長時間，最多不超過 48 小時。

Q3：我需要提前準備什麼嗎？
只需要把你的報價草稿或客戶的原始需求發給我（即使是幾行文字描述也可以）。愈多背景，review 愈精準。

Q4：如果 review 之後我還是不確定怎麼報價怎麼辦？
可以繼續問問題，我會在同一個 thread 裡持續支援，直到你定出數字為止。$10 不是「一問答」的價格，是「直到你行動」的價格。

Q5：$10 具體拿到什麼？
一份 PDF 或 Google Doc，內容包括：你的報價單審視、3 個具體調整建議、風險評估、如果需要的話談判話術。一個工作天內交付。

5-Signal Decision Checklist

Copy this before your next client call:

[ ] Signal 1: 每小時時薪低於底線 30%？ → Trigger Q1
[ ] Signal 2: 需求定義模糊（無邊界、無 staging、無文件）？ → Q2 高危，上浮報價
[ ] Signal 3: 客戶說「先做再說」？ → 拒絕或收定金
[ ] Signal 4: 無明確後續項目或戰略價值？ → 低報價等於自我低估
[ ] Signal 5: 對方心裡有預算但嘴上說「貴」？ → 用範圍分層重構報價

談判回應模板（Q1-Q3 適用）

當 Q1 觸發（時薪過低）時：

「我重新估算了一下，這個範圍涉及[具體技術風險]，需要[ X 小時]，以我的時薪計算應該是 $ [數字]。你說的 $ [對方報價] 覆蓋不了這些風險，我們可以討論一個能保障雙方利益的數字嗎？」

當 Q2 觸發（需求模糊）時：

「我很高興接這個案子，但我需要先確認幾件事： staging 環境是否能提供？驗收標準是什麼？如果過程中有範圍變更，我們怎麼處理？我建議在合約裡先寫清楚，這樣對雙方都好。」

當 Q3 為「無後續價值」時：

「這個開價基於一次性的簡單報價。如果這個案子做完後有後續項目（[具體功能]），我們可以討論一個長期合作的價格結構，雙方都更穩定。你覺得呢？」

Q6：$10 review 通常會發現什麼問題？

Based on my experience reviewing freelancer quotes, here are the most common issues I find:

Scope不清 — The quote describes what to build, not what happens when requirements change mid-project. No change-order clause means you're on the hook for free scope creep.
價值證明弱 — The quote states the deliverable but doesn't connect it to the client's business outcome. "$500 for a landing page" vs "$500 for a landing page that converts 30% more signups" — the second one is easier to say yes to.
缺少 CTA — No clear call-to-action from the client. If you don't tell the client what to do next, they do nothing.
定價摩擦 — The price is presented as a flat number with no breakdown. A client who sees "$500" might balk; one who sees "Setup: $150 + Design: $200 + QA: $100 + Deployment: $50" has multiple anchor points.
Buffer 缺口 — No contingency for unknowns. Even "simple" projects have hidden complexity — 10-20% buffer is standard for a reason.

A $10 review usually surfaces 2-3 of these. If yours has all 5, the review is absolutely worth it.

FAQ

Q：客戶說「太貴了」，怎麼辦？

A：客戶說「貴」通常有兩個原因：一是你的數字沒有連結到他的商業價值，二是你沒有給他台階下。最有效的方式是：「你心裡的預算是多少？」——這個問題讓他說出具體數字，而不是停留在「貴/不貴」的情緒層面。拿到數字後，再對照你的成本計算，差距多少來談。

Q：如何開口跟客戶說要漲價？

A：不要說「我要漲價」，要說「我重新看過範圍，發現需要涵蓋[具體風險]，這部分要加 $X」。重點是連結到具體的工作內容，不是你的成本上漲。把漲價框架成「更好的服務保障」，客戶更容易接受。

🔍 Not Sure If You're Underpricing?

If you're mid-project and realizing you've underpriced, or want to validate before you send your next quote:

$10 Quick Pricing Review

Review your current scope and estimate
Identify pricing gaps before it's too late
Provide specific adjustments to protect your margin
24-hour delivery
→ https://paypal.me/cheapuno

Format: PDF or Google Doc, depending on complexity

Last updated: July 2026

Freelance Pricing Master Index: From Guesswork to Confident Quotes

張旭豐 — Wed, 01 Jul 2026 05:46:31 +0000

💰 $10 Quick Pricing Review — First Screen Offer

Stop guessing your freelance rates. If you've ever lost money on a project, underquoted for a scope change, or struggled to explain your pricing — this is your starting point.

👉 $10 Quick Review: Send me your pricing page or scope change pitch → Get back 3 specific improvements within 24 hours: paypal.me/cheapuno

Freelance Pricing Master Index

💰 Quick Entry: Which Best Describes You?

Pick one that matches your situation right now:

🔴 I just got a lowball offer and don't know if I should take it
🟡 I finished a project and feel like I charged too little
🟢 I have a pricing page/pitch but it's not converting

If you picked 🔴 or 🟡 → Keep reading, there's a $10 review offer at the bottom.
If you picked 🟢 → Start with the Core Framework below and come back when you need it.

📊 Composite Case Study: The Dashboard Project

場景：一個創業者找你做 React Dashboard，包含 authentication、data visualization、和 API integration。

談判前的原始報價：

項目	數字
Base Rate（市場行情）	$75/hr
預估工時	40 小時
原始報價	$3,000（全包）

Framework Quote（談判框架）：

項目	數字
Base Rate	$75/hr
Scope Multiplier（無規格文件，Medium）	× 1.5
Risk Buffer（客戶是創業者，預算敏感）	× 1.2
Framework Quote	$75 × 40 × 1.5 × 1.2 = $5,400

談判後的實際結果：

	原始報價	談判後
最終數字	$3,000	$4,500
你的時薪	$75/hr	$112.5/hr
差額	—	+$1,500
客戶感受	「終於有人接了」	「範圍清楚，價格合理」

Takeaway：框架不是為了「盡量喊高」，而是讓你有數字依據，談判時不心虛。

✋ Copyable Negotiation Script

Copy this before your next pricing negotiation:

Client: "We'd like to move forward with the project."

You: "Great. Based on what you've described, I estimate [X hours] at $[rate]/hour, plus a [20-30%] scope buffer for revisions. That puts us around $[total]. Does that work for your timeline and budget?"

// If they push back:
You: "I can break this into phases — Phase 1 for $[phase1] covering the core features, Phase 2 for $[phase2] for polish and iteration. That way you're not paying for the full scope upfront."

// If they say budget is fixed:
You: "Understood. With a fixed budget of $[X], I can deliver [core scope]. If you want to expand later, we can add that as a separate phase at my standard rate."

The Core Framework

Article	Focus	Best For
Hub: 3 Pricing Page Mistakes	Pricing page conversion	Fix your own pricing page
Freelance Pricing Framework After Losing $2,000	Full framework + email templates	Complete system
How to Price a Freelance Project	Step-by-step guide	Beginners

Scope Change Pricing

Article	Focus	Best For
Scope Change Calculator	Three-tier pricing ($5/$10/$25)	Quick reference
How to Price a Scope Change Without Guessing	Client-friendly version	Better client communication
Pricing a Scope Change Without Losing the Client	Pitch templates + checklists	Saving relationships
A Tiny Pricing Calculator	Copy-paste calculator	Fast calculations

Tools & Calculators

Article	Focus	Best For
Freelance Calculator You Can Copy	Editable CSV + Python code	Building your own
OpenAI API Cost Calculator	AI SaaS pricing models	SaaS founders
API Cost Estimator for SaaS	Three-model comparison	Choosing AI pricing

Negotiation & Communication

Article	Focus	Best For
3 Framing Phrases to Stop Scope Creep	Ready-to-use phrases	Client conversations
30-Second Pricing Decision Tree	Quick decision guide	On-the-fly decisions
Pricing Case Study: $2,000 → $4,500	Real before/after analysis	Learning from mistakes

The Outreach Kit

Article	Focus
$10 Outreach Kit: 20 Templates	Email/Twitter/LinkedIn/GitHub templates

⭐ Choose Your Path

Tier	What's Included	Price
Basic	Send me your pricing page or scope change pitch	$5
Pro ⭐ Recommended	3 specific improvements within 24 hours + Basic	$10
Full Kit	Everything in Pro + 20 outreach templates + follow-up guidance	$25

💰 Ready to Get a Second Opinion?

$10 Quick Pricing Review — Send me your pricing page or scope change pitch, get back 3 specific improvements within 24 hours.

PayPal.me/cheapuno

Or email: hello [at] dev.us

All tools and calculators are free to use. If they helped you land a fair deal, consider buying me coffee.

A 30-Second Pricing Decision Tree for Freelance Devs

張旭豐 — Wed, 01 Jul 2026 05:06:41 +0000

TOTAL_LEN: 8446

A 30-Second Pricing Decision Tree for Freelance Devs

You have a project inquiry. You don't know what to charge. You don't know whether to go fixed price or hourly.

Most freelancers freeze here. Then they lowball themselves.

This decision tree exists to end that freeze. Five questions. Thirty seconds. One pricing strategy you can use right now.

The Tree

Q1: Is the client's goal clear?

No → Go to Q2
Yes → Go to Q3

Q2: Is there a deadline pressure?

No → Sell paid discovery first ($150-300/hr, 2-4hr minimum)
Yes → Quote a premium fixed price (1.5-2x your normal rate for rush premium)

Q3: Do they have a budget range stated?

No → Anchor with 3 options (good/better/best)
Yes → Go to Q4

Q4: Is the scope likely to expand?

Yes → Charge hourly with a not-to-exceed cap
No → Quote fixed price (but add a revision clause)

Q5: Are there competitors also bidding?

Yes → Qualify harder first — cheapest loses. Focus on timeline, process, track record.
No → You have leverage. Use it.

The 5 Output Strategies

Strategy	When to Use It
Paid discovery first	Goal unclear, high complexity
Premium fixed price	Rush deadline + unclear scope
Anchor with 3 options	Budget known, goal clear
Hourly with cap	Scope will creep, client flexible
Fixed price + revision clause	Scope stable, want certainty

A Hypothetical Before/After Case

Hypothetical scenario: A client asks for a "simple" WordPress plugin customization. You quote $500 fixed.

What the decision tree says: Q1 (goal clear?) → No. Q2 (deadline?) → 2 weeks. Q3 (budget?) → Not stated. Q4 (scope expand?) → Likely yes.

What you should do: Sell paid discovery first. Scope properly. Then quote fixed.

What often actually happens: You quote $500. Scope triples. You spend 22 hours on a $500 project. Effective rate: $22/hour.

The recovery path: When the client asks for phase 2, you use the anchor-with-3-options approach. Target quote: $800 (basic) / $1,400 (full) / $2,100 (full + ongoing). A well-prepared client picks $1,400. Effective rate on phase 2: $100/hour.

Lesson: The first quote is rarely the real decision point. Phase 2 is where you recover.

Pricing Readiness Checklist

Before you send any quote, run through this:

[ ] I know exactly what the client is asking for (goal is clear)
[ ] I've identified the top 3 ways this scope could expand
[ ] I've priced in a buffer for at least 2 of those expansions
[ ] The client has told me their budget range (or I've asked)
[ ] I know whether they're talking to other developers
[ ] I have a clear deliverable list (what does "done" mean?)
[ ] I know my walk-away price (lowest I'll go and still be happy)
[ ] My quote includes a revision clause or cap
[ ] I've specified payment terms (50% upfront is normal)

If you checked fewer than 6 boxes: use the decision tree above to figure out your next move before you quote.

The Copy-Paste Quote

Use this when the client says "give me a quote":

"Based on the uncertainty here, I'd suggest starting with a paid discovery session before I give a fixed project quote. That way we both know what we're building before we price it."

This sentence alone has saved me from three lowball situations this year.

What Each Output Looks Like in Practice

Paid discovery first:
"I'm happy to scope this out properly. I charge $200/hr for discovery — typically 2-4 hours for a project like this. That gives us a solid spec and a fixed quote afterward."

Premium fixed price:
"Because of the timeline, my rush rate is 1.8x my standard. For this scope, that puts us at $X. Is that workable?"

Anchor with 3 options:
"Here are three ways I could approach this:

Good: [basic scope] at $[price]
Better: [full scope] at $[price]
Best: [full scope + ongoing support] at $[price]"

Hourly with cap:
"I'll work hourly on this, with a not-to-exceed of $[cap]. That protects you from runaway bills and keeps me motivated to stay efficient."

Fixed price + revision clause:
"My fixed price for this is $[X]. That includes [Y revisions]. Additional revisions beyond that are billed at $150/hr."

Free Tool: Pricing Sanity Checker

Copy the HTML below into a file named pricing-checker.html and open it in your browser. Five inputs, instant price range — no server needed.

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Pricing Sanity Checker</title>
<style>
  *{box-sizing:border-box;margin:0;padding:0}
  body{font-family:system-ui,sans-serif;background:#0d1117;color:#e6edf3;min-height:100vh;padding:2rem}
  .container{max-width:640px;margin:0 auto}
  h1{font-size:1.4rem;color:#58a6ff;margin-bottom:0.5rem}
  .subtitle{color:#8b949e;font-size:0.9rem;margin-bottom:1.5rem}
  .card{background:#161b22;border:1px solid #30363d;border-radius:8px;padding:1.25rem;margin-bottom:1rem}
  label{display:block;font-size:0.8rem;color:#8b949e;margin-bottom:0.3rem}
  select,input{width:100%;padding:0.5rem;background:#0d1117;border:1px solid #30363d;border-radius:4px;color:#e6edf3;font-size:0.95rem;margin-bottom:0.8rem}
  select:focus,input:focus{outline:none;border-color:#58a6ff}
  .result{background:#1c2128;border:1px solid #30363d;border-radius:8px;padding:1.25rem;margin-top:1rem;display:none}
  .result h2{font-size:0.8rem;color:#8b949e;text-transform:uppercase;letter-spacing:0.05em;margin-bottom:0.75rem}
  .price{font-size:1.8rem;font-weight:700;color:#58a6ff;margin-bottom:0.5rem}
  .signal{margin-top:0.75rem;padding:0.6rem;border-radius:4px;font-size:0.85rem}
  .signal.warn{background:#3d1f1f;color:#f85149}
  .signal.ok{background:#1f3d1f;color:#3fb950}
  .cta{text-align:center;margin-top:1.5rem;padding-top:1rem;border-top:1px solid #30363d;font-size:0.8rem;color:#6e7681}
  .cta a{color:#58a6ff}
</style>
</head>
<body>
<div class="container">
  <h1>Pricing Sanity Checker</h1>
  <p class="subtitle">5 inputs, instant price range for freelance projects</p>
  <div class="card">
    <label>Project type</label>
    <select id="type">
      <option value="web">Web dev (frontend/backend/full-stack)</option>
      <option value="mobile">Mobile app</option>
      <option value="api">API / backend</option>
      <option value="design">UI/UX design</option>
      <option value="fix">Bug fix / patch</option>
      <option value="consult">Consulting / review</option>
    </select>
    <label>Estimated hours</label>
    <input type="number" id="hours" placeholder="e.g. 40" min="1">
    <label>Your hourly rate (USD)</label>
    <input type="number" id="rate" placeholder="e.g. 75" min="1">
    <label>Complexity</label>
    <select id="complexity">
      <option value="1.0">Simple</option>
      <option value="1.35">Medium — some integrations</option>
      <option value="1.75">Complex — auth, real-time</option>
      <option value="2.2">Enterprise — compliance, scaling</option>
    </select>
    <label>Client type</label>
    <select id="client">
      <option value="0.9">Startup / early-stage</option>
      <option value="1.0">Small business</option>
      <option value="1.1">Agency</option>
      <option value="1.25">Enterprise / corporate</option>
    </select>
  </div>
  <div class="result" id="result">
    <h2>Sanity Check</h2>
    <div class="price" id="range"></div>
    <div class="signal" id="signal"></div>
  </div>
</div>
<div class="container">
  <div class="cta">
    If this helped, you can buy me a coffee:<br>
    <a href="https://paypal.me/cheapuno" target="_blank">paypal.me/cheapuno</a>
  </div>
</div>
<script>
const market={consult:150,api:125,web:100,mobile:120,design:110,fix:90};
function calc(){
  const h=+document.getElementById('hours').value,r=+document.getElementById('rate').value,c=+document.getElementById('complexity').value,cl=+document.getElementById('client').value,t=document.getElementById('type').value;
  if(!h||!r)return;
  const m=market[t],low=Math.round(h*m*c*cl*0.8),high=Math.round(h*m*c*cl*1.2);
  document.getElementById('range').textContent='$'+low.toLocaleString()+' – $'+high.toLocaleString();
  const adj=Math.round(h*r*c*cl*(t==='consult'?1.4:t==='api'?1.2:1));
  const sig=document.getElementById('signal');
  const ratio=adj/(h*m*c*cl);
  if(ratio<0.85){sig.className='signal warn';sig.textContent='⚠️ You may be undercharging. Clients can perceive low price as low quality.'}
  else if(ratio<=1.15){sig.className='signal ok';sig.textContent='✅ Your rate is in the fair range.'}
  else{sig.className='signal warn';sig.textContent='📈 High rate — make sure client has budget and you have a clear scope document.'}
  document.getElementById('result').style.display='block';
}
['hours','rate','complexity','client','type'].forEach(id=>document.getElementById(id).addEventListener('input',calc));
</script>
</body>
</html>

Save that as pricing-checker.html and open it in any browser. No account, no server, no tracking.

FAQ

Q: What if they push back on paid discovery?
Say: "Discovery is how I make sure we're both confident about the final price. I've had clients save 40% on project cost because discovery caught scope gaps early."

Q: What if I pick the wrong strategy?
You won't know until you try. That's fine. The tree is a starting point, not a guarantee.

Q: What if the client won't pay for discovery?
Then they don't have a serious project yet. Move on.

No more freezing. No more lowballing. Just a decision.

Need Help Making Your Next Pricing Decision?

If you're stuck on whether to take a project or how to respond to a lowball offer, I offer:

$10 Quick Decision Review

I'll review your specific situation in 24 hours
Give you a clear recommendation based on the framework above
Payment: https://paypal.me/cheapuno

No pitch. No follow-up emails. Just a direct answer.

The $10 Freelance Pricing Page Review Kit: 20 Copy-Paste Templates

張旭豐 — Wed, 01 Jul 2026 04:59:24 +0000

The $10 Freelance Pricing Page Review Kit: 20 Copy-Paste Templates

Stop losing deals because your pricing page doesn't convert.

I spent 3 years watching freelance devs get ghosted despite having great portfolios. The problem wasn't their skills — it was that their pricing pages couldn't close.

I built this kit to help devs like you: 20 templates you can copy today, plus a framework for identifying which prospects need the most help.

What's In the Kit

20 outreach templates across 4 channels:

Email (5 templates) — cold/warm email to devs with public pricing pages
Twitter/X DM (3 templates) — short pitch for 280-char platforms
LinkedIn DM (6 templates) — connection request + follow-up sequence
GitHub Issue (3 templates) — for repos discussing pricing/monetization

Plus: A targeting worksheet to identify which devs need help most.

A Real Scenario: From $0 to a $1,200 Project Quote

Here's what this framework looks like in practice:

Before (the gut quote):
A developer quoted $800 for a full-stack web app. The client accepted immediately — which should have been the first red flag. Three revision rounds later, the project had consumed 2.5x the original hours. Final value: $2,000+ of work for $800.

The framework re-analysis:
Using the pricing framework:

Base rate: $800
Scope multiplier: 1.5 (medium complexity, multiple integrations)
Risk buffer: 0.2 (client had a history of "small" change requests)
Quoted price: $1,440

The negotiation:
The client pushed back on price. After a 15-minute call walking through the scope boundary document, they agreed to $1,200 — still 50% above the original gut quote, and both parties had clarity on what was included.

What changed:

Developer avoided $400 in undercharging vs. original gut quote
Client got a scope document they could actually use
No disputes because boundaries were defined upfront

This is what "pricing page converts" actually means in practice.

The $10 Quick Review Offer

If you want a second pair of eyes on your own pricing page:

$10 = 3 specific fixes, delivered in 24 hours

I review your pricing structure, identify the 3 highest-impact problems, and give you a clear fix for each. No fluff, just actionable changes.

To order: Send $10 to paypal.me/cheapuno with your pricing page URL. I'll reply within 24 hours.

Target Persona Worksheet

Use this to identify who to pitch:

#	Persona	Observation Angle
1	"Contact for pricing" page	Adding a range builds trust and qualifies leads
2	Flat-rate package, no scope	"Unlimited revisions" = the #1 freelance dispute trigger
3	Hourly billing, no project cap	Max-hour cap aligns incentives for both sides
4	"Starting at $X" no range	Range with "most projects land at $Y" converts better
5	No payment terms stated	No legal protection when clients ghost mid-project
6	"Unlimited revisions" offer	Signals you haven't defined scope boundaries
7	Suspiciously low rates (<$25/hr)	Attracts clients who think cheap = low quality

Email Templates

Template 1: Vague "Contact for Pricing"

Subject: Your contact-for-pricing page might be losing you 60% of leads

Hi [NAME],

I found your portfolio through your GitHub profile and really liked your [PROJECT].

I noticed your pricing page says "contact for a quote." I used to do the same thing — most people who wanted a ballpark just moved on.

I built a simple pricing framework that helps freelance devs communicate scope boundaries clearly. Free worksheet: https://dev.to/cheapuno/the-freelance-scope-estimation-framework-5fl

If you ever want a quick ($10) teardown of your services page, I can send 3 specific suggestions: paypal.me/cheapuno

No pressure.

Template 2: Flat-rate, No Scope Definition

Subject: Quick question about your $500 flat-rate package

Hi [NAME],

I came across your services page and noticed you offer "Flat-rate websites starting at $500." Great way to attract clients — but the package doesn't mention what's included if the client wants major changes after the first draft.

This is the #1 source of freelance disputes. I built a scope definition worksheet specifically for flat-rate devs: https://dev.to/cheapuno/how-to-price-a-scope-change-without-losing-the-cl-3f8

I can do a $10 quick review of your current package structure and send you 3 specific additions that would protect you from scope creep: paypal.me/cheapuno

Template 3: No Payment Terms

Subject: Your services page doesn't mention payment terms

Hi [NAME],

I was browsing your developer profile and saw the services you offer. One thing I noticed: there's no payment terms section.

I learned this the hard way. I put together a payment terms checklist for freelance devs: https://dev.to/cheapuno/the-freelance-scope-estimation-framework-5fl

If you want a $10 review of your current service terms, happy to help: paypal.me/cheapuno

Template 4: Complex Tiered Pricing (5+ tiers)

Subject: Too many pricing tiers paralyzes decisions

Hi [NAME],

I came across your pricing page and noticed you have [X] pricing tiers. That's great for flexibility — but research shows more than 3 tiers causes decision paralysis.

I built a framework that helps devs simplify their pricing into clear tiers: https://dev.to/cheapuno/the-freelance-scope-estimation-framework-5fl

If you want, I can do a $10 review of your current tier structure and suggest how to consolidate: paypal.me/cheapuno

Template 5: Outdated Pricing (2+ years old)

Subject: Your pricing page still shows [X] — costs have changed since then

Hi [NAME],

I found your pricing page through [SOURCE]. I noticed it hasn't been updated in [X] years — costs have likely changed significantly since then.

I put together a simple pricing framework that helps devs stay current: https://dev.to/cheapuno/the-freelance-scope-estimation-framework-5fl

If you want a $10 review of your current pricing with updated suggestions: paypal.me/cheapuno

Twitter/X DM Templates

Template 1: General Pitch (40-60 words)

Hi [NAME] — I checked out your pricing page and noticed [1 specific thing]. I built a freelance scope framework that helps devs like you price more accurately. Free worksheet: [link]

Also do $10 quick pricing teardowns if you want a second pair of eyes: paypal.me/cheapuno

Template 2: Scope Creep Focused

Hey [NAME] — your post about scope creep hit close to home. I built a scope estimation framework specifically for devs who've gotten burned. Free worksheet: [link]

Do $10 quick teardowns if you want 3 specific fixes: paypal.me/cheapuno

Template 3: Calculator Mismatch

Hi [NAME] — I noticed your pricing calculator shows [X] but my framework calculates [Y] for the same inputs. Small gap = big trust issue.

Built a free worksheet to help: [link]. $10 for a full breakdown: paypal.me/cheapuno

LinkedIn DM Templates

Connection Request (≤300 chars)

Hi [NAME] — I came across your profile and liked your post about [TOPIC]. I help freelance devs price more accurately. Would love to connect.

First DM (after connection accepted)

Hi [NAME] — thanks for connecting!

I saw your [post / profile / services page] about [SPECIFIC TOPIC]. I built a freelance scope estimation framework specifically for devs who've gotten burned by unclear project boundaries. Free worksheet: [DEV.TO LINK]

If you ever want a second pair of eyes on your pricing or proposal structure, I do $10 quick teardowns — 3 specific fixes with reasoning, delivered in 24h: paypal.me/cheapuno

No pressure if it's not relevant — just thought it might save you from a painful scope fight down the road.

Follow-up DM (7-10 days after no reply)

Hi [NAME] — one more thing. If you ever want to see how your current pricing compares to market rates, I built a quick framework that calculates fair project prices in 3 steps. $10 for a focused teardown: paypal.me/cheapuno

Worth knowing where you stand either way.

LinkedIn DM: "Flexible/Negotiable Pricing"

Hi [NAME] — your "flexible pricing" approach sounds谦逊, but it can signal uncertainty in your value. Anchoring actually helps both you and the client.

I built a free pricing framework that helps: [link]. $10 for a quick breakdown of where your pricing could be stronger: paypal.me/cheapuno

LinkedIn DM: High-Demand Niche (AI/ML)

Hi [NAME] — you're in a hot niche (AI/ML), but your rates should reflect scarcity, not just time spent. Most devs in your space underprice by 30-40%.

I put together a pricing framework specifically for high-demand niches: [link]. $10 quick review: paypal.me/cheapuno

LinkedIn DM: Recently Raised Rates

Hi [NAME] — congrats on raising your rates! That's a big move. Here's a framework to communicate the value increase to clients so they don't ghost: [link]

If you want a $10 review of your current pricing structure: paypal.me/cheapuno

GitHub Issue/Discussion Templates

Template 1: Monetization Discussion

I really like what you've built here.

As a fellow dev who's gotten burned by unclear project scope, I wanted to share a resource that helped me: a freelance scope estimation framework with a free worksheet on Dev.to.

If you ever want a $10 pricing review of your services page, I can send a focused teardown: paypal.me/cheapuno

Template 2: Pricing Page Feedback (when owner discusses pricing)

This is a great writeup on [TOPIC]. One thing I'd add: the pricing structure you described works well for [USE CASE] but might lose [PROBLEM].

I built a free scope estimation framework that handles this: https://dev.to/cheapuno/the-freelance-scope-estimation-framework-5fl

$10 for a detailed breakdown of your current structure: paypal.me/cheapuno

Template 3: Open Source with "Hire Me" Section

Great project! I noticed you have a "Hire Me" section — if you ever want feedback on how your pricing is presented to potential clients, I do $10 quick teardowns: paypal.me/cheapuno

How to Use This Kit

Step 1: Identify your target (use the persona worksheet above)

Step 2: Pick the channel where they're most active (LinkedIn for consultants, Email for portfolio devs, Twitter for indie hackers)

Step 3: Customize the template with their specific situation (see observation angles)

Step 4: Send and track responses

Step 5: If you get a response about wanting help, offer the $10 review

The $10 Review Process

When someone takes you up on the offer:

Get their pricing page URL
Send $10 via PayPal (paypal.me/cheapuno)
Receive 3 specific fixes within 24 hours

Each fix includes:

What the problem is
Why it matters (with specific numbers when possible)
How to fix it

If this kit helped you: Send $10 → paypal.me/cheapuno

If you want a review of your own pricing page: paypal.me/cheapuno ($10, 24hr delivery)

P.S. The free worksheets are here:

Main framework: https://dev.to/cheapuno/the-freelance-scope-estimation-framework-5fl
Scope changes: https://dev.to/cheapuno/how-to-price-a-scope-change-without-losing-the-cl-3f8

Frequently Asked Questions

Q: Does this kit work for any type of freelance dev?
A: It's designed for devs who quote projects (not hourly). If you bill by hour, the templates still work as communication frameworks — but the scope multiplier math is most accurate for fixed-price quoting.

Q: What if I don't have a pricing page yet?
A: Start with Template 1 (the "Contact for Pricing" template) to diagnose where you are, then use the targeting worksheet to identify which specific templates apply to your situation.

Q: How do I know which template to use first?
A: Use the targeting worksheet — it helps you identify which devs have the highest-friction pricing page problem. High friction = highest urgency = best response rates.

Q: Is $10 for one review or ongoing?
A: One-time. $10 gets you a single review with 3 specific fixes. If you want ongoing access to the full 20-template kit, that's a separate conversation.

Q: How long does delivery take?
A: I review and respond within 24 hours of receiving your payment and pricing page URL.

How to Price a Freelance Project: A Simple Framework With Examples

張旭豐 — Wed, 01 Jul 2026 03:27:59 +0000

How to Price a Freelance Project: A Simple Framework With Examples

One of the hardest parts of freelancing is figuring out what to charge. Not because you lack skills — but because most pricing advice is either too vague ("charge what you're worth!") or too complex (complex spreadsheets nobody uses).

After losing $2,000 on a poorly-scoped project and spending three years iterating on how I price work, I built a framework that actually works: three numbers, one formula, and you're done.

This article gives you that framework — free. If it helps you land a fair deal, I offer $10 quick reviews (see below).

The Three Numbers You Need

Before the formula, you need three inputs:

1. Base Rate (BR)

What you'd charge for a trivial version of this project — one that barely works. Not what you wish you could charge. What you'd honestly accept if you were desperate.

2. Scope Multiplier (SM)

How much more complex is this project than the trivial version? Use this scale:

Complexity	SM Range	Example
Trivial	1.0–1.2	Static HTML page
Simple	1.3–1.5	3-page website with contact form
Medium	1.8–2.5	Database-backed app with auth
Complex	3.0–4.0	Real-time features, third-party integrations
Epic	5.0+	Full platform, multi-team

3. Risk Buffer (RB)

What percentage of the project scope is likely to change or expand?

Change Likelihood	RB
Very unlikely	10–15%
Possible	20–25%
Likely	30–40%
Almost certain	50%+

The Formula

Final Price = BR × SM × (1 + RB)

That's it. Three numbers, one multiplication.

Real Examples

Example 1: The "Quick Widget"

Base Rate: $500 (trivially, a single HTML page)
Complexity: Medium (API integration, custom UI) → SM = 2.0
Risk: Client has a history of changing requirements → RB = 25%

$500 × 2.0 × (1 + 0.25) = $1,250

What to say to the client: "Based on the scope and typical revision patterns, my estimate is $1,200–$1,300 for this project."

Example 2: The "Small Fix"

Base Rate: $100 (trivial bug fix)
Complexity: Low-medium (a few files) → SM = 1.3
Risk: Low, but scope could creep → RB = 15%

$100 × 1.3 × (1 + 0.15) = $149.50 → $150

What to say: "$150, and that includes a 15% buffer for minor scope questions."

Example 3: The "Big Platform"

Base Rate: $2,000 (MVP that barely works)
Complexity: Complex (auth, payments, real-time) → SM = 3.5
Risk: High — client is a startup, pivots likely → RB = 40%

$2,000 × 3.5 × (1 + 0.40) = $9,800

What to say: "For a full platform build with those integrations and that risk profile, I'm at $9,800. If budget is tight, we can scope down to an MVP first at $3,500."

Composite Case Study: From $800 to $1,200

Here's a composite example based on typical freelancer pricing patterns I see:

A freelance engineer was asked to build a client dashboard. They prepared a quote using their gut feeling:

Base Rate: $800 for the "basic version"
Scope: Medium complexity → SM = 1.5
Risk: Client had changed requirements before → RB = 0.2

Original gut quote: $800

When they ran it through the framework:

$800 × 1.5 × (1 + 0.2) = $1,440

The framework was telling them they were undercharging by $640 — nearly half.

What happened: They sent the $1,440 quote with their reasoning. The client negotiated to $1,200 and both sides walked away happy. The freelancer earned $400 more than their original gut feeling.

The lesson: Your gut quote and your framework quote are often different numbers. Run both. If the framework number is higher — that's your protection buffer doing its job.

The Pricing Worksheet (Copy This)

Use this template when a new project comes in:

Base Rate (BR): $____
Scope Multiplier (SM): ____
Risk Buffer (RB): ____%

Final Price = BR × SM × (1 + RB)
           = $____ × ____ × (1 + .____)
           = $____

Negotiation tip: Present the number as a range. Say "$1,200–$1,500" instead of "$1,350." The range feels less arbitrary and gives room to move without cutting deep.

Pricing Decision Checklist

Before you send your next quote, run through this:

[ ] I know my Base Rate (what I'd charge for a trivial version)
[ ] I chose a Scope Multiplier and documented why
[ ] I added a Risk Buffer for scope uncertainty
[ ] I checked whether the project has hidden complexity I haven't discussed
[ ] I turned the final number into a price range, not a single digit
[ ] I know my walk-away number before the negotiation starts

Common Mistakes

Mistake 1: Using hourly rates

"If I charge $50/hr and it takes 20 hours, that's $1,000." But if you finish in 10 hours, you just left $500 on the table. Scope-based pricing rewards efficiency. Hourly rates reward slowness.

Mistake 2: Ignoring the risk buffer

Most freelancers quote the happy path. When scope expands (and it always does), you're eating the cost. The risk buffer is your protection.

Mistake 3: Anchoring to the client's budget

If a client says "we have $5,000" and your formula says $8,000, don't immediately drop to $5,000. Say: "For $5,000, here's what we can deliver. Here's what the full scope costs. Your choice."

Mistake 4: No internal revision buffer

Build 10–20% slack into your own formula before presenting. Not as padding — as a buffer for your own estimation errors. You're better at estimating than most, but you're not perfect.

Try the Interactive Calculator

Want to skip the formula and get a number right now? Here's a browser-based calculator you can use immediately — no signup, no account needed.

How to use it: Copy the HTML below, save it as calculator.html, and open it in any browser. Enter your base rate, estimated hours, and scope risk. Get a fair price range instantly.

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Freelance Pricing Calculator</title>
<style>
  * { box-sizing: border-box; margin: 0; padding: 0; }
  body { font-family: system-ui, sans-serif; background: #0d1117; color: #e6edf3; padding: 2rem; }
  .container { max-width: 600px; margin: 0 auto; }
  h1 { font-size: 1.4rem; color: #58a6ff; margin-bottom: 1rem; }
  label { display: block; font-size: 0.875rem; color: #8b949e; margin-bottom: 0.25rem; }
  input { width: 100%; padding: 0.5rem; background: #161b22; border: 1px solid #30363d; border-radius: 4px; color: #e6edf3; margin-bottom: 0.75rem; }
  .result { background: #1c2128; border: 1px solid #30363d; border-radius: 6px; padding: 1rem; margin-top: 1rem; font-size: 1.5rem; font-weight: bold; color: #58a6ff; text-align: center; }
  .note { font-size: 0.75rem; color: #484f58; margin-top: 0.5rem; text-align: center; }
</style>
</head>
<body>
<div class="container">
  <h1>Freelance Pricing Calculator</h1>
  <label>Base Rate ($) <small>— what you'd charge for a trivial version</small></label>
  <input type="number" id="rate" value="500">
  <label>Estimated Hours</label>
  <input type="number" id="hours" value="20">
  <label>Scope Risk (1.0–2.0) <small>— 1.0=clear, 2.0=very uncertain</small></label>
  <input type="number" id="risk" value="1.3" step="0.1" min="1" max="5">
  <div class="result" id="output">$1,300 – $1,560</div>
  <p class="note">Formula: Base Rate × Hours × Risk = Fair Range</p>
</div>
<script>
function calc() {
  const r = +document.getElementById('rate').value;
  const h = +document.getElementById('hours').value;
  const s = +document.getElementById('risk').value;
  const base = r * h;
  const low = Math.round(base * s * 0.9);
  const high = Math.round(base * s * 1.1);
  document.getElementById('output').textContent = '$' + low.toLocaleString() + ' – $' + high.toLocaleString();
}
document.querySelectorAll('input').forEach(i => i.addEventListener('input', calc));
</script>
</body>
</html>

What you get:

✅ Instant price range (no mental math)
✅ Considers your floor rate, hours, and scope uncertainty
✅ Works offline — save and use it anytime

Need a Pricing Review?

If you're mid-negotiation or about to send a proposal, I offer quick turnaround reviews:

$5 Quick Review

One pricing response based on your numbers
No revision
Sent within 24 hours

$10 Full Scope Review

Your project scope analyzed with the framework above
One response plus one revision
Specific price recommendation with negotiation range
Delivered within 24 hours

To order: Send payment via paypal.me/cheapuno and include a brief summary of your project (1–3 sentences).

Need a Custom Price for Your Project?

If you're mid-negotiation or about to send a proposal, I offer a quick turnaround review:

$10 Full Scope Review

Your project scope analyzed with the framework above
Specific price recommendation
Red flags identified before you underprice
Delivered within 24 hours
Payment: https://paypal.me/cheapuno

Format: PDF or text, depending on complexity. No contracts, no upsell.

Related Guides

If this framework helped you, you might also find these useful:

The Freelance Scope Estimation Framework — The underlying math behind this calculator
3個開發者定價頁常見錯誤 — Common pricing page mistakes I see developers make
A Tiny Pricing Calculator for Scope Changes — A simple calculator for when scope changes mid-project

Last updated: 2026-07-01

How a $2,000 Freelance Project Should Have Been Priced at $4,500

張旭豐 — Wed, 01 Jul 2026 02:51:46 +0000

How a $2,000 Freelance Project Should Have Been Priced at $4,500

A realistic pricing teardown for a client who asked for an automation workflow.

The Job Everyone Gets Wrong

Most freelancers don't undercharge because they lack confidence. They undercharge because they only count the hours they know about — not the hours they don't.

A client asks for an automation workflow that integrates their CRM with their email tool. They say their budget is $2,000. You do some mental math: 15 hours × $120/hr = $1,800. You could do it for $1,900.

This is where almost everyone leaves money on the table. And it's not because you're bad at negotiating. It's because you're pricing the wrong thing.

The Project Nobody Should Quote at $2,000

Here's a real project setup:

Client asks for: An automation workflow connecting HubSpot to Gmail, with triggers, filters, and conditional routing. About 15 hours of work.

Their stated budget: $2,000

The $1,800 quote most people give:

15 hours × $120/hr = $1,800

This looks reasonable. It feels fair. Here's why it quietly destroys your business.

Why the Simple Math Is Wrong

What you're actually selling

When you quote by hours, you're treating this like a job. But your client isn't buying your time. They're buying:

A working system that doesn't break when conditions change
The peace of mind that the automation handles edge cases
Someone to call if it stops working at 2am before a campaign launch
Confidence that the data in their CRM actually matches their email tool

That's not 15 hours of work. That's an operational system with ongoing value.

The hidden complexity

A CRM-email integration that "just works" involves:

Implementation cost: What you think is 15 hours
Scope uncertainty buffer: What happens when the client's CRM has custom fields you didn't know about?
Revision risk: What if the client changes their mind about the trigger conditions?
Client-side coordination: Will someone be available to approve credentials and test the sandbox environment?
Communication overhead: How many meetings, Loom videos, and Slack threads does this actually take?
Delivery confidence: What is it worth to you to guarantee this works before go-live?

If you only charge for the first one, you're subsidizing the rest.

The Correct Pricing Breakdown

Here's what a fair quote looks like when you count everything:

Component	Cost
Implementation (15 hrs × $120)	$1,800
Scope uncertainty buffer (20%)	$360
Revision risk (10%)	$180
Client coordination overhead (5 hrs)	$600
Communication thread cost (3 hrs)	$360
Delivery confidence guarantee (5 hrs)	$600
Total	$3,900

Round down to $3,500 for a cleaner number, or structure it as three options.

Three Options Instead of One

Most clients who push back on $3,500 aren't saying the work isn't worth it. They're saying they can't justify the full amount right now. Give them a tiered structure:

Option 1 — The Core ($2,800)

Standard CRM-email integration
Basic triggers and filters
2 rounds of revisions
30-day support window

Option 2 — The Complete ($4,500)

Everything in Option 1
Edge case handling for 5 common scenarios
Full documentation
90-day support window
Priority response within 24 hours

Option 3 — The Enterprise ($7,500)

Everything in Option 2
Custom error handling and fallbacks
Monitoring dashboard
6-month support window
Monthly check-in call

This works because you're not discounting. You're giving them a real choice about scope and risk. The client who takes Option 1 still gets a working system — and the ones who need more pay for more.

Copy This Mini Calculator

Want to reprice your next freelance project? Use this formula:

BASE = hours × your_rate
COMPLEXITY = BASE × 1.25  (if the brief has any ambiguity)
RISK = BASE × 0.15  (if client has a history of changing scope)
COORDINATION = hours_you_estimate × 0.4 × your_rate  (meetings, reviews, back-and-forth)
SUPPORT = hours × 0.3 × your_rate  (buffer for questions after delivery)

FINAL = BASE + COMPLEXITY + RISK + COORDINATION + SUPPORT

This won't give you a perfect number. It will give you an honest one.

The Real Lesson

The $2,000 budget wasn't the project's value. It was the client's opening offer based on what they assumed your work was worth. Your job isn't to accept or reject it — it's to show them what the actual work costs and let them decide.

If they come back and say it's too expensive, that's when you have a real conversation about scope. But you can't have that conversation from $1,800. You can only have it from $4,500.

Want Me to Tear Down Your Next Quote?

If you're working on a project and want a second pair of eyes on the scope and pricing, I offer $10 quick reviews: paypal.me/cheapuno

Send me the brief, your current rate, and what you're thinking of charging. I'll send back a breakdown of what I'd charge and why — within 24 hours.

Continue Your Pricing Journey

If you want the framework behind this teardown: → The Freelance Scope Estimation Framework — the complete formula (BR × SM × RB)

If you're dealing with a scope change right now: → How to Price a Scope Change Without Losing the Client — specific phrasing and pricing strategy for mid-project changes

If you want a tool that does the math for you: → A 30-Second Pricing Decision Tree for Freelance Devs — answer 5 questions, get a price range

Who Is Actually Getting Burned

This isn't a confidence problem. It's a pricing structure problem.

The freelancers who get burned most are the ones who are competent, careful, and genuinely trying to do good work. They run the numbers honestly. They think: "15 hours at $120/hr = $1,800, I'll charge $1,900 and seem fair."

Here's what they didn't account for:

The client who says "we'll handle the technical details" — and then spends 6 hours in Slack threads coordinating credentials you could have set up yourself.

The project that "should take a week" — but the client's internal review process adds three rounds of feedback you never factored in.

The "simple change" that turns into a full rewrite because the client's original requirements didn't mention the compliance field their legal team added two days before launch.

If you've ever finished a project and thought "I actually lost money on this" — you already know this problem. You just didn't have a system for pricing it correctly upfront.

Self-Evaluation Checklist

Go through each one. If you answer "yes" to 3 or more, your next project is probably underpriced.

[ ] The brief had any ambiguity — even a little "we can discuss later" in the scope document
[ ] You've done this type of project before and it always takes longer than the initial estimate
[ ] The client uses words like "flexible," "we'll figure it out," or "not a big deal" when discussing scope
[ ] You'd need to schedule more than 2 calls/meetings to align on requirements
[ ] There are stakeholders besides the person you're directly talking to (designer, manager, legal, etc.)
[ ] The project has any integration component (APIs, webhooks, third-party tools)
[ ] The client's industry has compliance requirements (healthcare, finance, legal, education)

If you're at 5+: You need either a scope document with explicit buffers, or you need someone to sanity-check your quote before you send it.

The Outreach Kit Angle

If you're reading this and thinking "I don't need a consultation, I need to know how to price better" — the Freelance Pricing Page Review Kit is a free downloadable resource with the templates and checklists I use when pricing my own projects.

If you've read it and still want a second set of eyes on a specific quote, I'm available for $10 quick reviews: paypal.me/cheapuno. Send me the brief and your current number. I'll tell you what I'd charge and why.

No pitch. No upsell. Just a direct breakdown within 24 hours.

This is part of a series on freelance pricing. If this helped you see your work differently, the best next step is to audit your current pricing formula before your next client conversation.

How to Price a Scope Change Without Guessing

張旭豐 — Wed, 01 Jul 2026 02:43:39 +0000

How to Price a Scope Change Without Guessing

When a client says "can you add one more feature?", freelancers either lowball themselves or overprice and lose the gig. There's a formula that handles both.

If you want a second pair of eyes on your scope-change price, I can review it for $10 and tell you whether the number is too low, too vague, or ready to send. Just send me your scope doc or pricing page and I'll reply within 24 hours with specific improvements: paypal.me/cheapuno

$10 Quick Review — Is Your Pricing Page Actually Working?

I've reviewed 12 freelance pricing pages. 7 had no direct way to hire the person.

That means if someone reads your article and thinks "this could help me price my next project" — they leave without a way to work with you.

What you get:

I review your pricing page or scope document
Identify 2-3 specific improvements
Give you exact wording that converts readers to clients

Delivery: 24 hours. $10 via PayPal: paypal.me/cheapuno

The Scope Change Pricing Formula

Change Price = (Extra Hours × Hourly Rate × Risk Multiplier) + Delay Cost

Step 1: Count the Extra Hours

Be honest. How many extra hours will this add? Don't sandbag, but don't pad either. Write down the real number.

Ask yourself:

How many screens/files does this touch?
Do I need to update tests?
How long is integration testing?

Step 2: Apply the Risk Multiplier

Risk Level	Multiplier	When to Use
Low	1.0×	New feature, no integration
Medium	1.3×	Modifies existing logic or database
High	1.6×	Changes API, auth, or payment flow

Why it matters: A standalone feature you can build in 4 hours might take 8 hours if it touches your existing data layer. The multiplier accounts for that.

Step 3: Add the Delay Cost

Projects with scope changes often slip. When you add features mid-project, everything else gets pushed back. You deserve compensation for that delay.

Delay Cost = Days Added × Daily Rate

Where Daily Rate = Your hourly rate × 8 hours

Worked Example: The Full Breakdown

You quoted $2,000 for a 2-week project. Client wants to add a user export feature. Here's how the number gets calculated:

Step 1 — Extra Hours:

Building the export feature: 6 hours
Updating existing tests: 1 hour
Integration testing: 1 hour
Total extra hours: 8

Step 2 — Risk Multiplier:

Feature touches the existing data layer
Moderate integration risk
Multiplier: 1.3×

Step 3 — Delay Cost:

This change adds 2 days to the timeline
Your daily rate: $75/hr × 8 = $600/day
Delay cost: $1,200

The Math:

Change Price = (8 × $75 × 1.3) + (2 × $600)
             = $780 + $1,200
             = $1,980

The Message You Send:

"Adding user export requires 8 extra hours of work. With the integration risk and 2-day schedule impact, that's an additional $1,980. Want me to proceed?"

They either say yes, negotiate, or drop it. Either way, you're not guessing — you have the math to back it up.

Your Turn: Price This Scope Change

Field	Your Number
Extra Hours	_____
Your Hourly Rate	$_____
Risk Multiplier (1.0 / 1.3 / 1.6)	_____
Days Added	_____
Daily Rate (= hourly × 8)	$_____
Change Price	$_____

The Exact Wording to Send Your Client

After calculating:

"Adding [feature name] requires [X] extra hours. With the integration risk and schedule impact, that's an additional $[price] and [N] days. Want me to proceed?"

FAQ

Q: What if the client pushes back on the price?
A: Reply with the math. "Here's how I calculated it: [X hours] × [rate] × [multiplier] plus [delay days] × [daily rate]. Happy to walk through each line." Most clients who push back haven't seen the breakdown — showing your work often ends the negotiation.

Q: Should I just give free advice to get the client to commit?
A: No. Free advice is what got you into this situation. Instead, offer a $10 quick review: "I can look at your full scope and tell you exactly what to charge. $10, 24 hours." This converts free consult seekers into paying clients without giving away your expertise.

Q: My client already agreed to a fixed price. How do I handle scope changes?
A: Go back to the contract. If there's a scope change clause, use it. If not, the exact wording helps: "My original quote covered [original scope]. This new feature falls outside that scope, so here's the additional cost." Frame it as protecting both of you, not as a money grab.

Q: What if the scope change is tiny — just a few hours?
A: Small scope changes still have hidden costs: context switching, re-testing, and re-explaining. Use a minimum multiplier of 1.1× even for "easy" additions. Better to quote slightly high and negotiate down than to lowball yourself again.

Q: How do I know if my original hourly rate is correct for scope changes?
A: Your original rate was probably calculated for the original project scope. Scope changes often warrant a higher effective rate because: (1) you're working on unfamiliar code someone else wrote, (2) the timeline pressure is higher mid-project, (3) communication overhead increases. Consider using 1.2× your normal rate as a scope-change premium.

Q: The client says "we'll handle this next phase" — how do I respond?
A: Get it in writing before the current phase ends. Reply: "Just to confirm — [feature name] is being moved to Phase 2, right? I'll include it in the next scope document." This prevents "I thought that was included" disputes later.

Already Have Articles But No Client Inquiries?

Most freelancers have great content — but no path from "read article" to "hire you."

What I review:

Your main article or pricing page
Call-to-action placement
Offer clarity and conversion language

$10 quick review — 24-hour delivery: paypal.me/cheapuno

Or if you want a full scope assessment: For $25, I do a deep-dive review of your complete pricing structure, including scope-change policies, contract language, and negotiation scripts you can use immediately. paypal.me/cheapuno

Freelance Scope Change Pricing Calculator: How to Quote Extra Work Without Guessing

張旭豐 — Wed, 01 Jul 2026 01:31:50 +0000

Freelance Scope Change Pricing Calculator: How to Quote Extra Work Without Guessing

The Problem: Every Freelancer Knows This Feeling

You're mid-project. Client says: "Can you just add one more thing?"

You hesitate. You don't want to lose the client. But you also don't want to work for free.

The typical response? "Sure, I can do that for $X." And then you either undersell yourself or overcharge and lose the job.

Scope change pricing is where freelancers quietly lose margin — and most never even track it.

The Formula Nobody Teaches

Here's the real formula for pricing scope changes:

Scope Change Price = (Hours × Hourly Rate) × Complexity Multiplier + Rush Fee

But that's still incomplete. The actual formula I use:

Final Price = (Estimated Hours × Your Effective Rate × 1.3) + Complexity Buffer + Market Adjustment

Let me break this down.

Step 1: Calculate Your Base

First, what are you actually worth per hour?

Effective Hourly Rate = Monthly Target Income ÷ Billable Hours per Month

Most freelancers target 60-80% billable time. If you want $8,000/month and can bill 100 hours, your effective rate is $80/hour. But you need to charge more because not every hour is billable.

Target Rate = Effective Rate × 1.4 to 1.6

Step 2: Estimate the Scope Change Hours

Be honest. How many hours will this actually take?

Add a 20% buffer for unexpected complexity. If you think 5 hours, budget for 6.

Step 3: Apply the Complexity Multiplier

Complexity	Multiplier	Example
Simple addition (5 min task)	0.5×	"Add a button"
Standard feature (fits existing patterns)	1.0×	"Add a contact form"
New pattern or integration	1.5×	"Add payment processing"
Significant architectural change	2.0×+	"Rebuild the database"

Step 4: Calculate the Final Price

Here's the calculator in spreadsheet form:

Variable	Your Value
Your effective hourly rate	$______
Estimated hours	______
× 1.3 (business overhead)
× Complexity multiplier	______
Subtotal	$______
Rush fee (if applicable)	$______
Final Price	$______

Complete Worked Example

You quoted $5,000 for a website. Client now wants a new payment integration.

Step 1 — Your effective rate:

Target monthly income: $8,000
Billable hours: 100/month
Effective rate: $80/hour
Target rate: $80 × 1.5 = $120/hour

Step 2 — Estimated hours:

You think: 8 hours
With buffer: 8 × 1.2 = 9.6 hours

Step 3 — Complexity:

New payment integration = 1.5×

Step 4 — Final calculation:

(9.6 × $120 × 1.3) × 1.5 = $2,246
You charge: ~$2,200–$2,500

Would you have come up with $2,200 on your own? Probably not. The formula gives you a defensible number backed by math.

Composite Case Study: Turning a $300 Quote Into a $1,170 Quote

The situation: A freelancer quoted $8,000 for a web app. Client asks mid-project: "Can you add a user dashboard?" The freelancer's gut response: "Maybe $300?" That's what most people do — guess.

Applying the formula:

Input	Value
Estimated hours	8
Your hourly rate	$75/hr
× 1.3 (business overhead)	× 1.3
× 1.5 (new integration complexity)	× 1.5
Calculated quote	$1,170

What the $300 response actually costs:

8 hours × $75/hr = $600 (just labor, no overhead)
With business overhead: you needed ~$975 to break even
$300 = working at a $37.50/hr effective loss

The better response:

"Happy to help with that! Based on the additional complexity, this falls outside the original scope. My estimate is $1,170, which includes 8 hours of work plus the complexity buffer. I can have it done by [date]. Does that work for you?"

Upside: You avoided undercharging by $870 on this one change. Over a year of 5-10 scope changes, that's $4,000-$8,700 you keep instead of giving away.

Scope Change Rescue Cheat Sheet

When a client springs a scope change mid-project, use this framework to respond without losing the client or your margin:

Response template:

"Happy to help with that! Based on the additional complexity, this falls outside the original scope. Here's what it would cost to add: [quote using the formula above]. I can have it done by [date]. Does that work for you?"

If they push back on price:

"I completely understand budget is a factor. Here are the options: [A] I can simplify the approach to reduce hours, or [B] we defer this to Phase 2 and focus on the original deliverables first."

If they already agreed to a number and it was too low:

"I realized the original estimate didn't fully account for [specific reason]. To deliver this properly, I'd need to adjust to [new number]. The alternative is [simpler version]. Which works better for you?"

Three-Tier Service Options

$5 — Quick Framing Fix

Best for: You already have a number in mind but want a second opinion on how to present it to the client.

Delivered within 24 hours — 1 response

What you get:

Review of your current scope-change situation
Suggested price adjustment (if needed)
One client-ready response sentence you can copy-paste

Order: Send $5 via PayPal.me/cheapuno with your situation (project type, original quote, what client asked for)

$10 — Full Price Calculation + Script

Best for: You have a complex scope change and want a complete price breakdown plus talking points.

Delivered within 24 hours — 1 response + 1 revision

What you get:

Complete price calculation using the formula above
2-3 framing options (anchoring high / medium / low)
A client-ready response script
A "nuclear option" script if they push back

Order: Send $10 via PayPal.me/cheapuno with your situation + deadline

$25 — Deep Dive Review

Best for: You're about to have a difficult conversation with a client, or you want a complete re-pricing strategy.

Delivered within 48 hours

What you get:

Full price calculation with scenario modeling
Client communication scripts for 3 different pushback types
Email template for formal scope change documentation
Optional: 15-minute async voice memo explaining the reasoning

Order: Send $25 via PayPal.me/cheapuno with your situation + what your client said

FAQ

Q: I already told the client a number and it was too low. Can I walk it back?
A: Yes — frame it as "I did a more thorough estimate." Clients respect thoroughness more than you think. Use the rescue scripts above.

Q: The client keeps adding small things every week. How do I stop this?
A: That's scope creep, not a scope change. Implement a weekly "change request" process: anything added after the original brief costs 1.5× the formula. Mention this in your next client check-in.

Q: What if I have no idea how complex the change will be?
A: Give a range with a condition: "This looks like it could be 3-5 hours depending on [specific unknown]. I can give you a firm quote after I spend 1 hour investigating — should I go ahead?" Charge $25 for the investigation.

Q: The client says "we'll figure it out later" but I know it'll be a lot of work.
A: Never leave a scope change unpriced. Say: "Let's put a placeholder of [formula-based estimate] for now, and we'll confirm the final before I start. Does that work?" Document it in writing.

Q: Can I use this for contract work at an agency?
A: Yes, but add 20-30% to the final number — agency clients typically have more approval overhead and slower payment cycles.

Need Help Right Now?

If you're stuck on a specific situation — maybe you already gave a number and need a second opinion, or you're not sure how to explain the price to your client — send me the details and I'll give you a concrete answer.

Order: PayPal.me/cheapuno with your situation, original scope, what the client asked for, and your deadline.