Your client's Windows rollout is blocked?
For business customers: €990 net plus applicable VAT. Start with a free feasibility review; we reply within one business day. For a confirmed feasible scope, we create one IntuneWin package with reproducible source, detection and handover documentation in five business days. A tested-package claim is made only after an agreed disposable Windows SYSTEM test has actually passed.
- B2B only
- Local, deterministic execution
- Human release approval
- No production access required
Three familiar reasons a rollout stops.
A vendor installer will not run silently; Intune needs a dependable detection and uninstall path; or an agreed Windows baseline exposes a reboot, dependency or launch blocker. Before work begins, we confirm the application, version, authorised inputs, target baseline, output and acceptance criteria in writing.
Included in the standard pilot
- Agreed requirements and scope sheet
- Repeatable installation workflow
- Uninstall workflow where vendor-supported
- One agreed deployment asset
- Validation on one Windows baseline
- Install, uninstall and exit-code checks
- Reboot-behaviour check
- Basic launch and functional smoke test
- Machine-readable execution log
- Handover report and one correction round
Not included
- Software licences or code-signing certificates
- Production access, rollout or enterprise deployment
- Drivers, firmware, kernel or security-agent packages
- Reverse engineering or third-party code changes
- Multiple versions, baselines, formats or tenants
- Security certification or ongoing operation
One package, one stated test result.
Included: one IntuneWin package created from the customer's authorised vendor installer, a repeatable install workflow, vendor-supported uninstall and handover documentation. When an agreed disposable Windows SYSTEM test environment is available and passes, its exact result is documented. We do not create a new MSI. A live Microsoft Intune tenant test, production rollout, licences, signing certificates, drivers, firmware, kernel or security-agent packages, reverse engineering, third-party code changes, multiple baselines, certification and ongoing operation are excluded.
From request to evidence-backed handover.
AI may support analysis and documentation. Concrete packaging and test steps remain inspectable, logged and subject to explicit human approval.
Check fit
Send the application, version, target and required result.
Confirm scope
We confirm price, inputs and acceptance criteria in writing.
Build and test
The workflow is created and run in a controlled test environment.
Human approval
No asset is marked release-ready without human review.
Handover
Receive the agreed asset, log, limitations and next steps.
The clock starts only when the scope is ready.
Free feasibility review first: send the application, target format, blocked rollout and required date. We reply within one business day. The five-business-day delivery clock starts after written scope and acceptance criteria, payment, and all valid authorised inputs are received. Delivery is accepted against the written criteria.
BLOCKED — SYSTEM proof gap: Smart Package Demo is our own harmless PowerShell sample, not customer work. A real .intunewin was created with Microsoft's signed Win32 Content Prep Tool 1.8.7. SYSTEM lifecycle evidence is not available for this release. The package is therefore offered for transparent inspection only, not as a tested result. It was not tested in a live Microsoft Intune tenant and does not prove arbitrary third-party application compatibility.
Download .intunewinDownload source and evidence kitRead the evidence report
SHA-256 values are published in the checksum file. The Microsoft packaging tool is not redistributed; its official source and licence terms apply separately.
Automated, not uncontrolled.
We do not request passwords, production credentials, licence keys, personal datasets or confidential files in the enquiry form. Do not email installers. If an approved pilot requires a file, separate protected transfer instructions are provided after scope confirmation.
Origin, signature and hash checks, malware scanning and isolated tests reduce risk; they cannot prove the absence of harmful or faulty behaviour. Customer acceptance testing remains required before production use.
Mandatory release gates
- Customer confirms rights to every source and material
- Build and test run in an isolated, disposable environment
- Source version, hashes and relevant results are recorded
- A human approves every deliverable
- Automation may assist preparation; reproducible tests and a named human control every delivery
- Production deployment requires a separate written mandate
A clear correction and refund path.
Correction, acceptance and refund
Business days are Berlin business days; email notices after 17:00 count on the next business day. The buyer has five business days for one consolidated defect report. The provider has five business days for one correction; clocks pause while required input is missing. The buyer then has three business days to retest; silence is acceptance. If the same in-scope defect remains after correction, the paid pilot amount including charged VAT is refunded within five business days, excluding separately approved third-party costs.
Start with one application.
Complete the short scope check. Your entries stay in your browser and are used to prepare an email in your own email application; this page does not upload them to a form provider.
Submitting an enquiry does not place an order. An engagement begins only after written confirmation of scope and commercial terms.
What buyers usually need to know.
Is €990 the fixed price?
Yes, for one confirmed application, format, target Windows version and correction round. Extensions are quoted first.
What do you need from us?
Application, version, authorised source, target baseline and testable acceptance criteria.
Do you need production access?
No. The standard pilot is tested without production access.
Who controls delivery?
Reproducible checks and documented human approval are mandatory.
What if packaging is not feasible?
You receive documented blockers, validation results and next steps.
Can we scale after the pilot?
Further packages can be quoted after the technical and commercial baseline is clear.
Know the result before you scale.
Start with one application and a controlled, evidence-backed pilot.
Request free feasibility reviewBusiness customers only · non-binding enquiry · written confirmation required