Visileo
Work · 2023 → Now

Software companies actually run on.

Each project below is a production system: real architecture, real shipped features, a real codebase owned by the client. No mockup-only concepts and no inflated metrics — just the work, broken down honestly.

Custom-built
every system from scratch
Production-grade
deployed and in use
Client-owned
full codebase handover
Documented
architecture & runbooks
Featured Case Studies

Two systems, end-to-end.

Click through for the full breakdown — challenge, solution, architecture, workflow and outcomes.

CareBridge patient mobile app — due doses and next appointment
In production
Healthcare · Clinic SoftwareRead case study

CareBridge

A custom patient management and booking platform for a clinical practice — replacing message threads, paper forms and spreadsheets with one operational system.

System features
  • Patient mobile app
  • Online booking
  • Email verification
  • Approval workflows
  • Clinical records
  • Dose & appointment reminders
  • +3 more
Stack
React · TanStack · Tailwind · Node.js
Architecture
Patient-facing app and clinical admin console share a single backend with role-based access, a Postgres source of truth and automated messaging on top.
Maison admin dashboard — revenue, orders and customer metrics
In production
Luxury Retail · CRM & CommerceRead case study

Maison

A bespoke CRM and ecommerce platform for a luxury retail brand — storefront, customer accounts, orders, inventory and loyalty in one custom system.

System features
  • Luxury storefront
  • Product catalogue
  • Cart & checkout
  • Payment workflow
  • Order management
  • Inventory tracking
  • +4 more
Stack
React · TanStack · Tailwind · Node.js
Architecture
Storefront and admin console share a unified commerce backend, CRM and inventory ledger — with payments and email integrated through dedicated workflows.
Case 01 · Healthcare · Clinic Software

CareBridge

A custom patient management and booking platform for a clinical practice — replacing message threads, paper forms and spreadsheets with one operational system.

In productionClient-owned codebase
CareBridge patient mobile app — due doses and next appointment
Patient mobile appDue doses · next appointment
Challenge

The clinic was running patient bookings, approvals and follow-ups across WhatsApp, email and disconnected spreadsheets. Information lived in inboxes, approvals waited days, and there was no single record of patient interactions or clinical history.

Solution

Visileo designed and built a custom patient platform with a mobile-first patient app, an admin console for clinical staff, and an automated messaging and approval pipeline — all on a single database the clinic fully owns.

Shipped features
  • Patient mobile app
  • Online booking
  • Email verification
  • Approval workflows
  • Clinical records
  • Dose & appointment reminders
  • Role-based admin controls
  • Transactional email
  • Audit trail
Technology stack
Frontend
ReactTanStackTailwind
Backend
Node.jsEdge FunctionsREST
Data
PostgresRow-level security
Integrations
Transactional emailMessaging API
Architecture

CareBridge — system architecture

Patient-facing app and clinical admin console share a single backend with role-based access, a Postgres source of truth and automated messaging on top.

01 · Client surfaces
Patient mobile app
Bookings · doses
Clinical admin console
Records · approvals
02 · Application services
Auth & roles
Patient · staff · admin
Booking service
Availability · approvals
Clinical records
Patient history
Notification engine
Reminders · alerts
03 · Data & integrations
Postgres database
Single source of truth
Audit log
Critical actions
Transactional email
Verification · receipts
Messaging API
Outbound reminders
Workflow

Booking & approvals — manual vs automated

What used to take days of back-and-forth now runs as a structured workflow inside one system.

Manual processHigh friction · human-in-the-loop
  1. 01
    Patient sends WhatsApp message
    Lands in personal inbox
  2. 02
    Staff types details into spreadsheet
    Risk of typos & duplicates
  3. 03
    Approval requested over chat
    Often waits 1–3 days
  4. 04
    Manual email reminder typed out
    Sometimes forgotten
  5. 05
    No central record of interaction
    History lives in chat
Automated systemSingle system · runs on its own
  1. 01
    Patient books in mobile app
    Identity verified by email
  2. 02
    Request lands in clinical inbox
    Structured, validated data
  3. 03
    Approval workflow with roles
    Tracked, time-stamped
  4. 04
    Automated confirmations & reminders
    Email + messaging
  5. 05
    Full audit trail in patient record
    Searchable history
Outcomes

What changed for the business.

  • One operational system
    Replaces WhatsApp, spreadsheets and paper forms.
  • Approvals as a workflow
    Time-stamped, role-based, fully traceable.
  • Automated patient comms
    Reminders and confirmations run on their own.
  • Full ownership
    Codebase, database and deployment owned by the clinic.
  • Role-based access
    Patients, staff and admins each get the right surface.
  • Scalable foundation
    New clinical modules can plug into the same backend.
Case 02 · Luxury Retail · CRM & Commerce

Maison

A bespoke CRM and ecommerce platform for a luxury retail brand — storefront, customer accounts, orders, inventory and loyalty in one custom system.

In productionClient-owned codebase
Maison admin dashboard — revenue, orders and customer metrics
Admin dashboardOperational control room
Challenge

An off-the-shelf store couldn't represent the brand the way it needed to, and couldn't handle local payment flows, custom inventory rules or the CRM workflows the team relied on. Customer data, orders and promotions lived across separate tools that didn't talk to each other.

Solution

Visileo built a custom luxury storefront on top of a unified CRM and commerce backend. The same database powers the public store, the customer account experience, the order pipeline, the inventory ledger and the admin operations console.

Shipped features
  • Luxury storefront
  • Product catalogue
  • Cart & checkout
  • Payment workflow
  • Order management
  • Inventory tracking
  • Customer CRM
  • Loyalty & discounts
  • Email automation
  • Admin dashboard
