Every one of them can change how finance, procurement and supply chain behave in production. One annual package covers all of them — automation build included.
What does a year cost?
One field. A senior QA lead comes back with an indicative annual range for a
platform your size, plus the two or three things we would need to firm it up.
500+clients since 2005
17 yearslongest live engagement
CMMI L3ISO/IEC 27001 certified
No implementation armtesting only, so no conflict
Your year on Dynamics 365 F&O
~30
update events reach your environment in twelve months
2
service updates you cannot refuse, whatever else is happening
0
proactive quality updates you are allowed to pause
Service updateFour a year; two of them mandatory
Proactive quality updateCannot be paused, excluded or deferred
Regression window14 days, every release
Your year on Oracle Fusion Cloud
4
quarterly updates, on dates Oracle sets for your cohort
14
days between your test pods updating and production following
26D
the release where Redwood stops being optional for Supply Chain
Quarterly updateOn the dates Oracle sets for your cohort
Test pod → production14 days between the two
Your year on Workday
2
feature releases, R1 in March and R2 in September
~5
weeks in the Preview tenant window — 2026R2 ran 15 Aug to 19 Sep
52
weekly service updates arriving between them
Feature releaseR1 in March, R2 in September
Service updateWeekly, between the feature releases
Preview tenant windowAbout five weeks before production
Trusted byABBAdobeAvivaGEIntelSamsungSiemens
What you actually receive
Before every update, one page that says go or no-go.
Not a dashboard you have to interpret. A signed recommendation with the
evidence behind it, in your inbox inside the window — so the decision is made before
the vendor makes it for you.
A verdict, not a report to read. Go or no-go, with the count of
checks passed and whether anything is blocking.
Every business process, by name. Procure-to-Pay, Order-to-Cash and
the rest — each with its own pass count.
Exceptions written in business terms. What broke, what it means for
the close, and whether it was this update or already there.
Signed by a named QA lead on your account, with the evidence pack
and run log attached.
A monthly regression report between updates, so the trend is visible
rather than reconstructed at audit.
What the year covers
Regression that already exists and stays current.
Rather than a project you scope again every release.
Full regression on every major update
Go/no-go report before each production update
Targeted regression on every interim update
Monthly regression report
Your customisations and extensions each cycle
Vendor roadmap monitoring
Your integrations each cycle
Test assets built in your environment
How the commercial works
One annual fee per platform. No charge per release.
Year-one automation buildIncluded
Separate onboarding feeNone
Per-release quotingNone
Unplanned interim updateCovered
Who owns the test assetsYou do
How it runs
Two months to stand it up. Then it just runs.
Against every release, without another conversation about scope.
1
We map your risk
Your modules, customisations, integrations and existing coverage, against the vendor's release calendar for your tenant.
Weeks 1–2
2
We build the suite
Automation stood up on Opkey and wired into your pipeline, starting from our pre-built ERP asset library and extended to your configuration.
Weeks 3–10
3
We run it all year
Every update tested inside the window before it reaches production, with a go/no-go call you can take to the board.
Month 3 onward
Proof
What it has done elsewhere.
Results on this model, for the platform you selected above.
19 → 3
Days per regression cycle at a global toy manufacturer, across six end-to-end flows.
201 test cases automated · D365 Supply Chain
Crestech engagement
~80%
Manual effort removed at a global benefits administration firm that started with zero automation.
300 test cases across seven modules · D365 F&O
Crestech engagement
~3 hrs
Full regression per entity, down from days of manual work before automation.
100+ regression scripts · D365 F&O
Crestech engagement
28
Man-days saved in the first upgrade cycle at a US consulting firm.
70% of the regression suite automated · Oracle EBS
Crestech engagement
87%
Reduction in testing cycle times at a healthcare system on Oracle Cloud.
Optimal test coverage reached · Oracle Cloud
Opkey platform case study
90%
Testing effort removed at a manufacturer, with updates certified 15× faster.
Oracle Cloud quarterly updates
Opkey platform case study
80%
Faster Workday test cycles at a construction and property group, at 60% lower testing cost.
85% of regression automated in two weeks · Workday
Opkey platform case study
13
Workday modules brought under regression coverage at an HR and benefits consultancy.
300+ test cases automated, cycles cut from days to hours
Opkey platform case study
97%
Reduction in test maintenance effort once the suite was self-healing.
Workday HCM, Payroll and Financials
Opkey platform case study
Cards marked Opkey platform case study are results published by Opkey,
the automation platform Crestech builds and runs these suites on. Crestech is an authorized
Opkey partner; those engagements were delivered by Opkey, not by Crestech.
See Opkey’s case studies.
Before you ask
The four questions everyone asks.
Is the automation build really included?
Yes. Year one covers the assessment, the framework set-up and the test assets built for your configuration. One annual number, not a build fee plus a subscription.
What if an unplanned update lands mid-cycle?
It's covered. On Dynamics 365 the proactive quality updates can't be paused or deferred at all, so treating them as out-of-scope events would make the package meaningless.
What happens to the test assets if we leave?
They stay. The suite, the assets and the documentation are built in your environment and belong to you. The annual fee buys the work of keeping them current, not access to something you'd lose.
You don't implement ERP. Is that a gap?
It's the point. We have had no implementation arm since 2005, so we're never signing off on our own build — and there's no commercial reason to soften what we report.
Find out what your year costs.
Leave a work email. No call first, and no sales sequence.
Your vendor has already set the dates.
The only open question is whether the testing is standing by when they arrive, or
scoped again in a hurry each time.