[{"data":1,"prerenderedAt":250},["ShallowReactive",2],{"site-info":3,"related-news-soeons-new-office-nanning":34},{"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,95,164],{"slug":36,"title":37,"category":40,"date":41,"excerpt":42,"author":45,"body":48},"soeons-sla-upgrade-2026",{"zh":38,"en":39},"运维响应标准升级：30 分钟内响应成为默认承诺","Upgraded Support Standards: 30-Minute Response Now the Default Commitment","announcement","2026-04-15",{"zh":43,"en":44},"从 2026 年 5 月起，所有在保项目的响应时效统一为 30 分钟内响应、4 小时内给出处理方案。","Starting in May 2026, every project under an active support contract will get a guaranteed response within 30 minutes and a resolution plan within 4 hours.",{"zh":46,"en":47},"莫思颖","Mo Siying",[49,54,58,64,82,87,91],{"type":50,"text":51},"paragraph",{"zh":52,"en":53},"从 2026 年 5 月 1 日起，我们对所有在保项目统一升级运维响应标准：严重故障 30 分钟内响应、4 小时内给出处理方案与预估恢复时间。","Effective May 1, 2026, we are upgrading support response standards across all projects under active warranty: for critical incidents, we will respond within 30 minutes and provide a resolution plan and estimated recovery time within 4 hours.",{"type":50,"text":55},{"zh":56,"en":57},"过去我们对不同规模的项目有不同的响应约定，实践中发现这经常让客户在关键时刻需要先做一轮商务沟通才能获得帮助。响应时效不应该取决于合同金额。","Previously, response terms varied by project size, and in practice this often meant clients had to go through a round of commercial negotiations before they could get help at a critical moment. Response times should not depend on contract value.",{"type":59,"text":60,"id":63},"heading",{"zh":61,"en":62},"具体包含什么","What It Covers","details",{"type":65,"items":66},"list",[67,70,73,76,79],{"zh":68,"en":69},"7×24 监控告警，故障自动通知到值班工程师","24\u002F7 monitoring and alerting, with incidents automatically routed to the on-call engineer",{"zh":71,"en":72},"严重故障 30 分钟内响应，4 小时内出具处理方案","Response within 30 minutes for critical incidents, with a resolution plan within 4 hours",{"zh":74,"en":75},"每月一次例行巡检并输出巡检报告","A monthly health inspection with a written inspection report",{"zh":77,"en":78},"每季度一次灾难恢复演练并出具演练报告","A quarterly disaster recovery drill with a written drill report",{"zh":80,"en":81},"备份策略按客户要求调整，默认每日全量 + 增量","Backup policy tailored to each client, defaulting to daily full plus incremental backups",{"type":59,"text":83,"id":86},{"zh":84,"en":85},"背后做了什么","What Went Into the Upgrade","behind",{"type":50,"text":88},{"zh":89,"en":90},"升级响应标准的前提是值班能力真的跟得上。为此我们在过去一年重做了监控体系：统一告警入口、值班排班系统、以及每个客户独立的健康度看板——任何时候打开，都能看到每个系统在最近 24 小时内的真实状态。","Upgrading response standards only works if on-call capacity can actually keep up. To get there, we rebuilt our monitoring over the past year: a single alert entry point, an on-call scheduling system, and a dedicated health dashboard for each client—open it at any time and you see the real status of every system over the past 24 hours.",{"type":50,"text":92},{"zh":93,"en":94},"软件的生命周期比合同长。我们的合同也是。","Software outlives its contract. So do ours.",{"slug":96,"title":97,"category":100,"date":101,"excerpt":102,"author":105,"body":107},"soeons-2026-mid-review",{"zh":98,"en":99},"耗以数载：SOEONS 七年交付复盘","Seven Years, Measured in Sustained Effort: A Look Back at SOEONS Deliveries","company","2026-09-18",{"zh":103,"en":104},"从 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":106,"en":106},"oaken",[108,112,116,121,125,139,147,152,156,160],{"type":50,"text":109},{"zh":110,"en":111},"七年前我们在玉林租下第一间办公室的时候，接的第一个项目是一套进销存系统。客户是做标准件的小型工厂，报价三万八，工期六周。系统上线那天，仓库的老会计问我们：这个做完以后，还用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":50,"text":113},{"zh":114,"en":115},"这件事后来变成了我们做事的起点。软件的价值不在于交付时那几屏漂亮的界面，而在于它接手了哪些原本压在具体某个人身上的重复劳动。今天回头看，一百二十余个项目里，活下来的系统有一个共同的特征：它们在交付时都不是最复杂的那个。","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":59,"text":117,"id":120},{"zh":118,"en":119},"活下来的系统长什么样","What Surviving Systems Have in Common","survivors",{"type":50,"text":122},{"zh":123,"en":124},"我们复盘后发现，被客户长期使用的系统有几个共同特征。第一，业务流程没有为了迁就软件而扭曲，而是软件去适应了真实流程——包括那些看起来很乱的流程。第二，接手了明确重复性工作，而不是提供一堆用不上的报表。第三，系统足够小，小到客户自己人敢改。","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":65,"items":126},[127,130,133,136],{"zh":128,"en":129},"软件适配真实流程，而不是让流程迁就软件","Software adapts to real workflows rather than forcing processes to fit the system",{"zh":131,"en":132},"优先接手明确的重复性劳动，而不是堆砌报表","Take over clearly repetitive work first, instead of piling on reports",{"zh":134,"en":135},"系统规模控制在客户团队敢自己动手改的程度","Keep the system small enough that the client's team dares to modify it themselves",{"zh":137,"en":138},"上线后有人可问、有事可管、有版本可升","After launch, someone to talk to, clear ownership, and a path to upgrade",{"type":140,"text":141,"source":144},"quote",{"zh":142,"en":143},"我们不追求把系统做得复杂，而是追求让系统能被用起来、被用下去。","We don't set out to make systems complex. We set out to make them usable—and used for the long haul.",{"zh":145,"en":146},"oaken · 创始人","oaken, Founder",{"type":59,"text":148,"id":151},{"zh":149,"en":150},"我们在做的改变","What We Have Changed","changes",{"type":50,"text":153},{"zh":154,"en":155},"七年间，我们拒绝了相当一部分看起来更赚钱的需求——那些要求在三个月内从零搭建一套完整 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":50,"text":157},{"zh":158,"en":159},"因此从两年前开始，我们会主动把咨询业务和开发业务分离开来卖：先诊断，再设计，最后才决定要不要做。很多客户在诊断阶段就决定不做了——这对我们是损失，但对他们是节省。","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":50,"text":161},{"zh":162,"en":163},"接下来的一年，我们会继续把重心放在已经交付客户的系统上：更多的巡检、更快的响应、更小步的迭代。七年不算长，「耗以数载」这件事，我们打算继续做下去。","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":165,"title":166,"category":169,"date":170,"excerpt":171,"author":174,"body":177},"sme-digitalization-myths",{"zh":167,"en":168},"中小企业数字化最常踩的五个坑","Five Common Pitfalls in SME Digitalization","insight","2026-08-12",{"zh":172,"en":173},"预算有限、需求模糊、人员流动快——这是中小企业的真实处境，也决定了他们的数字化不能照搬大公司的路径。","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":175,"en":176},"李文博","Li Wenbo",[178,182,187,191,195,200,211,216,220,224,229,233,237,242,246],{"type":50,"text":179},{"zh":180,"en":181},"过去两年我们接触了大量中小企业数字化需求，其中相当一部分在启动阶段就出现了偏差。这五个坑几乎覆盖了我们见到的所有失败案例。","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":59,"text":183,"id":186},{"zh":184,"en":185},"一、先买系统，后想清楚要解决什么","1. Buying the System Before Defining the Problem","myth-1",{"type":50,"text":188},{"zh":189,"en":190},"最常见的剧本是：听说某个系统不错 → 找供应商报价 → 挑功能最多的那个 → 上线后发现跟自己的业务流程对不上。采购顺序错了，后面所有投入都会打折。","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":50,"text":192},{"zh":193,"en":194},"正确的顺序是反过来的：先找到那个每天都在消耗团队时间的环节，把它量化出来，再去找能解决它的方案。没有第零步，方案对比就只是在比功能表。","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":59,"text":196,"id":199},{"zh":197,"en":198},"二、试图一次性覆盖全部业务","2. Trying to Cover Every Business Process at Once","myth-2",{"type":65,"items":201},[202,205,208],{"zh":203,"en":204},"先打通一个环节，形成闭环，再向两端延伸","Connect one process end to end first, then extend outward in both directions",{"zh":206,"en":207},"宁可做一个用起来的小系统，也不要一个没人敢用的全系统","Better a small system people actually use than a comprehensive one nobody dares to use",{"zh":209,"en":210},"每次扩展都应当由前一阶段的真实使用数据驱动","Every expansion should be driven by real usage data from the previous phase",{"type":59,"text":212,"id":215},{"zh":213,"en":214},"三、把数字化当成一次性项目","3. Treating Digitalization as a One-Off Project","myth-3",{"type":50,"text":217},{"zh":218,"en":219},"系统上线不是终点。我们统计过客户上线后三个月内的活跃度，通常在第二周会有一个明显的下坠——这不是系统不好用，而是没有人负责让它继续好用。","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":50,"text":221},{"zh":222,"en":223},"预算里必须留出运营的部分。这笔钱花的回报率，通常比多开发两个模块高得多。","The budget must include an operating share. That money typically delivers a much higher return than building two more modules.",{"type":59,"text":225,"id":228},{"zh":226,"en":227},"四、忽略数据迁移","4. Overlooking Data Migration","myth-4",{"type":50,"text":230},{"zh":231,"en":232},"历史数据不干净是常态。字段缺失、编码不一致、同一件事在系统里有三种写法。我们见过太多项目在上线前一天卡在数据清洗上，拖期三周。","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":50,"text":234},{"zh":235,"en":236},"数据迁移应当被当作一个独立的、有专人负责的工作项排进计划，而不是上线前的最后一道工序。","Data migration should be planned as a standalone workstream with a dedicated owner, not treated as the last step before launch.",{"type":59,"text":238,"id":241},{"zh":239,"en":240},"五、选了没有人的供应商","5. Choosing a Vendor Without the People","myth-5",{"type":50,"text":243},{"zh":244,"en":245},"软件公司和软件最大的区别在于：软件公司会在你上线三年后还在。换供应商的成本，远不止数据迁移那几周。","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":50,"text":247},{"zh":248,"en":249},"在签合同前问三个问题：你们交付过什么规模的项目？上线一年后你们还管吗？出了问题谁在第一时间响应？这三个问题的答案，比报价单更能说明未来三年。","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.",1793453941205]