Automation / Less handling, more control
Business process automation with operational control
Friday Works delivers business process automation by standardising the workflow before selecting tools and the appropriate level of autonomy. Every flow has ownership, logs, alerts, exception handling and a safe route back, reducing manual work without adding hidden operational debt.
- Indicative budget
- 7–18 million VNDPer workflow: up to two systems and ten steps; platform fees separate
- Timeline
- 1–3 weeksFor one workflow with clear inputs and an owner
- Approval
- Kept where it mattersMachines handle repetition, people approve consequential steps
- Monitoring
- Logs, alerts, exceptionsNo automation that fails silently
Common problems
What businesses usually ask us to solve
Situation 01
Staff spend hours each week copying data between forms, email and spreadsheets.
How Friday Works responds
The automated flow receives data, validates it, writes it to the right place and notifies the right person.
Situation 02
Quotes and payment requests wait because approvers do not know about them.
How Friday Works responds
Automatic reminders by deadline, and every case has a status showing where it is stuck.
Situation 03
Everyone does it differently, so results are inconsistent.
How Friday Works responds
Standardise first: inputs, rules, exceptions and accountability, then automate.
Situation 04
An automation tool fails silently and you hear about it from customers.
How Friday Works responds
Every flow has logs, alerts, a failure queue and an owner who monitors it.
Project types
Projects we typically take on
Lead and quotation workflows
Route requests, enrich data, create tasks and request approval through explicit criteria.
Operations and reconciliation
Connect forms, data stores and systems to reduce copying, omissions and manual status checks.
Documents and approvals
Create, route, validate and store documents through traceable states.
Which workflow should you automate first?
A good fit when
- It repeats often and the steps and rules are reasonably clear.
- Inputs are stable, such as forms, email or templated files, and the systems have APIs.
- One person owns the workflow and handles exceptions.
Not a fit when
- The process is still disputed, done differently each time and owned by nobody.
- You want consequential decisions fully automated with no approval step.
Work in production
Real products serving real users
How we work
Step by step: who does what and what you receive
Example schedule for one workflow with up to ten steps, two systems and one approval (package A01, 1–3 weeks). Cross-team programmes are split by workflow to deliver results early.
- 01Before signing
Conversation & workflow choice
Choose a workflow with clear value that is stable enough to automate.
Friday Works does
- Hear the steps, tools and recurring failures.
- Assess input stability and how each system can be connected.
- Propose the first workflow, the level of automation and the human approval points.
Your part
Describe the workflow and who does it and owns the result.
You receive
- A scope proposal with acceptance criteria
- Schedule and quotation
CheckpointSign the proposal and pay the first instalment (40%).↗︎
- 02Week 1
Observe & measure
Measure today's process so the saving can be proven.
Friday Works does
- Record every step, waiting time, error and piece of rework.
- List exceptions: missing data, wrong formats, follow-up questions.
- Capture a baseline for time and errors.
Your part
Allow observation or a screen recording and provide real input examples.
You receive
- A current-process map
- Baseline and exception list
CheckpointAgree the target workflow.↗︎
- 03Week 1
Standardise & design
Remove unnecessary steps before a machine repeats them.
Friday Works does
- Remove unnecessary handling and agree the rules.
- Design triggers, states, permissions and approval steps.
- Choose tools: direct APIs, n8n or Make, RPA, or AI/OCR for unstructured input.
Your part
Review the new flow with the people who do the work.
You receive
- The automation design
- Tool choice and expected platform costs
CheckpointApprove the flow design.↗︎
- 04Weeks 1–2
Build & trial
The flow runs on real data at small scale.
Friday Works does
- Build the automation and the required connections.
- Add logs, alerts and a queue for failures.
- Trial with real, masked data.
Your part
Check trial results and report anything that is not right.
You receive
- The flow running in a test environment
- Trial results
CheckpointFlow demo and the second instalment (40%).↗︎
- 05Weeks 2–3
Parallel run & go-live
Run alongside the old process briefly before switching over.
Friday Works does
- Compare automated results with manual results.
- Tune exception handling and alert thresholds.
- Switch to production once results are stable.
Your part
Confirm the comparison and the switch-over date.
You receive
- The flow in production
- Figures compared with the baseline
- 06After go-live
Handover & observation
The owner can monitor the flow and fall back to manual work when needed.
Friday Works does
- Write a runbook: monitoring, error handling, pausing and manual fallback.
- Hand over configuration, accounts and source code (if any).
- Observe the early period and fix defects during the warranty.
Your part
Name the person who monitors the flow and handles exceptions.
You receive
- Runbook and monitoring view
- Three months of defect fixes for Friday Works' implementation
CheckpointAcceptance and the final instalment (20%).↗︎
Deliverables
What you receive
Workflow
- Current map and baselineSteps, waiting time, errors and rework before automation.
- Exception inventoryUnusual cases and how each type is handled.
- New flow designTriggers, rules, states, permissions and approvals.
Automated flow
- Automation and connectionsOne workflow of up to ten steps across two systems (package A01).
- Notifications and approval remindersThe right person at the right time, with what they need to decide.
- AI or OCR steps when neededFor email and unstructured documents, with people approving important outputs.
Monitoring
- Per-run logsSee what every run processed and whether it succeeded.
- Alerts and failure queueFailures wait for a person instead of disappearing.
- Tracking viewRuns, error rate and time saved against the baseline.
Handover
- RunbookHow to monitor, handle errors, pause and fall back to manual work.
- Accounts and configurationAutomation-platform accounts registered in the company's name.
- Three months of fixesDefects in what Friday Works built are fixed after acceptance.
Technology and tools we commonly use
The exact stack is chosen for each project and recorded in the proposal rather than forcing one platform onto every problem.
- n8n, Make or custom codeReady-made tools for common flows; code when flows are complex or high-volume.
- APIs and webhooksDirect connections to CRM, email, spreadsheets and business software.
- RPA when no API existsSimulates interface actions, with its durability limits stated clearly.
- AI and OCRFor unstructured content such as email, invoices and scanned documents.
Collaboration
What both sides prepare
What you prepare
- A workflow owner responsible for handling exceptions.
- A description or screen recording of the current process.
- Least-privilege accounts for the systems involved.
- Real input examples with sensitive data masked, including difficult cases.
- A recipient for failure alerts.
What we check before handover
- Runs correctly on real data within the trial scope, including the listed exceptions.
- Errors are caught, logged and alerted without losing data.
- Approval steps cannot be bypassed.
- Accounts use least privilege; secrets are not exposed in the flow.
- There is a way to pause or fall back to manual work.
- Post-launch figures can be compared with the baseline.
Pricing
Indicative packages and how the budget is set
Related starting packages
Version 20 October 2026 · Unit: million VNDWorkflow automation
7–18million VND / workflow
Estimated: 1–3 weeks
Baseline scope. One workflow spanning up to two systems and ten steps; one approval where needed; notifications, logging and basic error handling.
Not included: Third-party platform or API usage fees.
These are indicative budgets for new engagements, not fixed quotations or prices from completed contracts. Scope, schedule and cost are confirmed for each project before work begins.
Typical timelines
- One focused workflow (A01)
- Often 1–3 weeks when the process, data and source systems are clear.
- Cross-team programme
- Divided by workflow to reduce change risk and create evidence early.
- Observation period
- Always needed after release to tune exceptions and validate the saving.
The budget depends on
- The number of steps, rules, roles and exception cases.
- The number of connected systems and the quality of existing APIs.
- Task volume, frequency and approval requirements.
- Observability, alerting, audit-trail and operational support needs.
Proposed payment schedule
- 40%Project start
- 40%Demo & core features
- 20%Acceptance & handover
Before a quote is final
- Agree the page, feature, data and acceptance-criteria list before implementation.
- The schedule starts after scope approval, receipt of required inputs and the first payment.
- The proposal includes three months of defect correction for Friday Works' implementation after acceptance.
- Domain, hosting, email, AI/API, data, licences, third-party services and applicable tax are shown separately.
After handover
Warranty, maintenance and next steps
Three months of defect fixes
Defects in the work Friday Works delivered are fixed for three months after acceptance and are not charged as maintenance.
Monthly maintenance
2–5 million VND / month
Up to 6 hours/month · One application; log review, compatibility updates and technical support.
Support is provided during business hours, not as a 24/7 service. Infrastructure and work above the included allowance are quoted separately. Warranty defects are not charged as maintenance.Frequently asked questions
Before we begin
01Can an unclear process be automated?
An unclear process can sometimes be prototyped, but automating an ambiguous process often makes errors happen faster. The first step clarifies inputs, rules, exceptions and accountability.
02What determines business process automation cost?
Business process automation cost depends on workflow steps and connected systems, input stability, exception volume, approval requirements, any AI or OCR component, logging, alerts and operating ownership. Friday Works begins with a workflow that has a measurable baseline before expansion.
03Does every workflow need AI?
Not every workflow needs AI. Deterministic rules should use conventional logic because it is easier to inspect and predict. AI is better suited to unstructured content or decision support, with suitable review.
04How do we stop automation failing silently?
To stop automation failing silently, the flow needs structured logs, threshold-based alerts, a failure queue, reconciliation visibility and a runbook. One person must own monitoring and exception handling.
05Should we use n8n, Make or custom code?
n8n or Make are quick for common flows and easy to adjust, but carry platform fees per run or plan. Custom code makes sense when flows are complex, high-volume or need tight data control. The choice and platform costs are documented during design.
06How soon will we see results?
Right after go-live there are figures for time and errors compared with the baseline. An observation period is usually needed to tune exceptions before the saving is confirmed as stable.
Talk to Friday Works
Choose one workflow worth improving
Share the current steps, connected systems and recurring failures. We will identify what to standardise, automate or keep under human control.
Describe your projectAfter you send a request
- 01Send a short brief
Your goal, current situation and preferred timing; attachments are welcome.
- 02A reply within one business day
Friday Works sends clarifying questions or proposes an online call.
- 03Discuss the scope
Review the goal, risks and an approach that fits the budget.
- 04Receive a written proposal
Scope, milestone schedule, cost and acceptance criteria.