[{"data":1,"prerenderedAt":227},["ShallowReactive",2],{"site-info":3,"related-news-sme-digitalization-myths":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,165],{"slug":36,"title":37,"category":40,"date":41,"excerpt":42,"author":45,"body":48},"data-dashboard-design-principles",{"zh":38,"en":39},"看板不是报表：中小企业数据可视化的四个设计原则","A Dashboard Is Not a Report: Four Design Principles for SME Data Visualization","insight","2026-05-28",{"zh":43,"en":44},"我们复盘了交付过的二十余个经营看板，发现真正被每天打开的只有三个。差别不在技术，在设计。","We reviewed more than twenty business dashboards we have delivered and found that clients actually open only about three of them every day. The difference isn't technology—it's design.",{"zh":46,"en":47},"韦晓芸","Wei Xiaoyun",[49,54,58,64,68,73,77,82,86,91],{"type":50,"text":51},"paragraph",{"zh":52,"en":53},"「做个数据看板」是我们接到过最多的需求之一。但交付之后，客户每天真的会打开的看板，平均只有三个。","“Build us a data dashboard” is one of the most frequent requests we receive. But after delivery, clients actually open only about three dashboards a day on average.",{"type":50,"text":55},{"zh":56,"en":57},"问题往往不在技术，而在没人定义过「看了之后要做什么决定」。","The problem usually isn't technical. It's that no one has defined what decision you are supposed to make after looking at it.",{"type":59,"text":60,"id":63},"heading",{"zh":61,"en":62},"原则一：每个数字都要绑定一个动作","Principle 1: Every Number Should Be Tied to an Action","p1",{"type":50,"text":65},{"zh":66,"en":67},"如果一个指标出现异常，看板上没有任何对应的处理指引，那它就没有存在的必要。好的看板会直接写清楚：超过什么阈值需要做什么。","If a metric goes off track and the dashboard offers no guidance on how to respond, it has no reason to exist. A good dashboard states plainly what to do when a threshold is crossed.",{"type":59,"text":69,"id":72},{"zh":70,"en":71},"原则二：先做口径，再做图表","Principle 2: Define the Metrics Before Building the Charts","p2",{"type":50,"text":74},{"zh":75,"en":76},"我们在项目早期一定要求客户把指标口径写下来：销售额含税还是不含税、退款怎么算、跨月订单归哪个月。口径不清时，画得再漂亮的图也只是把分歧可视化。","Early in every project, we require the client to write down metric definitions: is sales revenue before or after tax, how are refunds counted, which month do orders that span months belong to? Without clear definitions, even the most polished charts only visualize disagreement.",{"type":59,"text":78,"id":81},{"zh":79,"en":80},"原则三：分层而不是平铺","Principle 3: Layer, Don't Flatten","p3",{"type":50,"text":83},{"zh":84,"en":85},"老板看的是三行数字，一线看的是今天的待办。把所有指标平铺在一屏上，等于什么都没说。","Executives need three lines of numbers; frontline staff need today's to-do list. Flattening every metric onto a single screen says nothing to anyone.",{"type":59,"text":87,"id":90},{"zh":88,"en":89},"原则四：移动端优先","Principle 4: Design for Mobile First","p4",{"type":50,"text":92},{"zh":93,"en":94},"我们统计客户的实际打开场景，超过七成是在手机上看。看板的第一屏必须在竖屏手机上读完——这会倒逼你砍掉一半的指标，而那一半通常本来就不重要。","When we measured where clients actually open their dashboards, over 70% of views were on phones. The first screen must be readable on a phone in portrait mode—which forces you to cut half your metrics, and that half usually wasn't important anyway.",{"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,140,148,153,157,161],{"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":126,"items":127},"list",[128,131,134,137],{"zh":129,"en":130},"软件适配真实流程，而不是让流程迁就软件","Software adapts to real workflows rather than forcing processes to fit the system",{"zh":132,"en":133},"优先接手明确的重复性劳动，而不是堆砌报表","Take over clearly repetitive work first, instead of piling on reports",{"zh":135,"en":136},"系统规模控制在客户团队敢自己动手改的程度","Keep the system small enough that the client's team dares to modify it themselves",{"zh":138,"en":139},"上线后有人可问、有事可管、有版本可升","After launch, someone to talk to, clear ownership, and a path to upgrade",{"type":141,"text":142,"source":145},"quote",{"zh":143,"en":144},"我们不追求把系统做得复杂，而是追求让系统能被用起来、被用下去。","We don't set out to make systems complex. We set out to make them usable—and used for the long haul.",{"zh":146,"en":147},"oaken · 创始人","oaken, Founder",{"type":59,"text":149,"id":152},{"zh":150,"en":151},"我们在做的改变","What We Have Changed","changes",{"type":50,"text":154},{"zh":155,"en":156},"七年间，我们拒绝了相当一部分看起来更赚钱的需求——那些要求在三个月内从零搭建一套完整 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":158},{"zh":159,"en":160},"因此从两年前开始，我们会主动把咨询业务和开发业务分离开来卖：先诊断，再设计，最后才决定要不要做。很多客户在诊断阶段就决定不做了——这对我们是损失，但对他们是节省。","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":162},{"zh":163,"en":164},"接下来的一年，我们会继续把重心放在已经交付客户的系统上：更多的巡检、更快的响应、更小步的迭代。七年不算长，「耗以数载」这件事，我们打算继续做下去。","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":166,"title":167,"category":170,"date":171,"excerpt":172,"author":175,"body":176},"asean-cross-border-digitalization",{"zh":168,"en":169},"广西区位优势下的跨境数字化：从玉林出发","Cross-Border Digitalization from Guangxi: Starting in Yulin","industry","2026-07-05",{"zh":173,"en":174},"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":46,"en":47},[177,181,185,190,194,205,210,214,219,223],{"type":50,"text":178},{"zh":179,"en":180},"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":50,"text":182},{"zh":183,"en":184},"这个项目让我们意识到，跨境数字化的核心问题不是「要不要国际化」，而是「哪些东西必须统一，哪些东西必须分开」。","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":59,"text":186,"id":189},{"zh":187,"en":188},"观察一：主数据要统一，流程要本地化","Observation 1: Standardize Master Data, Localize Processes","obs-1",{"type":50,"text":191},{"zh":192,"en":193},"跨境企业最容易犯的错，是把国内整套系统原样复制一份到海外。结果是编码规则、审批层级、税务口径全部错位。","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":126,"items":195},[196,199,202],{"zh":197,"en":198},"物料编码、客户档案、组织结构保持统一，保证数据可比","Keep material codes, customer records, and organizational structure unified so data stays comparable",{"zh":200,"en":201},"审批流、税务单据、薪酬口径按当地法规与习惯本地化","Localize approval workflows, tax documents, and payroll rules to local regulations and customs",{"zh":203,"en":204},"界面语言、货币、时区在配置层解决，不做代码分支","Handle language, currency, and time zones through configuration, not separate code branches",{"type":59,"text":206,"id":209},{"zh":207,"en":208},"观察二：数据出境要提前设计","Observation 2: Design Cross-Border Data Transfer Upfront","obs-2",{"type":50,"text":211},{"zh":212,"en":213},"我们踩过的坑是：先做了跨境同步，再去补合规。这条路走不通。数据出境的路径、加密方式与审计留痕，必须在架构阶段就确定，而不是上线前找法务补。","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":59,"text":215,"id":218},{"zh":216,"en":217},"观察三：跨境系统的可用性标准要更高","Observation 3: Cross-Border Systems Need Higher Availability Standards","obs-3",{"type":50,"text":220},{"zh":221,"en":222},"网络链路不稳定是跨境环境的常态。系统在设计时就要假设「网络会断」，具备本地缓存与断点续传能力，否则每一次跨国会议都会变成一次故障复盘。","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":50,"text":224},{"zh":225,"en":226},"广西的区位让这件事在物理上更近了一层。对我们来说，这意味着同一个项目团队可以在一天之内同时出现在玉林和越南的现场——这在几年前是不可想象的。","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.",1793453940963]