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