[{"data":1,"prerenderedAt":695},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-crm-system-selection-guide":106,"article-related-zh-tw-crm-system-selection-guide":677},{"@context":4,"@graph":5},"https:\u002F\u002Fschema.org",[6,85,97],{"@type":7,"@id":8,"name":9,"alternateName":10,"description":17,"knowsAbout":18,"legalName":27,"foundingDate":28,"numberOfEmployees":29,"taxID":30,"url":31,"logo":32,"founder":33,"contactPoint":35,"address":49,"location":55,"sameAs":75},"Organization","https:\u002F\u002Fjoinx.co\u002F#organization","JoinX哲煜科技",[11,12,13,14,15,16],"JoinX","TWJOIN","哲煜科技","哲煜科技股份有限公司","TWJOIN 哲煜科技","twjoin.com","JoinX 哲煜科技（原品牌名 TWJOIN）是 2016 年在台北成立的軟體開發公司，80+ 人自有團隊，承接客製系統、APP、AI 導入與 IoT 開發，以及軟體外包與既有系統接手維運，服務 220+ 客戶、完成 520+ 專案。",[19,20,21,22,23,24,25,26],"軟體外包","客製化系統開發","APP 開發","AI 導入","AI Agent 開發","IoT APP 開發","ERP 系統整合","既有系統接手維運","JoinX Co., Ltd.","2016-04-28",80,"43774383","https:\u002F\u002Fjoinx.co","https:\u002F\u002Fjoinx.co\u002Fimages\u002Flogo-with-name.png",{"@id":34},"https:\u002F\u002Fjoinx.co\u002F#person-jack-lee",[36],{"@type":37,"contactType":38,"url":39,"telephone":40,"email":41,"areaServed":42,"availableLanguage":45},"ContactPoint","customer service","https:\u002F\u002Fjoinx.co\u002Fcontact-us","+886-2-8771-9095","service@joinx.co",[43,44],"TW","JP",[46,47,48],"zh-Hant","en","ja",{"@type":50,"streetAddress":51,"postalCode":52,"addressLocality":53,"addressRegion":54,"addressCountry":43},"PostalAddress","民生東路二段170號8樓","104","台北市中山區","台灣",[56,63,69],{"@type":57,"name":58,"address":59},"Place","JoinX 台中辦公室",{"@type":50,"streetAddress":60,"postalCode":61,"addressLocality":62,"addressRegion":54,"addressCountry":43},"台灣大道二段360號21樓C室","40453","台中市北區",{"@type":57,"name":64,"address":65},"JoinX 高雄辦公室",{"@type":50,"streetAddress":66,"postalCode":67,"addressLocality":68,"addressRegion":54,"addressCountry":43},"民族一路80號2樓之一","807","高雄市三民區",{"@type":57,"name":70,"address":71},"JoinX 東京辦公室",{"@type":50,"streetAddress":72,"postalCode":73,"addressLocality":74,"addressCountry":44},"東五反田5-22-37 Office Circle N 五反田 9樓","141-0022","東京都品川區",[76,77,78,79,80,81,82,83,84],"https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Ftwjoin","https:\u002F\u002Fwww.facebook.com\u002FJoinX.TW","https:\u002F\u002Ftw.linkedin.com\u002Fcompany\u002F%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fwww.youtube.com\u002Fc\u002Fjoinstuido%E5%93%B2%E7%85%9C%E7%A7%91%E6%8A%80","https:\u002F\u002Fmedium.com\u002Ftwjoin","https:\u002F\u002Fwww.104.com.tw\u002Fcompany\u002F1a2x6bjomb","https:\u002F\u002Fclutch.co\u002Fprofile\u002Fjoinx","https:\u002F\u002Fwww.goodfirms.co\u002Fcompany\u002Ftwjoin","https:\u002F\u002Ftwjoin.com",{"@type":86,"@id":34,"name":87,"alternateName":88,"jobTitle":89,"worksFor":90,"url":91,"sameAs":92},"Person","李秉哲","Jack Lee","創辦人暨執行長",{"@id":8},"https:\u002F\u002Fjack88.joinx.co\u002F",[93,94,95,96],"https:\u002F\u002Fwww.instagram.com\u002Fjack88.podcast\u002F","https:\u002F\u002Fwww.threads.net\u002F@jack88.podcast","https:\u002F\u002Fjoinx.co\u002Fjack88\u002F","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjacklee-taiwan\u002F",{"@type":98,"@id":99,"url":31,"name":9,"alternateName":100,"publisher":101,"inLanguage":102},"WebSite","https:\u002F\u002Fjoinx.co\u002F#website",[11,13,9],{"@id":8},[103,104,105],"zh-Hant-TW","en-US","ja-JP",{"id":107,"title":108,"body":109,"category":646,"cover":647,"dateModified":648,"description":649,"extension":650,"faq":648,"hasCoverTitle":651,"locale":652,"meta":653,"navigation":654,"need":143,"path":655,"seo":656,"seoDescription":648,"seoTitle":648,"sources":657,"stem":667,"takeaways":668,"time":674,"type":675,"__hash__":676},"content\u002Fzh-tw\u002Farticle\u002Fcrm-system-selection-guide.md","CRM 系統怎麼選？和 ERP、會員系統的分工、導入順序與費用（2026）",{"type":110,"value":111,"toc":628},"minimark",[112,120,125,128,224,227,231,234,268,277,281,284,346,354,357,361,364,454,462,466,469,540,543,547,550,583,590,592,597,600,604,607,611,614,618,621,625],[113,114,115,119],"p",{},[116,117,118],"strong",{},"選 CRM 之前，先確認你們缺的是不是 CRM。"," 很多企業說要導入 CRM，盤點之後發現真正卡住的是會員點數、訂單對帳，或是客戶資料散在三套系統對不起來。下面先說明 CRM、ERP 與會員系統的分工，再談導入順序、套裝與客製怎麼選，以及費用怎麼估。",[121,122,124],"h2",{"id":123},"crmerp會員系統差在哪","CRM、ERP、會員系統差在哪？",[113,126,127],{},"CRM 管客戶與商機的進度，ERP 管訂單、庫存與帳務，會員系統管消費者的帳號、點數與優惠。三者都會存到「客戶」，但用的人、記錄的事和要回答的問題都不一樣。",[129,130,131,150],"table",{},[132,133,134],"thead",{},[135,136,137,141,144,147],"tr",{},[138,139,140],"th",{},"比較項目",[138,142,143],{},"CRM",[138,145,146],{},"ERP",[138,148,149],{},"會員系統",[151,152,153,168,182,196,210],"tbody",{},[135,154,155,159,162,165],{},[156,157,158],"td",{},"主要使用者",[156,160,161],{},"業務、行銷、客服",[156,163,164],{},"財會、採購、倉儲、生產",[156,166,167],{},"消費者本人，以及行銷與門市",[135,169,170,173,176,179],{},[156,171,172],{},"記錄什麼",[156,174,175],{},"客戶、聯絡紀錄、商機、報價、行銷名單",[156,177,178],{},"訂單、出貨、庫存、應收應付、成本",[156,180,181],{},"會員帳號、消費紀錄、點數、優惠券",[135,183,184,187,190,193],{},[156,185,186],{},"回答的問題",[156,188,189],{},"這個客戶談到哪裡？下個月預計成交多少？",[156,191,192],{},"這筆訂單出貨了嗎？這個月毛利多少？",[156,194,195],{},"這位會員還有多少點？該推什麼優惠？",[135,197,198,201,204,207],{},[156,199,200],{},"常見型態",[156,202,203],{},"後台系統，業務用電腦或手機操作",[156,205,206],{},"後台系統，多部門共用",[156,208,209],{},"會員 APP、LINE 官方帳號、官網會員中心",[135,211,212,215,218,221],{},[156,213,214],{},"客戶類型",[156,216,217],{},"B2B 為主，也用於高單價 B2C",[156,219,220],{},"與客戶類型無關",[156,222,223],{},"B2C 為主",[113,225,226],{},"Gartner 對 CRM 的定義，是用來管理企業與客戶互動、提升客戶關係的策略與系統。重點在「互動與關係」，不在交易本身；交易與帳務是 ERP 的工作，消費者自己看得到的點數與優惠，則是會員系統的工作。",[121,228,230],{"id":229},"該先導入-crmerp-還是會員系統","該先導入 CRM、ERP 還是會員系統？",[113,232,233],{},"先導入哪一套，看客戶資料最常在哪裡斷掉。B2B 業務團隊常斷在「商機進度只在業務腦袋裡」，先缺 CRM；B2C 品牌常斷在「消費者到店和上網是兩個人」，先缺會員系統；訂單與帳對不起來，則先處理 ERP。",[235,236,237,244,250,256,262],"ol",{},[238,239,240,243],"li",{},[116,241,242],{},"列出客戶從接觸到成交、到回購的每一步。"," 每一步寫下現在用什麼工具記錄，例如 Excel、LINE 群組、名片、套裝軟體。",[238,245,246,249],{},[116,247,248],{},"找出資料斷掉的地方。"," 例如業務離職後客戶紀錄跟著消失、門市與官網的會員各算各的、業務報價後財會要重打一次訂單。",[238,251,252,255],{},[116,253,254],{},"算出斷掉的代價。"," 重打資料花多少人時、漏追多少商機、會員重複發了多少優惠。",[238,257,258,261],{},[116,259,260],{},"先補代價最大的那一段。"," 其他系統先維持現狀，之後再透過串接接起來。",[238,263,264,267],{},[116,265,266],{},"指定客戶資料的主要來源。"," 不管最後有幾套系統，同一個客戶只在一個地方新增與修改，其他系統同步。",[113,269,270,271,276],{},"第 5 步最常被忽略。CRM、ERP 與會員系統各自新增客戶，半年後就會出現同一個客戶三種寫法，報表永遠對不起來。串接設計可以參考",[272,273,275],"a",{"href":274},"\u002Fsystem-integration-api\u002F","系統整合與 API","的做法。",[121,278,280],{"id":279},"套裝-crm-和客製-crm-怎麼選","套裝 CRM 和客製 CRM 怎麼選？",[113,282,283],{},"銷售流程跟多數同業相近、想快點開始用時，套裝 CRM 比較省；套裝夠用、只差串接時，保留套裝補串接；流程特殊、要串很多既有系統，或資料必須留在自己主機時，才值得客製。",[129,285,286,302],{},[132,287,288],{},[135,289,290,293,296,299],{},[138,291,292],{},"做法",[138,294,295],{},"適合",[138,297,298],{},"費用怎麼算",[138,300,301],{},"要注意",[151,303,304,318,332],{},[135,305,306,309,312,315],{},[156,307,308],{},"套裝 CRM",[156,310,311],{},"銷售流程跟多數同業相近，想快點開始用",[156,313,314],{},"依使用人數按月或按年訂閱",[156,316,317],{},"欄位與流程要配合軟體，資料匯出與串接能力要先確認",[135,319,320,323,326,329],{},[156,321,322],{},"套裝 CRM＋客製串接",[156,324,325],{},"套裝夠用，只差和 ERP、官網或 LINE 的資料串接",[156,327,328],{},"每個整合點約 NT$5 萬至 20 萬",[156,330,331],{},"要看套裝 CRM 的 API 開放程度，訂閱費持續支付",[135,333,334,337,340,343],{},[156,335,336],{},"客製 CRM",[156,338,339],{},"流程特殊、要串很多既有系統，或資料要留在自己主機",[156,341,342],{},"小範圍 NT$15 萬起，依功能與串接數量估價",[156,344,345],{},"需求定義最花時間，建議分段上線；原始碼與文件歸屬寫進合約",[113,347,348,349,353],{},"比較時用同一個期間，例如 3 年，把訂閱費、串接費、開發費與維運費加總。套裝 CRM 的人數越多、年數越長，訂閱費累積越可觀；客製 CRM 前期投入較高，但不會隨人數增加。ERP 也有同樣的取捨，可以參考 ",[272,350,352],{"href":351},"\u002Farticle\u002Ferp-selection-packaged-vs-custom\u002F","ERP 怎麼選","。",[355,356],"article-cta",{},[121,358,360],{"id":359},"客製-crm-要多少錢","客製 CRM 要多少錢？",[113,362,363],{},"依 JoinX 公開的 2026 年台灣客製專案行情，需求梳理約 NT$10 萬至 30 萬，小型業務管理工具 NT$15 萬起，單一流程 CRM 約 NT$50 萬至 100 萬，每串接一個外部系統約 NT$5 萬至 20 萬，多部門共用的 CRM 依功能與串接數量估價。",[129,365,366,382],{},[132,367,368],{},[135,369,370,373,376,379],{},[138,371,372],{},"範圍",[138,374,375],{},"費用區間",[138,377,378],{},"常見內容",[138,380,381],{},"時程",[151,383,384,398,412,426,440],{},[135,385,386,389,392,395],{},[156,387,388],{},"需求梳理",[156,390,391],{},"NT$10 萬至 30 萬",[156,393,394],{},"盤點銷售流程與客戶資料，產出可比較的規格",[156,396,397],{},"2 至 4 週",[135,399,400,403,406,409],{},[156,401,402],{},"小型業務管理工具",[156,404,405],{},"NT$15 萬起",[156,407,408],{},"在既有系統或 Excel 旁補客戶、商機或日報其中一段",[156,410,411],{},"依範圍",[135,413,414,417,420,423],{},[156,415,416],{},"單一流程 CRM",[156,418,419],{},"NT$50 萬至 100 萬",[156,421,422],{},"客戶、商機、報價追蹤與基本報表",[156,424,425],{},"3 至 5 個月",[135,427,428,431,434,437],{},[156,429,430],{},"多部門 CRM",[156,432,433],{},"依功能與串接數量估價",[156,435,436],{},"業務、行銷與客服共用，含權限分層、行銷分群與多個串接",[156,438,439],{},"分段上線",[135,441,442,445,448,451],{},[156,443,444],{},"串接一個外部系統",[156,446,447],{},"每個整合點 NT$5 萬至 20 萬",[156,449,450],{},"ERP、會計、官網表單、LINE 或電商其中一個系統的資料同步",[156,452,453],{},"依對方 API 開放程度",[113,455,456,457,461],{},"第三方服務（簡訊、EDM、LINE 訊息）與雲端主機費用另計，上線後的維運另訂合約。完整說明見",[272,458,460],{"href":459},"\u002Fcrm-system\u002F","客製 CRM 開發","頁。",[121,463,465],{"id":464},"導入-crm-最常失敗在哪裡","導入 CRM 最常失敗在哪裡？",[113,467,468],{},"最常見的失敗不是系統做不出來，而是業務不用。欄位太多、流程跟實際做法不一樣、輸入比原本的 Excel 還麻煩，業務就會繼續用自己的方式記，系統裡的資料越來越少。",[129,470,471,483],{},[132,472,473],{},[135,474,475,478,481],{},[138,476,477],{},"常見問題",[138,479,480],{},"結果",[138,482,292],{},[151,484,485,496,507,518,529],{},[135,486,487,490,493],{},[156,488,489],{},"一次把所有功能做完",[156,491,492],{},"上線時程拉長，業務還沒用就要改",[156,494,495],{},"先上線客戶與商機管理，用一段時間再加行銷與報表",[135,497,498,501,504],{},[156,499,500],{},"照主管想看的報表設計欄位",[156,502,503],{},"業務要填的欄位太多，乾脆不填",[156,505,506],{},"先問業務每天會記什麼，報表從這些資料長出來",[135,508,509,512,515],{},[156,510,511],{},"舊資料直接匯入",[156,513,514],{},"重複客戶、錯誤資料一起帶進新系統",[156,516,517],{},"先統一欄位、合併重複，再分批匯入並核對",[135,519,520,523,526],{},[156,521,522],{},"權限沒有分層",[156,524,525],{},"客戶資料外流風險高，主管也不敢開放",[156,527,528],{},"依部門、區域與角色設定能看的客戶與欄位",[135,530,531,534,537],{},[156,532,533],{},"行銷名單沒有同意紀錄",[156,535,536],{},"發送行銷訊息時有個資爭議",[156,538,539],{},"記錄客戶同意的範圍與時間，退訂要能即時生效",[113,541,542],{},"最後一點和《個人資料保護法》有關：蒐集客戶資料要告知目的，用於行銷時要在告知範圍內，客戶表示拒絕後就要停止。權限設計則可以對照 ISO\u002FIEC 27001 的存取控制要求，敏感欄位遮罩、操作留下紀錄。",[121,544,546],{"id":545},"joinx-做過哪些-crm-與會員相關專案","JoinX 做過哪些 CRM 與會員相關專案？",[113,548,549],{},"JoinX 做過的客戶經營類專案，有獨立的行銷系統，也有在平台或 APP 裡串接 CRM、整合會員資料的做法。共同點是依實際流程設計，先上線最常用的一段，再分階段擴充。",[551,552,553,559,565,571,577],"ul",{},[238,554,555,558],{},[116,556,557],{},"凱基證券："," 投資教育平台，包含課程、直播與任務積分，並與 CRM 串接，讓學習行為回到客戶經營。",[238,560,561,564],{},[116,562,563],{},"萬事通理財顧問："," 依理財顧問公司的需求，客製開發行銷系統。",[238,566,567,570],{},[116,568,569],{},"中華汽車："," 負責車主 APP，並整併車主服務相關系統。",[238,572,573,576],{},[116,574,575],{},"微星："," msi 會員 APP 的開發與維運。",[238,578,579,582],{},[116,580,581],{},"某融資公司："," 會員平台的開發。",[113,584,585,586,353],{},"CRM 和會員資料常常要一起規劃：業務端看到的客戶，和會員 APP 裡的消費者，最好能對到同一筆資料。會員系統的做法可以參考",[272,587,589],{"href":588},"\u002Farticle\u002Fmembership-community-system-development\u002F","會員與社群系統開發",[121,591,477],{"id":477},[593,594,596],"h3",{"id":595},"中小企業需要-crm-嗎","中小企業需要 CRM 嗎？",[113,598,599],{},"看業務人數與客戶數量。業務只有一兩位、客戶不多時，共用的 Excel 也能管；業務超過三四位、商機進度要開會才知道，或業務離職會帶走客戶紀錄時，就值得導入 CRM。可以先用套裝 CRM 試用，確認流程後再決定要不要客製。",[593,601,603],{"id":602},"crm-可以和-erp-串接嗎","CRM 可以和 ERP 串接嗎？",[113,605,606],{},"可以。常見做法是 CRM 成交後把訂單送進 ERP，ERP 再把出貨與帳款狀態回傳給 CRM，業務不用另外問財會。串接前要先決定客戶主檔以哪一邊為準，以及對方系統有沒有開放 API；沒有 API 時也能用檔案交換，但要先評估穩定性。",[593,608,610],{"id":609},"已經有會員系統還需要-crm-嗎","已經有會員系統，還需要 CRM 嗎？",[113,612,613],{},"看會員系統解決的是誰的問題。會員系統主要服務消費者，處理點數與優惠；如果還有業務團隊在追企業客戶、經銷商或高單價客戶的商機，就需要 CRM。兩者並存時，要讓同一個客戶對到同一筆資料。",[593,615,617],{"id":616},"客製-crm-要做多久","客製 CRM 要做多久？",[113,619,620],{},"單一流程的 CRM 約 3 至 5 個月。建議分階段上線：先上線客戶與商機管理，讓業務用一段時間，再加行銷分群、報表與串接，每個階段都有可以驗收的成果。",[593,622,624],{"id":623},"excel-或名片裡的客戶資料可以匯入-crm-嗎","Excel 或名片裡的客戶資料可以匯入 CRM 嗎？",[113,626,627],{},"可以。匯入前先統一欄位與格式，合併重複客戶、清掉錯誤資料，再分批匯入並核對。上線初期可以新舊並行，確認資料對得上再切換。",{"title":629,"searchDepth":630,"depth":630,"links":631},"",2,[632,633,634,635,636,637,638],{"id":123,"depth":630,"text":124},{"id":229,"depth":630,"text":230},{"id":279,"depth":630,"text":280},{"id":359,"depth":630,"text":360},{"id":464,"depth":630,"text":465},{"id":545,"depth":630,"text":546},{"id":477,"depth":630,"text":477,"children":639},[640,642,643,644,645],{"id":595,"depth":641,"text":596},3,{"id":602,"depth":641,"text":603},{"id":609,"depth":641,"text":610},{"id":616,"depth":641,"text":617},{"id":623,"depth":641,"text":624},"技術分享","\u002Fimages\u002Fblog\u002Fcrm-system-selection-guide.webp",null,"CRM（客戶關係管理系統）管的是「客戶與商機」，ERP 管的是「訂單、庫存與帳務」，會員系統管的是「消費者的帳號、點數與優惠」。三者常被混為一談，結果買了 CRM 卻發現真正缺的是會員系統，或是三套系統各存一份客戶資料。本文說明三者怎麼分工、該先導入哪一套、套裝與客製 CRM 怎麼選，以及費用由哪些項目組成。","md",false,"zh-tw",{},true,"\u002Fzh-tw\u002Farticle\u002Fcrm-system-selection-guide",{"title":108,"description":649},[658,661,664],{"name":659,"issuer":660},"Customer Relationship Management (CRM)（Gartner Glossary）","Gartner",{"name":662,"issuer":663},"個人資料保護法","法務部（全國法規資料庫）",{"name":665,"issuer":666},"ISO\u002FIEC 27001:2022 Information security management systems","國際標準化組織（ISO）","zh-tw\u002Farticle\u002Fcrm-system-selection-guide",[669,670,671,672,673],"CRM 管客戶與商機，ERP 管訂單、庫存與帳務，會員系統管消費者的帳號、點數與優惠，三者處理的是不同的問題。","B2B 業務團隊多半先缺 CRM，B2C 品牌多半先缺會員系統；先導入哪一套，看客戶資料最常在哪裡斷掉。","不管導入幾套系統，客戶資料要先指定一個主要來源，其他系統透過串接同步，避免各存一份。","銷售流程跟同業相近時先用套裝 CRM；流程特殊、要串很多既有系統，或資料要留在自己主機時才值得客製。","依 JoinX 公開的 2026 年行情，客製小型業務管理工具 NT$15 萬起，單一流程 CRM 約 NT$50 萬至 100 萬。","2026\u002F11\u002F10","blog","af9hGqfoHr5mZ-Oe92obSNF3ipFI96vcINgoFFTR3CQ",[678,684,689],{"slug":679,"title":680,"time":681,"cover":682,"need":683},"pos-system-guide","POS 系統怎麼選？套裝、雲端 POS 與客製 POS 的差異、硬體、串接與費用（2026）","2026\u002F11\u002F12","\u002Fimages\u002Fblog\u002Fpos-system-guide.webp","POS 系統",{"slug":685,"title":686,"time":674,"cover":687,"need":688},"ai-customer-service-voice-agent","AI 語音客服怎麼導入？Voice Agent 的架構、適合場景、廠商評估與費用","\u002Fimages\u002Fblog\u002Fai-customer-service-voice-agent.webp","AI 客服",{"slug":690,"title":691,"time":692,"cover":693,"need":694},"enterprise-rag-knowledge-base","企業 RAG 知識庫怎麼做？資料準備、權限、準確率與費用","2026\u002F11\u002F06","\u002Fimages\u002Fblog\u002Fenterprise-rag-knowledge-base.webp","知識庫查詢",1794558635496]