Skip to content
Portal LabsSOFTWARE ENGINEERING R&D

Software built the wayscience is done.

Operational systems and WhatsApp-first products for domains where being wrong has a cost.

  • Method first
  • Evidence over assertion
  • Instrumented and reproducible
WHAT WE DO

Five things, done properly

The problems we solve repeatedly. Most of it ships on WhatsApp, because in Latin America that is where people already are.

  • WhatsApp systems and conversational interfaces

    Real systems delivered through WhatsApp, with nothing to install: field operations, customer service, interviews, loyalty, finance, emotional support. The same core runs on Telegram and email, with LINE next.

    • WhatsApp Business API at scale
    • Human handoff at defined thresholds
    • One core across WhatsApp, Telegram, email and web
  • Operational systems for the field

    Software that runs a physical operation: scanning, tracking, dispatch, chain of custody. Mobile-first, offline-tolerant, built for gloves and bad light.

    • Real-time state across devices
    • Offline capture with sync queues
    • Role hierarchies and audit trails
  • Standards and protocol integration

    Systems that must speak an industry's formal language: teletype messaging, laboratory test methods, biosecurity rules. Reading the specification is the job.

    • IATA Type B baggage messaging
    • ASTM test methods and acceptance criteria
    • Legacy and third-party bridges
  • Measurement and quality platforms

    Laboratory and quality-control software: specimen lifecycles, statistical process control, results traceable to the observation that produced them.

    • Sample and specimen tracking
    • Statistical process control
    • Instrument integration
  • Agent engineering and evaluation

    Language-model agents put under test: grounded in approved sources, gated by question suites, built to say when they are not sure. On hosted models or ones we host ourselves, including local models on a single consumer GPU.

    • Golden-question regression suites
    • Confidence thresholds and escalation
    • Local and self-hosted models
CHANNELS WE SHIP ON
  • WhatsApplive
  • Telegramlive
  • Emaillive
  • Weblive
  • Mobilelive
  • LINEin progress

WhatsApp is where most of Latin America already is. It is not a dependency: the same systems run on Telegram, email and the web.

Tell us where you are starting from. We take it from there.

Start a project
THE METHOD

We treat a build like an experiment

Every project runs this loop. It does not stop at launch.

  1. 01

    OBSERVE

    Go where the work happens

    The ramp at night, the lab bench, the counter at peak hour. Watching people work shows the process they actually follow.

  2. 02

    MODEL

    Write the domain down

    States, transitions, invariants, and the standard the system must obey. A state that cannot be drawn is not understood yet.

  3. 03

    INSTRUMENT

    Build it to be measured

    Every state change traceable to a person, a device and a moment. We do not claim what we cannot observe.

  4. 04

    FALSIFY

    Try to break it first

    Golden sets, simulated operations, adversarial inputs. We look for the case that disproves the design while being wrong is still cheap.

and back to observation. The loop does not close.

WHAT THAT BUYS YOU

Reproducibility

A result you cannot reproduce is an anecdote. Every output traces back to the run that produced it.

Uncertainty

A system that is always confident is not measuring anything. Ours say how sure they are, and hand off when they are not.

Traceability

Every figure on a report walks back to who recorded it, on what device, under which rules.

HOW WE WORK TOGETHER

Three ways a project starts

Clients arrive at different stages. We work with all three; only where we join changes.

  1. 01

    Discovery, design and build

    You know something is wrong or possible. You do not yet know what to build.

    We start by watching the work, not writing a proposal. The longest route in, and usually the cheapest, because the expensive mistake is building the wrong thing well.

    We handle
    • Field observation
    • Problem definition
    • System design
    • Implementation
  2. 02

    Design and build

    You know what you want. There is no technical design yet.

    You bring the requirement and the domain. We turn it into an architecture and decisions you can review before anyone writes code, then build it. Most of our work starts here.

    We handle
    • Architecture
    • Data modelling
    • Technical design
    • Implementation
  3. 03

    Build

    You have a design or specification and need it implemented properly.

    We implement what you specified. We will say where we think it will hurt later; if you still want it that way, we build it that way. It is your system.

    We handle
    • Implementation
    • Integration
    • Testing
    • Deployment
SELECTED WORK

A few of the things we have built

Systems in production, products of our own, and one research project. Client names are omitted.

OPERATIONAL SYSTEMS

Built for organisations that run physical operations at scale.

Tell us where you are starting from. We take it from there.

Start a project
CONTACT

Where are you starting from?

Two questions, then the form. It tells us who should read your message.

STEP 1 / 2

Do you already know what needs to be built?