STUDIO.01 — ABOUT

We engineer the layer around the model.

Recode Asia is an AI engineering studio for agents, retrieval, automation and operational software.

See the patternsSend a brief
STUDIO.02 — WHAT WE BUILD

Systems around real work.

Recode Asia builds AI systems and business software around the way a team already works: approvals, payment tracking, answers from documents and steps that run on their own.

The model is one component. The useful system also needs context, permissions, fixed rules, testing and a clear route to a person.

FULL CAPABILITY LEDGER

Seven ways we build.

The architecture changes with the constraint. The engineering standard does not.

  1. 01

    AI agents

    Agents that read, decide and take bounded action across your inbox, CRM and internal tools — with approval gates and a trace for every run.

    tool use / approval gates / activity log

  2. 02

    Controls around AI models

    Control layers around models: routing, structured outputs, fallbacks, caching, monitoring and testing.

    testing / routing / fallbacks

  3. 03

    Automated workflows

    Deterministic workflows with queues, retries and alerts that move data and work between systems without manual handoffs.

    webhooks / queues / retries

  4. 04

    Company knowledge search

    An org-knowledge product that makes documents, decisions and internal expertise searchable through one permission-aware interface.

    knowledge graph / search / access control

  5. 05

    Answers from your documents

    Answers built only from your source material, with citations, and tested for how often they find the right passage and stay true to it.

    sources / chunking / citations

  6. 06

    CRM/ERP web apps

    Operational software shaped around your workflows, roles and reporting — not a template your team has to work around.

    workflows / permissions / dashboards

  7. 07

    Websites

    Fast, instrumented pages that explain the offer, remove friction and turn qualified attention into a measurable action.

    webgl / gsap / analytics

STUDIO.03 — APPROACH

Start with the decision.

We begin with the workflow, the evidence it depends on and the action that follows. Then we define where AI belongs, where deterministic code wins and which cases must stop for review.

A production plan follows from those boundaries: inputs, tools, evaluation cases, failure routes and the smallest useful release.

STUDIO.04 — OPERATING PRINCIPLE

Control stays visible.

Prompts, retrieval, tools, outputs and approvals are treated as parts of one inspectable system. That makes changes easier to test and uncertain cases easier to stop.

THESIS.01 — SIGNAL

The model can read the corpus. The work is pointing it at the right thing.

The model is not the strategy. We identify the decision, evidence and action that matter — then engineer the system around them.

Real-world applications

Where the leverage is.

Nine industries that already run on data — scattered across screens that don't talk. The revolution isn't new machines; it's the systems that finally coordinate the ones you have.

01

Ports & shipping

Berth windows, container dwell and discharge planning as one scheduler.

Berth & dischargeOne scheduler
02

Rail freight

Yard assembly, crew rotations and brake checks sequenced automatically.

Yard assemblySequenced
03

Warehousing

Pick paths re-slotted nightly from actual order flow.

Pick pathsNightly
04

Construction

Drone progress scans reconciled against BIM weekly; defects flagged, not discovered.

DefectsFlagged
05

Agriculture

NDVI scouting, irrigation scheduling and yield prediction per plot.

Yield predictionPer plot
06

Solar & wind

String-level thermal monitoring with maintenance ranked by output at risk.

MaintenanceRanked
07

Manufacturing

OEE watch with drift detection before the spindle fails.

DriftDetected
08

Logistics fleets

Dispatch, hours-of-service and deadhead optimization across the fleet.

DeadheadOptimized
09

Finance

Reconciliation, KYC refresh and exception queues as one continuous flow.

ReconciliationContinuous

Your numbers get measured before any commitment — see the honest fit check on start a build.

Delivery timeline — estimates
Confirmed brief → first working version14–21days
First version → productionAgreedon day 2

Day 0, you get a written confirmation of your brief. Day 2, a first range for time and cost. Production timing depends on scope.