BOOTINGJRV//SYSTEMS/
JRV Systems started as the in-house tech team for the JRV group of companies — car rental, construction, mobility. We built websites, dashboards, and the WhatsApp bridges that ran day-to-day operations.
Around 2023 we started getting asked: "can you build that for us too?" — by other Malaysian SMEs who wanted the same craft tier without paying London or Singapore agency rates.
We said yes. Then we said yes again. Then yes, more. Now we're a software studio that ships premium custom builds for businesses that want to stop competing on price.
We still maintain the JRV group's stack. We still eat our own dog food. And we still pick up the phone when something breaks at 2am — which it almost never does, because we built it ourselves.
Counting only what shipped. Discovery decks, abandoned RFPs, and "we'll get back to you" calls don't make this list.
We've earned more business through built work than through decks. The first artifact you'll see from us is a working prototype, not a slide.
Most of what we ship runs internally for the JRV group first. If we won't trust it for our own car rental, we won't ship it for yours.
Claude, GPT, Gemini — they're parts of the stack like Postgres or React. We integrate them where they earn ROI; we don't slap a chatbot on every problem.
Every line of code is written by us. Every pixel is designed by us. You hire the studio, not a vendor relay race.
Not a service deck. The list of things we've shipped to production for paying clients in the last 18 months.
Built the first internal tools for the JRV group — car rental site, fleet ops dashboard, the WhatsApp ops bridge that still runs the rentals today.
Friends and partners of the group started asking. We took on three external builds in parallel with the in-house roadmap.
Spun out as a dedicated software studio. Signed the first retainer clients. Stopped using "the JRV tech team" as a phrase.
First production WhatsApp + Claude integrations went live for clinics and dealerships. Friday (the studio's own bridge) ships in tandem and dogfoods every release.
Started shipping clinic-management, billing, and CRM platforms as productised stacks instead of bespoke one-offs. Kept fixed-price model intact.
Relaunched with this site, the dot-matrix Jarvis system, and the deeper 3D / scroll craft layer. Same engine, fresh fingerprint.
Notes from the bench. What we're building, why, and what we got wrong.
JOURNAL →