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