Skip to content
← VantyRexVANTYREX SYSTEMS

VANTYREX // WORK

Reference builds

Here we show the systems we engineer and how we work. Client case studies are published only with each client's consent, so each reference build is anchored to a real capability we already run in production: the same contract, portal, billing, and audit spine that runs our own business.

Client case studies are published only with each client's consent, and we do not invent any. What you see here is what we design and build for clients, and the proof that we can: the same contract, portal, billing, and audit spine runs our own business today. Every build below is bespoke, with the client's brand and data their own — never a template, never a subscription product we resell.
S-01Two-sided marketplace platform

On-demand field-services marketplace

Customers post jobs; vetted providers get matched, agree, deliver, and get invoiced.

Market demand

On-demand home and field services is a large and growing category: customers expect to book a vetted professional in minutes, and providers need dispatch, scheduling and payments that keep up.

The problem

Home and field-service operators lose margin to phone tag, paper agreements, and untracked jobs. They need a marketplace that turns a request into a signed, tracked, invoiced job without a back office full of spreadsheets.

What we build

  1. 01.A public request flow captures the job — service type, location, photos, and a scoped brief — and turns it into a structured work order.
  2. 02.A matching layer we architect pairs each request with vetted providers by skill, coverage area, and availability, with quoting and acceptance built in.
  3. 03.On acceptance both sides e-sign a job agreement, sealed with a tamper-evident audit hash.
  4. 04.Field crews work from an installable app engineered to queue proof-of-completion — notes, photos, sign-off — and sync when they are back online.
  5. 05.Milestones drive VAT-correct invoicing and a payment-request record; each party sees only its own jobs through an isolated portal.
  6. 06.Notifications over SMS and email keep customer, provider, and back office in step at every stage.

Why we can prove it

E-SIGN · VAT · PORTAL

We can prove the spine underneath: e-signed job agreements on a hash-chained audit trail, milestone and phase tracking, VAT-correct invoicing, and hard multi-tenant isolation all run our own business today — in four languages, as an installable app.

Technical spine

React 19Installable PWAE-signatureVAT engineMulti-tenant
S-02Vertical SaaS platform

Multi-clinic patient platform

Passwordless access, isolated tenants, e-consent, and multilingual intake for healthcare.

Market demand

Analysts consistently rank healthcare among the fastest-growing vertical-SaaS categories, driven by the shift from paper records to owned, compliant digital systems.

The problem

A group of clinics needs each practice fully isolated, patients able to sign in without another password to lose, consent captured defensibly, and intake that works in every language its patients speak.

What we build

  1. 01.Patients and staff sign in without passwords — a one-time code to the email or phone on file, verified server-side.
  2. 02.Every clinic is a hard-isolated tenant: strict per-tenant rules keep one practice's records from ever surfacing in another's.
  3. 03.Intake and consent forms we design render in English, Hebrew, Arabic, and Russian with full right-to-left layout.
  4. 04.Consent is captured as a handwritten e-signature and sealed into a hash-chained audit trail.
  5. 05.Booking and scheduling we engineer sit on top, with reminders over SMS and email.
  6. 06.Visits and plans flow into a VAT-aware invoicing engine, with insurance-ready billing formats we build to each payer's spec.

Why we can prove it

OTP LOGIN · E-CONSENT · RTL

The trust-critical parts already run our business: passwordless one-time-code login, hard per-tenant isolation, e-signature on a hash-chained audit trail, four-language right-to-left rendering, and a working invoicing engine.

Technical spine

Passwordless OTPTenant isolationE-consentRTL · 4-lang
S-03Offline-capable PWA application

Logistics dispatch & delivery app

Dispatchers assign stops; drivers work offline and sign for delivery; proof of delivery feeds invoicing.

Market demand

Logistics software is a large category that analysts project to keep growing fast as operators digitize dispatch, proof-of-delivery, and billing.

The problem

Delivery operations run where signal does not. Drivers need an app that keeps working with no connection, captures a signature at the door, and feeds a clean invoice back to the office without re-keying.

What we build

  1. 01.Dispatchers assign stops and build the day's manifest from a back-office console.
  2. 02.Drivers carry an installable, offline-capable app — the shell and its data are precached, so it keeps working with no signal.
  3. 03.We engineer a write-queue that holds status changes, proof-of-delivery photos, and signatures on-device, then syncs them the moment connectivity returns.
  4. 04.Recipients sign for delivery on-screen; the captured signature is bound to the stop.
  5. 05.Live tracking and route sequencing we architect give the office a real-time picture and an optimized order of stops.
  6. 06.A completed run raises an event that auto-drafts the invoice and appends the job to a tamper-evident audit trail.

Why we can prove it

PWA · E-SIGN · AUDIT

