[{"data":1,"prerenderedAt":2599},["ShallowReactive",2],{"blog-\u002Fblog\u002Fcost-process\u002Fsheji-fei-yinsu":3,"blog-related-\u002Fblog\u002Fcost-process\u002Fsheji-fei-yinsu":429},{"id":4,"title":5,"author":6,"body":7,"category":398,"cover":399,"date":400,"description":401,"draft":402,"extension":403,"faq":404,"featured":402,"image":399,"keywords":414,"meta":419,"navigation":420,"path":421,"seo":422,"sitemap":423,"stem":424,"tags":425,"updated":400,"__hash__":428},"blog\u002Fblog\u002Fcost-process\u002Fsheji-fei-yinsu.md","设计费用在项目里占多少","HNREIS",{"type":8,"value":9,"toc":369},"minimark",[10,19,22,26,43,46,49,54,57,61,64,68,82,85,89,92,95,99,102,105,109,112,116,119,123,126,137,140,144,147,151,218,221,224,227,231,234,238,241,245,248,252,255,258,283,286,324,327,330,363],[11,12,13,14,18],"p",{},"UI\u002FUX 设计是软件项目里常被低估、却直接影响产品成败的一环。很多企业把预算大头压在开发上，觉得设计\"画几个图能花多少时间\"，结果产品上线后用户反馈难用、转化率低，才意识到设计省不得。",[15,16,17],"strong",{},"设计费占一定比例，别省。"," 这篇讲清设计费占多少、受什么影响、为什么值得投入。",[11,20,21],{},"设计的本质不是\"把东西画好看\"，而是把产品逻辑、用户需求、业务目标翻译成可用的界面。一个按钮的位置、一个表单的字段顺序、一个错误提示的措辞，背后都是设计决策。这些决策的累积，决定了用户用起来是顺畅还是别扭。理解了这一点，你就会明白为什么设计值得花钱。",[23,24,25],"h2",{"id":25},"设计费占多少",[27,28,29,37,40],"ul",{},[30,31,32,33,36],"li",{},"通常占项目",[15,34,35],{},"10%到20%","，具体看项目复杂度和品牌要求。",[30,38,39],{},"简单项目（页面少、交互常规）偏低，复杂项目（多端、多角色、强品牌）偏高。",[30,41,42],{},"是项目重要部分，不是可有可无的附加环节。",[11,44,45],{},"设计费占比看起来不高，但它对产品最终效果的影响远超这个比例。一个常见的比喻：设计费占项目总成本的 15%，但它对最终用户体验的影响可能占 50% 以上——因为用户能直接感知到的，全是设计的输出。",[23,47,48],{"id":48},"设计费的影响因素",[50,51,53],"h3",{"id":52},"_1-页面数","1. 页面数",[11,55,56],{},"页面数量直接决定设计工作量。一个简单的着陆页可能就 3–5 个页面，设计量小；一个 SaaS 后台可能有几十甚至上百个页面，每个页面都要单独设计、都要保持风格统一，工作量自然上去了。页面之间的跳转关系、空状态、错误状态、加载状态也都要设计，这些都是隐形成本。很多企业在算页面数的时候只数\"主要页面\"，忽略了每个主要页面背后的 5-10 种状态，实际设计工作量比预估的高出一截。",[50,58,60],{"id":59},"_2-复杂度","2. 复杂度",[11,62,63],{},"交互复杂度是另一个关键因素。一个静态展示页和带复杂表单、拖拽、实时数据可视化的工作台，设计难度完全不在一个量级。复杂交互需要更多的状态设计、边界情况考虑、动效设计，设计师投入的时间成倍增加。复杂度的另一个体现是数据展示：同样一个\"数据列表\"，简单的只要展示几列；复杂的可能涉及筛选、排序、分组、批量操作、自定义视图、导出，每一种都要设计对应的交互。",[50,65,67],{"id":66},"_3-品牌要求","3. 品牌要求",[27,69,70,76],{},[30,71,72,75],{},[15,73,74],{},"定制品牌设计","：需要从品牌调性出发，定制配色、字体、图标、插画风格，甚至做品牌规范，这类设计投入大、周期长。定制品牌设计的好处是产品有辨识度，用户能记住你，而不是觉得\"这个产品我在哪见过\"。",[30,77,78,81],{},[15,79,80],{},"通用模板","：基于成熟设计系统（如 Material、Tailwind UI）做适配，风格统一但定制感弱，成本可控。通用模板适合预算有限或者产品处于早期验证阶段的项目，先用成熟方案跑起来，后期再逐步品牌化。",[11,83,84],{},"品牌要求越高，设计成本越高，但产品的辨识度也越强。这是投入产出比的权衡，没有标准答案，要看你的业务阶段和品牌定位。",[50,86,88],{"id":87},"_4-迭代次数","4. 迭代次数",[11,90,91],{},"反复改是设计成本失控的常见原因。每改一轮设计师要重新出稿、评审、调整，三轮改下来成本翻倍。前期把需求确认清楚、给明确的设计方向（参考案例、风格倾向、品牌资料），能显著控制设计成本。改稿本身不是问题，问题是前期没想清楚导致的反复推翻。一个常见场景：第一轮设计师按你说的做了，你看了之后觉得\"好像不是这个感觉\"，推翻重来；第二轮换了方向，做完又觉得\"还是第一版更好\"——这种来回切换是最伤成本的，因为每一轮都是从头开始。",[11,93,94],{},"反复改是设计成本失控的常见原因。每改一轮设计师要重新出稿、评审、调整，三轮改下来成本翻倍。前期把需求确认清楚、给明确的设计方向，能显著控制设计成本。",[50,96,98],{"id":97},"_5-设计师级别","5. 设计师级别",[11,100,101],{},"资深设计师单价高，但出稿质量高、一次成型率高、返工少；初级设计师单价低，但可能需要多轮修改才能达到要求。算总账，资深未必更贵。资深设计师的另一个价值是判断力——他们能在需求阶段就指出\"这个交互行不通\"\"这个布局用户体验不好\"，避免后期返工。这种前置的判断力，往往比出稿本身更值钱。",[23,103,104],{"id":104},"设计的价值",[50,106,108],{"id":107},"_1-用户体验","1. 用户体验",[11,110,111],{},"好的设计让产品好用、流畅，用户能快速完成任务、少出错、少困惑。差的设计让用户在每个环节都卡顿、迷路、放弃。体验直接影响用户留存和口碑，这是设计最基础的价值。用户体验的好坏往往体现在细节里：一个表单的字段顺序是否符合用户的思考逻辑、一个按钮的反馈是否让用户知道操作成功了、一个错误提示是否告诉用户怎么修正而不是只说\"出错了\"。这些细节累积起来，就是好用和难用的差距。",[50,113,115],{"id":114},"_2-第一印象","2. 第一印象",[11,117,118],{},"用户打开产品的头几秒，就凭视觉判断\"这家公司靠不靠谱\"。好看、专业的设计建立信任；粗糙、业余的设计让人怀疑产品质量。这个第一印象往往决定了用户是继续用还是直接走。在线上产品的语境里，用户没有机会和你的销售聊、看不到你的办公室、感受不到你的服务态度，他们能感知到的全部信息就是界面。界面粗糙，用户就会觉得产品不可靠，这是人的本能反应。",[50,120,122],{"id":121},"_3-转化","3. 转化",[11,124,125],{},"设计影响转化率，这是它能带来真金白银的地方：",[27,127,128,131,134],{},[30,129,130],{},"营销型落地页的设计直接影响注册率、购买率。一个经过设计的落地页和一个随便做的落地页，转化率可能差几倍。",[30,132,133],{},"按钮位置、文案、配色、表单长度都会影响转化。这些看起来是小事，但每一个百分点的转化率提升都对应真金白银的收入。",[30,135,136],{},"好的结账流程设计能显著降低弃单率。电商领域的数据显示，结账环节的设计优化能让弃单率下降 20%-35%。",[11,138,139],{},"转化率是设计最直接的商业价值。同样的流量，好的落地页设计能让转化率提升 30%–100%，这部分收益远超设计费本身。这也是为什么很多有经验的团队在投放广告之前会先优化落地页设计——广告买来流量，设计决定流量能不能转化成客户。",[50,141,143],{"id":142},"_4-品牌","4. 品牌",[11,145,146],{},"设计是品牌的载体。统一的视觉风格、有辨识度的界面，让用户记住你的品牌，形成长期心智资产。这是设计带来的长期价值。品牌价值不是一朝一夕建立的，而是每次用户接触你的产品时累积起来的。统一的设计让每一次接触都在强化品牌认知，长期下来形成用户心智里的\"这就是这家公司的样子\"。",[23,148,150],{"id":149},"设计-vs-省设计","设计 vs 省设计",[152,153,154,170],"table",{},[155,156,157],"thead",{},[158,159,160,164,167],"tr",{},[161,162,163],"th",{},"维度",[161,165,166],{},"专业设计",[161,168,169],{},"省设计",[171,172,173,185,196,207],"tbody",{},[158,174,175,179,182],{},[176,177,178],"td",{},"体验",[176,180,181],{},"好",[176,183,184],{},"差",[158,186,187,190,193],{},[176,188,189],{},"印象",[176,191,192],{},"专业",[176,194,195],{},"业余",[158,197,198,201,204],{},[176,199,200],{},"转化",[176,202,203],{},"高",[176,205,206],{},"低",[158,208,209,212,215],{},[176,210,211],{},"成本",[176,213,214],{},"投入",[176,216,217],{},"省了但失转化",[11,219,220],{},"省下的设计费，往往会以转化率下降、用户流失的形式成倍还回来。一个典型的对比：省下 3 万设计费，转化率从 3% 掉到 1.5%，一年下来流失的订单利润可能是设计费的十几倍。省设计是这个世界上最不划算的省钱方式之一。",[23,222,223],{"id":223},"怎么优化设计费",[11,225,226],{},"优化不等于省，而是把钱花在刀刃上。",[50,228,230],{"id":229},"_1-用成熟设计系统","1. 用成熟设计系统",[11,232,233],{},"基于成熟的设计系统（如 Nuxt UI、shadcn\u002Fui、Tailwind UI）构建，大量组件已经设计好，只需要做适配和品牌化，能大幅减少定制设计量。成熟设计系统的好处不仅是省成本，还有质量保障——这些组件经过大量项目验证，在可用性、无障碍、响应式方面都有保证。",[50,235,237],{"id":236},"_2-组件化","2. 组件化",[11,239,240],{},"把通用元素（按钮、表单、卡片、弹窗）抽象成可复用组件，设计一次、到处用，避免每个页面都从头设计。组件化的另一个好处是一致性——所有页面用同一套组件，视觉风格天然统一，不会出现\"每个页面风格都不一样\"的散乱感。",[50,242,244],{"id":243},"_3-明确需求","3. 明确需求",[11,246,247],{},"前期把需求、风格、参考案例确认清楚，减少反复改稿。改稿是设计成本的最大变量，控制住它就控制住了总成本。给设计师参考案例是最有效的沟通方式——找到几个你喜欢的设计，告诉设计师喜欢它们的哪些方面，比用语言描述\"我想要什么感觉\"准确十倍。",[50,249,251],{"id":250},"_4-重点设计","4. 重点设计",[11,253,254],{},"不是所有页面都要重金设计。核心界面（首页、关键流程、转化页）要专业设计；次要界面（设置页、帮助页）可以基于组件库快速搭建。把预算集中在影响体验和转化的地方。这就像装修房子——客厅和主卧要花心思，储藏间用基础配置就行，把预算花在最能体现价值的地方。",[23,256,257],{"id":257},"别踩的坑",[27,259,260,265,271,277],{},[30,261,262,264],{},[15,263,169],{},"：体验差、转化低，省小钱失大钱。省设计是最常见的成本优化误区，因为它的代价（转化率、用户体验）是隐性的，不会立刻体现在账面上，但长期会以收入下降的形式回来。",[30,266,267,270],{},[15,268,269],{},"无设计直接开发","：开发凭感觉做界面，结果乱、不统一、返工多。没有设计稿的开发就像没有图纸的施工，每个开发者按自己的审美做，最后凑出来的产品一定是杂乱的。",[30,272,273,276],{},[15,274,275],{},"反复改不控制","：成本无序增长，最终比预算高出一截。改稿失控的本质是需求不清，把需求前置确认是控制改稿成本的关键。",[30,278,279,282],{},[15,280,281],{},"忽视体验","：只看视觉好不好看，不关心用户用得顺不顺。好看不好用的产品很多，但用户最终是为好用买单，不是为好看买单。",[23,284,285],{"id":285},"成本参考",[152,287,288,298],{},[155,289,290],{},[158,291,292,295],{},[161,293,294],{},"情况",[161,296,297],{},"设计占比",[171,299,300,308,316],{},[158,301,302,305],{},[176,303,304],{},"简单",[176,306,307],{},"10%",[158,309,310,313],{},[176,311,312],{},"中等",[176,314,315],{},"15%",[158,317,318,321],{},[176,319,320],{},"复杂\u002F品牌",[176,322,323],{},"20%+",[11,325,326],{},"注意这是参考比例，实际会因项目特点浮动。如果你的项目品牌要求高、交互复杂、多端覆盖，设计占比可能超过 20% 也合理；如果是工具型、内部系统，占比偏低也正常。",[23,328,329],{"id":329},"怎么做",[331,332,333,339,345,351,357],"ol",{},[30,334,335,338],{},[15,336,337],{},"给设计合理预算","：按项目规模预留 10%到20%。不要把设计预算压到 5% 以下，否则设计质量很难有保障。",[30,340,341,344],{},[15,342,343],{},"明确设计需求","：风格、参考、品牌资料提前给清楚。这是控制改稿成本最有效的手段。",[30,346,347,350],{},[15,348,349],{},"用设计系统优化","：减少不必要的定制设计。把定制预算留给真正需要差异化的地方。",[30,352,353,356],{},[15,354,355],{},"核心界面专业设计","：把预算花在影响体验和转化的地方。首页、注册流程、购买流程、核心功能页是重点。",[30,358,359,362],{},[15,360,361],{},"好设计值得投入","：它会以转化和口碑的形式回报你。好的设计不是成本，是投资。",[364,365,366],"blockquote",{},[11,367,368],{},"广州市汉诺雷斯（HNREIS）重视UI\u002FUX设计（专业设计师），平衡体验和成本。把你的项目需求告诉我们，我们给出方案。",{"title":370,"searchDepth":371,"depth":371,"links":372},"",2,[373,374,382,388,389,395,396,397],{"id":25,"depth":371,"text":25},{"id":48,"depth":371,"text":48,"children":375},[376,378,379,380,381],{"id":52,"depth":377,"text":53},3,{"id":59,"depth":377,"text":60},{"id":66,"depth":377,"text":67},{"id":87,"depth":377,"text":88},{"id":97,"depth":377,"text":98},{"id":104,"depth":371,"text":104,"children":383},[384,385,386,387],{"id":107,"depth":377,"text":108},{"id":114,"depth":377,"text":115},{"id":121,"depth":377,"text":122},{"id":142,"depth":377,"text":143},{"id":149,"depth":371,"text":150},{"id":223,"depth":371,"text":223,"children":390},[391,392,393,394],{"id":229,"depth":377,"text":230},{"id":236,"depth":377,"text":237},{"id":243,"depth":377,"text":244},{"id":250,"depth":377,"text":251},{"id":257,"depth":371,"text":257},{"id":285,"depth":371,"text":285},{"id":329,"depth":371,"text":329},"cost-process",null,"2025-05-28","UI\u002FUX设计是软件项目重要部分，费用占一定比例。本文讲清设计费用占比、影响因素和价值。",false,"md",[405,408,411],{"q":406,"a":407},"设计费用在项目里占多少？","UI\u002FUX设计通常占项目10%到20%（看复杂度）。设计是项目重要部分（界面\u002F交互\u002F体验），好设计提升用户体验和转化。设计费受页面数、复杂度、品牌要求、迭代次数影响。建议别省设计（影响体验）。",{"q":409,"a":410},"为什么设计要花钱？","设计决定用户体验和第一印象。好设计让产品好用、好看、专业，提升体验和转化；差设计让用户流失。设计是专业工作（设计师人力投入），要花钱。省设计省的是体验和转化。",{"q":412,"a":413},"设计费能省吗？","不建议省。设计影响用户体验和转化，省设计省的是这些。可以优化（用成熟设计系统\u002F组件，减少定制设计量），但核心界面\u002F体验要专业设计。建议给设计合理预算，好设计值得。",[415,416,417,418],"设计费用","UI设计费","设计成本","软件设计",{},true,"\u002Fblog\u002Fcost-process\u002Fsheji-fei-yinsu",{"title":5,"description":401},{"loc":421},"blog\u002Fcost-process\u002Fsheji-fei-yinsu",[426,211,427],"设计","报价","ximg9vfG_mPZn3l49QChwuR3dMC3FWgAu_b0OsuW7QE",[430,903,1389,2049],{"id":431,"title":432,"author":6,"body":433,"category":398,"cover":399,"date":877,"description":878,"draft":402,"extension":403,"faq":879,"featured":402,"image":399,"keywords":889,"meta":894,"navigation":420,"path":895,"seo":896,"sitemap":897,"stem":898,"tags":899,"updated":877,"__hash__":902},"blog\u002Fblog\u002Fcost-process\u002Fai-xiangmu-baojia-mingxi.md","AI项目报价为什么难统一",{"type":8,"value":434,"toc":860},[435,442,446,449,520,526,529,533,547,557,561,575,581,585,599,605,608,611,622,628,631,639,642,646,657,660,671,675,678,767,774,777,815,817,855],[11,436,437,438,441],{},"很多企业主拿着同一个 AI 需求问一圈，报价能从几万到几十万不等，差异大到让人怀疑有人在坑钱。",[15,439,440],{},"AI 项目报价难统一，不是有人黑心，而是 AI 这件事变量太多——同样的\"智能客服\"，做法不同成本天差地别。"," 这篇文章拆解 AI 报价背后的真实构成。",[23,443,445],{"id":444},"ai-报价为什么这么乱","AI 报价为什么这么乱",[11,447,448],{},"AI 项目和传统软件不一样，变量多：",[152,450,451,463],{},[155,452,453],{},[158,454,455,457,460],{},[161,456,163],{},[161,458,459],{},"选项",[161,461,462],{},"对价格影响",[171,464,465,476,487,498,509],{},[158,466,467,470,473],{},[176,468,469],{},"模型来源",[176,471,472],{},"调 API \u002F 开源微调 \u002F 从零训练",[176,474,475],{},"几万 vs 几十万 vs 百万级",[158,477,478,481,484],{},[176,479,480],{},"数据",[176,482,483],{},"现有数据 \u002F 要清洗 \u002F 要标注",[176,485,486],{},"大幅影响工时",[158,488,489,492,495],{},[176,490,491],{},"部署",[176,493,494],{},"云端 SaaS \u002F 私有化部署",[176,496,497],{},"私有化加 30%-100%",[158,499,500,503,506],{},[176,501,502],{},"业务深度",[176,504,505],{},"套壳问答 \u002F RAG 知识库 \u002F 多 Agent 协同",[176,507,508],{},"工时几倍差异",[158,510,511,514,517],{},[176,512,513],{},"调用量",[176,515,516],{},"低频 \u002F 高并发",[176,518,519],{},"影响 token 成本",[11,521,522,525],{},[15,523,524],{},"所以\"做个 AI 客服多少钱\"这个问题没法直接答","，必须先理清楚做哪种 AI。",[23,527,528],{"id":528},"三种主流做法的成本对比",[50,530,532],{"id":531},"_1-api-套壳最便宜","1. API 套壳（最便宜）",[27,534,535,538,541,544],{},[30,536,537],{},"用 OpenAI \u002F 文心 \u002F 通义 \u002F 智谱 等大厂 API。",[30,539,540],{},"开发主要是接口对接 + 业务封装 + 前端。",[30,542,543],{},"成本：几万到十几万。",[30,545,546],{},"适合：简单问答、文案生成、轻度智能化。",[11,548,549,552,553,556],{},[15,550,551],{},"优点","：快、便宜、能力强。",[15,554,555],{},"缺点","：依赖外部 API、数据出域、token 持续付费。",[50,558,560],{"id":559},"_2-rag-知识库中等","2. RAG 知识库（中等）",[27,562,563,566,569,572],{},[30,564,565],{},"API 大模型 + 自有知识库（向量检索）。",[30,567,568],{},"模型用 API，知识用自己数据。",[30,570,571],{},"成本：十几万到几十万。",[30,573,574],{},"适合：企业智能客服、文档问答、知识助手。",[11,576,577,580],{},[15,578,579],{},"目前企业落地 AI 的主流方案","——能力强、成本可控、数据可控。",[50,582,584],{"id":583},"_3-自训微调模型最贵","3. 自训\u002F微调模型（最贵）",[27,586,587,590,593,596],{},[30,588,589],{},"开源模型（Llama、Qwen）微调，或从零训练。",[30,591,592],{},"涉及数据采集清洗、标注、算力租用、调参。",[30,594,595],{},"成本：几十万到百万级。",[30,597,598],{},"适合：有海量专有数据、对延迟\u002F成本极度敏感、不能依赖外部 API。",[11,600,601,604],{},[15,602,603],{},"绝大多数企业不需要自训","——除非你有特殊场景和充足预算。",[23,606,607],{"id":607},"影响报价的关键因素",[50,609,610],{"id":610},"数据准备",[27,612,613,616,619],{},[30,614,615],{},"数据清洗（去重、纠错、脱敏）。",[30,617,618],{},"数据标注（人工标注、规则标注）。",[30,620,621],{},"向量库构建（embed、索引、调优）。",[11,623,624,627],{},[15,625,626],{},"数据是 AI 项目的隐形大头","，常常占总成本 20%-40%。",[50,629,630],{"id":630},"私有化部署",[27,632,633,636],{},[30,634,635],{},"云端调用：开发便宜，按 token 付费。",[30,637,638],{},"私有化：要把模型部署到自己的服务器，硬件和运维成本高。",[11,640,641],{},"私有化通常加 30%-100% 成本，但数据不出域。",[50,643,645],{"id":644},"ai-评测","AI 评测",[27,647,648,651,654],{},[30,649,650],{},"AI 输出不 deterministic，需要专门的评测集。",[30,652,653],{},"评测指标：准确率、相关性、安全、延迟。",[30,655,656],{},"评测工时容易被低估。",[50,658,659],{"id":659},"持续运营成本",[27,661,662,665,668],{},[30,663,664],{},"API token 费用（按月持续）。",[30,666,667],{},"模型迭代（数据更新、Prompt 调优）。",[30,669,670],{},"监控（异常输出、成本、延迟）。",[23,672,674],{"id":673},"成本参考一个典型-ai-项目","成本参考：一个典型 AI 项目",[11,676,677],{},"以企业知识库智能客服为例（API + RAG 方案）：",[152,679,680,693],{},[155,681,682],{},[158,683,684,687,690],{},[161,685,686],{},"模块",[161,688,689],{},"工作量",[161,691,692],{},"占比",[171,694,695,706,717,726,736,747,756],{},[158,696,697,700,703],{},[176,698,699],{},"需求与方案设计",[176,701,702],{},"1-2 周",[176,704,705],{},"10%-15%",[158,707,708,711,714],{},[176,709,710],{},"数据清洗与标注",[176,712,713],{},"2-4 周",[176,715,716],{},"20%-30%",[158,718,719,722,724],{},[176,720,721],{},"向量库与检索",[176,723,702],{},[176,725,705],{},[158,727,728,731,733],{},[176,729,730],{},"后端开发（接口、Agent）",[176,732,713],{},[176,734,735],{},"20%-25%",[158,737,738,741,744],{},[176,739,740],{},"前端开发",[176,742,743],{},"2-3 周",[176,745,746],{},"15%-20%",[158,748,749,752,754],{},[176,750,751],{},"测试与评测",[176,753,702],{},[176,755,705],{},[158,757,758,761,764],{},[176,759,760],{},"部署与运维",[176,762,763],{},"持续",[176,765,766],{},"5%-10%",[11,768,769,770,773],{},"具体价格看团队人天单价，区间通常十几万到几十万。",[15,771,772],{},"报价远低于这个的，大概率是套壳省了数据\u002F评测","。",[23,775,776],{"id":776},"常见误区",[27,778,779,785,791,797,803,809],{},[30,780,781,784],{},[15,782,783],{},"\"AI 现成的便宜\"","：调用 API 确实便宜，但要做好业务集成不便宜。",[30,786,787,790],{},[15,788,789],{},"\"自己训模型更专业\"","：除非必要，否则 API+RAG 完全够用。",[30,792,793,796],{},[15,794,795],{},"\"数据不用准备\"","：AI 项目数据是大头，省了数据质量一塌糊涂。",[30,798,799,802],{},[15,800,801],{},"\"上线就完事\"","：AI 需要持续迭代，token 成本持续。",[30,804,805,808],{},[15,806,807],{},"\"私有化简单\"","：私有化涉及硬件、运维、模型部署，成本翻倍。",[30,810,811,814],{},[15,812,813],{},"\"AI 输出天然准\"","：需要专门评测集，不评测的 AI 上线即翻车。",[23,816,329],{"id":329},[331,818,819,825,831,837,843,849],{},[30,820,821,824],{},[15,822,823],{},"先理清要什么 AI 能力","：问答、生成、检索、决策？不同能力做法差异大。",[30,826,827,830],{},[15,828,829],{},"决定模型方案","：API \u002F RAG \u002F 自训，根据预算和数据敏感度。",[30,832,833,836],{},[15,834,835],{},"盘点数据","：现有数据够不够、要不要清洗标注。",[30,838,839,842],{},[15,840,841],{},"要明细报价","：拆到数据、模型、开发、评测、部署。",[30,844,845,848],{},[15,846,847],{},"问清持续成本","：token、运维、迭代。",[30,850,851,854],{},[15,852,853],{},"看 AI 经验","：做过的 AI 项目、可演示 demo。",[364,856,857],{},[11,858,859],{},"广州市汉诺雷斯（HNREIS）做 AI 项目（智能客服、知识库、文档处理、Agent 工作流）坚持明细报价：先理需求、出方案、给模块工时明细。把你的 AI 需求告诉我们，我们给方案和报价。",{"title":370,"searchDepth":371,"depth":371,"links":861},[862,863,868,874,875,876],{"id":444,"depth":371,"text":445},{"id":528,"depth":371,"text":528,"children":864},[865,866,867],{"id":531,"depth":377,"text":532},{"id":559,"depth":377,"text":560},{"id":583,"depth":377,"text":584},{"id":607,"depth":371,"text":607,"children":869},[870,871,872,873],{"id":610,"depth":377,"text":610},{"id":630,"depth":377,"text":630},{"id":644,"depth":377,"text":645},{"id":659,"depth":377,"text":659},{"id":673,"depth":371,"text":674},{"id":776,"depth":371,"text":776},{"id":329,"depth":371,"text":329},"2024-05-17","AI项目的报价常常让企业主困惑——同样一个需求，A 报 10 万，B 报 50 万，差异巨大。本文拆解 AI 项目报价背后的真实构成，讲清需求复杂度、数据、模型选型如何决定价格，让你看懂 AI 外包报价。",[880,883,886],{"q":881,"a":882},"AI 项目报价为什么差异这么大？","AI 项目差异大，主要因为变量多：用现成 API（如 GPT、文心）调用，还是从零训练模型；数据要不要清洗、标注；要不要私有部署；调用量多大。同样一个\"智能客服\"，用 API 套壳可能几万块，做完整知识库+RAG+私有化可能几十万。报价差异反映的是做法和工作量的差异。",{"q":884,"a":885},"调用现成 AI API 和自己训模型，价格差多少？","差很多。调用大厂 API（OpenAI、文心、通义、智谱）是按 token 计费，开发主要是接口对接+业务封装，几万到十几万就能落地。自己训模型涉及数据采集清洗、算力租用、调参、评估，起步几十万到上百万。绝大多数企业应用用 API+RAG 就够，不必从头训模型。",{"q":887,"a":888},"AI 项目报价应该包含哪些明细？","至少包含：需求拆解（要做什么 AI 能力）、数据准备（清洗\u002F标注\u002F向量库）、模型方案（API 还是自训）、后端开发、前端开发、测试（含 AI 评测集）、私有化部署（如需）、运维、token 成本预估。只有总价没明细的报价，后期加项空间巨大。",[890,891,892,893],"AI项目报价","AI外包","AI开发成本","模型选型",{},"\u002Fblog\u002Fcost-process\u002Fai-xiangmu-baojia-mingxi",{"title":432,"description":878},{"loc":895},"blog\u002Fcost-process\u002Fai-xiangmu-baojia-mingxi",[900,427,901],"AI","透明","acIdRbDaJcEhnsXD4OIPN64UoHX0_rvqSA2Bx2ypIpc",{"id":904,"title":905,"author":6,"body":906,"category":398,"cover":399,"date":1363,"description":1364,"draft":402,"extension":403,"faq":1365,"featured":402,"image":399,"keywords":1375,"meta":1380,"navigation":420,"path":1381,"seo":1382,"sitemap":1383,"stem":1384,"tags":1385,"updated":1363,"__hash__":1388},"blog\u002Fblog\u002Fcost-process\u002Fbaojia-buhou-xiugai.md","报价包不包含后续修改",{"type":8,"value":907,"toc":1345},[908,914,917,920,1022,1027,1031,1034,1038,1052,1056,1073,1077,1088,1094,1098,1101,1109,1115,1118,1122,1133,1137,1151,1155,1166,1171,1175,1178,1189,1195,1199,1253,1260,1262,1300,1302,1340],[11,909,910,911],{},"\"上线了，但我现在想改个按钮位置、加个字段——这是不是改一点点的事，免费的吧？\"这种话在外包项目里天天出现。",[15,912,913],{},"报价里的\"开发完成\"通常只指合同约定功能，不包含后续修改——把范围和边界讲清楚，才能避免上线后扯皮加价。",[23,915,916],{"id":916},"报价到底包什么",[11,918,919],{},"软件外包报价通常包含这几部分：",[152,921,922,935],{},[155,923,924],{},[158,925,926,929,932],{},[161,927,928],{},"范围",[161,930,931],{},"包不包",[161,933,934],{},"说明",[171,936,937,948,958,968,979,990,1001,1012],{},[158,938,939,942,945],{},[176,940,941],{},"合同约定的功能开发",[176,943,944],{},"包",[176,946,947],{},"这是报价主体",[158,949,950,953,955],{},[176,951,952],{},"合同约定的设计稿实现",[176,954,944],{},[176,956,957],{},"按确认的 UI 稿做",[158,959,960,963,965],{},[176,961,962],{},"Bug 修复（质保期内）",[176,964,944],{},[176,966,967],{},"通常 1-3 个月免费",[158,969,970,973,976],{},[176,971,972],{},"文档与部署说明",[176,974,975],{},"看合同",[176,977,978],{},"规范公司包",[158,980,981,984,987],{},[176,982,983],{},"需求变更、加功能",[176,985,986],{},"不包",[176,988,989],{},"另签变更单",[158,991,992,995,998],{},[176,993,994],{},"设计稿调整（开发中）",[176,996,997],{},"看阶段",[176,999,1000],{},"早期改包，后期改另算",[158,1002,1003,1006,1009],{},[176,1004,1005],{},"上线后改文案\u002F图片",[176,1007,1008],{},"边界模糊",[176,1010,1011],{},"看合同约定",[158,1013,1014,1017,1019],{},[176,1015,1016],{},"新增页面\u002F模块",[176,1018,986],{},[176,1020,1021],{},"另计费",[11,1023,1024,773],{},[15,1025,1026],{},"只有合同写明的范围内才包，其他都是变更",[23,1028,1030],{"id":1029},"改一点点的边界","\"改一点点\"的边界",[11,1032,1033],{},"最容易扯皮的就是\"改一点点\"：",[50,1035,1037],{"id":1036},"算修改免费或低成本","算修改（免费或低成本）",[27,1039,1040,1043,1046,1049],{},[30,1041,1042],{},"文字错别字。",[30,1044,1045],{},"图片替换。",[30,1047,1048],{},"颜色微调。",[30,1050,1051],{},"Bug 修复（质保期内）。",[50,1053,1055],{"id":1054},"算需求变更另计费","算需求变更（另计费）",[27,1057,1058,1061,1064,1067,1070],{},[30,1059,1060],{},"加新功能、新页面。",[30,1062,1063],{},"改业务流程。",[30,1065,1066],{},"字段类型变化（如文本改下拉）。",[30,1068,1069],{},"改交互逻辑。",[30,1071,1072],{},"第三方对接新增。",[50,1074,1076],{"id":1075},"灰色地带看合同约定","灰色地带（看合同约定）",[27,1078,1079,1082,1085],{},[30,1080,1081],{},"按钮位置移动（小改？布局重排？）。",[30,1083,1084],{},"字段加几个（加 1 个？加 10 个？）。",[30,1086,1087],{},"列表加排序（小功能？还是整套筛选？）。",[11,1089,1090,1093],{},[15,1091,1092],{},"灰色地带要靠合同写清楚","，不然扯皮没完。",[23,1095,1097],{"id":1096},"为什么改一点点也要钱","为什么\"改一点点\"也要钱",[11,1099,1100],{},"很多企业主觉得\"加个字段多简单\"，但实际成本：",[27,1102,1103,1106],{},[30,1104,1105],{},"加字段：数据库改表 → 后端改接口 → 前端改表单 → 改校验 → 测试。",[30,1107,1108],{},"一个\"加字段\"涉及 4-5 处改动和测试，不是 5 分钟的事。",[11,1110,1111,1114],{},[15,1112,1113],{},"软件开发是连锁改动","，一处改处处改。所以即使看起来\"小\"，也涉及工时。",[23,1116,1117],{"id":1117},"怎么避免扯皮",[50,1119,1121],{"id":1120},"_1-需求文档写到字段级","1. 需求文档写到字段级",[27,1123,1124,1127,1130],{},[30,1125,1126],{},"每个页面有什么字段、什么交互。",[30,1128,1129],{},"字段类型、校验规则、来源。",[30,1131,1132],{},"越细越好，\"做成 XX 那样\"不算需求。",[50,1134,1136],{"id":1135},"_2-合同写清范围与变更","2. 合同写清范围与变更",[27,1138,1139,1142,1145,1148],{},[30,1140,1141],{},"开发范围（功能清单）。",[30,1143,1144],{},"质保期（修 bug 免费时长）。",[30,1146,1147],{},"变更流程（怎么提变更、怎么计费）。",[30,1149,1150],{},"设计稿确认机制（确认后改要另算）。",[50,1152,1154],{"id":1153},"_3-确认环节留痕","3. 确认环节留痕",[27,1156,1157,1160,1163],{},[30,1158,1159],{},"需求文档确认签字。",[30,1161,1162],{},"设计稿确认签字。",[30,1164,1165],{},"演示验收留记录。",[11,1167,1168,773],{},[15,1169,1170],{},"口头确认不算，必须文档留痕",[50,1172,1174],{"id":1173},"_4-变更单制度","4. 变更单制度",[11,1176,1177],{},"任何超出范围的改动走变更单：",[27,1179,1180,1183,1186],{},[30,1181,1182],{},"写明改什么。",[30,1184,1185],{},"估算工时和费用。",[30,1187,1188],{},"双方确认才执行。",[11,1190,1191,1194],{},[15,1192,1193],{},"变更单制度保护双方","——客户不会被乱加价，开发不会被无止境改。",[23,1196,1198],{"id":1197},"成本参考变更怎么计费","成本参考：变更怎么计费",[152,1200,1201,1211],{},[155,1202,1203],{},[158,1204,1205,1208],{},[161,1206,1207],{},"变更类型",[161,1209,1210],{},"计费方式",[171,1212,1213,1221,1229,1237,1245],{},[158,1214,1215,1218],{},[176,1216,1217],{},"小改动（文字、图片）",[176,1219,1220],{},"看合同，部分公司宽限",[158,1222,1223,1226],{},[176,1224,1225],{},"字段新增\u002F修改",[176,1227,1228],{},"按工时（约 0.5-2 人天）",[158,1230,1231,1234],{},[176,1232,1233],{},"新增页面",[176,1235,1236],{},"按页面工时（约 2-5 人天）",[158,1238,1239,1242],{},[176,1240,1241],{},"新增功能模块",[176,1243,1244],{},"单独签子合同",[158,1246,1247,1250],{},[176,1248,1249],{},"业务流程改动",[176,1251,1252],{},"按工时，可能涉及多端",[11,1254,1255,1256,1259],{},"人天单价参考 800-1500 元。",[15,1257,1258],{},"变更越早提，成本越低","——开发后期改成本是初期的 5-10 倍。",[23,1261,776],{"id":776},[27,1263,1264,1270,1276,1282,1288,1294],{},[30,1265,1266,1269],{},[15,1267,1268],{},"\"开发完会一直帮我改\"","：质保期外的修改要钱。",[30,1271,1272,1275],{},[15,1273,1274],{},"\"加个字段不收费吧\"","：涉及多端联动，是工时。",[30,1277,1278,1281],{},[15,1279,1280],{},"\"口头确认就行\"","：口头不算，扯皮没证据。",[30,1283,1284,1287],{},[15,1285,1286],{},"\"上线后再想需求\"","：上线后改成本高，需求前期定。",[30,1289,1290,1293],{},[15,1291,1292],{},"\"改一点点都不给改\"","：合同约定好的范围内，开发有义务做。",[30,1295,1296,1299],{},[15,1297,1298],{},"\"变更单麻烦\"","：变更单保护双方，必须走。",[23,1301,329],{"id":329},[331,1303,1304,1310,1316,1322,1328,1334],{},[30,1305,1306,1309],{},[15,1307,1308],{},"需求文档写到字段级","：每个功能描述清楚。",[30,1311,1312,1315],{},[15,1313,1314],{},"合同写范围和变更流程","：避免扯皮。",[30,1317,1318,1321],{},[15,1319,1320],{},"设计稿\u002F需求确认留痕","：签字或邮件确认。",[30,1323,1324,1327],{},[15,1325,1326],{},"建立变更单制度","：超范围改走流程。",[30,1329,1330,1333],{},[15,1331,1332],{},"变更尽早提","：越早成本越低。",[30,1335,1336,1339],{},[15,1337,1338],{},"找规范服务商","：愿意走文档流程的，靠谱。",[364,1341,1342],{},[11,1343,1344],{},"广州市汉诺雷斯（HNREIS）在合同里写清开发范围、质保期、变更流程，需求文档到字段级，变更走变更单透明计费。把你的项目需求告诉我们，我们出明细方案和报价。",{"title":370,"searchDepth":371,"depth":371,"links":1346},[1347,1348,1353,1354,1360,1361,1362],{"id":916,"depth":371,"text":916},{"id":1029,"depth":371,"text":1030,"children":1349},[1350,1351,1352],{"id":1036,"depth":377,"text":1037},{"id":1054,"depth":377,"text":1055},{"id":1075,"depth":377,"text":1076},{"id":1096,"depth":371,"text":1097},{"id":1117,"depth":371,"text":1117,"children":1355},[1356,1357,1358,1359],{"id":1120,"depth":377,"text":1121},{"id":1135,"depth":377,"text":1136},{"id":1153,"depth":377,"text":1154},{"id":1173,"depth":377,"text":1174},{"id":1197,"depth":371,"text":1198},{"id":776,"depth":371,"text":776},{"id":329,"depth":371,"text":329},"2024-05-29","软件外包报价单上写的\"开发完成\"，往往不包含上线后的修改和调整。本文讲清报价范围、修改边界、版本管理怎么定，避免上线后因\"改一点点\"扯皮加价。",[1366,1369,1372],{"q":1367,"a":1368},"报价里说的\"开发完成\"包含后续修改吗？","看合同怎么写。规范的报价会区分\"开发范围\"和\"质保期\"——开发范围是合同约定的功能，质保期是上线后修 bug 的免费期（通常 1-3 个月）。新增功能、改需求、调整设计都不在范围内，要另计费。签合同前必须把范围写清楚。",{"q":1370,"a":1371},"上线后改一个小功能要不要钱？","看是什么改动。修 bug 在质保期内免费；调整文字、改图标这种小改动看合同约定，有些公司宽限几小时不收费；但新增功能、改业务流程、加页面，都是需求变更要另计费。\"只是改一点点\"往往是扯皮起点，靠合同约定边界。",{"q":1373,"a":1374},"怎么避免上线后扯皮改需求？","三件事：一是需求文档足够细，每个功能描述到字段和交互；二是合同写清楚范围、修改边界、变更流程；三是确认环节要在文档上签字，不要口头确认。需求文档越细，后期扯皮越少。",[1376,1377,1378,1379],"报价包含修改","软件外包修改","需求变更","报价范围",{},"\u002Fblog\u002Fcost-process\u002Fbaojia-buhou-xiugai",{"title":905,"description":1364},{"loc":1381},"blog\u002Fcost-process\u002Fbaojia-buhou-xiugai",[427,1386,1387],"修改","避坑","YLc1PxAo2HP1n5HdiqnTdqnVtPdj6iJeOZDu0a53MpY",{"id":1390,"title":1391,"author":6,"body":1392,"category":398,"cover":399,"date":2024,"description":2025,"draft":402,"extension":403,"faq":2026,"featured":402,"image":399,"keywords":2036,"meta":2041,"navigation":420,"path":2042,"seo":2043,"sitemap":2044,"stem":2045,"tags":2046,"updated":2024,"__hash__":2048},"blog\u002Fblog\u002Fcost-process\u002Fbaojia-chaju-zenme-pan.md","不同公司报价差很多怎么判断",{"type":8,"value":1393,"toc":2001},[1394,1401,1404,1407,1511,1516,1520,1524,1527,1667,1672,1676,1695,1701,1705,1725,1731,1735,1755,1761,1764,1768,1771,1775,1789,1793,1796,1810,1814,1828,1833,1836,1840,1851,1856,1860,1871,1876,1880,1891,1896,1900,1911,1916,1918,1956,1958,1996],[11,1395,1396,1397,1400],{},"\"做个小程序，A 报 3 万，B 报 8 万，C 报 15 万——到底谁合理？\"这是企业主最常遇到的困境。",[15,1398,1399],{},"报价差异大不一定是有人黑心，而是大家\"做多少事、做到什么程度\"完全不同——拆开明细看，才知道谁合理。"," 这篇文章讲清怎么判断报价差异。",[23,1402,1403],{"id":1403},"报价为什么会差这么多",[11,1405,1406],{},"同一个需求报价差异大，主要因为：",[152,1408,1409,1422],{},[155,1410,1411],{},[158,1412,1413,1416,1419],{},[161,1414,1415],{},"因素",[161,1417,1418],{},"低价可能",[161,1420,1421],{},"高价可能",[171,1423,1424,1435,1446,1456,1467,1478,1489,1500],{},[158,1425,1426,1429,1432],{},[176,1427,1428],{},"工时",[176,1430,1431],{},"压缩（少做\u002F省环节）",[176,1433,1434],{},"充分（细致）",[158,1436,1437,1440,1443],{},[176,1438,1439],{},"团队",[176,1441,1442],{},"初级开发",[176,1444,1445],{},"资深团队",[158,1447,1448,1450,1453],{},[176,1449,426],{},[176,1451,1452],{},"套模板",[176,1454,1455],{},"原创设计",[158,1457,1458,1461,1464],{},[176,1459,1460],{},"测试",[176,1462,1463],{},"不测或简测",[176,1465,1466],{},"完整测试",[158,1468,1469,1472,1475],{},[176,1470,1471],{},"售后",[176,1473,1474],{},"上线失联",[176,1476,1477],{},"质保期+运维",[158,1479,1480,1483,1486],{},[176,1481,1482],{},"源码",[176,1484,1485],{},"不交或加钱",[176,1487,1488],{},"交付",[158,1490,1491,1494,1497],{},[176,1492,1493],{},"文档",[176,1495,1496],{},"无",[176,1498,1499],{},"完整文档",[158,1501,1502,1505,1508],{},[176,1503,1504],{},"技术",[176,1506,1507],{},"老旧\u002F杂牌",[176,1509,1510],{},"现代+规范",[11,1512,1513,773],{},[15,1514,1515],{},"看起来\"同一个需求\"，实际包含的工作量差几倍很正常",[23,1517,1519],{"id":1518},"_4-个维度判断报价合理性","4 个维度判断报价合理性",[50,1521,1523],{"id":1522},"维度-1报价包含什么","维度 1：报价包含什么",[11,1525,1526],{},"把每家报价的\"包含项\"列出来对比：",[152,1528,1529,1545],{},[155,1530,1531],{},[158,1532,1533,1536,1539,1542],{},[161,1534,1535],{},"项目",[161,1537,1538],{},"A（3万）",[161,1540,1541],{},"B（8万）",[161,1543,1544],{},"C（15万）",[171,1546,1547,1560,1573,1585,1597,1609,1620,1631,1643,1656],{},[158,1548,1549,1552,1554,1557],{},[176,1550,1551],{},"需求文档",[176,1553,1496],{},[176,1555,1556],{},"简要",[176,1558,1559],{},"详细",[158,1561,1562,1565,1567,1570],{},[176,1563,1564],{},"原型",[176,1566,1496],{},[176,1568,1569],{},"简单线框",[176,1571,1572],{},"完整原型",[158,1574,1575,1578,1580,1583],{},[176,1576,1577],{},"UI 设计",[176,1579,1452],{},[176,1581,1582],{},"半原创",[176,1584,1455],{},[158,1586,1587,1590,1593,1595],{},[176,1588,1589],{},"前后端开发",[176,1591,1592],{},"含",[176,1594,1592],{},[176,1596,1592],{},[158,1598,1599,1601,1604,1607],{},[176,1600,1460],{},[176,1602,1603],{},"不测",[176,1605,1606],{},"简测",[176,1608,1466],{},[158,1610,1611,1614,1616,1618],{},[176,1612,1613],{},"上线部署",[176,1615,1592],{},[176,1617,1592],{},[176,1619,1592],{},[158,1621,1622,1624,1626,1628],{},[176,1623,1493],{},[176,1625,1496],{},[176,1627,1556],{},[176,1629,1630],{},"完整",[158,1632,1633,1635,1638,1641],{},[176,1634,1482],{},[176,1636,1637],{},"不交",[176,1639,1640],{},"加钱交",[176,1642,1488],{},[158,1644,1645,1648,1650,1653],{},[176,1646,1647],{},"质保期",[176,1649,1496],{},[176,1651,1652],{},"1 个月",[176,1654,1655],{},"3 个月",[158,1657,1658,1661,1663,1665],{},[176,1659,1660],{},"培训",[176,1662,1496],{},[176,1664,1496],{},[176,1666,1592],{},[11,1668,1669,773],{},[15,1670,1671],{},"包含项差很多，价格差异就有依据",[50,1673,1675],{"id":1674},"维度-2团队配置","维度 2：团队配置",[27,1677,1678,1683,1689],{},[30,1679,1680,1682],{},[15,1681,1442],{},"：单价低（500-800 元\u002F人天），但能力弱、质量差。",[30,1684,1685,1688],{},[15,1686,1687],{},"中级开发","：单价中（800-1200 元\u002F人天），主力。",[30,1690,1691,1694],{},[15,1692,1693],{},"资深开发","：单价高（1200-2000 元\u002F人天），技术好。",[11,1696,1697,1698,773],{},"同样工时，团队级别不同，单价差异 2-3 倍。",[15,1699,1700],{},"低价报价通常用初级开发或外包再外包",[50,1702,1704],{"id":1703},"维度-3技术方案","维度 3：技术方案",[27,1706,1707,1713,1719],{},[30,1708,1709,1712],{},[15,1710,1711],{},"成熟方案","：Vue\u002FReact\u002FNode，开发者多，成本可控。",[30,1714,1715,1718],{},[15,1716,1717],{},"冷门技术","：特定框架、老旧语言，人才少，单价高。",[30,1720,1721,1724],{},[15,1722,1723],{},"过度设计","：简单的需求用复杂架构（微服务、K8s），成本虚高。",[11,1726,1727,1730],{},[15,1728,1729],{},"判断技术方案是否匹配需求复杂度","——简单需求过度设计是浪费，复杂需求用简陋方案是坑。",[50,1732,1734],{"id":1733},"维度-4工时合理性","维度 4：工时合理性",[27,1736,1737,1743,1749],{},[30,1738,1739,1742],{},[15,1740,1741],{},"工时太低","：低于合理范围，省环节或赶工。",[30,1744,1745,1748],{},[15,1746,1747],{},"工时合理","：匹配功能复杂度。",[30,1750,1751,1754],{},[15,1752,1753],{},"工时太高","：可能虚报或杀熟。",[11,1756,1757,1758,773],{},"参考：一个标准登录注册（含找回密码）约 2-3 人天；一个内容列表（增删改查）约 3-5 人天；一个商品详情页约 3-5 人天。",[15,1759,1760],{},"报价工时远低于这个，警惕",[23,1762,1763],{"id":1763},"怎么对比多家报价",[50,1765,1767],{"id":1766},"_1-要求统一格式","1. 要求统一格式",[11,1769,1770],{},"让每家用同样的明细格式报价（模块工时、单价、包含项），便于对比。",[50,1772,1774],{"id":1773},"_2-关注总工时和单价","2. 关注总工时和单价",[27,1776,1777,1780,1783,1786],{},[30,1778,1779],{},"总工时 = 所有模块工时之和。",[30,1781,1782],{},"单价 = 总价 \u002F 总工时。",[30,1784,1785],{},"单价低于 600 元\u002F人天的，警惕（低于合理成本）。",[30,1787,1788],{},"单价高于 2000 元\u002F人天的，问清楚为什么。",[50,1790,1792],{"id":1791},"_3-看省了什么","3. 看\"省了什么\"",[11,1794,1795],{},"低价报价一定省了什么——",[27,1797,1798,1801,1804,1807],{},[30,1799,1800],{},"省需求文档？后期扯皮。",[30,1802,1803],{},"省测试？上线一堆 bug。",[30,1805,1806],{},"省售后？出事没人管。",[30,1808,1809],{},"省源码？被绑架。",[50,1811,1813],{"id":1812},"_4-看合同条款","4. 看合同条款",[27,1815,1816,1819,1822,1825],{},[30,1817,1818],{},"敢写源码归属？",[30,1820,1821],{},"敢写违约责任？",[30,1823,1824],{},"敢写分期付款？",[30,1826,1827],{},"敢写验收标准？",[11,1829,1830,773],{},[15,1831,1832],{},"条款含糊的，再便宜也别签",[23,1834,1835],{"id":1835},"报价差异的几种情况",[50,1837,1839],{"id":1838},"情况-a低价正常","情况 A：低价正常",[27,1841,1842,1845,1848],{},[30,1843,1844],{},"模板建站。",[30,1846,1847],{},"SaaS 套餐。",[30,1849,1850],{},"简单重复工作。",[11,1852,1853,773],{},[15,1854,1855],{},"这些低价合理，因为是\"批量\u002F标准化\"",[50,1857,1859],{"id":1858},"情况-b低价不正常","情况 B：低价不正常",[27,1861,1862,1865,1868],{},[30,1863,1864],{},"定制开发报模板价。",[30,1866,1867],{},"远低于市场平均。",[30,1869,1870],{},"拒绝出明细。",[11,1872,1873,773],{},[15,1874,1875],{},"警惕，大概率是坑",[50,1877,1879],{"id":1878},"情况-c高价正常","情况 C：高价正常",[27,1881,1882,1885,1888],{},[30,1883,1884],{},"包含完整服务。",[30,1886,1887],{},"资深团队。",[30,1889,1890],{},"复杂需求。",[11,1892,1893,773],{},[15,1894,1895],{},"这种高价有依据",[50,1897,1899],{"id":1898},"情况-d高价不正常","情况 D：高价不正常",[27,1901,1902,1905,1908],{},[30,1903,1904],{},"工时虚高。",[30,1906,1907],{},"单价虚高。",[30,1909,1910],{},"杀熟。",[11,1912,1913,773],{},[15,1914,1915],{},"这种高价也是坑",[23,1917,776],{"id":776},[27,1919,1920,1926,1932,1938,1944,1950],{},[30,1921,1922,1925],{},[15,1923,1924],{},"\"选最便宜的\"","：低价往往更贵（加项\u002F绑架\u002F重做）。",[30,1927,1928,1931],{},[15,1929,1930],{},"\"选最贵的\"","：高价不一定靠谱，可能是杀熟。",[30,1933,1934,1937],{},[15,1935,1936],{},"\"只看总价\"","：必须拆明细才能判断。",[30,1939,1940,1943],{},[15,1941,1942],{},"\"报价快就是专业\"","：不出需求文档就报价，多半是套模板或猜。",[30,1945,1946,1949],{},[15,1947,1948],{},"\"承诺多就是好\"","：敢不敢写进合同比口头承诺重要。",[30,1951,1952,1955],{},[15,1953,1954],{},"\"案例多就是大公司\"","：编造的案例经不起验证。",[23,1957,329],{"id":329},[331,1959,1960,1966,1972,1978,1984,1990],{},[30,1961,1962,1965],{},[15,1963,1964],{},"先理清需求","：把功能、目标、预期讲清楚。",[30,1967,1968,1971],{},[15,1969,1970],{},"要求统一格式报价","：便于对比。",[30,1973,1974,1977],{},[15,1975,1976],{},"拆到模块工时和单价","：不只看总价。",[30,1979,1980,1983],{},[15,1981,1982],{},"对比包含项","：看省了什么。",[30,1985,1986,1989],{},[15,1987,1988],{},"看合同条款","：源码、违约、验收。",[30,1991,1992,1995],{},[15,1993,1994],{},"验证案例","：要真实可访问的。",[364,1997,1998],{},[11,1999,2000],{},"广州市汉诺雷斯（HNREIS）坚持透明明细报价，拆到模块工时、单价、包含项，写规范合同。把你的需求告诉我们，我们出明细报价——你可以拿去对比，看清谁合理。",{"title":370,"searchDepth":371,"depth":371,"links":2002},[2003,2004,2010,2016,2022,2023],{"id":1403,"depth":371,"text":1403},{"id":1518,"depth":371,"text":1519,"children":2005},[2006,2007,2008,2009],{"id":1522,"depth":377,"text":1523},{"id":1674,"depth":377,"text":1675},{"id":1703,"depth":377,"text":1704},{"id":1733,"depth":377,"text":1734},{"id":1763,"depth":371,"text":1763,"children":2011},[2012,2013,2014,2015],{"id":1766,"depth":377,"text":1767},{"id":1773,"depth":377,"text":1774},{"id":1791,"depth":377,"text":1792},{"id":1812,"depth":377,"text":1813},{"id":1835,"depth":371,"text":1835,"children":2017},[2018,2019,2020,2021],{"id":1838,"depth":377,"text":1839},{"id":1858,"depth":377,"text":1859},{"id":1878,"depth":377,"text":1879},{"id":1898,"depth":377,"text":1899},{"id":776,"depth":371,"text":776},{"id":329,"depth":371,"text":329},"2024-06-08","同一个软件需求，A 公司报 5 万，B 公司报 15 万，差好几倍。本文从报价明细、包含范围、团队配置、技术方案 4 个维度讲清怎么判断报价合理性，识破低价陷阱、避开虚高报价。",[2027,2030,2033],{"q":2028,"a":2029},"同一个需求报价差好几倍，怎么判断谁合理？","不能只看总价，要拆明细。看四点：报价包含什么（设计\u002F测试\u002F售后\u002F源码）、团队配置（初级还是资深）、技术方案（成熟还是冷门）、工时合理性（工时是不是被人为压低）。同样的需求，包含完整服务和省环节的报价差几倍很正常，关键是拆开看钱花在哪。",{"q":2031,"a":2032},"低价报价是不是一定不靠谱？","不一定，但远低于市场平均的要警惕。判断方法：要看明细——如果只给总价不拆工时，无法判断；要看省了什么——省了设计\u002F测试\u002F售后\u002F源码的便宜有原因；要看合同——敢不敢写源码、违约、验收。低得合理的有（标准化产品、模板），低得不合理的（定制开发远低市场）基本是坑。",{"q":2034,"a":2035},"高价就一定靠谱吗？","不一定。有的高价是包含完整服务（设计、测试、资深团队、售后），值这个钱；有的高价是品牌溢价或杀熟，不值。看高价报价要看明细——如果工时和单价合理，包含的服务完整，那高价有依据；如果只有总价没明细，或工时虚高，那高价也是坑。",[2037,2038,2039,2040],"报价差异","软件外包报价","怎么判断报价","低价陷阱",{},"\u002Fblog\u002Fcost-process\u002Fbaojia-chaju-zenme-pan",{"title":1391,"description":2025},{"loc":2042},"blog\u002Fcost-process\u002Fbaojia-chaju-zenme-pan",[427,2047,901],"决策","mB7BRictfurYpDWbxNpo5900YhfhMP0rUGPEp8NVo2U",{"id":2050,"title":2051,"author":6,"body":2052,"category":398,"cover":399,"date":2574,"description":2575,"draft":402,"extension":403,"faq":2576,"featured":402,"image":399,"keywords":2586,"meta":2591,"navigation":420,"path":2592,"seo":2593,"sitemap":2594,"stem":2595,"tags":2596,"updated":2574,"__hash__":2598},"blog\u002Fblog\u002Fcost-process\u002Fbaojia-tanpan.md","软件外包报价怎么谈判",{"type":8,"value":2053,"toc":2550},[2054,2061,2065,2068,2072,2086,2092,2096,2108,2112,2123,2128,2131,2135,2165,2171,2175,2186,2190,2204,2208,2211,2228,2233,2237,2248,2251,2255,2258,2269,2274,2278,2289,2293,2304,2309,2312,2315,2369,2374,2377,2380,2418,2423,2427,2465,2467,2504,2506,2545],[11,2055,2056,2057,2060],{},"拿到报价单，第一反应往往是\"能不能便宜点\"。",[15,2058,2059],{},"软件外包报价当然可以谈，但要谈对地方——盲目砍价只会让开发方从质量和服务里找回来，最后吃亏的还是你。"," 这篇文章讲清怎么谈判才合理。",[23,2062,2064],{"id":2063},"谈判前先拆报价","谈判前：先拆报价",[11,2066,2067],{},"谈判前必须做的事：",[50,2069,2071],{"id":2070},"_1-要求明细报价","1. 要求明细报价",[27,2073,2074,2077,2080,2083],{},[30,2075,2076],{},"模块清单。",[30,2078,2079],{},"每模块工时（人天）。",[30,2081,2082],{},"人天单价。",[30,2084,2085],{},"设计费、测试费、管理费、售后。",[11,2087,2088,2091],{},[15,2089,2090],{},"只有总价没法谈","——你不知道哪部分虚高。",[50,2093,2095],{"id":2094},"_2-算出总工时和单价","2. 算出总工时和单价",[27,2097,2098,2100,2102,2105],{},[30,2099,1779],{},[30,2101,1782],{},[30,2103,2104],{},"单价低于 600 元\u002F人天 → 不正常（可能省环节）。",[30,2106,2107],{},"单价高于 2000 元\u002F人天 → 问清为什么。",[50,2109,2111],{"id":2110},"_3-识别虚高部分","3. 识别虚高部分",[27,2113,2114,2117,2120],{},[30,2115,2116],{},"工时虚报（一个登录说 10 人天）。",[30,2118,2119],{},"单价虚高（中级开发报资深价）。",[30,2121,2122],{},"重复收费（设计费算了两次）。",[11,2124,2125,773],{},[15,2126,2127],{},"虚高部分才是谈判空间，合理部分硬砍只会被反噬",[23,2129,2130],{"id":2130},"可以谈的几个点",[50,2132,2134],{"id":2133},"_1-付款节点","1. 付款节点",[152,2136,2137,2147],{},[155,2138,2139],{},[158,2140,2141,2144],{},[161,2142,2143],{},"原方案",[161,2145,2146],{},"可谈方案",[171,2148,2149,2157],{},[158,2150,2151,2154],{},[176,2152,2153],{},"50% 预付 + 50% 验收",[176,2155,2156],{},"30% 预付 + 30% 中期 + 40% 验收",[158,2158,2159,2162],{},[176,2160,2161],{},"验收付清",[176,2163,2164],{},"留 10% 质保金 3 个月",[11,2166,2167,2170],{},[15,2168,2169],{},"拉长分期、留质保金，降低风险","——这是合理的谈判点。",[50,2172,2174],{"id":2173},"_2-工期","2. 工期",[27,2176,2177,2180,2183],{},[30,2178,2179],{},"加急费通常上浮 20%-50%。",[30,2181,2182],{},"不急的话可以谈延长工期，换价格让步。",[30,2184,2185],{},"但工期不能无限延长，否则拖延更亏。",[50,2187,2189],{"id":2188},"_3-范围调整","3. 范围调整",[27,2191,2192,2195,2198],{},[30,2193,2194],{},"砍边缘功能，先做核心 MVP。",[30,2196,2197],{},"把\"锦上添花\"放到二期。",[30,2199,2200,2203],{},[15,2201,2202],{},"核心功能不能砍","，否则失去项目价值。",[50,2205,2207],{"id":2206},"_4-增值服务","4. 增值服务",[11,2209,2210],{},"谈判时可以争取的\"白送\"：",[27,2212,2213,2216,2219,2222,2225],{},[30,2214,2215],{},"完整文档（部署、API、用户手册）。",[30,2217,2218],{},"培训（运维培训、用户培训）。",[30,2220,2221],{},"延长质保期（1 个月 → 3 个月）。",[30,2223,2224],{},"一段时间免费运维（3-6 个月）。",[30,2226,2227],{},"备份和监控方案。",[11,2229,2230,773],{},[15,2231,2232],{},"这些是开发方能给但客户容易忽略的",[50,2234,2236],{"id":2235},"_5-单价让步","5. 单价让步",[27,2238,2239,2242,2245],{},[30,2240,2241],{},"多家对比，单价高的可以让。",[30,2243,2244],{},"但让步空间有限（5%-15%），不能再低。",[30,2246,2247],{},"让步后看是不是改了团队配置（资深降中级）。",[23,2249,2250],{"id":2250},"不该谈的点",[50,2252,2254],{"id":2253},"_1-质量","1. 质量",[11,2256,2257],{},"砍价导致：",[27,2259,2260,2263,2266],{},[30,2261,2262],{},"省测试 → 上线一堆 bug。",[30,2264,2265],{},"用初级开发 → 工期长、质量差。",[30,2267,2268],{},"压缩工时 → 赶工粗糙。",[11,2270,2271,773],{},[15,2272,2273],{},"质量是底线，压价会从质量找回来",[50,2275,2277],{"id":2276},"_2-源码归属","2. 源码归属",[27,2279,2280,2283,2286],{},[30,2281,2282],{},"必须给客户。",[30,2284,2285],{},"不交源码 = 被绑架。",[30,2287,2288],{},"这个不能让步。",[50,2290,2292],{"id":2291},"_3-合同保障","3. 合同保障",[27,2294,2295,2298,2301],{},[30,2296,2297],{},"违约责任。",[30,2299,2300],{},"验收标准。",[30,2302,2303],{},"知识产权。",[11,2305,2306,773],{},[15,2307,2308],{},"保障条款弱化等于放弃保护",[23,2310,2311],{"id":2311},"谈判的合理目标",[11,2313,2314],{},"不是砍到底，而是：",[152,2316,2317,2327],{},[155,2318,2319],{},[158,2320,2321,2324],{},[161,2322,2323],{},"目标",[161,2325,2326],{},"做法",[171,2328,2329,2337,2345,2353,2361],{},[158,2330,2331,2334],{},[176,2332,2333],{},"价格合理",[176,2335,2336],{},"拆虚高部分，砍虚高不砍合理",[158,2338,2339,2342],{},[176,2340,2341],{},"风险可控",[176,2343,2344],{},"分期付款、留质保金",[158,2346,2347,2350],{},[176,2348,2349],{},"范围清晰",[176,2351,2352],{},"边缘功能砍到二期",[158,2354,2355,2358],{},[176,2356,2357],{},"增值多",[176,2359,2360],{},"文档、培训、运维",[158,2362,2363,2366],{},[176,2364,2365],{},"保障足",[176,2367,2368],{},"合同条款完整",[11,2370,2371,773],{},[15,2372,2373],{},"好的谈判是双赢——你拿到合理价和保障，开发方拿到合理利润",[23,2375,2376],{"id":2376},"谈判中的红旗信号",[11,2378,2379],{},"如果开发方在谈判中出现这些，要警惕：",[27,2381,2382,2388,2394,2400,2406,2412],{},[30,2383,2384,2387],{},[15,2385,2386],{},"轻易接受大幅砍价","：说明报价虚高太多，或者准备从别处找回来。",[30,2389,2390,2393],{},[15,2391,2392],{},"口头承诺多","：不写进合同的承诺不算数。",[30,2395,2396,2399],{},[15,2397,2398],{},"急着成交","：可能准备拿钱走人。",[30,2401,2402,2405],{},[15,2403,2404],{},"拒绝明细报价","：只给总价，无法判断合理性。",[30,2407,2408,2411],{},[15,2409,2410],{},"要求全款\u002F大头预付","：风险转嫁给客户。",[30,2413,2414,2417],{},[15,2415,2416],{},"不愿写违约\u002F源码条款","：心虚。",[11,2419,2420,773],{},[15,2421,2422],{},"靠谱的服务商谈判时会守住底线（源码、质量），让步在合理范围（付款、增值）",[23,2424,2426],{"id":2425},"谈判策略分阶段谈","谈判策略：分阶段谈",[331,2428,2429,2435,2441,2447,2453,2459],{},[30,2430,2431,2434],{},[15,2432,2433],{},"先要求明细报价","：拿到明细才能谈。",[30,2436,2437,2440],{},[15,2438,2439],{},"指出虚高部分","：具体到哪个模块工时高、单价高。",[30,2442,2443,2446],{},[15,2444,2445],{},"谈付款和范围","：拉长分期、砍边缘功能。",[30,2448,2449,2452],{},[15,2450,2451],{},"争取增值","：文档、培训、运维。",[30,2454,2455,2458],{},[15,2456,2457],{},"锁定合同保障","：源码、违约、验收写死。",[30,2460,2461,2464],{},[15,2462,2463],{},"不急拍板","：多对比、多沟通。",[23,2466,776],{"id":776},[27,2468,2469,2475,2481,2487,2493,2498],{},[30,2470,2471,2474],{},[15,2472,2473],{},"\"砍得越狠越赚\"","：开发方从质量找回，吃亏的是你。",[30,2476,2477,2480],{},[15,2478,2479],{},"\"口头承诺就行\"","：不写合同的承诺无效。",[30,2482,2483,2486],{},[15,2484,2485],{},"\"急着成交\"","：被对方看穿，谈判被动。",[30,2488,2489,2492],{},[15,2490,2491],{},"\"全款换低价\"","：风险全转嫁，出事没人管。",[30,2494,2495,2497],{},[15,2496,1936],{},"：必须拆明细才能谈。",[30,2499,2500,2503],{},[15,2501,2502],{},"\"敢让步就是好公司\"","：轻易让步的反而要警惕。",[23,2505,329],{"id":329},[331,2507,2508,2514,2520,2526,2531,2535,2539],{},[30,2509,2510,2513],{},[15,2511,2512],{},"要求明细报价","：拆到模块工时。",[30,2515,2516,2519],{},[15,2517,2518],{},"算总工时和单价","：判断合理性。",[30,2521,2522,2525],{},[15,2523,2524],{},"识别虚高部分","：针对性谈。",[30,2527,2528,2530],{},[15,2529,2445],{},"：风险和成本平衡。",[30,2532,2533,2452],{},[15,2534,2451],{},[30,2536,2537,1989],{},[15,2538,2457],{},[30,2540,2541,2544],{},[15,2542,2543],{},"多对比不急拍板","：合理谈判。",[364,2546,2547],{},[11,2548,2549],{},"广州市汉诺雷斯（HNREIS）坚持透明明细报价，欢迎客户拆工时、对比、谈判——我们守源码和质量底线，在付款和增值上合理让步。把需求告诉我们，我们出明细报价，你看着谈。",{"title":370,"searchDepth":371,"depth":371,"links":2551},[2552,2557,2564,2569,2570,2571,2572,2573],{"id":2063,"depth":371,"text":2064,"children":2553},[2554,2555,2556],{"id":2070,"depth":377,"text":2071},{"id":2094,"depth":377,"text":2095},{"id":2110,"depth":377,"text":2111},{"id":2130,"depth":371,"text":2130,"children":2558},[2559,2560,2561,2562,2563],{"id":2133,"depth":377,"text":2134},{"id":2173,"depth":377,"text":2174},{"id":2188,"depth":377,"text":2189},{"id":2206,"depth":377,"text":2207},{"id":2235,"depth":377,"text":2236},{"id":2250,"depth":371,"text":2250,"children":2565},[2566,2567,2568],{"id":2253,"depth":377,"text":2254},{"id":2276,"depth":377,"text":2277},{"id":2291,"depth":377,"text":2292},{"id":2311,"depth":371,"text":2311},{"id":2376,"depth":371,"text":2376},{"id":2425,"depth":371,"text":2426},{"id":776,"depth":371,"text":776},{"id":329,"depth":371,"text":329},"2024-06-19","拿到软件外包报价后，怎么谈才不吃亏？本文讲清谈判前的准备、可谈的几个点（付款、范围、工期、增值）、不该谈的点（质量、源码），帮你谈出合理价又不踩坑。",[2577,2580,2583],{"q":2578,"a":2579},"软件外包报价能砍多少合理？","取决于报价是否虚高。如果报价是按规范工时和单价算出来的，砍价空间有限（5%-10% 是常见的让利空间，用于建立合作）。如果报价虚高（工时虚报、单价虚高），可以拆出不合理部分谈。盲目砍价的副作用是开发方会从别处找回来——省工时、降质量、加项。",{"q":2581,"a":2582},"谈判时哪些点能谈，哪些不能？","能谈的：付款节点（拉长分期降低风险）、工期（延长减少加急费）、范围（先做核心砍边缘功能）、增值（要文档、培训、延长质保）、运维（含一段时间免费运维）。不该谈的：质量（压价会导致省测试\u002F降质量）、源码归属（必须给客户）、合同保障条款（违约、验收不能弱化）。",{"q":2584,"a":2585},"报价砍太狠会有什么后果？","开发方接受低价后，必然从别处找回来：省测试（bug 多）、用初级开发（质量差）、压缩工时（赶工粗糙）、后期加项（\"这个不在范围\"）、不交源码（绑架交付）、上线失联（无售后）。砍价的本质是把成本转移，最后客户付出的是质量、维护、扯皮的代价。砍价要合理，不能盲目压低。",[2587,2588,2589,2590],"外包报价谈判","软件外包谈价","报价谈判技巧","外包合同",{},"\u002Fblog\u002Fcost-process\u002Fbaojia-tanpan",{"title":2051,"description":2575},{"loc":2592},"blog\u002Fcost-process\u002Fbaojia-tanpan",[2597,427,2047],"谈判","SqN9trtZWP93iZRrrOY6ULCCPIfmZ2ZCmxLAL40jDEo",1781688911305]