[{"data":1,"prerenderedAt":602},["ShallowReactive",2],{"navigation-en":3,"uslugi-slug-en-code-audit-and-project-takeover":87,"language-switcher-\u002Fen\u002Fservices\u002Fcode-audit-and-project-takeover":597},{"services":4,"industries":48,"caseStudies":69},[5,10,14,19,23,27,31,35,39,43],{"slug":6,"navLabel":7,"navGroup":8,"heroHeadline":9},"web-applications","Web applications","build","A web application built around your process",{"slug":11,"navLabel":12,"navGroup":8,"heroHeadline":13},"erp-systems","ERP systems","An ERP system built for your company, not the other way round",{"slug":15,"navLabel":16,"navGroup":17,"heroHeadline":18},"integrations-and-api","Integrations and APIs","improve","Your systems stop being islands",{"slug":20,"navLabel":21,"navGroup":17,"heroHeadline":22},"ai-implementation","AI implementation","AI deployed where it actually saves time",{"slug":24,"navLabel":25,"navGroup":17,"heroHeadline":26},"process-automation","Process automation","Work no one should be doing by hand",{"slug":28,"navLabel":29,"navGroup":8,"heroHeadline":30},"websites","Websites","A site that loads instantly and brings in inquiries",{"slug":32,"navLabel":33,"navGroup":8,"heroHeadline":34},"mobile-applications","Mobile applications","One codebase, both platforms",{"slug":36,"navLabel":37,"navGroup":17,"heroHeadline":38},"code-audit-and-project-takeover","Code audit and takeover","The project stalled. We'll take it over and tell you the truth about its condition",{"slug":40,"navLabel":41,"navGroup":17,"heroHeadline":42},"maintenance-and-support","Maintenance and support","A system needs someone watching it after launch",{"slug":44,"navLabel":45,"navGroup":46,"heroHeadline":47},"discovery-workshop","Discovery workshop","start","Before you decide to build, find out exactly what you're building",[49,53,57,61,65],{"slug":50,"navLabel":51,"heroHeadline":52},"manufacturing","Manufacturing","The works order reaches the floor as a printout from an email",{"slug":54,"navLabel":55,"heroHeadline":56},"automotive","Automotive","The customer exists in three places at once",{"slug":58,"navLabel":59,"heroHeadline":60},"industrial-automation","Industrial automation","You sell competence that doesn't photograph",{"slug":62,"navLabel":63,"heroHeadline":64},"e-commerce","E-commerce","The shop works. What sits behind it comes apart",{"slug":66,"navLabel":67,"heroHeadline":68},"logistics","Transport and logistics","The job arrives by email, the status comes back by phone",[70,77,82],{"slug":71,"client":72,"tag":73,"year":74,"summary":75,"image":76},"dss-by-caredo","Caredo","Product",2025,"We build the whole DSS product together with the Caredo team — from the CRM and planner to the software behind the key lockers and totems.","\u002Fimg\u002Fcase-studies\u002Fdss\u002Fkluczykomat\u002Fframe_0169.webp",{"slug":78,"client":72,"tag":79,"year":74,"summary":80,"image":81},"dss-by-caredo-website","Product website","We built the DSS product website end to end — from design to launch — on Caredo's visual identity.","\u002Fimg\u002Fscreenshots\u002Fdss-desktop.jpg",{"slug":83,"client":83,"tag":84,"year":74,"summary":85,"image":86},"2motion","Brand and website","A whole brand from scratch — logo, colours, business cards — a company website and blog posts that position 2motion in search.","\u002Fimg\u002Fscreenshots\u002F2motion-desktop.jpg",{"service":88,"relatedCase":203,"relatedPosts":319,"i18nSlugs":594,"subServices":596},{"id":89,"title":90,"audience":91,"body":95,"description":124,"extension":125,"faq":126,"heroHeadline":38,"heroSubline":139,"keyword":140,"meta":141,"navGroup":17,"navLabel":37,"navigation":142,"order":143,"path":144,"pricingModels":145,"process":155,"relatedCase":71,"relatedPosts":172,"scope":174,"seo":190,"sitemap":191,"slug":36,"stem":201,"__hash__":202},"servicesEn\u002Fservices\u002Fcode-audit-and-project-takeover.md","Code audit and project takeover",[92,93,94],"Companies that parted ways with their team, left with code nobody understands","Boards facing an investment decision, needing an independent technical assessment","Product owners where every release breaks something else",{"type":96,"value":97,"toc":117},"minimark",[98,103,107,110,114],[99,100,102],"h2",{"id":101},"the-most-common-findings","The most common findings",[104,105,106],"p",{},"No backups, or backups nobody has ever restored. Production keys committed to the repository. Dependencies untouched for years, with publicly known vulnerabilities. Deployment done by hand by one person, who has since left.",[104,108,109],{},"None of it is a death sentence. All of it is fixable — provided someone names it first.",[99,111,113],{"id":112},"when-we-recommend-a-rewrite","When we recommend a rewrite",[104,115,116],{},"Rarely, and only when the cost of getting the existing code to a state where it can be changed safely exceeds the cost of writing it from scratch. In practice that usually means: no tests whatsoever, unsupported technology, and an architecture that makes any change impossible without rewriting half the system.",{"title":118,"searchDepth":119,"depth":119,"links":120},"",3,[121,123],{"id":101,"depth":122,"text":102},2,{"id":112,"depth":122,"text":113},"We take over development from another vendor. We start with a code and infrastructure audit that says plainly what can be saved and what needs to be rewritten.","md",[127,130,133,136],{"q":128,"a":129},"What if the previous vendor won't hand over access?","It happens more often than it should. We help reconstruct the infrastructure from what's available and flag what's missing. It's worth checking in advance whose accounts the domain, hosting and repository sit on — that's the most common flashpoint.",{"q":131,"a":132},"Is the audit unbiased if you want to take the project over yourselves?","A fair question. That's why the audit can be bought separately and used with any vendor. A recommendation to rewrite is financially better for us, so when we recommend extending the existing code — which is what we do most often — that goes against our own short-term interest.",{"q":134,"a":135},"How long does it take to get up to speed on someone else's code?","For a mid-sized project with any documentation at all, 2–3 weeks to the first safe changes. With no tests and no documentation, it can take twice as long.",{"q":137,"a":138},"What do I get in the report?","A risk list ranked by the cost of ignoring each one, a code and infrastructure quality assessment, a list of security vulnerabilities, and a recommendation with costs for both options. Written so the board can understand it, with a technical appendix for developers.","When the relationship with the previous vendor ends, the first question isn't \"how much to fix this\" — it's \"what is even here.\"","taking over a project from a software house",{},true,8,"\u002Fservices\u002Fcode-audit-and-project-takeover",[146,149,152],{"name":147,"body":148},"Audit only, fixed price","From PLN 12k net. Ends with a report that's yours to keep and doesn't commit you to further work with us.",{"name":150,"body":151},"Audit with takeover","The audit cost is credited against the first month of development.",{"name":153,"body":154},"Development after takeover","Time & material or an SLA retainer, depending on the pace of change.",[156,160,164,168],{"step":157,"duration":158,"body":159},"Access and first review","2–3 days","Repository, infrastructure, documentation. This stage alone often surfaces the most serious risks.",{"step":161,"duration":162,"body":163},"The audit itself","1–2 weeks","Code and infrastructure analysis, ending in a report with a risk list and a recommendation.",{"step":165,"duration":166,"body":167},"Report walkthrough","1 meeting","We go through the findings and agree a plan together. You can stop here and use the report elsewhere.",{"step":169,"duration":170,"body":171},"Takeover","2–6 weeks","Stabilisation, cleaning up deployments, and settling into a normal development rhythm.",[173],"dedykowany-erp-czy-gotowy-system",[175,178,181,184,187],{"title":176,"body":177},"Code audit","Quality, technical debt, test coverage, dependency freshness and security vulnerabilities. With a risk list ranked by the cost of leaving each one unaddressed.",{"title":179,"body":180},"Infrastructure audit","Where it runs, who has access, what deployment looks like, whether backups exist, and whether anyone has ever confirmed they can be restored.",{"title":182,"body":183},"Takeover feasibility assessment","How long it'll take a new team to get up to speed, and what needs doing first to ship changes safely.",{"title":185,"body":186},"Recommendation: extend or rewrite","With a cost comparison of both options. Rewriting is sometimes cheaper, but far less often than first impressions suggest.",{"title":188,"body":189},"Takeover and stabilisation","Cleaning up deployments, adding tests in the riskiest spots, and taking over ongoing development.",{"title":90,"description":124},{"loc":192,"alternatives":193},"\u002Fen\u002Fservices\u002Fcode-audit-and-project-takeover",[194,197,199],{"hreflang":195,"href":196},"x-default","\u002Fuslugi\u002Faudyt-i-przejecie-projektu",{"hreflang":198,"href":196},"pl-PL",{"hreflang":200,"href":192},"en-US","services\u002Fcode-audit-and-project-takeover","EWZzpaLCzH7LvPyTizItdvW_unSDmE9ObjaWmOKwDvo",{"id":204,"title":205,"body":206,"challenge":271,"client":72,"description":272,"extension":125,"features":273,"meta":280,"navigation":142,"order":281,"path":282,"relatedServices":283,"results":284,"screenshotDesktop":76,"screenshotMobile":288,"seo":289,"sequence":290,"sitemap":293,"slug":71,"solution":300,"stack":301,"stem":306,"summary":75,"tag":73,"url":307,"usedBy":308,"year":74,"__hash__":318},"caseStudiesEn\u002Fcase-studies\u002Fdss-by-caredo.md","DSS by Caredo — a product we build together with the Caredo team",{"type":96,"value":207,"toc":265},[208,212,215,218,222,238,245,249,252,256],[99,209,211],{"id":210},"starting-point","Starting point",[104,213,214],{},"DSS (Digital Service Station) is a system for car dealerships and service centres that takes the customer from the moment they pull into the car park to the moment they collect their car. A totem greets them and shows them where to park, a key locker takes the key without the front desk, a parts dispenser hands a mechanic the parts for a specific work order.",[104,216,217],{},"Each of those devices only makes sense if it knows who the customer is and which work order is in progress. That is the software's job — and that is the part we build together with Caredo.",[99,219,221],{"id":220},"what-we-build-together","What we build together",[104,223,224,225,229,230,233,234,237],{},"A ",[226,227,228],"strong",{},"CRM"," where the customer, their history and their work orders are one record. A ",[226,231,232],{},"planner"," where the schedule of visits and work orders is made. A ",[226,235,236],{},"key handover system",": the customer drops off or collects a key at any hour, and the system assigns it to the work order and logs every operation on its own.",[104,239,240,241,244],{},"On top of that, ",[226,242,243],{},"device integrations"," — external and internal key lockers, the parts dispenser, the tool dispenser and the parking totem — so that each one is part of a single process rather than a separate machine with its own database.",[99,246,248],{"id":247},"device-interfaces-for-brands","Device interfaces for brands",[104,250,251],{},"A Porsche customer shouldn't see the same key-locker screen as a Kia customer. For Mercedes-Benz, Porsche, Toyota and Kia dealers we build device interfaces in each brand's identity — screens the customer uses alone, with no member of staff beside them, so they have to make sense from the first touch.",[99,253,255],{"id":254},"how-we-work-together","How we work together",[104,257,258,259,264],{},"We're not the vendor of a single module. We work with the Caredo team on the whole product: when a new device is designed, its software and its integration with the rest of the system are built alongside it, not after the fact. The product website, dssbycaredo.com, we built separately — it's a ",[260,261,263],"a",{"href":262},"\u002Fen\u002Fcase-studies\u002Fdss-by-caredo-website","separate case study",".",{"title":118,"searchDepth":119,"depth":119,"links":266},[267,268,269,270],{"id":210,"depth":122,"text":211},{"id":220,"depth":122,"text":221},{"id":247,"depth":122,"text":248},{"id":254,"depth":122,"text":255},"Caredo designs devices for dealerships and service centres: key lockers, parts dispensers, parking totems. The hardware is half the product. The other half is the software that connects each device to the customer, the work order and the service team — and that has to look like the brand's showroom, not like a technical panel.","Together with the Caredo team we build the whole DSS product: the CRM, the planner, the key handover system, the integrations of the devices on site and the device interfaces for Mercedes-Benz, Porsche, Toyota and Kia dealers.",[274,275,276,277,278,279],"A CRM with customer history, work orders and permissions per branch and role","A planner for visits and service orders","A 24\u002F7 key drop-off and pickup system that assigns each key to its work order","Integrations for the key lockers, parts and tool dispensers and the parking totem","Customer-facing device interfaces in Mercedes-Benz, Porsche, Toyota and Kia identity","An analytics dashboard with real-time data",{},1,"\u002Fcase-studies\u002Fdss-by-caredo",[6,15,24],[285],{"metric":286,"label":287},"100%","System uptime",null,{"title":205,"description":272},{"path":291,"frames":292,"poster":76},"\u002Fimg\u002Fcase-studies\u002Fdss\u002Fkluczykomat\u002Fframe_",169,{"loc":294,"alternatives":295},"\u002Fen\u002Fcase-studies\u002Fdss-by-caredo",[296,298,299],{"hreflang":195,"href":297},"\u002Frealizacje\u002Fdss-by-caredo",{"hreflang":198,"href":297},{"hreflang":200,"href":294},"We work as part of the Caredo team: together we build the CRM, the planner, the key drop-off and pickup system and the integrations that bring every device into one system. For Mercedes-Benz, Porsche, Toyota and Kia dealers we design device interfaces in each brand's identity.",[302,303,304,305],"TypeScript","Nuxt","Node.js","PostgreSQL","case-studies\u002Fdss-by-caredo","https:\u002F\u002Fdssbycaredo.com",[309,310,311,312,313,314,315,316,317],"Mercedes-Benz","Porsche","Toyota","Kia","Audi","Cupra","Ford","Škoda","Volkswagen","MS9XoW0yDSBUBi4JOZJ4VQn87W5x7rIKYo99PuI8oSg",[320],{"id":321,"title":322,"author":323,"body":324,"category":578,"date":579,"description":580,"draft":581,"editorialNote":288,"extension":125,"image":582,"meta":583,"navigation":142,"path":584,"rawbody":585,"seo":586,"sitemap":587,"stem":588,"tags":589,"translationKey":592,"updated":288,"__hash__":593},"blogEn\u002Fblog\u002Fdedykowany-erp-czy-gotowy-system.md","Dedicated ERP or off-the-shelf — how to choose","zespol",{"type":96,"value":325,"toc":565},[326,333,336,340,345,348,352,355,359,362,366,369,373,376,470,477,481,500,503,507,513,516,519,523,529,535,541,545,548,555,562],[104,327,328,329,332],{},"The answer is: ",[226,330,331],{},"off-the-shelf, in most cases",". Worth stating up front, since a piece written by a company that builds dedicated systems might be expected to argue the opposite.",[104,334,335],{},"An off-the-shelf ERP wins when your process resembles other companies' in the industry and the budget is limited. Licence plus rollout is then cheaper than building, and the risk is lower. A dedicated system makes sense in a narrower set of situations — and this piece is about recognising when you're in that set.",[99,337,339],{"id":338},"four-deciding-questions","Four deciding questions",[341,342,344],"h3",{"id":343},"_1-is-your-process-a-source-of-advantage","1. Is your process a source of advantage?",[104,346,347],{},"If a company makes money because it does something differently from its competitors, flattening that \"differently\" into a standard module costs more than the licence. If, on the other hand, the process is standard and the advantage lies elsewhere — relationships, price, location — an off-the-shelf system is the right choice.",[341,349,351],{"id":350},"_2-what-does-adapting-the-off-the-shelf-system-cost","2. What does adapting the off-the-shelf system cost?",[104,353,354],{},"This question settles it most often. Ask the vendor for a quote on the modifications you need. If the sum of licence, rollout and modifications approaches the cost of building your own system, the choice stops being obvious — because for the same money you get either an 80%-fit system, or a 100%-fit one.",[341,356,358],{"id":357},"_3-how-many-users-do-you-have","3. How many users do you have?",[104,360,361],{},"A per-user licence changes the maths over time. At twenty people the difference is negligible. At two hundred, over a five-year horizon, it can exceed the cost of building your own system.",[341,363,365],{"id":364},"_4-how-much-will-the-process-change","4. How much will the process change?",[104,367,368],{},"A company in a stable industry, doing the same thing for a decade, fits well into an off-the-shelf system. A company changing its business model every two years will keep fighting limitations that can't be worked around except through the vendor.",[99,370,372],{"id":371},"the-five-year-comparison","The five-year comparison",[104,374,375],{},"Comparing only the rollout cost is misleading. Below is an example for a manufacturing company with 120 users. The figures are illustrative — meant to show the cost structure, not a quote.",[377,378,379,395],"table",{},[380,381,382],"thead",{},[383,384,385,389,392],"tr",{},[386,387,388],"th",{},"Line item",[386,390,391],{},"Off-the-shelf ERP",[386,393,394],{},"Dedicated",[396,397,398,410,421,432,442,453],"tbody",{},[383,399,400,404,407],{},[401,402,403],"td",{},"Rollout \u002F build",[401,405,406],{},"PLN 250k",[401,408,409],{},"PLN 450k",[383,411,412,415,418],{},[401,413,414],{},"Licences over 5 years",[401,416,417],{},"PLN 430k",[401,419,420],{},"0",[383,422,423,426,429],{},[401,424,425],{},"Modifications and extensions",[401,427,428],{},"PLN 180k",[401,430,431],{},"PLN 150k",[383,433,434,436,439],{},[401,435,41],{},[401,437,438],{},"PLN 120k",[401,440,441],{},"PLN 220k",[383,443,444,447,450],{},[401,445,446],{},"Infrastructure",[401,448,449],{},"included in licence",[401,451,452],{},"PLN 90k",[383,454,455,460,465],{},[401,456,457],{},[226,458,459],{},"Total",[401,461,462],{},[226,463,464],{},"PLN 980k",[401,466,467],{},[226,468,469],{},"PLN 910k",[104,471,472,473,476],{},"The takeaway isn't \"dedicated is cheaper.\" It's: ",[226,474,475],{},"at this scale the costs converge, so the decision should be made on a different basis than price",". At thirty users the same table looks completely different, and the off-the-shelf system wins outright.",[99,478,480],{"id":479},"signals-that-an-off-the-shelf-system-has-stopped-fitting","Signals that an off-the-shelf system has stopped fitting",[482,483,484,488,491,494,497],"ul",{},[485,486,487],"li",{},"The team keeps the \"real\" data in a spreadsheet next to the system.",[485,489,490],{},"A key report is produced by exporting to Excel and stitching it together by hand.",[485,492,493],{},"Every process change requires a ticket to the vendor and waits for quarters.",[485,495,496],{},"You're paying for modules nobody ever turned on.",[485,498,499],{},"A new hire is learning less the system than the list of workarounds the team invented.",[104,501,502],{},"One of these signals is normal friction. Three or more mean the cost of the mismatch has exceeded the cost of change.",[99,504,506],{"id":505},"a-third-path-thats-rarely-discussed","A third path that's rarely discussed",[104,508,509,510,264],{},"The choice isn't binary. A common and underrated approach is to ",[226,511,512],{},"keep an off-the-shelf ERP as the finance-and-accounting core and build your own modules where the company is genuinely atypical",[104,514,515],{},"Accounting, HR and payroll are regulated areas where an in-house build is an expense with no return — the rules change every year and someone has to keep up. A production module, or handling a specific sales channel, is exactly where a custom fit pays off.",[104,517,518],{},"The condition is an ERP with a decent API. Without one, this path is closed — and that's an important criterion in choosing an off-the-shelf system that almost nobody asks about before signing.",[99,520,522],{"id":521},"what-not-to-weigh-in-the-decision","What not to weigh in the decision",[104,524,525,528],{},[226,526,527],{},"\"Everyone in the industry has X.\""," Your competitors made that decision at a different scale, in a different year, with a different process.",[104,530,531,534],{},[226,532,533],{},"The sales demo."," Every system looks good in a demo the vendor prepared. Ask for access to a test environment and run your own real case through it — ideally the most unusual one you have.",[104,536,537,540],{},[226,538,539],{},"The promise that \"it'll get configured.\""," Ask who will configure it, how long it'll take, and what a consultant's day costs. The answers are sometimes surprising.",[99,542,544],{"id":543},"how-to-make-this-decision-properly","How to make this decision properly",[104,546,547],{},"Do two things before you choose.",[104,549,550,551,554],{},"First: ",[226,552,553],{},"write down your process as it actually is",", workarounds included. Those workarounds are information about what the previous tool was missing — and the best material for testing candidates.",[104,556,557,558,561],{},"Second: ",[226,559,560],{},"ask both types of vendor to quote the same, written-down scope",". As long as one is quoting a licence and the other a build, the offers aren't comparable.",[104,563,564],{},"Only once you have both of those does the \"dedicated or off-the-shelf\" conversation stop being a matter of opinion and become a calculation.",{"title":118,"searchDepth":119,"depth":119,"links":566},[567,573,574,575,576,577],{"id":338,"depth":122,"text":339,"children":568},[569,570,571,572],{"id":343,"depth":119,"text":344},{"id":350,"depth":119,"text":351},{"id":357,"depth":119,"text":358},{"id":364,"depth":119,"text":365},{"id":371,"depth":122,"text":372},{"id":479,"depth":122,"text":480},{"id":505,"depth":122,"text":506},{"id":521,"depth":122,"text":522},{"id":543,"depth":122,"text":544},"erp","2026-09-02","Decision criteria, a five-year cost comparison, and the signals that tell you an off-the-shelf ERP has stopped fitting your company.",false,"\u002Fimg\u002Fblog\u002Ferp-dedykowany-czy-gotowy.jpg",{},"\u002Fblog\u002Fdedykowany-erp-czy-gotowy-system","---\ntitle: Dedicated ERP or off-the-shelf — how to choose\ndescription: Decision criteria, a five-year cost comparison, and the signals that tell you an off-the-shelf ERP has stopped fitting your company.\ndate: 2026-09-02\ncategory: erp\ntags:\n  - erp\n  - rollouts\n  - decisions\nauthor: zespol\nimage: \u002Fimg\u002Fblog\u002Ferp-dedykowany-czy-gotowy.jpg\ntranslationKey: custom-erp-or-off-the-shelf\ndraft: false\n---\n\nThe answer is: **off-the-shelf, in most cases**. Worth stating up front, since a piece written by a company that builds dedicated systems might be expected to argue the opposite.\n\nAn off-the-shelf ERP wins when your process resembles other companies' in the industry and the budget is limited. Licence plus rollout is then cheaper than building, and the risk is lower. A dedicated system makes sense in a narrower set of situations — and this piece is about recognising when you're in that set.\n\n## Four deciding questions\n\n### 1. Is your process a source of advantage?\n\nIf a company makes money because it does something differently from its competitors, flattening that \"differently\" into a standard module costs more than the licence. If, on the other hand, the process is standard and the advantage lies elsewhere — relationships, price, location — an off-the-shelf system is the right choice.\n\n### 2. What does adapting the off-the-shelf system cost?\n\nThis question settles it most often. Ask the vendor for a quote on the modifications you need. If the sum of licence, rollout and modifications approaches the cost of building your own system, the choice stops being obvious — because for the same money you get either an 80%-fit system, or a 100%-fit one.\n\n### 3. How many users do you have?\n\nA per-user licence changes the maths over time. At twenty people the difference is negligible. At two hundred, over a five-year horizon, it can exceed the cost of building your own system.\n\n### 4. How much will the process change?\n\nA company in a stable industry, doing the same thing for a decade, fits well into an off-the-shelf system. A company changing its business model every two years will keep fighting limitations that can't be worked around except through the vendor.\n\n## The five-year comparison\n\nComparing only the rollout cost is misleading. Below is an example for a manufacturing company with 120 users. The figures are illustrative — meant to show the cost structure, not a quote.\n\n| Line item | Off-the-shelf ERP | Dedicated |\n|---|---|---|\n| Rollout \u002F build | PLN 250k | PLN 450k |\n| Licences over 5 years | PLN 430k | 0 |\n| Modifications and extensions | PLN 180k | PLN 150k |\n| Maintenance and support | PLN 120k | PLN 220k |\n| Infrastructure | included in licence | PLN 90k |\n| **Total** | **PLN 980k** | **PLN 910k** |\n\nThe takeaway isn't \"dedicated is cheaper.\" It's: **at this scale the costs converge, so the decision should be made on a different basis than price**. At thirty users the same table looks completely different, and the off-the-shelf system wins outright.\n\n## Signals that an off-the-shelf system has stopped fitting\n\n- The team keeps the \"real\" data in a spreadsheet next to the system.\n- A key report is produced by exporting to Excel and stitching it together by hand.\n- Every process change requires a ticket to the vendor and waits for quarters.\n- You're paying for modules nobody ever turned on.\n- A new hire is learning less the system than the list of workarounds the team invented.\n\nOne of these signals is normal friction. Three or more mean the cost of the mismatch has exceeded the cost of change.\n\n## A third path that's rarely discussed\n\nThe choice isn't binary. A common and underrated approach is to **keep an off-the-shelf ERP as the finance-and-accounting core and build your own modules where the company is genuinely atypical**.\n\nAccounting, HR and payroll are regulated areas where an in-house build is an expense with no return — the rules change every year and someone has to keep up. A production module, or handling a specific sales channel, is exactly where a custom fit pays off.\n\nThe condition is an ERP with a decent API. Without one, this path is closed — and that's an important criterion in choosing an off-the-shelf system that almost nobody asks about before signing.\n\n## What not to weigh in the decision\n\n**\"Everyone in the industry has X.\"** Your competitors made that decision at a different scale, in a different year, with a different process.\n\n**The sales demo.** Every system looks good in a demo the vendor prepared. Ask for access to a test environment and run your own real case through it — ideally the most unusual one you have.\n\n**The promise that \"it'll get configured.\"** Ask who will configure it, how long it'll take, and what a consultant's day costs. The answers are sometimes surprising.\n\n## How to make this decision properly\n\nDo two things before you choose.\n\nFirst: **write down your process as it actually is**, workarounds included. Those workarounds are information about what the previous tool was missing — and the best material for testing candidates.\n\nSecond: **ask both types of vendor to quote the same, written-down scope**. As long as one is quoting a licence and the other a build, the offers aren't comparable.\n\nOnly once you have both of those does the \"dedicated or off-the-shelf\" conversation stop being a matter of opinion and become a calculation.\n",{"title":322,"description":580},{"loc":584},"blog\u002Fdedykowany-erp-czy-gotowy-system",[578,590,591],"rollouts","decisions","custom-erp-or-off-the-shelf","SGZvpSbYxgHfAtuwEdBGzG6HA0KOjIg3dfXrHzqXe4U",{"pl":595,"en":36},"audyt-i-przejecie-projektu",[],[598],{"code":599,"label":600,"name":601,"to":196},"pl","PL","Polish",1790522544770]