[{"data":1,"prerenderedAt":899},["ShallowReactive",2],{"site-info":3,"services":34,"process-steps":362,"values":466,"featured-cases":499,"latest-news":676},{"name":4,"nameEn":5,"legalNameEn":6,"shortName":7,"domain":8,"url":9,"slogan":10,"sloganEn":11,"description":12,"descriptionEn":13,"founded":14,"year":15,"icp":16,"contact":19,"social":29},"广西耗以数载科技有限公司","SOEONS","Guangxi Haoyi Shuzai Technology Co., Ltd.","耗以数载","soeons.com","https:\u002F\u002Fsoeons.com","锲而不舍 · 耗以数载","Built over years, not over quarters.","广西耗以数载科技有限公司（SOEONS）专注软件定制开发与数字化服务，为中小企业提供数字化咨询、系统定制开发、系统集成部署与长期运维支持，立足广西，面向东盟与西南市场。","SOEONS (Guangxi Haoyi Shuzai Technology Co., Ltd.) specializes in custom software development and digital transformation services. We provide small and midsize businesses with digital consulting, custom software development, systems integration and deployment, and long-term operations support—rooted in Guangxi and serving the southwest China and ASEAN markets.",2019,2026,{"text":17,"url":18},"桂ICP备2024029466号-2","https:\u002F\u002Fbeian.miit.gov.cn",{"phone":20,"mobile":21,"email":22,"address":23,"addressEn":24,"workingHours":25,"workingHoursEn":26,"mapNote":27,"mapNoteEn":28},"0775-XXXXXXX","1XX-XXXX-XXXX","chat@soeons.com","广西壮族自治区玉林市XXXX（待补充）","Yulin, Guangxi, China","周一至周五 09:00 – 18:00","Monday–Friday, 9:00 AM – 6:00 PM (CST)","玉林市","Yulin, Guangxi",{"wechat":30,"linkedin":33},{"label":31,"handle":32},"微信公众号","soeons","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fsoeons",[35,101,166,231,296],{"slug":36,"icon":37,"title":38,"shortTitle":41,"tagline":44,"description":47,"capabilities":50,"deliverables":66,"outcomes":79},"consulting","compass",{"zh":39,"en":40},"数字化咨询与规划","Digital Consulting & Roadmapping",{"zh":42,"en":43},"数字化咨询","Consulting",{"zh":45,"en":46},"先把想清楚，再动手写","Think it through before you write code.",{"zh":48,"en":49},"在写第一行代码之前，先把业务跑通。我们通过流程梳理、现状诊断与目标拆解，帮企业找到「钱该花在哪一处」——数字化最贵的从来不是系统，而是投错方向。","Before anyone writes the first line of code, the business model has to work. Through process mapping, current-state assessment, and goal breakdown, we help you identify where the money should actually go—because the most expensive part of digitalization is rarely the software; it is investing in the wrong direction.",[51,54,57,60,63],{"zh":52,"en":53},"业务流程梳理与瓶颈诊断","Business process mapping and bottleneck analysis",{"zh":55,"en":56},"数字化成熟度评估","Digital maturity assessment",{"zh":58,"en":59},"信息化路线图与预算规划","IT roadmap and budget planning",{"zh":61,"en":62},"数据资产盘点与治理框架","Data asset inventory and governance framework",{"zh":64,"en":65},"供应商选型与验收标准制定","Vendor selection and acceptance criteria",[67,70,73,76],{"zh":68,"en":69},"现状诊断报告","Current-state assessment report",{"zh":71,"en":72},"数字化路线图","Digitalization roadmap",{"zh":74,"en":75},"分阶段投入产出测算","Phased ROI projections",{"zh":77,"en":78},"需求规格说明书","Requirements specification",[80,87,94],{"label":81,"value":84},{"zh":82,"en":83},"平均周期","Typical timeline",{"zh":85,"en":86},"2–4 周","2–4 weeks",{"label":88,"value":91},{"zh":89,"en":90},"无效投入","Wasted investment",{"zh":92,"en":93},"减少 30%+","Reduced by 30%+",{"label":95,"value":98},{"zh":96,"en":97},"交付物","Deliverables",{"zh":99,"en":100},"4 类文档","4 document sets",{"slug":102,"icon":103,"title":104,"shortTitle":107,"tagline":110,"description":113,"capabilities":116,"deliverables":132,"outcomes":145},"development","code",{"zh":105,"en":106},"定制软件开发","Custom Software Development",{"zh":108,"en":109},"定制开发","Custom Development",{"zh":111,"en":112},"不套模板，为你的流程而写","No off-the-shelf templates—built for your workflow.",{"zh":114,"en":115},"从后台管理系统到面向客户的小程序、Web 应用，我们用成熟的工程体系承接每一个非标需求。代码可维护、文档可交接、上线后能持续演进——这才是软件真正的价值。","From back-office management systems to customer-facing mini programs and web apps, we take on every non-standard requirement with a mature engineering practice. Maintainable code, handover-ready documentation, and continued evolution after launch—that is where software delivers real value.",[117,120,123,126,129],{"zh":118,"en":119},"Web 管理系统与业务中台","Web management systems and business middle platforms",{"zh":121,"en":122},"微信小程序 \u002F 企业微信应用","WeChat Mini Programs and WeCom apps",{"zh":124,"en":125},"移动端 App（iOS \u002F Android）","Native mobile apps (iOS and Android)",{"zh":127,"en":128},"SaaS 多租户架构","Multi-tenant SaaS architecture",{"zh":130,"en":131},"与既有 ERP \u002F OA \u002F 财务系统对接","Integration with existing ERP, OA, and finance systems",[133,136,139,142],{"zh":134,"en":135},"可运行的生产环境系统","Production-ready, fully operational system",{"zh":137,"en":138},"源码与 Git 仓库","Source code and Git repository",{"zh":140,"en":141},"部署文档与运维手册","Deployment and operations guides",{"zh":143,"en":144},"接口文档与数据字典","API documentation and data dictionary",[146,153,159],{"label":147,"value":150},{"zh":148,"en":149},"平均交付","Typical delivery",{"zh":151,"en":152},"8–16 周","8–16 weeks",{"label":154,"value":157},{"zh":155,"en":156},"代码交付率","Source code handover",{"zh":158,"en":158},"100%",{"label":160,"value":163},{"zh":161,"en":162},"免费质保","Warranty period",{"zh":164,"en":165},"12 个月","12 months",{"slug":167,"icon":168,"title":169,"shortTitle":172,"tagline":175,"description":178,"capabilities":181,"deliverables":197,"outcomes":210},"integration","layers",{"zh":170,"en":171},"系统集成与部署","Systems Integration & Deployment",{"zh":173,"en":174},"系统集成","Integration",{"zh":176,"en":177},"让散落的数据真正流动起来","Make scattered data actually flow.",{"zh":179,"en":180},"企业的问题往往不是缺系统，而是系统之间互不相通。我们负责打通已有系统、建设统一数据层，并把私有化 \u002F 云端 \u002F 本地混合的部署环境一次配好。","More often than not, the problem isn't a missing system—it's that existing systems can't talk to each other. We connect what you already run, build a unified data layer, and set up your on-premise, cloud, or hybrid deployment environment in one go.",[182,185,188,191,194],{"zh":183,"en":184},"异构系统接口对接与数据同步","Cross-system API integration and data synchronization",{"zh":186,"en":187},"统一数据中台与主数据治理","Unified data platform and master data governance",{"zh":189,"en":190},"私有化 \u002F 公有云 \u002F 混合部署","On-premise, public cloud, and hybrid deployment",{"zh":192,"en":193},"国产化环境适配与迁移","Domestically developed stack adaptation and migration",{"zh":195,"en":196},"高性能高可用架构搭建","High-performance, high-availability architecture",[198,201,204,207],{"zh":199,"en":200},"集成方案与接口文档","Integration plan and API documentation",{"zh":202,"en":203},"数据同步链路与监控","Data synchronization pipelines and monitoring",{"zh":205,"en":206},"部署环境与运维手册","Deployed environment and operations manual",{"zh":208,"en":209},"性能压测报告","Load testing report",[211,218,225],{"label":212,"value":215},{"zh":213,"en":214},"数据打通","Systems connected",{"zh":216,"en":217},"平均 6+ 系统","6+ systems on average",{"label":219,"value":222},{"zh":220,"en":221},"同步延迟","Sync latency",{"zh":223,"en":224},"\u003C 1 秒","\u003C 1 second",{"label":226,"value":229},{"zh":227,"en":228},"可用性","Availability",{"zh":230,"en":230},"99.9%",{"slug":232,"icon":233,"title":234,"shortTitle":237,"tagline":240,"description":243,"capabilities":246,"deliverables":262,"outcomes":275},"operations","gear",{"zh":235,"en":236},"云服务与运维支持","Cloud Services & Operations Support",{"zh":238,"en":239},"云与运维","Cloud & Ops",{"zh":241,"en":242},"上线才是开始，不是终点","Go-live is the beginning, not the end.",{"zh":244,"en":245},"很多项目在验收那天就结束了。我们的运维团队按月驻场或远程值守，负责监控、备份、迭代与应急响应——软件的生命周期，本就该比合同长。","Too many projects end on the day they are signed off. Our operations team works on-site or remotely on a monthly basis, handling monitoring, backups, iterative improvements, and incident response—a software system should outlive the contract that built it.",[247,250,253,256,259],{"zh":248,"en":249},"7×24 监控与告警","24\u002F7 monitoring and alerting",{"zh":251,"en":252},"自动备份与灾难恢复演练","Automated backups and disaster recovery drills",{"zh":254,"en":255},"例行巡检与容量规划","Routine inspections and capacity planning",{"zh":257,"en":258},"安全漏洞修复与补丁管理","Security patching and vulnerability remediation",{"zh":260,"en":261},"持续迭代与小步发布","Continuous iteration and small, frequent releases",[263,266,269,272],{"zh":264,"en":265},"SLA 服务等级协议","SLA agreement",{"zh":267,"en":268},"监控大盘与告警规则","Monitoring dashboards and alert rules",{"zh":270,"en":271},"备份与恢复预案","Backup and recovery plan",{"zh":273,"en":274},"季度运维报告","Quarterly operations report",[276,283,289],{"label":277,"value":280},{"zh":278,"en":279},"响应时效","Response time",{"zh":281,"en":282},"\u003C 30 分钟","\u003C 30 minutes",{"label":284,"value":287},{"zh":285,"en":286},"服务可用性","Service availability",{"zh":288,"en":288},"99.9%+",{"label":290,"value":293},{"zh":291,"en":292},"驻场支持","On-site support",{"zh":294,"en":295},"按月 \u002F 按年","Monthly or annual",{"slug":297,"icon":298,"title":299,"shortTitle":302,"tagline":305,"description":308,"capabilities":311,"deliverables":327,"outcomes":340},"analytics","chart",{"zh":300,"en":301},"数据看板与经营分析","Dashboards & Business Analytics",{"zh":303,"en":304},"数据看板","Dashboards",{"zh":306,"en":307},"让每一笔投入都能被看见","Make every investment visible.",{"zh":309,"en":310},"把散落在各系统里的经营数据汇到一处，转化为每天早上打开就知道该做什么的决策看板。我们不只画图，还负责把指标口径定义清楚。","We bring business data scattered across systems into one place and turn it into a decision dashboard you can open each morning and know exactly what to do. We don't just draw charts—we make sure every metric is defined the same way across the business.",[312,315,318,321,324],{"zh":313,"en":314},"经营指标体系设计","KPI framework design",{"zh":316,"en":317},"多源数据汇聚与清洗","Multi-source data aggregation and cleansing",{"zh":319,"en":320},"实时 \u002F 准实时看板","Real-time and near-real-time dashboards",{"zh":322,"en":323},"异常预警与自动日报","Anomaly alerts and automated daily reports",{"zh":325,"en":326},"移动端可视化与订阅推送","Mobile visualization and subscription push",[328,331,334,337],{"zh":329,"en":330},"指标口径字典","Metric definition dictionary",{"zh":332,"en":333},"可视化看板（PC + 移动）","Dashboards for desktop and mobile",{"zh":335,"en":336},"预警规则与推送配置","Alert rules and notification setup",{"zh":338,"en":339},"使用培训与文档","User training and documentation",[341,348,355],{"label":342,"value":345},{"zh":343,"en":344},"数据延迟","Data latency",{"zh":346,"en":347},"准实时","Near real-time",{"label":349,"value":352},{"zh":350,"en":351},"手工报表","Manual reports",{"zh":353,"en":354},"减少 70%","Reduced by 70%",{"label":356,"value":359},{"zh":357,"en":358},"指标统一","Metric consistency",{"zh":360,"en":361},"全口径","Company-wide",[363,384,405,426,445],{"index":364,"title":365,"duration":368,"description":371,"deliverables":374},"01",{"zh":366,"en":367},"诊断","Diagnose",{"zh":369,"en":370},"1–2 周","1–2 weeks",{"zh":372,"en":373},"不谈需求，先看现场。我们走访业务部门、梳理现有流程、盘点已有系统，输出问题清单与改进优先级——把「想要什么」还原成「该解决什么」。","Before we talk about features, we look at the ground truth. We interview business teams, map existing processes, and audit current systems to produce a prioritized list of problems—turning \"what we want\" into \"what we actually need to solve.\"",[375,378,381],{"zh":376,"en":377},"业务调研记录","Business discovery notes",{"zh":379,"en":380},"现状流程图","Current-state process maps",{"zh":382,"en":383},"问题优先级清单","Prioritized issue list",{"index":385,"title":386,"duration":389,"description":392,"deliverables":395},"02",{"zh":387,"en":388},"设计","Design",{"zh":390,"en":391},"2–3 周","2–3 weeks",{"zh":393,"en":394},"确定系统边界与技术路线，产出原型、架构设计与接口规范。这一步会明确「哪些自研、哪些复用、哪些采购」，避免后期扯皮。","We define system boundaries and the technical approach, and produce prototypes, architecture designs, and API specifications. This stage settles what to build in-house, what to reuse, and what to buy—so there are no surprises later.",[396,399,402],{"zh":397,"en":398},"交互原型","Interactive prototypes",{"zh":400,"en":401},"系统架构设计","System architecture design",{"zh":403,"en":404},"接口与数据规范","API and data specifications",{"index":406,"title":407,"duration":410,"description":413,"deliverables":416},"03",{"zh":408,"en":409},"开发","Build",{"zh":411,"en":412},"4–10 周","4–10 weeks",{"zh":414,"en":415},"以两周一个迭代推进，每个迭代交付可运行的版本与演示。看板全程开放，随时能看到进度，不用等到最后才知道长什么样。","We work in two-week sprints, each delivering a runnable build and a demo. The board stays open throughout, so you can see progress at any time—no surprises at the end.",[417,420,423],{"zh":418,"en":419},"可运行迭代版本","Runnable sprint builds",{"zh":421,"en":422},"迭代进度看板","Sprint progress board",{"zh":424,"en":425},"持续集成流水线","CI\u002FCD pipelines",{"index":427,"title":428,"duration":431,"description":432,"deliverables":435},"04",{"zh":429,"en":430},"上线","Launch",{"zh":369,"en":370},{"zh":433,"en":434},"包含数据迁移、用户培训、试运行与正式切换。我们会准备回滚预案，上线当天工程师驻场，直到系统稳定运行。","This covers data migration, user training, trial runs, and the final cutover. We prepare a rollback plan and have engineers on site on launch day until the system is running smoothly.",[436,439,442],{"zh":437,"en":438},"数据迁移脚本","Data migration scripts",{"zh":440,"en":441},"用户操作手册","User manuals",{"zh":443,"en":444},"上线与回滚预案","Launch and rollback plan",{"index":446,"title":447,"duration":450,"description":453,"deliverables":456},"05",{"zh":448,"en":449},"陪跑","Support",{"zh":451,"en":452},"长期","Ongoing",{"zh":454,"en":455},"质保期内响应报障、每月巡检、按季度输出优化建议。多数系统真正的价值发生在上线之后的第 6 到第 18 个月。","Through the warranty period we respond to incidents, run monthly inspections, and issue quarterly optimization recommendations. For most systems, the real value shows up between six and eighteen months after launch.",[457,460,463],{"zh":458,"en":459},"质保期响应服务","Warranty-period incident response",{"zh":461,"en":462},"月度巡检报告","Monthly inspection reports",{"zh":464,"en":465},"季度优化建议书","Quarterly optimization recommendations",[467,475,483,491],{"icon":468,"title":469,"description":472},"clock",{"zh":470,"en":471},"长期主义","Long-Term Commitment",{"zh":473,"en":474},"我们不追求签下多少单子，更在意交付三年后系统还在不在、还在不在被用。「耗以数载」不是口号，是我们给客户的承诺周期。","We care less about how many deals we sign and more about whether the system is still up and still in use three years later. \"Built over years\" isn't a slogan—it's the time horizon we commit to with every client.",{"icon":476,"title":477,"description":480},"target",{"zh":478,"en":479},"先诊断，后开方","Diagnose First, Prescribe Second",{"zh":481,"en":482},"接到需求的第一件事不是报价，而是弄清楚业务到底卡在哪。找准问题的成本远低于做错方向的代价。","The first thing we do with a new request isn't send a quote—it's figure out where the business is actually stuck. Finding the real problem costs far less than heading in the wrong direction.",{"icon":484,"title":485,"description":488},"handshake",{"zh":486,"en":487},"交付完整，不留烂摊子","Complete Handover, No Loose Ends",{"zh":489,"en":490},"源码、数据字典、部署文档、运维手册，一份不少地交到客户手里。我们清楚自己可能被替换，但更清楚不该被需要。","Source code, data dictionaries, deployment guides, operations manuals—everything is handed over in full. We accept that we may one day be replaced, but we make sure we don't need to be.",{"icon":492,"title":493,"description":496},"users",{"zh":494,"en":495},"把自己人当伙伴","Treat Your Team as Partners",{"zh":497,"en":498},"项目组驻场办公、跟客户同一条产线开早会。系统好不好用，最终由每天用它的同事说了算。","Our project teams work on-site and join morning stand-ups on the same production line as our clients. In the end, whether a system works is decided by the people who use it every day.",[500,561,619],{"slug":501,"title":502,"client":505,"industry":508,"region":509,"summary":512,"challenge":515,"solution":518,"results":531,"stack":553,"year":559,"featured":560},"precision-manufacturing-mes",{"zh":503,"en":504},"精密零部件制造的工单与追溯体系","Work Order and Traceability System for Precision Components Manufacturing",{"zh":506,"en":507},"某精密制造集团","A precision manufacturing group","manufacturing",{"zh":510,"en":511},"广西 · 柳州","Liuzhou, Guangxi",{"zh":513,"en":514},"为一家做精密结构件的制造集团重建工单体系，把订单、工艺、质检与仓储串成一条可追溯的链路。","Rebuilt the work order system for a precision structural components manufacturer, linking orders, processes, quality inspection, and warehousing into a single traceable chain.",{"zh":516,"en":517},"生产订单靠 Excel 在车间、仓库、质检三方之间传递，版本经常对不上；客户要求提供产品全过程追溯时，需要人工翻找两个月的纸质记录。","Production orders moved between the shop floor, warehouse, and QA team in Excel, and version mismatches were routine. When a customer requested full product traceability, staff had to dig through two months of paper records by hand.",[519,522,525,528],{"zh":520,"en":521},"梳理 14 类工单模板与 23 个关键流转节点，替换全部线下 Excel","Mapped 14 work order templates and 23 key handoff points, replacing all offline Excel workflows",{"zh":523,"en":524},"搭建统一工序编码规则，实现批次级全链路追溯","Established a unified process coding standard for end-to-end batch-level traceability",{"zh":526,"en":527},"对接已有 ERP 与财务系统，避免重复录入","Integrated with the existing ERP and finance systems to eliminate duplicate data entry",{"zh":529,"en":530},"车间大屏实时显示在制工单进度与异常件","Rolled out shop floor displays showing live work order progress and exception items",[532,539,546],{"label":533,"value":536},{"zh":534,"en":535},"工单流转耗时","Work order cycle time",{"zh":537,"en":538},"缩短 62%","Reduced by 62%",{"label":540,"value":543},{"zh":541,"en":542},"追溯查询","Traceability lookup",{"zh":544,"en":545},"2 小时 → 30 秒","2 hours → 30 seconds",{"label":547,"value":550},{"zh":548,"en":549},"数据重复录入","Duplicate data entry",{"zh":551,"en":552},"减少 80%","Reduced by 80%",[554,555,556,557,558],"Java","Spring Boot","MySQL","Vue","Docker",2025,true,{"slug":562,"title":563,"client":566,"industry":569,"region":570,"summary":573,"challenge":576,"solution":579,"results":592,"stack":613,"year":559,"featured":560},"retail-chain-omnichannel",{"zh":564,"en":565},"连锁零售的会员与门店一体化平台","Unified Loyalty and Store Platform for a Retail Chain",{"zh":567,"en":568},"某区域连锁零售品牌","A regional retail chain","retail",{"zh":571,"en":572},"广西 · 南宁","Nanning, Guangxi",{"zh":574,"en":575},"把 60 余家门店的会员、储值、库存与营销活动整合到统一平台，实现线上线下同一套会员体系。","Consolidated loyalty, stored value, inventory, and campaign data from 60+ stores onto one platform, giving online and offline channels a single unified loyalty program.",{"zh":577,"en":578},"门店系统与电商后台各自为政，同一顾客在两边是两个身份；活动效果只能看总营收，无法判断哪一次活动真正带来了复购。","Store systems and the e-commerce back office operated independently, so the same customer had two separate identities. Campaign performance could only be measured by total revenue—impossible to tell which campaign actually drove repeat purchases.",[580,583,586,589],{"zh":581,"en":582},"建立统一会员主数据模型，完成存量会员去重与合并","Built a unified customer master data model and de-duplicated and merged existing member records",{"zh":584,"en":585},"打通门店 POS、电商与小程序三端的会员与储值数据","Connected membership and stored-value data across in-store POS, e-commerce, and the mini program",{"zh":587,"en":588},"重构活动分析指标体系，支持单次活动的 ROI 归因","Redesigned campaign analytics to attribute ROI to individual campaigns",{"zh":590,"en":591},"上线门店与区域两级经营看板","Delivered store-level and regional performance dashboards",[593,600,607],{"label":594,"value":597},{"zh":595,"en":596},"会员识别率","Member identification rate",{"zh":598,"en":599},"提升至 94%","Increased to 94%",{"label":601,"value":604},{"zh":602,"en":603},"活动 ROI 可归因","Campaign ROI attribution",{"zh":605,"en":606},"从 0 到 100%","0% → 100%",{"label":608,"value":611},{"zh":609,"en":610},"月度复购率","Monthly repeat purchase rate",{"zh":612,"en":612},"+17%",[614,615,616,617,618],"Next.js","NestJS","PostgreSQL","Redis","ECharts",{"slug":620,"title":621,"client":624,"industry":627,"region":628,"summary":630,"challenge":633,"solution":636,"results":649,"stack":669,"year":675,"featured":560},"agriculture-supply-chain",{"zh":622,"en":623},"农产品产地供应链的溯源与调度","Traceability and Fleet Dispatch for an Agricultural Supply Chain",{"zh":625,"en":626},"某农产品供应链集团","An agricultural supply chain group","agriculture",{"zh":629,"en":28},"广西 · 玉林",{"zh":631,"en":632},"为覆盖 3 个地级市、200 余个合作社的供应链网络搭建溯源与运力调度系统。","Built a traceability and transport dispatch system for a supply chain network spanning 3 prefecture-level cities and 200+ cooperatives.",{"zh":634,"en":635},"货源信息靠微信群和电话协调，运力调度全凭调度员经验；出了问题追溯不到具体批次，消费者信任度持续走低。","Supply information was coordinated over WeChat groups and phone calls, and dispatching relied entirely on individual dispatchers' experience. When problems arose, there was no way to trace a specific batch, and consumer trust kept declining.",[637,640,643,646],{"zh":638,"en":639},"设计产地分级、质检、入库、发货五段式溯源编码","Designed a five-stage traceability coding scheme covering origin grading, quality inspection, warehousing, and shipping",{"zh":641,"en":642},"开发基于订单时效与车辆位置的运力调度看板","Built a dispatch dashboard driven by order deadlines and real-time vehicle locations",{"zh":644,"en":645},"搭建面向合作社的轻量化移动端录入工具","Developed a lightweight mobile data entry tool for cooperatives",{"zh":647,"en":648},"对接监管平台完成数据上报","Integrated with regulatory platforms for automated data reporting",[650,657,664],{"label":651,"value":654},{"zh":652,"en":653},"调度响应","Dispatch response",{"zh":655,"en":656},"从小时级到分钟级","From hours to minutes",{"label":658,"value":661},{"zh":659,"en":660},"运力空驶率","Empty-running rate",{"zh":662,"en":663},"下降 28%","Down 28%",{"label":665,"value":668},{"zh":666,"en":667},"溯源覆盖率","Traceability coverage",{"zh":158,"en":158},[670,671,672,673,674],"Go","React","ClickHouse","Kafka","Kubernetes",2024,[677,749,835],{"slug":678,"title":679,"category":682,"date":683,"excerpt":684,"author":687,"body":689},"soeons-2026-mid-review",{"zh":680,"en":681},"耗以数载：SOEONS 七年交付复盘","Seven Years, Measured in Sustained Effort: A Look Back at SOEONS Deliveries","company","2026-09-18",{"zh":685,"en":686},"从 2019 年三个人到今天六十余人的技术团队，我们把过去七年交付的一百二十余个项目摊开来看，想弄清楚一件事：什么样的软件，才能真正陪企业走得更远。","From three people in 2019 to a technical team of more than sixty today, we laid out the 120-plus projects we have delivered over the past seven years to answer one question: what kind of software can truly grow with a business over the long run?",{"zh":688,"en":688},"oaken",[690,695,699,705,709,724,732,737,741,745],{"type":691,"text":692},"paragraph",{"zh":693,"en":694},"七年前我们在玉林租下第一间办公室的时候，接的第一个项目是一套进销存系统。客户是做标准件的小型工厂，报价三万八，工期六周。系统上线那天，仓库的老会计问我们：这个做完以后，还用Excel吗？我们说不用了。他当时没说话，三个月后主动打电话来说，仓库现在每天少加一次班。","When we rented our first office in Yulin seven years ago, our first project was an inventory management system. The client was a small factory making standard parts. The quote was ¥38,000, the schedule six weeks. On the day the system went live, the veteran accountant in the warehouse asked us: “Now that this is done, will we still need Excel?” We said no. He said nothing at the time, but three months later he called us himself to say the warehouse was now working one fewer overtime shift every day.",{"type":691,"text":696},{"zh":697,"en":698},"这件事后来变成了我们做事的起点。软件的价值不在于交付时那几屏漂亮的界面，而在于它接手了哪些原本压在具体某个人身上的重复劳动。今天回头看，一百二十余个项目里，活下来的系统有一个共同的特征：它们在交付时都不是最复杂的那个。","That moment became the starting point for how we work. The value of software lies not in the few polished screens at handover, but in the repetitive work it takes off the shoulders of specific people. Looking back today, the systems that have survived among those 120-plus projects share one trait: at the time of delivery, they were never the most complex option.",{"type":700,"text":701,"id":704},"heading",{"zh":702,"en":703},"活下来的系统长什么样","What Surviving Systems Have in Common","survivors",{"type":691,"text":706},{"zh":707,"en":708},"我们复盘后发现，被客户长期使用的系统有几个共同特征。第一，业务流程没有为了迁就软件而扭曲，而是软件去适应了真实流程——包括那些看起来很乱的流程。第二，接手了明确重复性工作，而不是提供一堆用不上的报表。第三，系统足够小，小到客户自己人敢改。","Our review found several shared characteristics among the systems clients keep using long term. First, business processes were not bent to fit the software; the software adapted to real workflows, including the messy-looking ones. Second, it took over clearly repetitive work rather than adding a pile of reports nobody used. Third, the system was small enough that the client's own staff felt comfortable making changes to it.",{"type":710,"items":711},"list",[712,715,718,721],{"zh":713,"en":714},"软件适配真实流程，而不是让流程迁就软件","Software adapts to real workflows rather than forcing processes to fit the system",{"zh":716,"en":717},"优先接手明确的重复性劳动，而不是堆砌报表","Take over clearly repetitive work first, instead of piling on reports",{"zh":719,"en":720},"系统规模控制在客户团队敢自己动手改的程度","Keep the system small enough that the client's team dares to modify it themselves",{"zh":722,"en":723},"上线后有人可问、有事可管、有版本可升","After launch, someone to talk to, clear ownership, and a path to upgrade",{"type":725,"text":726,"source":729},"quote",{"zh":727,"en":728},"我们不追求把系统做得复杂，而是追求让系统能被用起来、被用下去。","We don't set out to make systems complex. We set out to make them usable—and used for the long haul.",{"zh":730,"en":731},"oaken · 创始人","oaken, Founder",{"type":700,"text":733,"id":736},{"zh":734,"en":735},"我们在做的改变","What We Have Changed","changes",{"type":691,"text":738},{"zh":739,"en":740},"七年间，我们拒绝了相当一部分看起来更赚钱的需求——那些要求在三个月内从零搭建一套完整 ERP 的项目。我们的经验是，在业务本身还没有跑顺的阶段上一套完整系统，最终往往是系统被闲置。","Over the past seven years, we turned down a fair number of seemingly more profitable opportunities—projects that asked for a complete ERP built from scratch in three months. In our experience, deploying a full system before the business itself has settled into a rhythm usually ends with the system sitting idle.",{"type":691,"text":742},{"zh":743,"en":744},"因此从两年前开始，我们会主动把咨询业务和开发业务分离开来卖：先诊断，再设计，最后才决定要不要做。很多客户在诊断阶段就决定不做了——这对我们是损失，但对他们是节省。","So two years ago, we began selling consulting and development separately: diagnose first, design next, and only then decide whether to build. Many clients decide not to proceed at the diagnosis stage. That costs us revenue, but it saves them money.",{"type":691,"text":746},{"zh":747,"en":748},"接下来的一年，我们会继续把重心放在已经交付客户的系统上：更多的巡检、更快的响应、更小步的迭代。七年不算长，「耗以数载」这件事，我们打算继续做下去。","Over the coming year, we will keep our focus on the systems we have already delivered: more frequent inspections, faster response, and smaller iterations. Seven years is not long, and we intend to keep spending our years on exactly this.",{"slug":750,"title":751,"category":754,"date":755,"excerpt":756,"author":759,"body":762},"sme-digitalization-myths",{"zh":752,"en":753},"中小企业数字化最常踩的五个坑","Five Common Pitfalls in SME Digitalization","insight","2026-08-12",{"zh":757,"en":758},"预算有限、需求模糊、人员流动快——这是中小企业的真实处境，也决定了他们的数字化不能照搬大公司的路径。","Limited budgets, vague requirements, and rapid staff turnover—these are the realities small and midsize businesses face, and they mean SMEs cannot simply copy the paths taken by large corporations.",{"zh":760,"en":761},"李文博","Li Wenbo",[763,767,772,776,780,785,796,801,805,809,814,818,822,827,831],{"type":691,"text":764},{"zh":765,"en":766},"过去两年我们接触了大量中小企业数字化需求，其中相当一部分在启动阶段就出现了偏差。这五个坑几乎覆盖了我们见到的所有失败案例。","Over the past two years we have worked on many digitalization requests from SMEs, and a considerable share went off track right at the start. These five pitfalls account for nearly every failed case we have seen.",{"type":700,"text":768,"id":771},{"zh":769,"en":770},"一、先买系统，后想清楚要解决什么","1. Buying the System Before Defining the Problem","myth-1",{"type":691,"text":773},{"zh":774,"en":775},"最常见的剧本是：听说某个系统不错 → 找供应商报价 → 挑功能最多的那个 → 上线后发现跟自己的业务流程对不上。采购顺序错了，后面所有投入都会打折。","The most common script: hear that a certain system is good → ask vendors for quotes → pick the one with the most features → discover after go-live that it doesn't match your workflows. Get the buying order wrong, and every dollar that follows is discounted.",{"type":691,"text":777},{"zh":778,"en":779},"正确的顺序是反过来的：先找到那个每天都在消耗团队时间的环节，把它量化出来，再去找能解决它的方案。没有第零步，方案对比就只是在比功能表。","The right order is the reverse: first identify the step that drains your team's time every single day, quantify it, and then look for a solution that addresses it. Without that step zero, comparing proposals is just comparing feature lists.",{"type":700,"text":781,"id":784},{"zh":782,"en":783},"二、试图一次性覆盖全部业务","2. Trying to Cover Every Business Process at Once","myth-2",{"type":710,"items":786},[787,790,793],{"zh":788,"en":789},"先打通一个环节，形成闭环，再向两端延伸","Connect one process end to end first, then extend outward in both directions",{"zh":791,"en":792},"宁可做一个用起来的小系统，也不要一个没人敢用的全系统","Better a small system people actually use than a comprehensive one nobody dares to use",{"zh":794,"en":795},"每次扩展都应当由前一阶段的真实使用数据驱动","Every expansion should be driven by real usage data from the previous phase",{"type":700,"text":797,"id":800},{"zh":798,"en":799},"三、把数字化当成一次性项目","3. Treating Digitalization as a One-Off Project","myth-3",{"type":691,"text":802},{"zh":803,"en":804},"系统上线不是终点。我们统计过客户上线后三个月内的活跃度，通常在第二周会有一个明显的下坠——这不是系统不好用，而是没有人负责让它继续好用。","Go-live is not the finish line. When we tracked activity in the first three months after launch, we typically saw a sharp drop in the second week—not because the system was hard to use, but because no one was responsible for keeping it that way.",{"type":691,"text":806},{"zh":807,"en":808},"预算里必须留出运营的部分。这笔钱花的回报率，通常比多开发两个模块高得多。","The budget must include an operating share. That money typically delivers a much higher return than building two more modules.",{"type":700,"text":810,"id":813},{"zh":811,"en":812},"四、忽略数据迁移","4. Overlooking Data Migration","myth-4",{"type":691,"text":815},{"zh":816,"en":817},"历史数据不干净是常态。字段缺失、编码不一致、同一件事在系统里有三种写法。我们见过太多项目在上线前一天卡在数据清洗上，拖期三周。","Dirty historical data is the norm: missing fields, inconsistent codes, the same thing recorded three different ways. We have seen far too many projects stall on data cleansing the day before go-live, pushing the launch back three weeks.",{"type":691,"text":819},{"zh":820,"en":821},"数据迁移应当被当作一个独立的、有专人负责的工作项排进计划，而不是上线前的最后一道工序。","Data migration should be planned as a standalone workstream with a dedicated owner, not treated as the last step before launch.",{"type":700,"text":823,"id":826},{"zh":824,"en":825},"五、选了没有人的供应商","5. Choosing a Vendor Without the People","myth-5",{"type":691,"text":828},{"zh":829,"en":830},"软件公司和软件最大的区别在于：软件公司会在你上线三年后还在。换供应商的成本，远不止数据迁移那几周。","The biggest difference between a software company and software is this: a software company will still be there three years after you go live. The cost of switching vendors goes far beyond the few weeks of data migration.",{"type":691,"text":832},{"zh":833,"en":834},"在签合同前问三个问题：你们交付过什么规模的项目？上线一年后你们还管吗？出了问题谁在第一时间响应？这三个问题的答案，比报价单更能说明未来三年。","Before signing, ask three questions: what scale of project have you delivered? Will you still be supporting us a year after launch? Who responds first when something goes wrong? The answers will tell you more about the next three years than any quote.",{"slug":836,"title":837,"category":840,"date":841,"excerpt":842,"author":845,"body":848},"asean-cross-border-digitalization",{"zh":838,"en":839},"广西区位优势下的跨境数字化：从玉林出发","Cross-Border Digitalization from Guangxi: Starting in Yulin","industry","2026-07-05",{"zh":843,"en":844},"RCEP 生效以来，广西的通道价值被重新定价。我们把过去两年在越南的试点经验整理成三点观察。","Since RCEP took effect, Guangxi’s value as a corridor has been revalued. We distilled two years of pilot experience in Vietnam into three observations.",{"zh":846,"en":847},"韦晓芸","Wei Xiaoyun",[849,853,857,862,866,877,882,886,891,895],{"type":691,"text":850},{"zh":851,"en":852},"2024 年我们接了第一个在越南经营的中资客户。客户总部在玉林，工厂在海防，用的是同一套在国内已经跑顺的 ERP，但越南工厂的工单还停留在纸单上。","In 2024 we took on our first Chinese-owned client operating in Vietnam. The headquarters is in Yulin, the factory in Hai Phong, and the company runs the same ERP that already works well in China—yet work orders at the Vietnam factory were still on paper.",{"type":691,"text":854},{"zh":855,"en":856},"这个项目让我们意识到，跨境数字化的核心问题不是「要不要国际化」，而是「哪些东西必须统一，哪些东西必须分开」。","The project made one thing clear: the core question in cross-border digitalization is not whether to go international, but what must be standardized and what must be kept separate.",{"type":700,"text":858,"id":861},{"zh":859,"en":860},"观察一：主数据要统一，流程要本地化","Observation 1: Standardize Master Data, Localize Processes","obs-1",{"type":691,"text":863},{"zh":864,"en":865},"跨境企业最容易犯的错，是把国内整套系统原样复制一份到海外。结果是编码规则、审批层级、税务口径全部错位。","The most common mistake cross-border companies make is copying the entire domestic system overseas as-is. The result is misaligned coding rules, approval levels, and tax treatments.",{"type":710,"items":867},[868,871,874],{"zh":869,"en":870},"物料编码、客户档案、组织结构保持统一，保证数据可比","Keep material codes, customer records, and organizational structure unified so data stays comparable",{"zh":872,"en":873},"审批流、税务单据、薪酬口径按当地法规与习惯本地化","Localize approval workflows, tax documents, and payroll rules to local regulations and customs",{"zh":875,"en":876},"界面语言、货币、时区在配置层解决，不做代码分支","Handle language, currency, and time zones through configuration, not separate code branches",{"type":700,"text":878,"id":881},{"zh":879,"en":880},"观察二：数据出境要提前设计","Observation 2: Design Cross-Border Data Transfer Upfront","obs-2",{"type":691,"text":883},{"zh":884,"en":885},"我们踩过的坑是：先做了跨境同步，再去补合规。这条路走不通。数据出境的路径、加密方式与审计留痕，必须在架构阶段就确定，而不是上线前找法务补。","The pitfall we ran into: building cross-border syncing first and patching in compliance afterward. That approach doesn't work. Data transfer paths, encryption methods, and audit trails must be decided at the architecture stage, not bolted on by legal before go-live.",{"type":700,"text":887,"id":890},{"zh":888,"en":889},"观察三：跨境系统的可用性标准要更高","Observation 3: Cross-Border Systems Need Higher Availability Standards","obs-3",{"type":691,"text":892},{"zh":893,"en":894},"网络链路不稳定是跨境环境的常态。系统在设计时就要假设「网络会断」，具备本地缓存与断点续传能力，否则每一次跨国会议都会变成一次故障复盘。","Unstable network links are a fact of life in cross-border operations. Systems must be designed on the assumption that the network will drop, with local caching and resumable transfers—otherwise every cross-border meeting turns into an incident review.",{"type":691,"text":896},{"zh":897,"en":898},"广西的区位让这件事在物理上更近了一层。对我们来说，这意味着同一个项目团队可以在一天之内同时出现在玉林和越南的现场——这在几年前是不可想象的。","Guangxi’s location brings this physically closer. For us, it means the same project team can be on site in Yulin and in Vietnam on the same day—something that was unthinkable just a few years ago.",1793453940708]