Cyber readiness configurator
Step 0 — Tell us about yourself and your priorities
Capture profile, operating context, and outcomes together so we can infer priorities in one pass.
~ 2–3 minutes
Your business
i
This appears in Review and in copied/exported summaries.
Outcome discovery
i
Answer quickly. We use these signals to infer your top 3 outcomes without forcing a “pick from six”.
0 of 3 selected
0 of 2 selected
Based on what you said, your top outcomes look like:
i
Use these to validate discovery confidence. You can tune the signals above if the order looks wrong.
Complete the discovery questions above to see your top outcomes.
Does this feel right? If not, adjust your answers above.
Step 1 — Coverage
Who needs to be ready — and how do you run readiness today?
~ 1–2 minutes
Teams who need to be ready (select any)
i
Coverage shapes the plan (and the tier). Select all groups you need to include in the readiness program.
Cyber resilience cadence today (best fit)
i
Choose the option that best applies. Cadence and realism affect the operating rhythm we propose (and whether Advanced/Ultimate is justified).
How do you measure readiness today?
i
Completion metrics are a starting point. Performance metrics (speed, accuracy, decisions) strengthen evidence and confidence.
Advanced (optional)
What triggered this conversation? (pick up to 3)
i
These are outcome signals, not a pricing wizard. We use them to shape tier rationale and follow-up agenda.
Pick up to three triggers. Each maps to one or more outcomes.
0 of 3 selected
Outcome drill-down (optional)
i
One extra question per inferred top outcome to sharpen the next-meeting agenda.
Only shown for your current top outcomes.
Step 2 — Package fit
Add the remaining fit signals (realism, scope, delivery) before we recommend a starting tier.
~ 1–2 minutes
These fit signals map directly to Core / Advanced / Ultimate and refine the recommendation.
1) How realistic do exercises need to be?
i
Realism increases trust and supports scrutiny, but changes the delivery model.
2) Scope of the program
i
Scope is about the breadth of coverage needed to deliver ROI and defensible outcomes.
3) Current state (closest match)
i
Be honest about the starting point; it improves the recommendation.
4) Delivery style they need
i
Services signal how much support is needed to deliver outcomes.
5) How they describe the problem
i
How teams frame the problem indicates maturity and evidence needs.
Step 3 — Context
Add just enough context for relevance — without turning into the master configurator.
~ 1–2 minutes
Context from Step 0
i
Industry and region are set in Step 0 and used here to tailor suggested regulations.
Complete Step 0 to personalize regulation suggestions.
Regulatory / assurance context (optional)
i
Suggested based on your business and region. Used to tailor evidence language and stakeholder framing. Not legal advice.
Suggested for: your selected context
Suggested list is tailored by industry and region. “All” shows the full library A–Z. Tags show Regulation / Framework / Assurance.
Security tools & platforms (optional)
i
Pick the platforms you want hands‑on simulations and examples to align to. This helps make the plan feel “your world”.
Select any tools or platforms you want to practice workflows for.
Security tools & SOC platforms
Cloud platforms
Cloud‑native & DevSecOps
Other domains
Step 4 — ROI estimate
Immersive estimate based on Immersive assumptions and outcomes seen in organizations of similar size and scale. Start with revenue or budget to size quickly, then adjust team sizes and spend.
~ 1 minute
How this estimate works
i
This estimate uses Immersive assumptions informed by delivery experience with organizations of similar size and scale. It is for planning guidance and decision support.
This is an Immersive estimate to help you sanity-check ROI. Start with annual revenue / operating budget to get a typical footprint + indicative spend, then fine-tune team sizes and spend to match your reality. Based on Immersive assumptions and comparable customer profiles.
i
Revenue is used as a quick sizing proxy to suggest a typical starting footprint. You can override team sizes below.
$10B
i
Used to scale cyber workforce benefits (attrition, hiring, training efficiency) in the preview.
200
i
Used to scale developer productivity benefits in the preview.
1,000
i
Used for suggested footprint context and workforce-ready planning (not a precise model input).
3,000
i
Directional estimate based on revenue + footprint (revenue + team footprint). Preview is capped at roughly US$9M/yr equivalent for realism. If you model materially higher/lower spend, we apply diminishing returns to keep outputs sensible.
$250,000
Estimated outcomes
Choose an assumption range for estimated ROI, NPV and payback.
3‑year ROI (estimate)
—
3‑year NPV (estimate)
—
Payback (est.)
—
Indicative spend
—
Adjust assumptions
Salary inputs scale benefits in this estimate. FX defaults are placeholders for the prototype and can be edited for your environment.
Step 5 — Review
Confirm our understanding of your business. If anything looks off, jump back to edit — then book a consultation.
Our understanding of your business
Review what we’ve captured across the configurator. Use “Edit” to adjust any section.
Organisation
—
ROI inputs
—
Challenge
—
Top outcomes
—
Tier + why
—
Recommended next meeting agenda
—
Who to bring
—
Recommended resources
—
Coverage
—
Package fit
—
Context
—
Security tools & platforms
—
Book your consultation
Share your contact details and we’ll follow up to tailor a consultation around your snapshot.
By submitting, you acknowledge that Immersive will process your personal information in accordance with its Privacy Notice.