100+ Hours of Manual Legal Admin Per Month. Down to 20–30. In 3 Months. 100+ Jam Admin Legal Manual Per Bulan. Turun Jadi 20–30. Dalam 3 Bulan.
Exclolab built a centralized legal operations platform for Rechtshulp Zekerheid — automating dealer onboarding via RDW and KVK national APIs, syncing WooCommerce subscriptions in real time, and cutting manual admin by 75–80%. A Netherlands automotive legal firm went from constant operational firefighting to confident expansion — and is no longer afraid of scaling its client base — in a single 3-month waterfall delivery. Exclolab membangun platform operasional legal terpusat untuk Rechtshulp Zekerheid — mengotomatisasi onboarding dealer lewat API nasional RDW dan KVK, menyinkronkan langganan WooCommerce secara real time, dan memangkas admin manual hingga 75–80%. Firma legal otomotif Belanda ini beralih dari terus-menerus memadamkan api operasional menjadi ekspansi yang percaya diri — dalam satu siklus waterfall 3 bulan.
Compliance-sensitive legal work, run on spreadsheetsPekerjaan legal sensitif-kepatuhan, dijalankan di spreadsheet
Rechtshulp Zekerheid is a Netherlands-based legal consulting firm specializing in automotive dealership claims — managing dealer onboarding, vehicle warranty cases, subscription lifecycle, and legal claim processing for hundreds of dealer clients. Despite handling complex, compliance-sensitive legal work, their entire operation ran on manual processes: spreadsheets, emails, and disconnected tools that were never designed for the demands of a growing legal services business. Every new dealer, every vehicle claim, every subscription renewal was a manual effort — and the risks that came with that were mounting. In a legal context, manual errors aren't just inconvenient. They carry consequences. Rechtshulp Zekerheid adalah firma konsultan hukum berbasis Belanda yang berfokus pada klaim dealer otomotif — mengelola onboarding dealer, kasus garansi kendaraan, siklus langganan, dan pemrosesan klaim hukum untuk ratusan klien dealer. Meski menangani pekerjaan legal yang kompleks dan sensitif terhadap kepatuhan, seluruh operasi mereka berjalan dengan proses manual: spreadsheet, email, dan tools terpisah yang tidak pernah dirancang untuk kebutuhan bisnis jasa legal yang berkembang. Setiap dealer baru, setiap klaim kendaraan, setiap perpanjangan langganan adalah usaha manual — dan risiko yang menyertainya terus bertambah. Dalam konteks hukum, error manual bukan sekadar tidak nyaman. Ada konsekuensinya.
{{ pp.en }}{{ pp.id }}
{{ bi.en }}{{ bi.id }}
This wasn't a tools problem. It was running a compliance-sensitive legal business on tools built for a hobby project. Ini bukan masalah tools. Ini menjalankan bisnis legal yang sensitif terhadap kepatuhan di atas tools yang dibuat untuk proyek hobi.
{{ nt.descEn }}{{ nt.descId }}
It was structural: Ini struktural: Rechtshulp Zekerheid was operating a complex, compliance-sensitive legal business on tools built for general-purpose use. WooCommerce handled subscriptions on the website but had no connection to internal case management. Vehicle data was entered by hand despite being available via national API. Dealer company verification was manual despite a national registry existing for exactly that purpose. There was no single system connecting client onboarding, vehicle tracking, subscription status, and claim management — meaning every process was siloed, every handoff was manual, and every error required a human to catch and fix. In a legal context, those errors carry consequences far beyond operational inconvenience. Rechtshulp Zekerheid menjalankan bisnis legal yang kompleks dan sensitif terhadap kepatuhan di atas tools untuk kebutuhan umum. WooCommerce menangani langganan di website tapi tidak terhubung ke manajemen kasus internal. Data kendaraan dientri manual padahal tersedia lewat API nasional. Verifikasi perusahaan dealer dilakukan manual padahal ada registri nasional untuk tujuan itu persis. Tidak ada satu sistem yang menghubungkan onboarding klien, pelacakan kendaraan, status langganan, dan manajemen klaim — artinya setiap proses terisolasi, setiap handoff manual, dan setiap error butuh manusia untuk menangkap dan memperbaikinya. Dalam konteks hukum, error itu membawa konsekuensi jauh melampaui ketidaknyamanan operasional.
Root Cause First. Waterfall by Design.Akar Masalah Dulu. Waterfall by Design.
Exclolab's engagement started by mapping Rechtshulp Zekerheid's complete operational workflow — how dealers were onboarded, how vehicles were tracked, how subscriptions were managed, how claims were processed, and where every manual handoff was creating delay or risk. The root cause was clear: the operation had no single system connecting any of its parts. WooCommerce, spreadsheets, email, and manual data entry were all running in parallel — with no automated bridge between any of them. That diagnosis also shaped the delivery model. This engagement ran as a 3-month waterfall — not iterative sprints — because compliance requirements, API integration complexity, and the sensitivity of legal data demanded a complete, thoroughly tested system before going live. In a legal services context, deploying a half-built system to production is not an acceptable milestone. Engagement Exclolab dimulai dengan memetakan seluruh workflow operasional Rechtshulp Zekerheid — bagaimana dealer di-onboard, bagaimana kendaraan dilacak, bagaimana langganan dikelola, bagaimana klaim diproses, dan di mana setiap handoff manual menciptakan keterlambatan atau risiko. Akar masalahnya jelas: operasi ini tidak memiliki satu sistem yang menghubungkan semua bagiannya. WooCommerce, spreadsheet, email, dan entri data manual semuanya berjalan paralel — tanpa jembatan otomatis di antaranya. Diagnosis itu juga membentuk model delivery. Engagement ini berjalan sebagai waterfall 3 bulan — bukan sprint iteratif — karena kebutuhan kepatuhan, kompleksitas integrasi API, dan sensitivitas data legal menuntut sistem yang lengkap dan teruji sepenuhnya sebelum go-live. Dalam konteks jasa legal, mendeploy sistem setengah jadi ke produksi bukan milestone yang bisa diterima.
Why waterfall here: Mengapa waterfall di sini: Exclolab's default delivery approach is iterative — but the right methodology depends on the engagement. For Rechtshulp Zekerheid, the combination of compliance sensitivity, multi-API integration dependencies, and the need to go live with complete legal data integrity made a single structured delivery cycle the appropriate choice. The 3-month waterfall delivered a complete, tested, integrated platform — rather than incremental improvements to a live legal operation that couldn't afford partial states. Pendekatan delivery default Exclolab bersifat iteratif — tapi metodologi yang tepat bergantung pada engagement-nya. Untuk Rechtshulp Zekerheid, kombinasi sensitivitas kepatuhan, ketergantungan integrasi multi-API, dan kebutuhan go-live dengan integritas data legal yang lengkap membuat satu siklus delivery terstruktur menjadi pilihan yang tepat. Waterfall 3 bulan menghadirkan platform yang lengkap, teruji, dan terintegrasi — bukan peningkatan bertahap pada operasi legal live yang tidak mampu menanggung kondisi setengah jadi.
Five phases, one structured waterfall cycleLima fase, satu siklus waterfall terstruktur
This engagement ran as a 3-month waterfall — the full platform scoped, designed, built, tested, and delivered in a single structured cycle. Every integration was tested against live Dutch national APIs before go-live. No partial deployment. Engagement ini berjalan sebagai waterfall 3 bulan — seluruh platform di-scope, dirancang, dibangun, diuji, dan dikirim dalam satu siklus terstruktur. Setiap integrasi diuji terhadap API nasional Belanda yang live sebelum go-live. Tidak ada deployment parsial.
Before, after, and what it meantSebelum, sesudah, dan artinya
{{ kw.en }}{{ kw.id }}
In their own wordsDalam kata-kata mereka sendiri
The Technical StoryCerita Teknisnya
For readers who want the specifics: here's exactly what Rechtshulp Zekerheid's platform is built on, and why each decision was made — including why this engagement used Next.js rather than Exclolab's typical Laravel-native frontend stack.Untuk pembaca yang ingin detail spesifik: berikut yang menjadi basis platform Rechtshulp Zekerheid, dan mengapa setiap keputusan diambil — termasuk mengapa engagement ini menggunakan Next.js alih-alih stack frontend Laravel-native yang biasa dipakai Exclolab.
{{ rd.en }}{{ rd.id }}
Plain Language Summary: Ringkasan Bahasa Sederhana: Rechtshulp Zekerheid was running a legal services business on tools that had no business handling legal data. Vehicle records were entered by hand despite a national database existing for exactly that purpose. Subscriptions purchased on the website had no connection to the internal case system. Claim updates were sent manually by email. Exclolab connected all of it — Dutch national APIs, WooCommerce, and internal case management — into one auditable platform, delivered in 3 months, tested completely before go-live. Manual admin dropped from 100+ hours a month to 20–30. Rechtshulp Zekerheid menjalankan bisnis jasa legal di atas tools yang sebenarnya tidak layak menangani data legal. Data kendaraan dientri manual padahal database nasional ada untuk tujuan itu persis. Langganan yang dibeli di website tidak terhubung ke sistem kasus internal. Update klaim dikirim manual lewat email. Exclolab menghubungkan semuanya — API nasional Belanda, WooCommerce, dan manajemen kasus internal — menjadi satu platform yang auditable, dikirim dalam 3 bulan, diuji sepenuhnya sebelum go-live. Admin manual turun dari 100+ jam per bulan jadi 20–30.
3 months, one structured waterfall, zero partial deployments3 bulan, satu waterfall terstruktur, nol deployment parsial
{{ tl.bodyEn }}{{ tl.bodyId }}
3 months. One complete, tested, compliant platform. No partial deployments, no compliance gaps.3 bulan. Satu platform yang lengkap, teruji, dan compliant. Tanpa deployment parsial, tanpa celah kepatuhan.