Tell us where to send it. Add your objectives — upload or paste. RiskCompass reads them and surfaces the risks that actually threaten them — mapped, rated and ready to action.
No spreadsheets. No consultants. Built for Australian SMBs.
A sample register. Yours is built from your own objectives.
One field before we start. We build your register against your organisation, so we set it up now and email you the result when it’s ready — usually within a few minutes. No password, no card, and you can stop at any point.
Start my register →Please add your organisation name and a valid work email.
We keep your strategy and your register for 60 days so you can pick up where you left off — subscribe any time and it's retained for good. After 60 days both are permanently deleted. Your strategy stays private, is never shared, and your data is hosted in Australia. Nothing is charged and no workspace opens until you choose to subscribe — and every application is reviewed before activation. Privacy Policy
RiskCompass reads each objective, then finds the risks that threaten it — rated, reasoned and mapped to your obligations.
An example of what RiskCompass produces. Your own register is built from your document after you submit it.
Three or four lines is enough. We read objectives, not prose.
Add your strategy or objectives document first — your risks come from your objectives.
By sending us a document you confirm you have the right to share it, and you accept our Terms & Conditions and Privacy Policy. Your document is scanned for malicious content and its text is processed by an AI service to build your register.
About 90 seconds · no card required · data hosted in Australia
These set the context on your register — where you operate, your industry, and the rules that bind you. Your risks come from your objectives.
7 questions · about 30 seconds · captured as context on your register
Nothing is charged and no workspace opens until you choose to subscribe.
All 12 objectives, all 68 risks — each rated and ready to manage. Plus your 5×5 risk matrix, the regulations they trigger and the controls that treat them.
RiskCompassStrategicSelectorScreen.jsx verbatim (Jurisdiction · Strategic time horizon · Operating model · Industries · Regulations · Workforce · Technology posture, with the real option values); per that source those questions are register metadata and do not drive the semantic matcher — the objectives do — and the copy says so rather than implying otherwise. Shows shows 2 objectives × 2 risks, the rest pixelated. Free-trial wording removed throughout (RiskCompass has no free trial — access is reviewed, approval before payment); "Cancel anytime" removed (12-month minimum term); Treatments/Dashboard claims removed (both stubbed). Real logo wired. Stage A now uses the "Watch it build" treatment (Option C, chosen 16-Jul-2026 from RC_marketing_try-hero_3-options_16-Jul-2026.html) — objectives tick in, counters climb and rated rows land around an inset indicative mini-register, so the visitor sees the artefact before handing over their document; motion is CSS-only and honours prefers-reduced-motion. Retention: the gate now states the strategy + register are kept for 60 days (subscribe to retain; deleted after) — this drives the retention-led comms sequence. NOTE: that retention promise is a real obligation once live — it needs the Privacy Policy to cover uploaded strategy documents, an auto-delete job at 60 days, and consent captured at the gate. WIRED 16-Jul-2026: the gate now POSTs to the live public/try-strategy endpoint (Dev API unless served from the prod host), which stores the lead, applies the guardrails (kill switch · 1 per email per 24h · per-IP hourly cap · daily cap · document size · disposable-domain reject) and queues the acknowledgement email. Server errors (429/400/413) are surfaced to the visitor verbatim. The register itself is still produced by hand in Slice 1 — deliberately: no anonymous path reaches an LLM. The document BLOB is not yet uploaded (Slice 1b reuses the strategy-document upload-url pattern); only its filename and size are recorded. The 60-day deletion is honoured by the lead_retention_worker timer and is covered by Privacy Policy v1.1.