01 / INPUT
A qualified prospect replies with a product and pricing question.
Recode Asia — AI systems for growing businesses
AI systems that cut the manual work in your business.
Approvals, payment tracking and answers from your own documents. We build each system around how your team already works, and you own the code.
Why recode
Approvals, payments, customer records and document searches:these tasks often depend on email, spreadsheets and staff knowledge.Software can sort requests and draft replies or record updates.By default, a person approves before anything is sent, paid or changed in your records.You can choose to automate specific low-risk steps, such as routine reminders, agreed in writing.
The rest of this page shows how we work.
VISION.01 — COUNT
Computer Vision for Your Business
Every animal boxed, tracked and tallied in a single pass — the same instrument we point at your yard, your line or your floor.
SYS.01 — What we build
See the system, not the pitch.
Representative architectures show how we turn an operating rule into a bounded, observable production system.
SYSTEM PATTERN / SELECT A BUILD
One constraint. One observable path.
These are representative patterns, not client results. Each build is designed around the real data, permissions and failure modes in scope.
REPRESENTATIVE ARCHITECTURE
NO CLIENT DATA
02 / DECISION PATH
- 01Classify intent
- 02Read account context
- 03Check response policy
03 / TOOL + ACTION
Draft the reply and prepare the CRM update.
05 / OUTCOME
An approved reply is queued and the opportunity trace is stored.
REPRESENTATIVE ARCHITECTURE
NO CLIENT DATA
01 / INPUT
An account lead asks what changed in the enterprise SLA.
02 / DECISION PATH
- 01Resolve access
- 02Retrieve versioned clauses
- 03Rerank the evidence
03 / TOOL + ACTION
Compose an answer only from approved source passages.
05 / OUTCOME
The answer links to the paragraphs it uses.
REPRESENTATIVE ARCHITECTURE
NO CLIENT DATA
01 / INPUT
A paid invoice event arrives from the billing system.
02 / DECISION PATH
- 01Verify the event
- 02Match the customer
- 03Resolve entitlements
03 / TOOL + ACTION
With automatic updates agreed in writing, give the customer the access they paid for and update the connected records.
05 / OUTCOME
The workspace is reconciled; an operator only sees the exception path.
REPRESENTATIVE ARCHITECTURE
NO CLIENT DATA
01 / INPUT
An operations manager opens a fulfillment exception.
02 / DECISION PATH
- 01Verify the role
- 02Validate the policy
- 03Load the audit context
03 / TOOL + ACTION
Approve the exception and synchronize the ERP record.
05 / OUTCOME
The workflow completes with its decision, actor and system trace attached.
SYS.02 — Work — case study, patterns & demo
Three real workflows. Three patterns. One interface to try.
Start with operational case studies, then inspect the system patterns and playable company-brain demo.
Answers — the question wall
Ask the question you'd ask a senior engineer.
Four questions we get asked in the first call. Answers included — the hedged kind, with ranges.
Founder — 12-person trading firm
“Can inbound leads qualify themselves before my morning?”
Mostly. The system sorts each enquiry and drafts a reply on its own. By default, a person approves before anything is sent, paid or changed in your records. You can choose to automate specific low-risk steps, such as routine reminders, agreed in writing. Complex tenders go to a person, with the draft attached.
Complex tendersSentto a person
Every enquiryDraftedautomatically
Default reply rulePersonapproves
Handover & ownership
What you own when we leave.
The failure mode of custom builds is a system only its author understands. We structure every engagement so that can't happen.
Repository
Your git remote and CI from day one. Nothing we build lives in a vendor account you can't reach.
Documentation
Architecture decisions, data flows and operating notes live in the repo — written while we build, not after.
Credentials
Keys go into your secret manager. After handover we hold none, by design.
Runbook
Written steps your team can follow when something breaks, and when to call a developer.
The honest no
Three things we won't build.
No.
Chatbots that improvise
If a system can't show which of your documents an answer came from, we won't hand it over.
No.
Judgement your regulator attributes to you
Approvals with legal weight stay with the responsible person. Software can send the reminders, draft the documents and run the checks. It does not sign.
No.
A pilot that exists to be a pilot
A trial needs an agreed task and a result to measure. When it ends, we say in writing whether the result supports going further, and stop if it doesn't.