Work · sample deliverables
Sample deliverables
What you receive at each step, shown as excerpts. These are format samples: the business is invented, there are no client names and no client figures.
Sample · format only · no client data
Scope and architecture note
Sent with the fixed-price proposal, after the Operations Review.
Problem
Order lines are typed by hand from Zalo and email into Excel, then again into the accounting system.
In scope
Read orders from a shared inbox and a Zalo export · validate SKUs against the price list · write approved orders to the accounting system · daily exception list.
Out of scope
Marketplace integrations such as Shopee and TikTok Shop · changes to the accounting system itself.
Architecture
A small service with a queue. Every order keeps its source file and an audit trail. A person approves anything the rules cannot match.
Acceptance
Listed per stage in the acceptance checklist, agreed before work starts.
Risks
The price list is kept in two places today. In week 1 we agree which one is the source of truth.
Sample · format only · no client data
Weekly report
Every Friday, one page, in writing.
Done this week
Inbox reader running on test data · SKU validation rules drafted with the sales admin.
Next week
Exception list · first demo on a copy of real orders, at the mid-point stage.
Blocked / needs you
Access to a view-only copy of the price list.
Decisions made
Orders the rules cannot match go to a person, never auto-approved.
Stage status
Stage 1 of 3 · on schedule · no change to price or scope.
Sample · format only · no client data
Acceptance checklist
Agreed before work starts and checked together at each stage.
- Every test order from the agreed sample set is imported or listed as an exception, none silently dropped.
- An approved order appears in the accounting system with the same lines, prices and customer code.
- Each imported order links back to its source message or file.
- The daily exception list reaches the named person by email.
- Runbook and admin guide handed over in English or Vietnamese.
- Source code and access are handed over, and the 30-day warranty starts.
Real documents are shared only under NDA. Formats vary with the project, but the structure above stays the same.
How we work
The same five steps on every project, whether it is one workflow or a whole product stage.
- 0130-minute callWe check whether it is worth solving. The call is free, with no proposal and no obligation. The Founder or the Solution Architect joins.
- 02NDA and process reviewWe sign an NDA before you share real files, then walk through the process with the people who do it.
- 03Operations Review and fixed quoteA written map of the manual work, the cost it carries today and a fixed-price scope with agreed finish criteria. 1–2 weeks.
- 04Build in stagesWork ships in stages with a demo on real data at the mid-point and a short written report every week.
- 05Acceptance and handoverEach stage is checked against the agreed list. Source code is handed over at acceptance, and a 30-day warranty follows.
Where a project like this starts
Workflow Automation
Still copying order details from Zalo into Excel? We’ll use AI to automate that task and measure the time it saves.
