[{"data":1,"prerenderedAt":47},["Reactive",2],{"blog-inspiration-building-is-cheap-owning-isnt":3},{"id":4,"status":5,"approved":6,"type":7,"publication_date":8,"feature_image":9,"show_circle_in_top_image":6,"tags":10,"top_background_color":11,"top_text_color":12,"logo":10,"use_case_categories":10,"translations":13,"author":33,"blog_id":16,"language_code":26,"title":27,"slug":28,"summary":20,"excerpt":29,"content":30,"extra_info":46,"result_highlights":10,"region":10,"industry":10,"company_type":10,"integrations":10,"key_features":10,"meta_title":31,"meta_description":32,"faqs":46,"partner_image":10,"partner_biography":10,"partner_author":10},821,"published",true,"inspiration","2026-09-17T12:00:00","/images/cms/bd156feb-8c4f-41c2-8534-e76bb59a210f.png",null,"#090049","#FFFFFF",[14,25],{"id":15,"blog_id":16,"language_code":17,"title":18,"slug":19,"summary":20,"excerpt":21,"content":22,"extra_info":10,"result_highlights":10,"region":10,"industry":10,"company_type":10,"integrations":10,"key_features":10,"meta_title":23,"meta_description":24,"faqs":10,"partner_image":10,"partner_biography":10,"partner_author":10},820,535,"nl","Bouwen is goedkoop geworden. Bezitten niet.","bouwen-is-goedkoop-bezitten-niet","\u003Cp>-\u003C/p>","\u003Cp>Zelf een planningstool bouwen? Met AI is dat ineens een stuk realistischer. Maar zodra die tool dagelijks gebruikt wordt, verandert de rekensom. Want bouwen is &eacute;&eacute;n ding. Software jarenlang beheren, beveiligen en doorontwikkelen is iets anders.&nbsp;\u003C/p>\n\u003Cp>In deze blog vergelijken we zelf bouwen met standaardsoftware en kijken we waarom de slimste oplossing steeds vaker ergens tussen die twee ligt.&nbsp;\u003C/p>","\u003Cp>Met AI kun je in korte tijd een eerste versie van een planningstool bouwen. Daarmee is de vraag aan onze tafel veranderd. Niet meer alleen of je iets zelf kunt bouwen, maar vooral welk deel je daarna ook echt zelf wilt bezitten.\u003C/p>\n\u003Cp>Zo gaat dat gesprek bijvoorbeeld. Er zit een ondernemer tegenover ons, een bedrijf in staal met 46 medewerkers en twee vestigingen. Zijn zoon heeft met behulp van AI in twee avonden een eerste planningstool gemaakt, misschien stiekem een beetje ge&iuml;nspireerd door de werking en look &amp; feel van vPlan. 😉 Nog lang niet met alle mogelijkheden en logica van een volwassen planningsoplossing, maar wel genoeg om medewerkers en werkzaamheden op een tijdlijn te zetten en te verschuiven.&nbsp;\u003C/p>\n\u003Cp>En eerlijk is eerlijk: dat is indrukwekkend. Iets wat een paar jaar geleden al snel een serieus softwareproject was, komt ineens verrassend dichtbij. Waarom zou je dan voor standaardsoftware betalen als je steeds makkelijker zelf iets kunt maken?\u003C/p>\n\u003Cp>Die vraag is terecht. Software bouwen is goedkoper en toegankelijker geworden en daardoor wordt ook maatwerk opnieuw interessant. De keuze is wat ons betreft alleen niet zo simpel als zelf bouwen of software kopen. De interessantere vraag is welk deel je als standaard koopt en welk deel zo specifiek is voor jouw bedrijf dat je het beter zelf kunt maken.&nbsp;\u003C/p>\n\u003Chr>\n\u003Ch2>Wat AI werkelijk heeft veranderd\u003C/h2>\n\u003Cp>Maatwerk was lange tijd duur en tijdrovend. Zelfs voor een relatief kleine toepassing moest een businesscase worden gemaakt, een ontwikkelaar worden gevonden en soms maanden worden gewacht. Niet omdat maatwerk geen waarde had, maar omdat de kosten en het onderhoud vaak niet opwogen tegen de voordelen. AI verandert die verhouding.&nbsp;\u003C/p>\n\u003Cp>Werk waar vroeger veel handmatig programmeerwerk in zat, kan met AI veel sneller worden uitgevoerd. Schermen bouwen, testdata maken, koppelingen schrijven, documentatie opzetten en bestaande patronen vertalen naar werkende software. Daardoor worden toepassingen interessant die een paar jaar geleden simpelweg te duur waren om te ontwikkelen.&nbsp;\u003C/p>\n\u003Cp>Die ontwikkeling geldt natuurlijk ook voor ons. Binnen vPlan gebruiken we AI volop in onze ontwikkelprocessen om sneller te ontwikkelen, code te controleren, tests te maken en idee&euml;n sneller om te zetten naar werkende functionaliteit. Dezelfde technologie die maatwerk toegankelijker maakt, helpt standaardsoftware dus ook sneller door te ontwikkelen.\u003C/p>\n\u003Cp>De denkfout zit daarom niet in het enthousiasme over zelf bouwen, maar in wat je denkt te hebben als de eerste versie werkt. Met AI kun je steeds sneller een huis bouwen, maar zodra je erin gaat wonen moet de verwarming blijven werken, moeten lekkages worden opgelost en heeft het huis onderhoud nodig. Bij software werkt het niet anders.&nbsp;\u003C/p>\n\u003Chr>\n\u003Ch2>Wat je bezit zodra het in gebruik gaat\u003C/h2>\n\u003Cp>Zodra software onderdeel wordt van je dagelijkse operatie, ontstaat een andere verantwoordelijkheid. Twee planners kunnen tegelijkertijd dezelfde order aanpassen, een koppeling kan stoppen omdat een leverancier zijn API wijzigt en een back-up heeft pas waarde als je hem ook daadwerkelijk kunt herstellen. Het zijn geen onderwerpen die een eerste demo aantrekkelijker maken, maar ze bepalen wel of mensen iedere dag op de software kunnen vertrouwen.\u003C/p>\n\u003Cp>Ook de software blijft veranderen. Er komen medewerkers, processen, wensen en koppelingen bij. Een kleine wijziging kan na een paar jaar gevolgen hebben voor allerlei andere onderdelen. Dat geldt voor iedere softwareoplossing, maar bij zelfbouw organiseer en betaal je dat beheer zelf.&nbsp;\u003C/p>\n\u003Chr>\n\u003Ch2>Waarom maatwerk opnieuw interessant wordt\u003C/h2>\n\u003Cp>Dat is geen argument om niets zelf te bouwen. Integendeel. Juist doordat AI de ontwikkelkosten verlaagt, wordt het interessanter om software te maken voor processen die echt specifiek zijn voor jouw organisatie.\u003C/p>\n\u003Cp>Neem opnieuw het staalbedrijf. Misschien bepalen materiaaldikte, snijtijd, omsteltijd en eigen regels voor restmateriaal op welke machine een productieorder het beste kan worden ingepland. Dat is specifieke bedrijfskennis waarvoor maatwerk veel waarde kan toevoegen.\u003C/p>\n\u003Cp>Maar voor die ene slimme berekening heeft het bedrijf nog steeds medewerkers, machines, roosters, capaciteit, orders, rechten, historie, mobiele toegang, beveiliging en koppelingen nodig. Waarom zou je dat fundament opnieuw bouwen als juist de berekening het onderscheidende deel is?&nbsp;\u003C/p>\n\u003Cp>Daar ligt wat ons betreft de kans: gebruik standaardsoftware voor wat voor veel bedrijven hetzelfde is en maatwerk voor wat jouw proces anders maakt.&nbsp;\u003C/p>\n\u003Chr>\n\u003Ch2>Maar maatwerk brengt ook verantwoordelijkheid mee\u003C/h2>\n\u003Cp>AI maakt maatwerk veel interessanter. Alleen verdwijnen daarmee niet automatisch de risico's die bij maatwerk horen. Sterker nog, doordat je tegenwoordig zo snel iets werkends kunt maken, is het makkelijker om die risico's in het begin over het hoofd te zien.&nbsp;\u003C/p>\n\u003Cdiv style=\"overflow-x: auto;\">\n\u003Ctable style=\"width: 100%; border-collapse: collapse; height: 264px;\">\n\u003Cthead>\n\u003Ctr style=\"height: 24px;\">\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Risico bij maatwerk\u003C/th>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding-top: 12px; padding-right: 12px; padding-bottom: 12px; width: 59.1732%; height: 24px;\">Wat betekent dit in de praktijk?\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Afhankelijkheid van kennis\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Vaak weet een klein aantal mensen hoe de oplossing is gebouwd en waarom bepaalde keuzes zijn gemaakt. Valt die kennis weg, dan wordt aanpassen en herstellen lastiger.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Onderhoud &amp; doorontwikkeling\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Processen veranderen, nieuwe wensen ontstaan en techniek veroudert. De software moet daarin blijven meegroeien.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Continu&iuml;teit\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Bij een storing moet iemand kunnen ingrijpen. Monitoring, back-ups en herstel moeten dus goed geregeld en getest zijn.&nbsp;\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Security &amp; Privacy\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Rechten, updates, kwetsbaarheden en persoonsgegevens moeten blijvend goed worden beheerd.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Groeiende complexiteit\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Wat begint als een kleine toepassing kan door nieuwe functies, uitzonderingen en koppelingen ongemerkt uitgroeien tot bedrijfskritische software.\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\n\u003C/div>\n\u003Cp>Dat zijn geen redenen om maatwerk niet te gebruiken. Wel om bewust te kiezen welk deel je zelf wilt bezitten. Voor specifieke bedrijfslogica kunnen de voordelen van maatwerk ruimschoots opwegen tegen deze risico's. Voor functionaliteiten die honderden andere bedrijven ook nodig hebben, ligt die afweging anders.\u003C/p>\n\u003Chr>\n\u003Ch2>Maak wel de volledige rekensom\u003C/h2>\n\u003Cp>Wie zelf bouwen overweegt, zou minimaal drie jaar vooruit moeten kijken. Vergelijk daarbij niet \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro;\u003C/span>300 per maand aan software met alleen \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro;\u003C/span>7.500 aan ontwikkelkosten. Bij SaaS betaal je met de licentie ook voor hosting, back-ups, beveiliging, support, monitoring, onderhoud en doorontwikkeling. Bij zelfbouw verdwijnen die kosten niet, maar organiseer je ze zelf.\u003C/p>\n\u003Cp>Een vereenvoudigde vergelijking over drie jaar kan er bijvoorbeeld zo uitzien:&nbsp;\u003C/p>\n\u003Cdiv style=\"overflow-x: auto;\">\n\u003Ctable style=\"width: 100%; border-collapse: collapse;\">\n\u003Cthead>\n\u003Ctr>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Kostenpost\u003C/th>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">vPlan\u003C/th>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding-top: 12px; padding-right: 12px; padding-bottom: 12px; width: 38.0822%;\">Zelf bouwen\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Licentie\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>300 p/m x 36 = \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>10.800\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">-\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Implementatie\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>2.500\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">-\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Eerste ontwikkeling\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>7.500\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Hosting en infrastructuur\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>1.800\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Back-ups en monitoring\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 900\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Beveiliging en updates\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 1.800\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Support aan gebruikers\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 1.800\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Onderhoud en kleine wijzigingen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 14.400\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">Doorontwikkeling standaardproject\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">Inbegrepen\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">Eigen verantwoordelijkheid\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%;\">\u003Cstrong>Totaal over 3 jaar\u003C/strong>\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%;\">\u003Cstrong>\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>13.300\u003C/strong>\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding-top: 12px; padding-right: 12px; padding-bottom: 12px; width: 38.0822%;\">\u003Cstrong>\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 28.200 + doorontwikkeling\u003C/span>\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\n\u003C/div>\n\u003Cp>Het zijn voorbeeldbedragen en de uitkomst zal per organisatie verschillen. Het belangrijkste is dat je dezelfde kosten vergelijkt. Vooral interne uren verdwijnen makkelijk uit beeld: vier uur beheer per maand tegen \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro;\u003C/span>100 per uur is over drie jaar al \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>14.400. De SaaS-licentie zie je iedere maand op een factuur, interne tijd veel minder snel.&nbsp;\u003C/p>\n\u003Chr>\n\u003Ch2>Koop de basis, bouw het verschil\u003C/h2>\n\u003Cp>Maatwerk hoeft daarbij niet tegenover vPlan te staan. Stel dat het staalbedrijf voor \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>5.000 zijn eigen slimme machine berekening bouwt. Die kan ook bovenop een bestaande planning worden geplaatst. Je hoeft voor een specifieke behoefte dus niet automatisch de volledige applicatie zelf te bouwen.\u003C/p>\n\u003Cp>Dat leidt tot een vrij eenvoudige verdeling.&nbsp;\u003Cstrong>Koop de basis:&nbsp;\u003C/strong>planning, capaciteit, medewerkers, machines, roosters, rechten, mobiele toegang, koppelingen, back-ups, beveiliging en beheer.&nbsp;\u003Cstrong>Bouw het verschil\u003C/strong>: de logica, automatisering of AI-toepassing die specifiek is voor de manier waarop jouw organisatie werkt.&nbsp;\u003C/p>\n\u003Cp>API's, koppelingen, automatiseringen en AI maken die combinatie steeds makkelijker. De keuze verschuift daardoor van&nbsp;\u003Cem>build versus buy&nbsp;\u003C/em>naar veel vaker&nbsp;\u003Cem>build en buy.\u003C/em>\u003C/p>\n\u003Cp>Een simpele vraag kan daarbij helpen:&nbsp;\u003Cstrong>zou ik dit ook aan mijn concurrent kunnen verkopen?&nbsp;\u003C/strong>Een planbord, gebruikersbeheer of capaciteitsberekening waarschijnlijk wel. Je eigen productielogica, specifieke keuring of unieke manier van werken waarschijnlijk niet. Juist in dat laatste deel zit de ruimte voor maatwerk.\u003C/p>\n\u003Chr>\n\u003Ch2>Voordat je begint\u003C/h2>\n\u003Cp>Als je zelf wilt bouwen, bepaal dan vooraf wie het over drie jaar onderhoudt, wat een dag zonder planning kost en wat er gebeurt als degene met de meeste technische kennis vertrekt. Vraag jezelf vooral af welk deel van de oplossing daadwerkelijk specifiek is voor jouw bedrijf en of je alleen dat deel kunt bouwen.&nbsp;\u003C/p>\n\u003Cp>AI maakt het makkelijker en goedkoper om eigen software te ontwikkelen. Dat is een kans die bedrijven wat ons betreft juist moeten benutten. Alleen hoeft maatwerk niet meer te betekenen dat je alles zelf bouwt.&nbsp;\u003C/p>\n\u003Cp>\u003Cstrong>Koop wat standaard is. Bouw wat jou onderscheidt.&nbsp;\u003C/strong>\u003C/p>","Zelf software bouwen met AI of kopen | vPlan","AI maakt zelf software bouwen sneller en goedkoper. Maar wat kost het beheer daarna? Ontdek wanneer je beter bouwt, koopt of beide combineert.",{"id":4,"blog_id":16,"language_code":26,"title":27,"slug":28,"summary":20,"excerpt":29,"content":30,"extra_info":10,"result_highlights":10,"region":10,"industry":10,"company_type":10,"integrations":10,"key_features":10,"meta_title":31,"meta_description":32,"faqs":10,"partner_image":10,"partner_biography":10,"partner_author":10},"en","Building has become cheap. Owning hasn’t.","building-is-cheap-owning-isnt","\u003Cp class=\"isSelectedEnd\">Build your own planning tool? With AI, that has suddenly become a lot more realistic. But as soon as that tool is used every day, the sums change. Because building is one thing. Managing, securing and developing software for years is another.\u003C/p>\n\u003Cp>In this blog, we compare building your own software with off-the-shelf software and look at why the smartest solution increasingly lies somewhere between the two.\u003C/p>","\u003Cp>With AI, you can build a first version of a planning tool in a short space of time. That has changed the question around our table. It&rsquo;s no longer just about whether you can build something yourself, but above all which parts you actually want to own afterwards.\u003C/p>\n\u003Cp>Here&rsquo;s an example of how that conversation goes. Sitting across from us is an entrepreneur who runs a steel company with 46 employees and two sites. With the help of AI, his son built a first version of a planning tool in two evenings, perhaps secretly taking a little inspiration from how vPlan works and its look &amp; feel. 😉 It&rsquo;s still a long way from having all the features and logic of a mature planning solution, but it&rsquo;s enough to put employees and jobs on a timeline and move them around.\u003C/p>\n\u003Cp class=\"isSelectedEnd\">And to be fair: that&rsquo;s impressive. Something that would have quickly become a serious software project just a few years ago suddenly feels surprisingly within reach. So why pay for off-the-shelf software when it&rsquo;s becoming easier and easier to build something yourself?\u003C/p>\n\u003Cp>It&rsquo;s a fair question. Building software has become cheaper and more accessible, which also makes custom software an attractive option again. In our view, however, the choice isn&rsquo;t as simple as building it yourself or buying software. The more interesting question is which parts you buy as standard and which parts are so specific to your business that you&rsquo;re better off building them yourself.\u003C/p>\n\u003Chr>\n\u003Ch2>What AI has really changed\u003C/h2>\n\u003Cp>Custom software was expensive and time-consuming for a long time. Even for a relatively small application, a business case had to be made, a developer found and sometimes months spent waiting. Not because custom software didn&rsquo;t offer value, but because the costs and maintenance often outweighed the benefits. AI is changing that balance.&nbsp;\u003C/p>\n\u003Cp>Work that used to involve a lot of manual programming can now be done much faster with AI. Building screens, creating test data, writing integrations, producing documentation and translating existing patterns into working software. As a result, applications that would simply have been too expensive to develop a few years ago are now becoming viable.\u003C/p>\n\u003Cp>Of course, this development applies to us too. At vPlan, we make extensive use of AI in our development processes to develop faster, review code, create tests and turn ideas into working functionality more quickly. So the same technology that makes custom software more accessible also helps off-the-shelf software evolve faster.\u003C/p>\n\u003Cdiv class=\"relative z-[1]\">\n\u003Cdiv class=\"mt4SwW_editor [--wb-text-primary:var(--text-primary)] [--wb-text-secondary:var(--text-secondary)] [--wb-text-tertiary:var(--text-tertiary)] [--wb-surface-primary:var(--bg-primary)] [--wb-surface-secondary:var(--bg-tertiary)] [--wb-border:rgb(0_0_0/7%)] [--wb-border-hover:rgb(0_0_0/7%)] [--wb-divider:var(--border-light)] [--wb-focus:var(--border-strong)] [--wb-control-border:var(--interactive-border-focus)] [--wb-entity-accent:var(--theme-entity-accent)] [--wb-accent:var(--interactive-label-accent-default)] [--wb-on-accent:var(--bg-primary)] [--wb-interactive-background:var(--interactive-bg-accent-default)] [--wb-selection:var(--theme-user-selection-bg,var(--selection))] [--wb-radius-sm:var(--radius-sm)] [--wb-shadow-lg:var(--shadow-lg)] [--wb-font-sans:var(--font-sans)] [--wb-font-mono:var(--font-mono)] [--wb-shimmer-dark-contrast:var(--gray-550)] [--wb-shimmer-dark-secondary:var(--text-tertiary)] [--wb-radius:24px] [--wb-shadow:0_4px_80px_rgb(0_0_0/2%)] [contain:none] writing-block-editor markdown-new-styling relative flow-root\" data-task-list-drag-label=\"Checklist-item verplaatsen\">\n\u003Cdiv class=\"outline-none data-[writing-block-fullscreen-editor]:grow ProseMirror markdown prose writing-block-typography dark:prose-invert w-full min-h-6 break-words focus:outline-none writing-block-open-link-mode\" dir=\"auto\" contenteditable=\"true\" translate=\"no\" data-writing-block-fullscreen-editor-region=\"true\" data-writing-block-fullscreen-editor-layout=\"inline\" aria-disabled=\"false\">\n\u003Cp>The misconception, therefore, isn&rsquo;t the enthusiasm for building software yourself, but what you think you have once the first version works. With AI, you can build a house faster and faster, but once you move in, the heating needs to keep working, leaks need to be fixed and the house needs maintenance. Software is no different.\u003C/p>\n\u003C/div>\n\u003C/div>\n\u003C/div>\n\u003Chr>\n\u003Ch2>What you own once it goes into use\u003C/h2>\n\u003Cp>As soon as software becomes part of your day-to-day operations, a different kind of responsibility arises. Two planners might edit the same order at the same time, an integration might stop working because a supplier changes its API, and a backup is only useful if you can actually restore it. These aren&rsquo;t the things that make an initial demo more appealing, but they do determine whether people can rely on the software every day.\u003C/p>\n\u003Cp>The software itself also continues to change. New employees, processes, requirements and integrations are added. After a few years, a small change can have consequences for all sorts of other areas. That applies to any software solution, but when you build it yourself, you organise and pay for that maintenance yourself.&nbsp;\u003C/p>\n\u003Chr>\n\u003Ch2>Why custom software is becoming attractive again\u003C/h2>\n\u003Cp>That&rsquo;s not an argument against building anything yourself. Quite the opposite. Precisely because AI reduces development costs, it&rsquo;s becoming more attractive to build software for processes that are genuinely specific to your organisation.\u003C/p>\n\u003Cp class=\"isSelectedEnd\">Take the steel company again. Perhaps material thickness, cutting time, changeover time and its own rules for leftover material determine which machine a production order is best planned on. That&rsquo;s specific business knowledge where custom software can add a great deal of value.\u003C/p>\n\u003Cp>But for that one clever calculation, the company still needs employees, machines, rotas, capacity, orders, permissions, history, mobile access, security and integrations. Why rebuild that foundation when the calculation itself is the part that sets the business apart?\u003C/p>\n\u003Cp>That&rsquo;s where we see the opportunity: use off-the-shelf software for what is the same for many businesses and custom software for what makes your process different.\u003C/p>\n\u003Chr>\n\u003Ch2>But custom software also comes with responsibility\u003C/h2>\n\u003Cp>AI makes custom software much more attractive. But that doesn&rsquo;t automatically eliminate the risks that come with it. In fact, because you can now create something that works so quickly, it&rsquo;s easier to overlook those risks at the outset.\u003C/p>\n\u003Cdiv style=\"overflow-x: auto;\">\n\u003Ctable style=\"width: 100%; border-collapse: collapse; height: 264px;\">\n\u003Cthead>\n\u003Ctr style=\"height: 24px;\">\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Custom software risk\u003C/th>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding-top: 12px; padding-right: 12px; padding-bottom: 12px; width: 59.1732%; height: 24px;\">What does this mean in practice?\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Dependency on knowledge\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Often, only a small number of people know how the solution was built and why certain choices were made. If that knowledge is lost, making changes and fixing issues becomes more difficult.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Maintenance &amp; ongoing development\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Processes change, new requirements emerge and technology becomes outdated. The software needs to keep evolving alongside them.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Continuity\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">In the event of a failure, someone needs to be able to intervene. Monitoring, backups and recovery therefore need to be properly set up and tested.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Security &amp; Privacy\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">Permissions, updates, vulnerabilities and personal data need to be managed properly on an ongoing basis.\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 40.8268%; height: 24px;\">Groeiende complexiteit\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 59.1732%; height: 24px;\">What starts as a small application can gradually grow into business-critical software as new features, exceptions and integrations are added.\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\n\u003C/div>\n\u003Cp>These aren&rsquo;t reasons not to use custom software. But they are reasons to think carefully about which parts you want to own yourself. For specific business logic, the benefits of custom software can far outweigh these risks. For functionality that hundreds of other businesses also need, the considerations are different.\u003C/p>\n\u003Chr>\n\u003Ch2>Make sure you calculate the full cost\u003C/h2>\n\u003Cp class=\"isSelectedEnd\">If you&rsquo;re considering building your own software, you should look at least three years ahead. Don&rsquo;t compare &euro;300 a month for software with just &euro;7,500 in development costs. With SaaS, your licence also covers hosting, backups, security, support, monitoring, maintenance and ongoing development. Those costs don&rsquo;t disappear when you build your own software; you simply have to manage them yourself.\u003C/p>\n\u003Cp>A simplified comparison over three years might look something like this:\u003C/p>\n\u003Cdiv style=\"overflow-x: auto;\">\n\u003Ctable style=\"width: 100%; border-collapse: collapse; height: 504px;\">\n\u003Cthead>\n\u003Ctr style=\"height: 24px;\">\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 24px;\">Cost item\u003C/th>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 24px;\">vPlan\u003C/th>\n\u003Cth style=\"border: 1px solid rgb(209, 213, 219); padding-top: 12px; padding-right: 12px; padding-bottom: 12px; width: 38.0822%; height: 24px;\">Build your own\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr style=\"height: 96px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 96px;\">Licence\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 96px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>300 p/m x 36 = \u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>10.800\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 96px;\">-\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 24px;\">Implementation\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 24px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>2.500\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 24px;\">-\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">Initial development\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 48px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>7.500\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">Hosting and infrastructure\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 48px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>1.800\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">Backups and monitoring\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 48px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 900\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">Security and updates\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 48px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 1.800\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 24px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 24px;\">User support\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 24px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 24px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 1.800\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">Maintenance and minor changes\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 48px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; 14.400\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">Ongoing development of the standard product\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">Included\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 38.0822%; height: 48px;\">\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">Eigen verantwoordelijkheid\u003C/span>\u003C/td>\n\u003C/tr>\n\u003Ctr style=\"height: 48px;\">\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 30.411%; height: 48px;\">\u003Cstrong>Total over 3 years\u003C/strong>\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding: 12px; width: 31.3699%; height: 48px;\">\u003Cstrong>\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro; \u003C/span>13.300\u003C/strong>\u003C/td>\n\u003Ctd style=\"border: 1px solid rgb(209, 213, 219); padding-top: 12px; padding-right: 12px; padding-bottom: 12px; width: 38.0822%; height: 48px;\">\u003Cstrong>\u003Cspan style=\"font-size: 12.0pt; line-height: 115%; font-family: 'Aptos',sans-serif; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: DengXian; mso-fareast-theme-font: minor-fareast; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: Arial; mso-bidi-theme-font: minor-bidi; mso-ansi-language: #1000; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA;\">&euro;28,200 + ongoing development\u003C/span>\u003C/strong>\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\n\u003C/div>\n\u003Cp>These are example figures and the outcome will vary from one organisation to another. The most important thing is to compare like-for-like costs. Internal hours in particular are easily overlooked: four hours of maintenance per month at &euro;100 per hour already adds up to &euro;14,400 over three years. You see the SaaS licence on an invoice every month, whereas internal time is much less visible.\u003C/p>\n\u003Chr>\n\u003Ch2>Buy the foundation, build the difference\u003C/h2>\n\u003Cp>Custom software doesn&rsquo;t have to be an alternative to vPlan. Suppose the steel company builds its own smart machine calculation for &euro;5,000. That calculation could also be added on top of an existing planning tool. So, having a specific requirement doesn&rsquo;t automatically mean you need to build the entire application yourself.\u003C/p>\n\u003Cp class=\"isSelectedEnd\">That leads to a fairly simple distinction. \u003Cstrong>Buy the foundation\u003C/strong>: planning, capacity, employees, machines, rotas, permissions, mobile access, integrations, backups, security and management.&nbsp;\u003Cstrong>Build the difference\u003C/strong>: the logic, automation or AI application that is specific to the way your organisation works.\u003C/p>\n\u003Cp>APIs, integrations, automation and AI are making this combination increasingly easy. As a result, the choice is shifting from \u003Cem>build versus buy\u003C/em> to, increasingly, \u003Cem>build and buy.\u003C/em>\u003C/p>\n\u003Cp>One simple question can help: \u003Cstrong>could I sell this to my competitor too? \u003C/strong>A planning board, user management or capacity calculation probably could be. Your own production logic, specific inspection process or unique way of working probably couldn&rsquo;t. That latter part is precisely where there is room for custom software.\u003C/p>\n\u003Chr>\n\u003Ch2>Before you start\u003C/h2>\n\u003Cp>If you want to build your own software, decide in advance who will maintain it in three years&rsquo; time, what a day without planning would cost and what happens if the person with the most technical knowledge leaves. Above all, ask yourself which part of the solution is genuinely specific to your business and whether you can build just that part.\u003C/p>\n\u003Cp class=\"isSelectedEnd\">AI makes it easier and cheaper to develop your own software. In our view, that&rsquo;s an opportunity businesses should embrace. But custom software no longer has to mean building everything yourself.\u003C/p>\n\u003Cp>\u003Cstrong>Buy what&rsquo;s standard. Build what sets you apart.\u003C/strong>\u003C/p>","Build your own software with AI or buy it | vPlan","AI makes building your own software faster and cheaper. But what does it cost to maintain afterwards? Discover when it’s better to build, buy or combine both.",{"id":34,"status":5,"photo":35,"first_name":36,"last_name":37,"role":38,"employed":6,"translations":39,"biography":45},2,"/images/cms/c3ae1b88-16be-4ca3-87cd-f9847f9ffb3e.jpg","Jeroen","Mensink",15,[40,43],{"id":41,"team_id":34,"language_code":17,"biography":42},3,"\u003Cp class=\"MsoNormal\">Jeroen Mensink is mede-oprichter van vPlan en vanaf het eerste uur betrokken bij de ontwikkeling van het platform. Met jarenlange ervaring in de softwarebranche en een sterke achtergrond met HR-tooling zag Jeroen van dichtbij waar het vaak misgaat: het gebrek aan overzicht en inzicht in capaciteit. Gedreven door die uitdaging verdiepte hij zich in de vraag hoe bedrijven slimmer kunnen plannen en hun processen beter kunnen stroomlijnen. Met zijn technische kennis, analytisch vermogen en oog voor de praktijk heeft hij vPlan helpen vormen tot het krachtige en gebruiksvriendelijke planningsplatform dat het vandaag de dag is.\u003C/p>",{"id":44,"team_id":34,"language_code":26,"biography":45},9,"\u003Cp>Jeroen Mensink is the co-founder of vPlan and has been involved in the platform&rsquo;s development from day one. With many years of experience in the software industry and a strong background in HR tooling, Jeroen saw firsthand where things often go wrong: the lack of overview and insight into capacity. Driven by this challenge, he dove into the question of how companies can plan more intelligently and streamline their processes more effectively. With his technical expertise, analytical skills, and practical mindset, he has helped shape vPlan into the powerful and user-friendly planning platform it is today.\u003C/p>","",1789958363860]