01 / ENVIRONMENT REALISM
Real cloud accounts and Kubernetes clusters vs. VM replicas
Your buyers and learners can tell the difference between "a VM with our software installed" and the actual environment they'll run in production. If your product is cloud-native — it ships on Kubernetes, integrates with AWS services, configures cloud IAM — a Windows VM screenshot tour won't build conviction.
HOW CLOUDSHARE APPROACHES IT
Pre-configured, licensed Windows and Linux VM templates with one-click cloning, OVF/OVA imports, and genuinely advanced networking (nested virtualization, Layer 2 control). Excellent for desktop software and network-security topologies. Docker is available as a VM template, but there's no container-native or Kubernetes-native runtime, and learners don't get their own cloud accounts.
HOW INSTRUQT APPROACHES IT
Every participant gets an isolated sandbox built from the same primitives your product runs on: containers, VMs, full Kubernetes clusters — and disposable cloud accounts (a real AWS account, GCP project, or Azure subscription), provisioned on demand and destroyed afterwards with zero risk to production.
Why it matters: realism is conviction. A prospect who has created resources in a real cloud account inside your product doesn't need to imagine anything — they've already used it in their world.
SCENARIO · SALES ENGINEERING
An SE at a Kubernetes-security vendor runs a POC. On a VM platform, she'd spend days simulating a cluster. On Instruqt, each stakeholder gets their own live cluster with the product pre-deployed, in seconds — and she watches their progress live to see exactly where the deal's technical champion got excited (or stuck).
