Test one workflow, then hand it over.
We set up one clearly named workflow in a test environment you control and hand it to the person who will run it. €2,000 net.
Deliverables
What you have at the end
One clearly named workflow in one test environment you control
A boundary that prevents production writes
The tested setup and its operating notes
Verification against the agreed scope
Handover to the named operator
Decision filter
Does the setup fit?
Yes, if…
- The recurring workflow is clearly named
- A person is ready to operate it afterwards
- A client-controlled test environment is available
- The access and success criteria can be agreed before work begins
No, if…
- The workflow is not clear enough to test
- No one is available to own the workflow after handover
- You expect Groundlens to write to production systems
- You want a result for the whole company
- You are an agency, an IT company, or a software company
Investment
FAQ
The questions that matter
How the test environment, handover, and verification work.
Check if it fitsWho runs the workflow afterwards?
A named person in your business works with us during setup and handover. They take control of the workflow before the Pilot ends.
Where does it run?
In one named test environment you control. The Pilot has no production write access and does not run on Groundlens-hosted infrastructure.
What gets measured?
We verify the workflow against the written scope. The Pilot does not promise a specific business or savings result.
Does the price include the plan?
No. The Blueprint and Pilot are separate purchases. A clear workflow can start directly with a Pilot. If you buy both, they are quoted and invoiced separately.
Is the workflow clear enough to test?
Describe the work, operator, and test environment in the free fit check. We will assess whether a Pilot makes sense.