Essential
Focused delivery
One process map and a sandbox flow with up to 5 steps.
Price confirmed after discovery
Discuss EssentialAutomation, AI & Systems Integration
Process Mapping & No-Code Workflow Automation
Reduce avoidable manual handoffs with a defined, recoverable workflow.
Scope & availability confirmed after discovery · Quotation-based
Who this is for
A defined brief. A usable output.
Teams with repeatable rules and an identifiable process owner.
Included in the agreed delivery
- Current and future process maps
- Field mapping, validation and approval rules
- Sandbox workflow and exception scenarios
- Owner runbook and measurement plan
Scope options
Start with the right level of work.
These are starting scope configurations, not instant purchases. The selected option is checked against your requirements and confirmed in a statement of work.
Professional
Broader business scope
One workflow with up to 10 steps and 2 supported systems.
Price confirmed after discovery
Discuss ProfessionalExtended
Expanded requirements
Up to 3 related workflows with shared exception handling and handover.
Price confirmed after discovery
Discuss ExtendedWhat we need from you
- Current process and decision rules
- Synthetic examples and exception list
- Approved system access and licenses
Nominate one approver and provide consolidated feedback. Delays in content, access or decisions can change the schedule. Share credentials only through an approved secure process.
Outside the baseline scope
- Unlimited runs or third-party subscription fees
- Automating unclear business decisions
- Guaranteed time savings without a measured baseline
Any additional work, subscription, licensed asset or third-party service must be itemized and approved before commitment.
From first brief to handover
01
Discover
Confirm the audience, purpose, source material, platform, owner and desired outcome. Identify anything that requires further capability or risk review.
02
Agree
Select a scope option and issue a written proposal covering quantities, exclusions, schedule, fees, dependencies, ownership and acceptance.
03
Create
Prepare the first agreed output in a controlled workspace. Keep approved content and creative or technical decisions traceable.
04
Review
Collect one consolidated feedback list from the nominated approver. Complete the agreed correction rounds and log any new scope.
05
Accept & hand over
Review the acceptance checklist, deliver the contracted formats, explain how to use or maintain them and record sign-off.
Acceptance criteria
Know what completion means.
- Happy path and exception path demonstrated
- Duplicate handling is specified
- Failure produces an actionable owner task
- Manual fallback and recovery steps documented
Files, ownership & aftercare
Your proposal identifies final exports, editable source files, repositories, account ownership and any licensed components. Third-party assets remain subject to their licenses. Agree ownership and usage rights in writing before work begins.
Handover includes the contracted outputs and relevant operating notes. A defect-correction window, maintenance allowance, support hours and response targets are specified in the agreement; ongoing support is included only when expressly scoped.
See the work
MapleWorks Admin • Request Routing
A runnable local workflow simulation. Choose a normal, incomplete or duplicate request to see the routing outcome.
VSPO-authored demonstration based on VSPA-SIM-018. Fictional organization and synthetic data; not client work or an assessed learner submission. The sample is representative, not every deliverable in the package.