Cambodia-based B2B software development company

Software built for the way your organisation works.

We design and build custom operational software for businesses and institutions.

DAVO software team working together in a Phnom Penh studio
Product thinking, engineering and delivery from one close team.
Based
Cambodia
Founded
2023
Team
16 people
Focus
B2B only

Your operation is specific. Your software should be too.

We turn organisation-specific workflows, rules and integrations into dependable software, staying close from the first working session through rollout and improvement.

Integration testing workspace with laptops, network equipment and payment hardware

Custom software development

Understand the operation

We map users, decisions, data, exceptions and the systems already in place.

Design the right system

We define workflows, architecture and interfaces before complexity reaches production.

Build it into real use

We develop, test, integrate and support the software as it becomes part of day-to-day work.

Selected work

Software we have built.

Eight anonymised client commissions across finance, education, logistics and the public sector. Each system was built around one organisation's operating problem.

Draft case-study figures. KPI values are provisional examples for DAVO and client validation, not verified performance claims.

Working professionals completing practical accounting exercises in an evening class

Anonymised client case study

Professional education provider, accounting

A learning platform built for accounting practice

A managed environment for accountants, instructors and programme teams, designed around practice and assessment.

What DAVO built
Curriculum management, ledger-based exercises, assessments, learner and instructor portals, cohort administration and certificates.
Read full case study

Situation

The provider needed more than a library of recorded lessons. Its programmes relied on practical accounting exercises, instructor review, timed assessments and formal certification across multiple cohorts.

Challenge

Bring enrolment, curriculum delivery, ledger-based practice, assessment and certification into one managed learning journey.

What DAVO delivered

  • Curriculum and cohort management
  • Interactive journals and ledger exercises
  • Assessment, marking and instructor feedback
  • Certificate generation and learner records

Example workflow

A learner completes a double-entry bookkeeping exercise inside a simulated ledger. Validation identifies an unbalanced entry, the instructor can review the working and the final assessment feeds directly into the learner record. Programme staff can then issue the correct certificate without rebuilding results in a spreadsheet.

System outcome

Enrolment, practice, assessment and programme administration now happen within one connected platform.

Draft KPI examples

Provisional figures for client validation.

+29%
Course completion rate
-44%
Administration time per cohort
2.3x
Faster certificate issuance
University registrar verifying a graduate credential at a service counter

Anonymised client case study

University, digital credentials

University credentials that can be verified

A university-controlled system for issuing, revoking and independently verifying academic credentials.

What DAVO built
Permissioned blockchain proofs, issuance and revocation workflows, secure records and a public verification flow.
Read full case study

Situation

Employers and partner institutions depended on the registrar to confirm certificates manually. The university wanted faster verification without publishing private student records or giving up control of credential issuance.

Challenge

Create an independently verifiable credential proof while keeping personal data private and every issuance decision under registrar control.

What DAVO delivered

  • Registrar issuance and revocation controls
  • Permissioned blockchain credential proofs
  • Secure graduate and programme records
  • Public QR and reference verification

Example workflow

After graduation is approved, the registrar issues a digital credential linked to a tamper-evident proof. An employer scans the QR code and receives a valid, revoked or not-found response. The verification confirms authenticity without exposing grades, identity documents or the university's internal records.

System outcome

Graduates and employers can confirm authenticity while the university remains in control of its academic data.

Draft KPI examples

Provisional figures for client validation.

<15 sec
Typical public verification time
-79%
Manual verification requests
100%
Issued credentials with lifecycle history
Postal workers sorting parcels during an early morning depot shift

Anonymised client case study

Postal operator, core operations

A connected record for every postal item

An operational system following items from counter acceptance and sorting to routing and final handover.

What DAVO built
Parcel acceptance, labels, bag manifests, sorting, route management, tracking events, exceptions and administration.
Read full case study

Situation

Parcel events were created by different teams at counters, sorting facilities and delivery locations. Missing handoff information made customer enquiries and exception investigation slow.

Challenge

Create one item record across acceptance, bagging, sorting, routing, exceptions and final handover, with simple workflows for busy operational teams.

What DAVO delivered

  • Counter acceptance and label generation
  • Bag manifests and facility handoffs
  • Sorting, routing and tracking events
  • Exception handling and operational reporting

Example workflow

A counter operator accepts a parcel and prints its label. The item is scanned into a dispatch bag, transferred between facilities and assigned to a route. If a handoff scan is missing or delivery fails, an exception appears with the parcel's previous events and responsible location.

System outcome

Teams can follow each item through a consistent workflow and investigate issues with clearer context.

Draft KPI examples

Provisional figures for client validation.

-32%
Time spent recording handoffs
-41%
Missing tracking events
+24%
Same-day exception resolution
Courier and shop owner completing a delivery handover on a rainy Phnom Penh street

Anonymised client case study

Delivery business, network operations

One operating system for delivery

A shared platform for merchants, dispatchers, couriers and customer-support teams.

What DAVO built
A merchant portal, dispatch console, courier workflow, service zones, pricing rules, notifications and proof of handover.
Read full case study

Situation

Orders, dispatch decisions and courier updates moved through separate channels. Merchants and support teams often had to contact dispatch directly to understand the current delivery state.

Challenge