The load-bearing pieces are already in production for us: an installable offline-capable app shell, on-device signature capture, a phase-completion event that gates invoice drafting — we draft on a completed phase, we never auto-charge — and a tamper-evident audit trail. Automatic invoicing, live tracking, route sequencing, and the driver offline write-queue are what we build on top.

Technical spine

Offline-capable PWAsignature_padEvent-driven billingAudit chain
S-04AI-assisted contract-lifecycle SaaS

Contract-lifecycle back office (CLM)

Clause library, assembly, approval routing, renewals, invoicing — under a tamper-evident ledger.

Market demand

Workflow automation, legal-tech document automation, and compliance automation rank among the highest-demand enterprise software categories.

The problem

Teams that live on contracts drown in copy-pasted clauses, ad-hoc approvals, and missed renewals. They need one system that assembles the right language, routes it for sign-off, and never lets a renewal date slip.

What we build

  1. 01.A clause library holds approved, versioned language; an assembly engine composes a contract from the exact clauses a deal needs.
  2. 02.Approval routing, modeled as an orchestrated state machine, sends each draft to the right reviewers in the right order before anyone can sign.
  3. 03.Execution runs on the e-sign platform: identity-verified, handwritten signature, sealed with a hash.
  4. 04.A tamper-evident, hash-chained ledger records every step, so a contract's history can be independently verified.
  5. 05.Renewal tracking watches notice windows and opt-out dates and raises them before they lapse.
  6. 06.AI-assisted drafting we build suggests language from the approved library — assistive, never autonomous; a human always approves.
  7. 07.The same engine issues pro-forma invoices and tracks accounts receivable against each agreement.

Why we can prove it

CLM · APPROVALS · LEDGER

We did not prototype this for a pitch — we built it for ourselves and run our own contracts on it: clause library and assembly, orchestrated approval routing, renewal tracking, and pro-forma invoicing with AR, all under a tamper-evident hash-chained ledger.

Technical spine

Clause libraryStep FunctionsRenewal trackingHash-chained ledger
S-05Booking & commerce platform

High-value rental commerce platform

Bookings become e-signed agreements; retainage and three-way match protect every release.

Market demand

High-value rental and booking commerce is underserved by generic storefront tools that cannot hold a deposit, protect a release, or track condition — the money is in the controls a template cannot provide.

The problem

Renting equipment, vehicles, or venues is not selling a product: you need a signed agreement, money held back until the item comes back intact, and a check before that money is released.

What we build

  1. 01.A storefront we design lists high-value rental inventory with an availability calendar and booking rules per item.
  2. 02.Each booking converts to an e-signed rental agreement, sealed with an audit hash.
  3. 03.At execution the engine withholds retainage — a defined amount held back until the item is returned and inspected.
  4. 04.Release runs a three-way match: agreement, condition report, and charge must agree before retainage is freed.
  5. 05.VAT-correct pro-forma invoices and payment requests are issued from the same engine; deposits and multi-currency pricing are capabilities we engineer per market.
  6. 06.The whole storefront installs as a PWA and works like an app on phone and desktop.

Why we can prove it

RETAINAGE · 3-WAY MATCH · VAT

Retainage is the proof: our own billing engine withholds retainage, runs a three-way match before releasing it, and issues VAT-correct pro-forma invoices — with e-signed agreements and a hash-chained audit trail behind them.

Technical spine

RetainageThree-way matchVAT enginePWA storefront

Proven in production — our own stack

Every build above borrows from software we already run to operate VantyRex. We did not mock these systems for a portfolio; we use them daily, and we can show any of them working in a live demo.

E-sign contract platformIdentity-verified, handwritten e-signatures with OTP verification, sealed into a SHA-256 hash-chained, tamper-evident audit ledger.
IN PRODUCTION
Multi-tenant client portalPasswordless one-time-code login with strict per-client isolation and an OTP store that self-destructs after a capped number of attempts.
IN PRODUCTION
Contract-lifecycle engineClause library and assembly, orchestrated approval routing, and renewal tracking that we run against our own agreements.
OUR BACK OFFICE
VAT & billing engineA VAT-aware engine we run in our own back office: pro-forma invoices and payment requests, retainage withholding, three-way match, and ERP-ready CSV export — recorded manually, never auto-charging anyone.
OUR BACK OFFICE
4-language RTL site + installable PWAThis very site: English, Hebrew, Arabic, and Russian with full right-to-left support, shipped as an installable, offline-capable progressive web app.
IN PRODUCTION

Have a system like one of these in mind?

Tell us what you are building. You will talk to the engineers who would design and build it — and we will show you the production stack behind every claim on this page.

Start your project

Contact form

VantyRex Systems © 2026

VantyRex Systems · www.vantyrex.com/work/

ENHEARRU