NLV-26-CRM
Delivered
Twenty requests, one row. Replies and bookings into a CRM exactly once.
A Nordic B2B SaaS
20 → 1
Concurrent requests to rows written
0
Errors in the 24-hour shadow run
Writing code since 2023 · client work since 02/2025 · 26 shipments · 10 systems live
I build what your business needs: web systems, automations and AI agents.
Tell me the job and I pick the tools for it. Every shipment on the board links to its proof: a live system, the tests, or before-and-after numbers.
Departures · since 02/2025HCMC GMT+7
Tracking ID, Shipment, Proof, Status
- NLV-26-CRMDELIVEREDInto the CRM, exactly onceA Nordic B2B SaaS20 → 1
- NLV-26-PRFDELIVEREDTwo slow intros removedVan Data Team4,493 → 526 MS
- NLV-26-HRMLIVEFactory HR, clock to timesheetA furniture manufacturer in Vietnam79,262 → 6,354
- NLV-26-AGTDELIVEREDNews agents with human gatesVan Data Team8 ROLE AGENTS
- NLV-25-EVSLIVEeVS e-invoice platformPratekEVSAPP.VN
Worked on
PratekUniben FoodsVietcoseVSVan Data TeamOntevo
and 9 private clients in Vietnam, the US, Europe and Singapore, names withheld
Partners
Tran Tien Van (Van Data Team) and Tim N. (Repurgo), both Upwork Top Rated Plus with 100% Job Success (their profiles, read 21 Oct 2026)
What shipped, and how it was checked
Four records and a test count, each with a different kind of proof: a load test, a speed report, production data and a public demo.
NLV-26-PRF
Delivered
Two slow intros removed, and what they were hiding fixed
Van Data Team
Top of the page visible on desktop: 4,493 ms → 526 ms. JavaScript loaded in the first 6 seconds: 2,425 KB → 695 KB
NLV-26-RIB
Live
Twenty account briefs that refresh themselves
A US industrial supplier
20
Account briefs kept current
Read the record →Open the demo ↗
NLV-26-HRM
Live
An HR system for a furniture factory, from time clock to timesheet
A furniture manufacturer in Vietnam
79,262 → 6,354
Time-clock punches turned into workdays
1,338
test cases in 8 repositories where I wrote most of the commits
Counted on 21 Oct 2026
- NLV-26-KOL473
- NLV-26-CRM199
- NLV-26-HRM153
- NLV-26-RIB147
- NLV-26-XCL110
- NLV-26-OUT108
- NLV-26-LCL93
- NLV-26-REV55
The 66-second version
Built in code from the same data as this page, with an AI coding assistant. Every figure in it has a record. Turn the sound on for the narration.
What I build
Built to your brief, on the tools that fit it. A single project, a contract, or a seat on your team.
FIG 03 · THE ROW THAT CHANGED 01
Web systems
Order, invoice, HR and internal tools, or features in a product you already run. Anything that should get faster is measured before and after.
You get
- Working software with tests
- Before-and-after numbers for speed work
- Notes your team can keep
FIG 04 · SORT, STORE, TELL A PERSON 02
Automations
Leads, replies and reports moving between your tools without sending twice or losing one. Rules decide first; a model is asked only when the rules are unsure.
You get
- The workflows and the code around them
- Tests on real payloads
- A shadow run before the switch
FIG 05 · ROLES, A CHECK, A PERSON 03
AI agents
Agents that research, draft, check and act inside your tools. Each one has a narrow role, a check it must pass, and a person approving whatever leaves the building.
You get
- Agents with limits on cost, retries and time
- A log of every run
- Approval steps where you want them
FIG 06 · FRAMES, CAPTIONS, WAVEFORM 04
Explainer video
Explainers and short videos with scenes written in code, captions timed to each word, and checks on every render. Vietnamese or English.
You get
- MP4 in the formats you post
- Caption files and an editable project
- A QA sheet for every render
Watch a run fail and recover
Two real systems, anonymized where needed. Each plays once when it comes into view; step through it yourself.
Replies from LinkedIn and email outreach and Calendly bookings arrive as webhooks, sometimes more than once.
- Normal run01DoneReplies from LinkedIn and email outreach and Calendly bookings arrive as webhooks, sometimes more than once.
- 02DoneEach event gets a key. An atomic claim on a Data Table lets only the first copy through: 20 concurrent requests write 1 row.
- 03DoneRetries and duplicates stop here instead of reaching Slack twice.
- 04DoneReplies are classified into six labels, in English and Finnish. Rules decide first.
- 05DoneThe CRM is written first, so nothing that reached Slack is missing from the CRM.
- 06DoneOnly replies that need action go to Slack and a person. Declines are stored in the CRM and stop there.
- Something breaks07FailedOne workflow reported success while Slack received nothing. Its filter required a campaign field that real reply events do not carry.
- Recovery08DoneI fixed the condition and replayed exactly the 3 events that were lost. The tests now run on real payloads, not sample ones.
A research agent collects primary sources and writes a claim registry: every usable fact with its source and date.
- Normal run01DoneA research agent collects primary sources and writes a claim registry: every usable fact with its source and date.
- 02DoneThe hook and the script are drafted by their own agents. Each sentence carries the ID of the claim it states, and a person approves both.
- 03DoneA scene agent gives each sentence one visual; voice and visuals are produced with their rights recorded. No synthetic evidence.
- 04DoneWord timings come from forced alignment against the script, not from estimates.
- 05DoneScenes render in code, and a person signs off before anything is published.
- Something breaks06FailedIf a spoken word cannot be matched to the script, the gate fails closed and the stage is sent back instead of guessing.
- Recovery07DoneThe stage is revised and checked again. Limits on revisions, budget and time stop a run that would otherwise loop.
How work starts
- 1
A 20-minute call
We go through what runs today, what should change, and how you will know it worked.
- 2
Scope in writing
One page: what changes, what stays, the checks that define done, and the first slice.
- 3
Small slices
Work lands in pieces you can review, each with its tests or before-and-after numbers.
- 4
Handover
Code, tests, a runbook and the editable files, so your team can run it without me.
Explainer videos, checked frame by frame and handed over editable
Pin Yếu, a character drawn in code, walks across the section.
A recent delivery
For a network of education and storytelling channels: a new 4:30 narration with the existing scenes re-timed to it, 178 subtitle lines with 27 keywords highlighted, and a CapCut project split into 16 scenes with separate voice and music tracks. The client then learned to run the same pipeline in a call.
The client is not named and the video is not published.
Tell me what you need built
A few lines are enough: what runs today, what should change, and by when. For a role, paste the job link.