Integration / One reliable data flow
CRM and ERP integration, APIs and data synchronisation
Friday Works delivers CRM and ERP integration that connects data and business states across the platforms a company already uses. Each integration is designed with mapping, access control, logs, retries and reconciliation so manual handling is reduced without hiding failures.
- Indicative budget
- 5–15 million VNDPer connection: one data flow between two systems, up to five documented APIs
- Timeline
- 1–3 weeksPer connection, when APIs, sandboxes and documentation are ready
- Data
- No duplicates, no lossesStable identifiers, controlled retries and regular reconciliation
- Operation
- Logs & alertsKnow immediately when sync fails, with a runbook to fix it
Common problems
What businesses usually ask us to solve
Situation 01
Website leads are copied into the CRM by hand, and some go missing.
How Friday Works responds
Forms and campaigns push leads straight into the right CRM pipeline with their source, without re-entry.
Situation 02
Website orders and ERP stock levels often disagree.
How Friday Works responds
Sync follows explicit rules: which system holds the canonical data, how often it syncs and how conflicts are resolved.
Situation 03
One flaky connection and records are duplicated.
How Friday Works responds
Every record has a stable identifier, so repeated delivery still creates one record; failures go to a queue for reprocessing.
Situation 04
Sync breaks silently and nobody notices for days.
How Friday Works responds
Structured logs, threshold alerts and a reconciliation view show how many records succeeded, failed or are pending each day.
Project types
Projects we typically take on
Website to CRM
Send leads, campaign sources and customer requests into the right pipeline without duplicate entry.
CRM to ERP
Synchronise customers, orders or approved states according to explicit business rules.
Partner APIs and data
Connect payment, logistics, reporting or industry platforms through managed APIs.
When is API integration the right choice?
A good fit when
- Both systems offer an API or a stable export and import mechanism.
- A daily, repeated data flow is handled manually or often goes wrong.
- You know which system holds the canonical data and who handles sync failures.
Not a fit when
- The target system has no API and no file exchange, yet real-time sync is required.
- A large historical migration or changes to a third-party system are expected within one connection package.
How we work
Step by step: who does what and what you receive
Example schedule for one data flow between two systems with up to five documented APIs (package S03, 1–3 weeks). Multi-system flows are staged, one measurable flow at a time.
- 01Before signing
Conversation & priority flow
Start with the most valuable data flow instead of connecting everything at once.
Friday Works does
- Understand the source and target systems, the data and the failures you see.
- Review API documentation, sandboxes (test environments) and provider limits.
- Propose the priority flow, sync direction and acceptance criteria.
Your part
List the systems in use and provide API documentation or a vendor contact.
You receive
- A scope proposal: flow, data objects and sync direction
- Schedule and quotation
CheckpointSign the proposal and pay the first instalment (40%).↗︎
- 02Week 1
Data map & rules
Agree on paper how data moves before the first line of code.
Friday Works does
- Draw the system map and identify where canonical data lives.
- Build a field and state mapping between the two systems.
- Agree frequency, duplicate prevention, conflict handling and least-privilege API access.
Your part
Provide sandbox accounts and least-privilege API keys, and confirm business rules.
You receive
- An integration map
- A data mapping and sync rules
CheckpointApprove the mapping and rules.↗︎
- 03Weeks 1–2
Build & test the connection
Test the good paths and the bad ones on a test environment.
Friday Works does
- Build the integration service, webhook or scheduled job.
- Add authentication, bounded retries, duplicate prevention and logging.
- Test success, failure, timeout and duplicate delivery in the sandbox.
Your part
Confirm sync results on test data.
You receive
- A connection running in the test environment
- Results for each tested scenario
CheckpointSync demo and the second instalment (40%).↗︎
- 04Weeks 2–3
Controlled go-live
Switch on in parts, reconcile the numbers, then run in full.
Friday Works does
- Enable in production in small batches or alongside the old process.
- Reconcile record counts between the two systems.
- Turn on alerts for the accountable owner.
Your part
Monitor the first days together and confirm the reconciliation figures.
You receive
- The sync flow running in production
- A reconciliation report
- 05After go-live
Handover & runbook
The owner can recognise failures and act on them without guesswork.
Friday Works does
- Write a runbook: detecting failures, reprocessing and contacting the provider when an API changes.
- Hand over source code, configuration and accounts.
- Fix defects during the warranty period.
Your part
Name the alert recipient and accept the work against the criteria.
You receive
- Runbook and configuration documentation
- Three months of defect fixes for Friday Works' implementation
CheckpointAcceptance and the final instalment (20%).↗︎
Deliverables
What you receive
Integration design
- System mapThe systems involved, the data direction and where canonical data lives.
- Data mappingMatching fields, formats and states between the two systems.
- Sync rulesFrequency, duplicate prevention, conflict handling and access rights.
A working connection
- Integration serviceWebhooks, queues or scheduled jobs, depending on real-time or batch needs.
- Authentication and retriesBounded retries on temporary failures without creating duplicates.
- Protected credentialsAPI keys stored securely and kept out of source code.
Observability & reconciliation
- Structured logsTrace every record through the flow without logging sensitive data.
- Threshold alertsNotify the owner when failures exceed the agreed level.
- Reconciliation viewDaily counts of successful, failed and pending records.
Handover
- Incident runbookSteps to recognise failures, recover and coordinate with providers.
- Source code and configurationHanded over under the contract with the related accounts.
- Three months of fixesDefects in Friday Works' implementation 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.
- REST APIs and webhooksThe most common way to connect CRM, ERP, payment and partner platforms.
- Queues and scheduled jobsKeep the flow resilient to temporary failures and allow batch processing.
- Node.js / TypeScriptTyped integration services that are easy to test.
- Logs, alerts and reconciliationSee how the flow is running without opening every system.
Collaboration
What both sides prepare
What you prepare
- API documentation, sandbox accounts and least-privilege API keys.
- People who understand the business rules of each system.
- Sample data, including the cases that usually cause errors.
- A contact at the CRM, ERP or partner-platform vendor.
- A recipient for sync-failure alerts.
What we check before handover
- Success, failure, timeout and duplicate-delivery scenarios are tested.
- Re-sending the same event does not create a duplicate record.
- Reconciliation figures match between both systems on test data.
- API keys are stored securely with only the permissions needed.
- Logs contain no sensitive data.
- Alerts reach the right person when failures cross the threshold.
Pricing
Indicative packages and how the budget is set
Related starting packages
Version 20 October 2026 · Unit: million VNDAPI integration & synchronisation
5–15million VND / connection
Estimated: 1–3 weeks
Baseline scope. One data flow between two systems; up to five documented APIs; authentication, mapping, logging, retry and duplicate control.
Not included: Creating missing APIs, large historical migrations or third-party system changes.
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 standard connection (S03)
- Often 1–3 weeks when APIs, sandboxes and documentation are available on both sides.
- Multi-system flow
- Usually divided into stages by data source and operational importance.
- Technical discovery
- May be required before scheduling when APIs are closed, data is legacy or rules are unclear.
The budget depends on
- The number of systems, endpoints, data objects and synchronisation directions.
- API quality, sandboxes, documentation and provider limits.
- Data volume, frequency, migration and conflict rules.
- Logging, alerting, security and operational support requirements.
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 you integrate a system without an API?
A system without an API can sometimes be integrated through exports, imports, file exchange or automation tools, but reliability and maintainability differ. Technical discovery must identify a safe option and make the limitations explicit.
02What determines CRM, ERP or API integration cost?
CRM, ERP or API integration cost depends on the number of systems and data flows, API documentation quality, mapping rules, real-time synchronisation, migration, access controls, reconciliation and the required operating support. Technical discovery defines a priority flow, failure cases and acceptance criteria before pricing.
03How do you prevent duplicate data?
To prevent duplicate data, the integration flow needs stable identifiers, idempotency rules, state mapping and reconciliation. Retries and repeated event delivery must be tested before production use.
04Who is responsible if a third-party API changes?
Responsibility for third-party API changes is set in the operating scope, which defines ownership, alerting and support. The runbook explains how to detect failure, recover and coordinate with the provider when a contract changes.
05Should we sync in real time or on a schedule?
Real-time sync through webhooks suits leads, orders or states that need immediate action. Scheduled batch sync suits reports, catalogues or data that tolerates delay, and is usually cheaper and easier to reconcile. Many systems combine both.
06Our software is a local Vietnamese product. Can it be integrated?
Local Vietnamese software can be integrated if it offers an API or a suitable export and import mechanism and the business has access. Friday Works reads the vendor's API documentation during the first conversation to confirm feasibility before quoting.
Talk to Friday Works
Connect systems through a clear data flow
Tell us the source, destination, data to synchronise and the failures you see today. The first step is an integration map that can be tested.
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.