MATCHDESK / BY WORKFLOWLABSINGAPORE & MALAYSIA · 01° N

Catch the gap.Keep theproof.

Invoice. Delivery order. Purchase order.
Bring the pieces together. See what needs a person.

A local matching prototype for manufacturers.
People still approve payment.

SAMPLE REVIEW EXAMPLE

100 billed.
80 received.

20 units need review.Inspect the example →
SCROLL TO EXPLORESOURCE → CHECK → HUMAN DECISION

The work is complicated.
The review shouldn’t be.

WorkflowLab builds AI-assisted document and knowledge workflows in Singapore. Our current focus is invoice matching for manufacturers in Singapore and Malaysia. Matchdesk puts the source beside the check, so your team can inspect the exception and decide what happens next.

02 / SELECTED WORK

Built around
real work.

One matching prototype.
Earlier company tools in use.
Different work. Clear boundaries.

Proposal preparation

In use

A local PowerPoint proposal assembler for a tax-incentives consultancy, in use on many proposals. The practitioner reviews the output.

No measured time saving or firm-wide rollout is claimed.

See the earlier walkthrough

Shared company knowledge

In use

A deployed, read-only connector lets a consumer-health product team’s Slack assistant answer from 66 code repositories. Maintained by the product manager.

Source-linked answers support review. No usage count or measured time saving is claimed.

Explore the knowledge story

Earlier company work does not establish Matchdesk adoption or production accuracy. A matching pilot needs your own baseline, document checks and acceptance criteria.

03 / THE PROCESS

Follow the line.
Keep the human.

From scattered documents to a review you can explain. The original evidence stays in reach.

Explore the review
01BRING THE DOCUMENTS

Same purchase.
One place to look.

Bring source PDFs and a read-only ERP snapshot into one review. Inspect the extracted line against its source before accepting the reading.

02INSPECT THE EXCEPTIONS

A gap needs
a clear next step.

Waiting needs a missing document or ERP row. Exception needs a person to resolve a failed check. Matched means the configured checks passed.

✓ Matched◷ Waiting↗ Exception
03KEEP THE DECISION

The correction.
The reason. The record.

Edit a reading, rerun the checks and export the saved review with its correction history. Your team resolves exceptions and approves payment.

ALSO FROM THE LAB

Less form-filling.
More final checking.

Free beta

Declaration Preparer

Prepare two declaration drafts from a company profile and supporting records. Review, edit and download the PDFs.

Use a sample or supported PDF, PNG and JPEG files. The forms are provisional drafts; check each result before use.

Explore the declaration story
04 / A CLEAR STARTING POINT

Find the gap.
Then decide.

Describe your documents, ERP, who checks them and what remains manual. First, find out whether existing matching tools already cover the work.

No raw client files or credentials needed for the first conversation.

WORKFLOW DIAGNOSTIC

S$1,000–1,500

HALF A DAY. A CONCRETE DECISION.

  • A baseline of today’s workflow
  • A readiness or no-build decision
  • A fixed pilot scope and quote

Diagnostic fee credited if your pilot starts within 30 days.

Discuss your matching workflow Full pricing & scope details →
THE PRACTICAL QUESTIONS

Before we
build anything.

What does WorkflowLab do?

WorkflowLab is a Singapore-based studio led by Phua Kuan Yu. We build AI-assisted document and knowledge workflows with source evidence and human review. Explore invoice matching, proposal preparation, shared knowledge and declaration drafts.

How can I contact WorkflowLab?

Email kuan@workflowlab.sg. Describe the recurring task, its owner, the files or systems and what remains manual. Read how to start a conversation →

Do we need to share confidential files?

No. Describe your documents, ERP and remaining manual checks. The diagnostic defines which representative material is needed, where it can be processed and who approves access.

Does Matchdesk approve payments or update the ERP?

No. The prototype uses read-only ERP snapshots and produces review outputs. Your team resolves exceptions and approves payment. Any integration needs its own agreed scope.

What if the workflow is not viable?

You receive the baseline, teardown and written no-build or wait recommendation. The engagement stops there.

What do we own at handover?

The pilot scope names the workflow-specific code or configuration, tests, outputs and operating notes your team receives. Ownership, third-party dependencies and continuing support are agreed before work starts.

Can we roll this out across our sites?

A wider rollout needs agreed installation, ERP access, data boundaries and support. The local prototype has not established production accuracy on your documents. Follow-on work is validated and quoted separately.

START WITH THE CHECK THAT STILL HAPPENS BY HAND
Let’s untangle
the paperwork.
Kuan Yu

Built with Kuan Yu in Singapore.
Small systems around the work you already do.

kuan@workflowlab.sg