WorkflowLab pricing · Manufacturing workflows

Scope the matching work first.

For manufacturers in Singapore and Malaysia comparing supplier invoices and paper delivery orders with PO and goods-receipt lines.

The Workflow Diagnostic maps what your team checks, what the ERP already handles and what still needs human review. You leave with a readiness decision and a fixed pilot scope and quote.

See the pricing path See the sample matching demo
First purchasePaid diagnostic Build scopeOne workflow ApprovalKept with your team QuoteFixed before build
The commercial path

Check the workflow. Then decide what to build.

Start with the documents and the person doing the check. The diagnostic establishes whether a pilot is useful. Any build, handover and ongoing support have their own agreed scope.

01 · Decide Start here

Workflow Diagnostic

A half-day working session to map one matching workflow, establish a baseline and decide whether a pilot is ready.

At a glance

  • Half-day working session
  • One workflow and one process owner
  • Written go, wait or do-not-build decision

Pricing

S$1,000–1,500 Credited if the pilot starts within 30 days.

Full scope

  • Invoice, delivery-order and ERP workflow map
  • Baseline and measurable acceptance target
  • Representative-case readiness check
  • Access, security and ownership decision
  • Fixed pilot scope, quote and assumptions
Discuss your matching workflow
02 · Prove

Matching workflow pilot

Separately scoped work to compare agreed documents, surface missing evidence and mismatches, and keep payment approval with your team.

At a glance

  • Starts only after the diagnostic
  • Delivery date agreed in the written scope
  • One workflow, owner and user team

Pricing

Quoted separately Your diagnostic produces the fixed quote before build.

Agree before build

  • Source formats, ERP exports and matching rules
  • Representative test cases and acceptance criteria
  • Review, correction and exception handling
  • Baseline, measures and user review rounds
  • Access controls, training and handover
  • Maintenance responsibilities and support limits
See what the scope covers
03 · Choose

After acceptance

Take the agreed workflow in-house. Decide on any maintenance or further work from what your team learned using it.

At a glance

  • No mandatory retainer
  • Workflow-specific build handed over
  • New scope stays visibly separate

Pricing

Own it
Agreed handover
Operate it
Scoped separately
Expand it
Scoped separately

Full options

  • Own: agreed code, configuration, tests and runbook
  • Operate: agree responsibilities, response times and fees
  • Expand: scope additional formats or workflows separately
  • Net-new features require a new written scope
Read common questions
How the fixed price stays fixed

Agree the boundaries before a pilot.

The written scope defines

  1. 01One workflow, one process owner and one user team
  2. 02Invoice, delivery-order and ERP export formats
  3. 03Permitted data access and any integrations
  4. 04Representative cases and acceptance criteria
  5. 05User review rounds, corrections and delivery date
  6. 06Human approval, training and handover responsibilities

Re-scope before adding

  1. +A second workflow, team or approval path
  2. +Additional systems, destinations or environments
  3. +New language, role, format or delivery channel
  4. +A different review or approval responsibility
  5. +Changed acceptance criteria after sign-off
  6. +New security, hosting, compliance or data-cleanup work
Commercial terms

Set the terms before work starts.

Payment milestones

The written quote sets the payment schedule and what each stage covers.

Third-party costs

Identify any software, hosting or model charges and who pays them before build.

Agreed handover

Specify the workflow code, configuration, tests and operating notes your team receives.

Ownership and access

Agree rights to the build, dependencies and source material in the written scope.

Questions

What buyers usually need settled.

Can we skip the diagnostic and go straight to a pilot?

Not for the standard engagement. The diagnostic is what fixes the baseline, readiness, acceptance target and build limits. Skipping it would turn the pilot price into a guess.

How is a matching pilot priced?

Follow-on work is scoped separately. The diagnostic fixes the workflow, sources, test cases and controls needed for an exact quote. You receive that quote before deciding whether to build.

Do we need to share confidential files for the first conversation?

No. The first fit check works from a sanitized description. The diagnostic defines what representative material is needed, where it can be processed and who approves access.

What happens if the diagnostic says the workflow is not viable?

You receive the current-state teardown, baseline and written go, wait or do-not-build recommendation. The engagement stops there rather than converting uncertainty into a larger build.

Does a match approve an invoice for payment?

No. Matching checks support review. Missing receipts and mismatches still need a person to resolve them, and payment approval stays with your team.

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 any continuing support are agreed before work starts.

Are software and model costs included?

The written quote identifies any third-party software, hosting, model or licence charges separately and states who pays them. Ongoing costs need to be clear before you approve a pilot.

Start with the matching workflow

Which document checks still happen by hand?

Describe the invoices, delivery orders and ERP records involved, who compares them, and what remains manual. The first conversation needs a description, without confidential files or credentials.

Discuss your matching workflow See the matching workflow