[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-quote-by-scope-not-hours-zh-CN":3,"blog-related-quote-by-scope-not-hours-zh-CN":28,"blog-adjacent-quote-by-scope-not-hours-zh-CN":61},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":27},10,"quote-by-scope-not-hours","我们为什么不按人天报价","按人天报价看起来公平，实际把不确定性都推给了客户。我们更愿意先讲清范围和假设，再谈价格。","\u003Cp>创业早期，我们和大多数软件团队一样按人天报价：客户问多少钱，我们就算人数乘天数再乘单价。这种方式简单，也容易被比较，但做得越久，越发现它解决不了真正的问题。\u003C\u002Fp>\n\u003Ch2>人天报价的三个副作用\u003C\u002Fh2>\n\u003Cp>第一，它把客户的注意力引到工时上，而不是方案上。同样的需求有没有更简单的实现路径，反而没人愿意讨论。\u003C\u002Fp>\n\u003Cp>第二，团队会不自觉地填满工时。人天既是计价单位，也是工作量证明，提前做完反而不好解释。\u003C\u002Fp>\n\u003Ch2>我们改成怎么报价\u003C\u002Fh2>\n\u003Cp>先做一次范围梳理，把需求拆成必须做、可以后做、明确不做三类，再用区间价给出承诺。范围写清楚，价格自然站得住。\u003C\u002Fp>\n\u003Cp>报价单同步列出假设：第三方接口由谁提供、数据由谁清洗、验收标准怎么定。假设变了，价格可以重新谈。\u003C\u002Fp>\n\u003Cp>这套做法一开始让我们丢过单子，但也筛出了愿意把问题讲清楚的客户。长期看，这比低价拿单划算得多。\u003C\u002Fp>","","blue","佳益方圆团队","2026-10-07T09:00:00+08:00",1,false,[16,17,18],"创业","报价","合作方式",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":4,"count":21},6,0,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool","article",{},[29,40,50],{"id":30,"slug":31,"title":32,"excerpt":33,"content":9,"cover":9,"tone":34,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":39},11,"three-lessons-from-first-client","第一单客户教会我们的三件事","2019 年的第一个项目只有三万元，却让我们明白了合同、验收和沟通的分量。","cyan","2026-09-25T10:13:00+08:00",[16,37,38],"客户","合同",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":4,"count":21},{"id":41,"slug":42,"title":43,"excerpt":44,"content":9,"cover":9,"tone":45,"author":11,"publishedAt":46,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"category":49},12,"choosing-clients-not-deals","选客户比选项目重要","同一份合同，有的客户让团队成长，有的客户让团队耗尽心气。我们用三个问题筛选客户。","indigo","2026-09-13T11:26:00+08:00",[16,37,48],"选择",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":4,"count":21},{"id":51,"slug":52,"title":53,"excerpt":54,"content":9,"cover":9,"tone":55,"author":11,"publishedAt":56,"updatedAt":56,"readingMinutes":13,"featured":14,"tags":57,"category":60},13,"cash-flow-before-margin","现金流比利润率更重要","利润率是账面数字，现金流决定公司能不能活到下一个项目回款。","teal","2026-09-01T12:39:00+08:00",[16,58,59],"现金流","经营",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":4,"count":21},{"previous":62,"next":79},{"id":63,"slug":64,"title":65,"excerpt":66,"content":9,"cover":9,"tone":67,"author":11,"publishedAt":68,"updatedAt":68,"readingMinutes":13,"featured":14,"tags":69,"category":73},108,"gansu-manufacturing-digitalization","甘肃制造业数字化的三个观察","跑了十几家本地制造企业之后，我们看到数字化不再是买软件，而是补基础。","slate","2026-10-09T09:00:00+08:00",[70,71,72],"行业观察","制造业","数字化",{"id":74,"parentId":21,"slug":75,"name":70,"description":76,"icon":77,"cover":9,"tone":10,"kind":26,"sortOrder":78,"count":21},5,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20,{"id":80,"slug":81,"title":82,"excerpt":83,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":84,"updatedAt":84,"readingMinutes":13,"featured":14,"tags":85,"category":89},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[86,87,88],"接口设计","幂等","可靠性",{"id":13,"parentId":21,"slug":90,"name":91,"description":92,"icon":93,"cover":9,"tone":10,"kind":26,"sortOrder":94,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60]