Give every participant the same live order state while supporting service zones, pricing rules, courier assignment and evidence of handover.

What DAVO delivered

  • Merchant order and account portal
  • Dispatcher queue and courier assignment
  • Courier mobile workflow and status events
  • Pricing, notifications and proof of handover

Example workflow

A merchant submits an order and receives a price based on the service zone. Dispatch sees available couriers and assigns the job. The courier records pickup, arrival and handover from a mobile workflow, while the merchant and support team see the same events without calling dispatch.

System outcome

Every participant works from the same delivery state, reducing manual coordination across the network.

Draft KPI examples

Provisional figures for client validation.

+18%
Orders managed per dispatcher
-27%
Failed first-attempt deliveries
-36%
Support requests about order status
Small-business owner submitting tax documents at a public-service counter

Anonymised client case study

Public-sector organisation, tax administration

A clearer digital tax journey

A controlled platform connecting taxpayer services with internal case management.

What DAVO built
Taxpayer services, internal case management, configurable rules, payment integrations, audit history and reporting.
Read full case study

Situation

Taxpayers needed a clearer route through registration, declarations and payment. Internal teams also needed consistent case records, configurable rules and evidence for review decisions.

Challenge

Connect the public taxpayer journey with the internal review process while preserving permissions, audit history and policy-driven rules.

What DAVO delivered

  • Taxpayer registration and account services
  • Declarations, calculations and submissions
  • Payment and reconciliation integrations
  • Internal reviews, cases and audit reporting

Example workflow

A business creates an account, submits a declaration and receives validation before payment. If a submission requires review, the platform opens an internal case with the declaration, payment state and supporting documents already connected. Authorised officers record decisions against the same history.

System outcome

Taxpayers have a clearer path while authorised teams retain traceability across each case and decision.

Draft KPI examples

Provisional figures for client validation.

-43%
Registration processing time
-31%
Incomplete submissions
+26%
Taxpayers completing self-service
Bank risk reviewers completing a dual-control vendor approval process

Anonymised client case study

Bank, vendor governance

Vendor approvals built around bank policy

An internal application for governed vendor onboarding, review and approval.

What DAVO built
Document intake, validation, a configurable approval matrix, required reviewers, escalation, comments and version history.
Read full case study

Situation

Vendor requests differed by risk, value, service type and requesting department. Email approvals made it difficult to apply the right matrix consistently or show why a vendor had been approved.

Challenge

Translate bank policy into a configurable approval matrix that could route each request to the correct reviewers and preserve supporting evidence.

What DAVO delivered

  • Vendor profile and document intake
  • Risk and contract-value classification
  • Configurable approval matrix and escalation
  • Comments, decisions and version history

Example workflow

A department submits a vendor with the proposed contract and risk information. The matrix calculates which compliance, procurement, finance and executive approvals are required. A material contract change creates a new version and reroutes only the approvals affected by that change.

System outcome

Requests follow a consistent governance model with visible status and a complete approval trail.

Draft KPI examples

Provisional figures for client validation.

-48%
Average vendor approval cycle
-57%
Manual approval status follow-ups
91%
Requests complete at first review
Payment technician and cafe owner testing a point-of-sale integration before opening

Anonymised client case study

Bank, merchant payments

One POS architecture, different business needs

A common integration layer supporting both large-business and small-business merchants.

What DAVO built
Integration adapters, authorisation and reversal flows, settlement, reconciliation, monitoring and merchant onboarding components.
Read full case study

Situation

Large merchants and small businesses used different terminal setups, onboarding paths and operational processes. The bank needed to support both without duplicating transaction and settlement logic.

Challenge

Create a common integration architecture for authorisation, reversals, settlement and reconciliation, with adaptable connectors for each merchant environment.

What DAVO delivered

  • Terminal and merchant-system adapters
  • Authorisation, reversal and retry flows
  • Settlement and reconciliation processing
  • Monitoring and merchant onboarding tools

Example workflow

A small merchant can be onboarded through a standard terminal profile, while a large retailer connects its own POS estate through a dedicated adapter. Both routes use the same authorisation, reversal, settlement and monitoring components downstream.

System outcome

The bank can support different merchant profiles through one maintainable architecture and consistent downstream services.

Draft KPI examples

Provisional figures for client validation.

-34%
Merchant onboarding lead time
-46%
Reconciliation exceptions
+21%
Terminal certification throughput

From business brief to working system.

A close, visible delivery process keeps the software connected to the operation it has to support.

  1. Understand

    We learn the operation, users, constraints, approvals, risks and existing technology.

  2. Define

    We turn the brief into clear workflows, architecture, interfaces and a delivery plan.

  3. Build

    We develop, test, review and integrate the software in visible increments.

  4. Launch and improve

    We prepare rollout, documentation and support, then improve what matters in use.

DAVO team members arriving at their Phnom Penh office

Built in Cambodia. Close to the work.

Our team works across product, software engineering, quality assurance, delivery and support. The people defining the system stay connected to the people building it.

We work directly with brands, financial institutions, government agencies and institutional teams. Our role is to understand the operation, build the software it needs and remain accountable as it moves into real use.

Let's talk about the system behind your operation.

Tell us what needs to work better, who uses it and what the software must connect to.

B2B project enquirieshellodavoit.com