Technology stack
Frontend
ReactTanStackTailwind
Backend
Node.jsEdge FunctionsREST
Data
PostgresRow-level security
Integrations
Payment workflowTransactional emailInventory sync
Architecture

Maison — system architecture

Storefront and admin console share a unified commerce backend, CRM and inventory ledger — with payments and email integrated through dedicated workflows.

01 · Client surfaces
Luxury storefront
Catalog · checkout
Customer accounts
Orders · loyalty
Admin console
Operations · CRM
02 · Application services
Catalog service
Products · variants
Order pipeline
Cart → fulfilment
Customer CRM
Profiles · history
Loyalty & discounts
Rules engine
03 · Data & integrations
Postgres database
Commerce · CRM
Inventory ledger
Stock · movements
Payment workflow
Checkout integration
Transactional email
Receipts · campaigns
Workflow

Order operations — manual vs automated

Order, inventory and customer data stay in sync from checkout to fulfilment.

Manual processHigh friction · human-in-the-loop
  1. 01
    Order taken over message / call
    No structured record
  2. 02
    Stock checked manually in a sheet
    Often out of date
  3. 03
    Payment confirmed via screenshots
    Hard to reconcile
  4. 04
    Customer details retyped each time
    No persistent CRM
  5. 05
    Promotions tracked on paper
    Easy to over-issue
Automated systemSingle system · runs on its own
  1. 01
    Order placed through the storefront
    Structured cart + checkout
  2. 02
    Inventory ledger updates in real time
    Same source as the store
  3. 03
    Payment workflow handles confirmation
    Logged against the order
  4. 04
    Customer profile builds automatically
    Order history persists
  5. 05
    Loyalty & discount rules enforced
    By the engine, not by hand
Outcomes

What changed for the business.

  • One commerce + CRM system
    Storefront, orders and customers share one backend.
  • Real-time inventory
    Stock movements update with every order.
  • Persistent customer profiles
    History, preferences and loyalty in one place.
  • Operational admin console
    Run the business without leaving the platform.
  • Brand-led storefront
    Custom UI, not a generic theme.
  • Client-owned codebase
    No SaaS lock-in or per-seat tax.
How We Replace Manual Ops

From scattered process to single system.

The shape every Visileo build takes — regardless of industry.

Workflow

Manual operations → automated platform

The same pattern repeats across healthcare, retail, fintech and HR work.

Manual processHigh friction · human-in-the-loop
  1. 01
    Work coordinated in chat
    WhatsApp · email · DMs
  2. 02
    Data lives in spreadsheets
    Versions, tabs, drift
  3. 03
    Approvals over messages
    Untracked, slow
  4. 04
    Manual data re-entry
    Across 2–4 tools
  5. 05
    Reporting after the fact
    Stale by the time it lands
Automated systemSingle system · runs on its own
  1. 01
    Structured workflows in-product
    One surface for the team
  2. 02
    Single source of truth
    Postgres-backed
  3. 03
    Role-based approval pipelines
    Time-stamped, auditable
  4. 04
    Integrated automations
    Email · messaging · webhooks
  5. 05
    Live operational dashboards
    Decide on current data
Reference Architecture

The shape of a Visileo build.

Most platforms we ship follow this layered architecture — adapted to the domain, owned end-to-end by the client.

Architecture

Production reference architecture

Client surfaces, application services, data and integrations — typed contracts between every layer.

01 · Client surfaces
Web app
React · TanStack
Mobile app
Native-feeling
Admin console
Operations UI
02 · Application services
Auth & roles
RBAC · sessions
Domain API
Typed contracts
Background jobs
Queues · cron
AI workflows
Agents · automations
03 · Data & integrations
Postgres
Source of truth
Audit log
Traceability
Email · messaging
Transactional
Payments
Where required
More Projects

A wider sample of the work.

Each is a custom platform with its own architecture, stack and operating model.

03 · Fintech · Modelling

Investment Simulator

Interactive scenario modelling, forecasting and reporting for asset managers and advisors.

System features
  • Scenario inputs
  • Forecasting engine
  • Interactive charts
  • Reporting views
Stack
  • React
  • TanStack
  • Node.js
  • Postgres
Architecture

Calculation engine + reporting layer on shared data model.

04 · HR Tech · Workforce

Employment Tracking System

Workforce platform unifying employee records, scheduling, timesheets and operational reporting.

System features
  • Employee records
  • Scheduling
  • Timesheets
  • Admin reporting
Stack
  • React
  • Node.js
  • Postgres
  • Role-based auth
Architecture

Records · scheduling · reporting modules on a shared admin backend.

05 · SaaS · Operations

Gym Management Platform

Member management, class bookings, billing and a multi-location operations dashboard.

System features
  • Member management
  • Class bookings
  • Billing workflows
  • Multi-location
Stack
  • React
  • Node.js
  • Postgres
  • Edge Functions
Architecture

Member + bookings + billing services on a single multi-tenant backend.

Capabilities

Across the stack.

Frontend
  • React
  • TanStack
  • Tailwind
  • React Native
  • Vite
Backend
  • Node.js
  • Edge Functions
  • Postgres
  • REST · GraphQL
  • Webhooks
AI & Infra
  • OpenAI · Anthropic
  • Vector DBs
  • Cloud Workers
  • Background jobs
  • Realtime
Start a projectHow we build
Start a project

Ready to build something exceptional?

Whether you need a lean Starter System or a full custom platform, we'll help scope the right build for your stage.

Schedule a Discovery CallExplore Work