The census & pilot. Four weeks, measured on your cases.
One proof of concept, run the same way every time: a census of your workbooks, then a 20-case pilot on a frozen build, every case imported and executed in your own Certify. Fixed scope, fixed fee, credited against the first-year licence.
- Week 0 · KickoffPrerequisites, agreement, success criteria in writing
- Week 1 · CensusEvery workbook parsed and classified
- Weeks 2–3 · Pilot20 cases imported and executed in your Certify
- Week 4 · ReadoutMeasured results, scale plan and price
Week by week
- Week 0
Prerequisites and kickoff
Prerequisites signed off by your IT, NDA and POC agreement in place, baseline cases received. Success criteria agreed in writing.
Output: Kickoff
- Week 1
Census
Every workbook you offer is parsed (parse-only) and classified by application, template and step patterns. Three manual captures are timed as your baseline.
Output: Census report: what is drivable, gaps per sheet, sizing
- Weeks 2–3
Pilot
20 cases chosen for variety, not volume, in batches on a frozen build. Every case imported and executed in your Certify, and every run timed.
Output: Results per case
- Week 4
Readout
What was measured, against your baseline and your own hand captures, with the defects found and fixed along the way.
Output: Readout, scale plan and proposal
Your numbers, set before the pilot starts.
At kickoff we agree in writing what success means: for example, how many of the 20 cases must execute green in Certify after review, the review time per case you will accept, and that no credential leaves the runner. The thresholds are yours. The pilot build is frozen: fixes go into the next build and the affected cases are re-run, never hot-swapped mid-pilot.
What we need from you
- A Windows 10/11 or Server 2019+ runner with an interactive desktop, which can open every application in scope (Python 3.10+ on it, until the signed installer ships)
- Microsoft Edge on the runner, or Chromium where your policy allows it
- For SAP GUI: the front end installed, scripting enabled in client and server, and a SAP Logon entry per connection
- Test users for each environment and role the cases need
- Your Certify version, and an export of your XF configuration or Application Preset
- Five representative workbooks for the census
- For Cloud: outbound HTTPS 443 from the runner to the portal
What you get
- A census report: per workbook, what is drivable, what each sheet is missing, and a sizing
- Pilot results for each of the 20 cases, imported and executed in your Certify
- Measured accuracy, review time and hours per case against your own baseline, on your cases
- The defects we found and fixed, and the build each fix went into
- A scale plan and a price, sized on your cases
Messy sheets are not a reason to wait: the census tells you, sheet by sheet, what is missing, which is useful on its own. Security questions first? See security & trust.
Tell us about your test cases.
An engineer replies to every request. The first call covers how many cases you have and in what format, which applications and technologies they touch, your Certify version, what is driving the timeline, and whether a runner in your network can reach the applications.
- No customer system is touched without your written permission.
- Pricing comes after the census, because it is sized on your cases.
Worksoft and Certify are trademarks of their owner. MindMap AutoTestr is a MindMap Digital product; naming Certify describes the files AutoTestr produces and does not imply endorsement by Worksoft. Capability status words on these pages (Built, Built not run live, Roadmap) describe the current release.