[{"data":1,"prerenderedAt":511},["ShallowReactive",2],{"site-schema":3,"article-zh-tw-staffing-vs-onsite-vs-outsourcing-vs-fdt":106,"article-related-zh-tw-staffing-vs-onsite-vs-outsourcing-vs-fdt":497},{"@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":465,"cover":466,"dateModified":467,"description":468,"extension":469,"faq":467,"hasCoverTitle":470,"locale":471,"meta":472,"navigation":473,"need":474,"path":475,"seo":476,"seoDescription":467,"seoTitle":467,"sources":477,"stem":487,"takeaways":488,"time":494,"type":495,"__hash__":496},"content\u002Fzh-tw\u002Farticle\u002Fstaffing-vs-onsite-vs-outsourcing-vs-fdt.md","人力派遣、駐點、軟體外包、FDT 差在哪？誰負責結果、怎麼計價",{"type":110,"value":111,"toc":447},"minimark",[112,120,125,128,155,164,168,171,296,299,303,306,309,312,316,319,322,330,333,337,340,343,346,373,377,380,383,386,408,411,416,419,423,426,430,433,437,440,444],[113,114,115,119],"p",{},[116,117,118],"strong",{},"人力派遣與駐點買的是工程師的時間，工作由企業自己指揮，結果也由企業負責；軟體外包與 FDT 買的是成果，由廠商負責交付。"," 四種方式沒有絕對的好壞，差別在企業內部有沒有人能帶工程師、需求清不清楚，以及做完之後知識要留在哪裡。",[121,122,124],"h2",{"id":123},"人力派遣駐點軟體外包fdt-各是什麼","人力派遣、駐點、軟體外包、FDT 各是什麼？",[113,126,127],{},"四種都是「找外部的人來做軟體」，但買的東西不同：派遣買的是人，駐點買的是在你公司上班的工程師時間，軟體外包買的是依規格完成的系統，FDT 買的是從找題目到上線的整段成果。",[129,130,131,138,144,149],"ul",{},[132,133,134,137],"li",{},[116,135,136],{},"人力派遣","：派遣公司聘僱工程師，派到企業（要派單位）工作，日常工作由企業指揮。依《勞動基準法》，派遣勞工的雇主是派遣公司，要派單位不得在派遣前面試、指定特定勞工。",[132,139,140,143],{},[116,141,142],{},"駐點","：廠商的工程師到企業辦公室上班，通常依人月計費，做的事由企業的主管安排。實務上常和派遣混用，差別在合約是勞動派遣還是委外服務。",[132,145,146,148],{},[116,147,19],{},"：企業把一個系統委託給廠商開發，廠商依規格交付成果，屬於《民法》的承攬：完成約定的工作後才給付報酬。",[132,150,151,154],{},[116,152,153],{},"FDT（Forward Deployed Team）","：由 PM、設計、前後端與 AI 工程師組成的團隊，進到企業流程裡找題目、做出原型，再做到正式上線與維運，依階段用成果驗收。",[113,156,157,158,163],{},"FDT 和 FDE、AI 顧問的差別，可以參考",[159,160,162],"a",{"href":161},"\u002Farticle\u002Fforward-deployed-engineer-fde-fdt\u002F","FDE 是什麼","；這篇的重點是把它和派遣、駐點放在一起比。",[121,165,167],{"id":166},"四種合作方式差在哪","四種合作方式差在哪？",[113,169,170],{},"最大的差別是誰負責結果。派遣與駐點由企業指揮、企業承擔結果；軟體外包與 FDT 由廠商負責交付。計價方式、知識留存與管理成本，都是從這一點延伸出來的。",[172,173,174,193],"table",{},[175,176,177],"thead",{},[178,179,180,184,186,188,190],"tr",{},[181,182,183],"th",{},"比較項目",[181,185,136],{},[181,187,142],{},[181,189,19],{},[181,191,192],{},"FDT",[194,195,196,214,230,246,262,279],"tbody",{},[178,197,198,202,205,208,211],{},[199,200,201],"td",{},"誰指揮工作",[199,203,204],{},"企業",[199,206,207],{},"企業的主管，廠商負責補人",[199,209,210],{},"廠商依規格安排",[199,212,213],{},"廠商的 PM，和企業窗口一起定題目",[178,215,216,219,221,224,227],{},[199,217,218],{},"誰負責結果",[199,220,204],{},[199,222,223],{},"企業；廠商負責人員到位",[199,225,226],{},"廠商依規格交付",[199,228,229],{},"廠商依階段門檻交付",[178,231,232,235,238,240,243],{},[199,233,234],{},"怎麼計價",[199,236,237],{},"依人月或工時",[199,239,237],{},[199,241,242],{},"固定總價或分階段",[199,244,245],{},"依階段計價，每階段用成果驗收",[178,247,248,251,254,256,259],{},[199,249,250],{},"原始碼與知識怎麼留下",[199,252,253],{},"程式碼在企業，知識在人身上",[199,255,253],{},[199,257,258],{},"依合約交付原始碼與文件",[199,260,261],{},"原始碼、規格與測試文件列進交付範圍",[178,263,264,267,270,273,276],{},[199,265,266],{},"企業的管理成本",[199,268,269],{},"高：要有人分派工作、審程式碼",[199,271,272],{},"高：同派遣，另要管理出勤與座位",[199,274,275],{},"中：寫規格、驗收",[199,277,278],{},"中：派窗口參與找題目與驗收",[178,280,281,284,287,290,293],{},[199,282,283],{},"人員異動的影響",[199,285,286],{},"大，要重新找人與交接",[199,288,289],{},"大，常見交接斷層",[199,291,292],{},"小，由廠商內部接手",[199,294,295],{},"小，同一個團隊延續",[113,297,298],{},"這張表不是說哪一種比較好。內部已經有 PM 與技術主管、只是缺人手時，派遣或駐點最直接；需求清楚、想把結果交給廠商時，軟體外包比較省事；題目還要一起找、做完要長期用時，FDT 比較合適。",[121,300,302],{"id":301},"誰負責結果為什麼這一點最重要","誰負責結果？為什麼這一點最重要？",[113,304,305],{},"因為它決定出問題時找誰。派遣與駐點時，系統做不出來或做錯，責任在企業自己的管理；外包與 FDT 時，廠商要依合約或驗收門檻交付，沒達到就要修到達到為止。",[113,307,308],{},"法律上也是這樣區分。派遣屬於勞動關係，要派單位指揮勞工工作，《勞動基準法》第 63 條之 1 還規定，派遣勞工發生職業災害時，要派單位與派遣公司要負連帶補償責任，所以企業要承擔一部分雇主的管理義務。軟體外包多半屬於《民法》第 490 條的承攬，承攬人要完成約定的工作，定作人在工作完成後給付報酬。",[113,310,311],{},"實務上最容易出問題的，是名義上找外包、實際上卻用派遣的方式管理：企業主管每天直接指揮廠商工程師，規格隨時改，最後交付不如預期時，很難說清楚是誰的責任。合作前先決定「誰指揮、誰負責」，比挑哪一家更重要。",[121,313,315],{"id":314},"怎麼計價哪一種比較省","怎麼計價？哪一種比較省？",[113,317,318],{},"派遣與駐點依人月或工時計價，工作多少就付多少，但產出由企業自己管理；軟體外包多採固定總價或分階段；FDT 依階段計價，每一階段先用成果驗收，再決定要不要投入下一階段。",[113,320,321],{},"哪一種比較省，要看企業自己能不能管好工程師。內部有經驗的技術主管，派遣或駐點的單位成本可能較低；沒有的話，花在溝通、返工與交接上的時間，常常比帳面上的人月費更貴。",[113,323,324,325,329],{},"FDT 的分階段計價以 JoinX 的 AI 導入陪跑為例：PoC 約 NT$30 萬至 80 萬、MVP 約 NT$50 萬至 120 萬、正式上線約 NT$80 萬至 250 萬，跨部門、多系統依範圍估價；AI 模型 API 與雲端費用依用量另計。完整說明見",[159,326,328],{"href":327},"\u002Fai-implementation-team\u002F","AI 導入陪跑團隊","。",[331,332],"article-cta",{},[121,334,336],{"id":335},"原始碼和知識怎麼留下來","原始碼和知識怎麼留下來？",[113,338,339],{},"原始碼要靠合約，知識要靠文件。派遣與駐點寫的程式碼通常在企業的環境裡，但系統為什麼這樣設計，多半只在工程師腦中；人一換，知識就跟著走。外包與 FDT 要把原始碼、規格與測試文件列進交付範圍。",[113,341,342],{},"依《著作權法》第 12 條，出資聘請他人完成的著作，沒有約定時著作財產權歸實際完成的一方，出資人只能使用。所以不論哪一種合作方式，程式碼歸屬都要寫進合約。",[113,344,345],{},"要讓知識留得下來，交付範圍至少要包含：",[347,348,349,355,361,367],"ol",{},[132,350,351,354],{},[116,352,353],{},"原始碼與部署方式","：放在企業可以存取的版本控制，附上部署與環境設定說明。",[132,356,357,360],{},[116,358,359],{},"規格文件","：功能規格、流程與例外情況，說明系統為什麼這樣設計。",[132,362,363,366],{},[116,364,365],{},"測試","：自動化測試與測試案例，讓下一個接手的人改程式時知道有沒有改壞。",[132,368,369,372],{},[116,370,371],{},"交接與培訓","：操作與維護的說明，列進驗收項目，而不是口頭交代。",[121,374,376],{"id":375},"joinx-用哪一種方式合作","JoinX 用哪一種方式合作？",[113,378,379],{},"JoinX 的成員都是自己聘僱的正職團隊，不做人力派遣，也不以駐點方式合作。我們以軟體外包與 FDT 的方式負責交付，需要時會定期到客戶辦公室參與會議，直接和第一線同仁確認需求、討論做法。",[113,381,382],{},"不駐點，不代表不了解現場。訪談、流程觀察與測試會到客戶現場進行，日常開發在 JoinX 內部由同一個團隊完成，這樣 PM、設計與工程師的分工與程式碼審查不會因為人分散在各處而中斷。",[113,384,385],{},"開發時用規格驅動開發（SDD）把流程與例外情況寫清楚，再用測試驅動開發（TDD）確保每次改版都不會破壞既有功能；原始碼與文件同步交付，交接與培訓列入驗收。實際的長期合作例子：",[129,387,388,398],{},[132,389,390,393,394,329],{},[116,391,392],{},"驊曖體育","：瑜伽館管理系統從 2020 年起合作，陸續推出到第九版，上線後由同一個團隊持續維運，詳見",[159,395,397],{"href":396},"\u002Fcase-studies\u002Fwhayoga\u002F","驊曖體育案例",[132,399,400,403,404,329],{},[116,401,402],{},"群益投信","：JoinX 是符合金管會要求標準的資訊委外開發廠商，群益投信的官網、ETF 網站與 APP 都由 JoinX 維護，詳見",[159,405,407],{"href":406},"\u002Fcase-studies\u002Fcapital\u002F","群益投信案例",[121,409,410],{"id":410},"常見問題",[412,413,415],"h3",{"id":414},"駐點工程師和外包工程師有什麼不同","駐點工程師和外包工程師有什麼不同？",[113,417,418],{},"差在誰指揮與誰負責結果。駐點工程師在企業辦公室上班，工作由企業主管安排，結果由企業負責；外包工程師由廠商安排工作，廠商依規格對交付的系統負責。實務上兩者常被混用，簽約前要確認合約的性質。",[412,420,422],{"id":421},"軟體專案可以用派遣的方式做嗎","軟體專案可以用派遣的方式做嗎？",[113,424,425],{},"可以，但前提是企業內部有能帶工程師的 PM 與技術主管。派遣工程師由企業指揮，需求怎麼拆、程式碼怎麼審、品質怎麼把關，都要企業自己負責；沒有這些角色時，外包或 FDT 通常比較穩。",[412,427,429],{"id":428},"fdt-也要每天待在客戶公司嗎","FDT 也要每天待在客戶公司嗎？",[113,431,432],{},"不一定。FDT 的重點是開發的人直接接觸資料與第一線人員，訪談與測試可以到現場，日常開發可以在團隊內部進行。JoinX 不以駐點方式合作，但會定期到客戶辦公室開會、直接確認需求。",[412,434,436],{"id":435},"派遣或駐點的工程師離職了系統怎麼辦","派遣或駐點的工程師離職了，系統怎麼辦？",[113,438,439],{},"要看文件與程式碼有沒有留好。程式碼在企業的版本控制裡、規格與測試文件齊全時，新的工程師或廠商可以接手；如果知識只在離職的人身上，接手前通常要先盤點程式碼與架構，再決定怎麼維護。",[412,441,443],{"id":442},"從駐點改成外包或-fdt要怎麼轉換","從駐點改成外包或 FDT，要怎麼轉換？",[113,445,446],{},"先盤點現有系統的程式碼、文件與進行中的需求，把這段交接列成一個階段，再由新的團隊依規格或階段門檻接手。轉換期可以安排新舊人員重疊一段時間，避免知識在交接時斷掉。",{"title":448,"searchDepth":449,"depth":449,"links":450},"",2,[451,452,453,454,455,456,457],{"id":123,"depth":449,"text":124},{"id":166,"depth":449,"text":167},{"id":301,"depth":449,"text":302},{"id":314,"depth":449,"text":315},{"id":335,"depth":449,"text":336},{"id":375,"depth":449,"text":376},{"id":410,"depth":449,"text":410,"children":458},[459,461,462,463,464],{"id":414,"depth":460,"text":415},3,{"id":421,"depth":460,"text":422},{"id":428,"depth":460,"text":429},{"id":435,"depth":460,"text":436},{"id":442,"depth":460,"text":443},"技術分享","\u002Fimages\u002Fblog\u002Fstaffing-vs-onsite-vs-outsourcing-vs-fdt.webp",null,"人力派遣與駐點買的是工程師的時間，工作由企業自己指揮，結果也由企業負責；軟體外包買的是依規格完成的系統，由廠商負責交付；FDT（Forward Deployed Team）則是由一整個團隊從找題目做到上線，依階段計價、用成果驗收。本文用一張對照表比較四種合作方式在誰負責結果、怎麼計價、原始碼和知識怎麼留下、企業要花多少管理成本上的差異，並說明各自適合的情況。","md",false,"zh-tw",{},true,"客製化系統","\u002Fzh-tw\u002Farticle\u002Fstaffing-vs-onsite-vs-outsourcing-vs-fdt",{"title":108,"description":468},[478,481,484],{"name":479,"issuer":480},"《勞動基準法》第 17 條之 1、第 63 條之 1（派遣勞工保護）","勞動部",{"name":482,"issuer":483},"《民法》第 490 條（承攬）","法務部",{"name":485,"issuer":486},"《著作權法》第 12 條","經濟部智慧財產局","zh-tw\u002Farticle\u002Fstaffing-vs-onsite-vs-outsourcing-vs-fdt",[489,490,491,492,493],"人力派遣與駐點買的是工程師的時間，由企業指揮工作、承擔結果；軟體外包與 FDT 買的是成果，由廠商負責交付。","派遣與駐點多半依人月或工時計價，軟體外包依固定總價或分階段計價，FDT 依階段計價、每階段用成果驗收。","派遣與駐點的知識留在人身上，人一換就容易斷；外包與 FDT 要把原始碼、規格與測試文件列進交付範圍，知識才留得下來。","企業內部已有 PM 與技術主管、只缺人手時，派遣或駐點最直接；規格清楚時找軟體外包；題目還要一起找、做完要長期用時，FDT 比較合適。","JoinX 不做人力派遣、也不以駐點方式合作，但會定期到客戶辦公室開會，直接和第一線同仁確認需求。","2026\u002F11\u002F04","blog","oc_M0cokSLMihXtYB9Os6p-GNRPBcWlwwToFN7GBWEk",[498,503,507],{"slug":499,"title":500,"time":501,"cover":502,"need":474},"financial-system-development-guide","金融業系統委外開發怎麼選？投信、銀行的資訊委外規範與廠商檢核重點","2026\u002F11\u002F06","\u002Fimages\u002Fblog\u002Ffinancial-system-development-guide.webp",{"slug":504,"title":505,"time":494,"cover":506,"need":474},"admin-backoffice-system-development","後台管理系統開發：模組、權限、費用與驗收","\u002Fimages\u002Fblog\u002Fadmin-backoffice-system-development.webp",{"slug":508,"title":509,"time":494,"cover":510,"need":474},"custom-system-development-types-cost-cases","客製化系統開發：適合誰、有哪些類型、費用與台灣案例","\u002Fimages\u002Fblog\u002Fcustom-system-development-types-cost-cases.webp",1794558645014]