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.
WL / 001
DOCUMENT REVIEW / LOCAL PROTOTYPE
100 billed. 80 received. That’s a conversation worth having.
The browser example shows the difference, its source and the reviewer’s next action.
15-second illustrative animation. The browser example is separate from the local Matchdesk prototype. Its recorded walkthrough uses saved readings; accuracy on your documents, ERP fit and installation still need evaluation. Film description →
WL / 002
YOUR PROPOSAL
FROM THE BRIEFA clearer starting point.01 / 12
↗
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.
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.
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.
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.
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.