Skip to content
The operating system for a cold-chain calibration company
Metrology · Cold-Chain Calibration
Web & App Development Integrations Consulting & Strategy

Global Sensors

The operating system for a cold-chain calibration company

Global Sensors runs ISO 17025-accredited calibration for the cold-chain industry in Colombia, and was running sales, orders, invoicing and compliance paperwork on spreadsheets and email. We designed and built one platform — a commercial CRM, a quoting engine with signed PDFs, a service-order and invoicing backbone, a client-signature compliance form, a structured WhatsApp intake and a reporting layer — on a hardened Postgres backend with row-level security on every table.

Duration

Ongoing · since June 2026

Started

June 19, 2026

The operating system for a cold-chain calibration company
15
Systems in production

CRM, quoting, orders, invoicing, ISO forms, WhatsApp intake, reports, portal, automation and more

~7 wks
From first commit to live data

June 19 to August 5, 2026; in continuous evolution since

46/46
Tables under row-level security

103 policies and a role-permission matrix

1,350+
Clients migrated from legacy data

With NIT check-digit validation and duplicate detection

The Challenge

Global Sensors ran its whole commercial and operational cycle in Excel and email: no traceability, no offer versioning, no role permissions and manual numbering prone to error.

  • — Critical processes in spreadsheets, with no single source of truth and no record of who changed what
  • — Manual ISO 17025 compliance: the client form required before calibrating was filled in and signed outside any system
  • — Scattered inbound — WhatsApp, web form, calls — with no structured capture or advisor assignment
  • — No management visibility: sales, conversion and billing metrics were assembled by hand, mixing quoted with actually invoiced
Our Solution

Fifteen systems on a single Supabase/Postgres backend, live with real data seven weeks after the first commit and evolving ever since.

The code now lives in the client’s own organization, with WebMinds as technical partner.

  • + Quoting engine · offers with per-item VAT, annexes from a library, server-side PDFs with merged annexes cached by content signature, a public approval link with client signature, versioning and automatic expiry
  • + Lead-to-cash pipeline · CRM in Kanban and list views with bulk CSV import, service orders with purchase-order evidence, invoicing reconciled automatically against orders
  • + ISO 17025 client signature · a multi-equipment, multi-channel form the client signs before calibration, with a frozen snapshot of client data; no calibration order can be created without it
  • + Structured WhatsApp intake · a five-question flow on the Cloud API that links each message to the CRM by phone or creates the lead, stores media and tracks sent, delivered and read
  • + Automation, audit and reporting · a daily SLA engine, multichannel notifications (in-app, email, web push), audit triggers on every key entity, a client portal and management reports with or without VAT
Selected Frames

Inside the build.

Brand, interface and system — shown as they shipped.

Offer builder with per-item VAT and PDF preview
OFFER BUILDER
Per-item VAT, annexes and a signed, cached PDF
ISO 17025 client-signature form
CLIENT SIGNATURE · ISO 17025
Equipment, magnitudes and channels, signed before calibration
WhatsApp inbox with structured intake
WHATSAPP · INTAKE
A five-step intake that lands as a lead in the CRM
Audit timeline
AUDIT TRAIL
Every change to clients, leads, offers, orders and invoices, recorded by trigger
Under the hood

This was never a website.

Most of the work is backend: a relational domain model, row-level security on every table, business-rule triggers, SLA engines and external integrations. By our estimate, three quarters of the effort lives below the interface.

46/46
Tables with row-level security
103
Security policies
66
SQL functions
57
Database triggers
117
Versioned migrations
13,000+
Audited events since launch
01

A signature that freezes the facts

When the client signs the ISO form, their data is snapshotted, so certificates already issued never change if the client record is edited later.

02

Inactivity measured by real follow-up

Leads close automatically after 15 days without follow-up — measured from the last real activity, not from a timestamp that background processes kept refreshing — and long-cycle projects are excluded.

03

PDFs that only render when they change

Offers are rendered on the server with annexes merged in and cached by a content signature, and hardened against page breaks splitting rows, totals or signatures.

04

Row security without breaking the reports

Advisors see only their own orders while coordinators and the technical lead see everything, and every dashboard still adds up — billed revenue only, with or without VAT.

05

Handover without downtime

The codebase moved to the client’s own organization and the hosting was reconnected with no production downtime; WebMinds stays on as technical collaborator.

06

Hybrid AI Coding

Senior WebMinds engineering steered AI agents (Claude Code) for implementation, with a QA agent reviewing every change. The product itself runs no AI: the WhatsApp intake is a deterministic flow, by design.

The Stack

Technologies & Tools

The tech stack powering this solution

PWA
Next.js
End to end
TypeScript
Postgres · Auth · pg_cron
Supabase
Triggers · Row security
PostgreSQL RLS
Signed offers
React-PDF
Structured intake
WhatsApp Cloud API
Email
Resend
E2E QA
Playwright
Hosting
Vercel
Claude Code
Hybrid AI Coding
The Impact

Beyond the numbers, we delivered a system that transformed how this client operates.

01

From Excel to a single source of truth

The full lead-to-offer-to-order-to-invoice cycle lives in one platform with traceability, versioning and audit — more than 1,350 clients migrated and over 13,000 audited events since launch.

02

ISO compliance that enforces itself

The client-signed ISO 17025 form is now a requirement the system enforces before any calibration order, with an immutable client snapshot and full traceability.

03

A commercial operation that runs itself

WhatsApp — the top lead channel, about half of all leads — flows into the CRM structured; the pipeline manages itself by SLA, and invoices and offers reconcile and expire on their own.

Timeline
  1. Jun 2026
    Design, mockups and use cases
  2. Jun 19–26, 2026
    Platform bootstrap, then SSO, CRM pipeline, offers with PDF, orders, invoicing, client portal, audit and notifications
  3. Jul 2026
    Row-level security hardening after QA and authentication on every endpoint
  4. Aug 4–5, 2026
    Final delivery approved and live with real data
  5. Sep 2026
    WhatsApp automation switch, delivery timestamps, per-item VAT in PDF, owner-based row security
  6. Oct 6, 2026
    Codebase handed over to the client’s organization; support and new features ongoing
Start Your Project

Ready to achieve similar results?

Let's discuss how we can transform your business with a tailored digital solution.

Hi! I'm Atlas