Technical data catalog platform
Replacing a legacy tool with an in-house platform, built from scratch.
An internal web application for cataloguing and search, built from scratch by a team of seven whose architecture and code review I own.
Work
Systems running in production: the context, what I built, the results.
Replacing a legacy tool with an in-house platform, built from scratch.
An internal web application for cataloguing and search, built from scratch by a team of seven whose architecture and code review I own.
13 interconnected apps: sales, workshop, rentals, invoicing and e-commerce
A complete information system for an SME: central API, e-commerce, ERP and point of sale, SSO and 6 business apps.
E-commerce API, storefront and back-office, with an ERP-driven catalogue
A 3-app headless e-commerce platform: ERP-driven catalogue, Mollie payments, legal invoicing and returns handling.
One backend for the workshop, rentals, sales, invoicing and bank reconciliation
Central Node.js API: ~250 endpoints, 44 data models, quotes signed online, idempotent invoicing and server-side OIDC SSO.
One identity, a second factor and central revocation across 9 applications
Self-hosted OIDC single sign-on for 9 applications: passkey or TOTP MFA, server-side tokens and migration with no lost access.
Dolibarr 22 with 8 custom modules, a connected POS and e-invoicing
Dolibarr 22 ERP with 8 custom modules: hardware-connected point of sale, offline inventory and a 4× faster product list.
Large supplier price lists imported into the ERP, no rekeying, existing data untouched.
A prototype in 4 days, then a 7-step import wizard inside the ERP: 2,200+ products created in production without touching existing data.
2 hardened servers, zero exposed app ports, tag-based rollback and pull backups.
Two hardened, monitored production servers: no exposed application ports, tag-based rollback and three-tier backups.
A monorepo of 3 published packages: UI, SSO session and BFF shared across apps.
A pnpm monorepo of 3 published packages, delivered in 11 days: shared UI, an SSO session client and an OIDC BFF, with no token exposed to JavaScript.
Field intake, workshop tracking, scheduling and invoices synced with the ERP.
Two workshop apps: field intake with photos and signature, then repair tracking, time logging, scheduling and invoices synced with the ERP.
From booking to a contract signed on a tablet, with no risk of double bookings.
Two rental apps: fleet, conflict-free bookings, pricing and payment tracking, then customer handover with a PDF contract signed on a tablet.
From a remotely signed quote to an invoice issued in the field.
Two apps to sell and install: quotes signed remotely, site visits on iPad, invoices synced with the ERP.
Bank statements matched to invoices automatically, each with a confidence score.
Fuzzy matching between a bank statement and an invoice export, with confidence scores and guided review: v1 and v2 shipped in 15 days.
A showcase website built for local SEO and for turning visits into quote requests.
A Next.js showcase site with strong local SEO: structured data, online quotes tied to real stock, on-demand catalogue revalidation and two calculators.
Engineer first: AI executes; I design, decide, review and prove.
Versioned specs, skills and multi-agent browser testing: an AI pipeline under engineering control, with over 800 test cases run.
A responsive takeaway store, built for SEO and performance.
A responsive takeaway store: Next.js server rendering for SEO, Stripe payments, an Express API backed by MongoDB.
Let's talk about your context: I'll tell you frankly what is feasible, and how long it takes.