Write to a person, not a queue. Everything below says what happens after you do — who answers, what we ask, and what you keep whether or not we ever speak again.
Five things, and the fourth is optional. If you would rather not fill in a form, the same five things in a paragraph, by mail, work just as well.
If you describe a case, describe it without personal data — the demo runs on a synthetic company either way.Who replies.
A member of the founding team — not a sales sequence. Your message lands in a named person’s mailbox and that person answers it. It is not scored, routed or fed to a sequence. No automated follow-ups: if you do not reply, we do not chase. What you send is kept only so that answer can happen, and the form says for how long.
What we ask on the first call.
Thirty minutes, three questions: where you are licensed and which regulators you answer to; which jurisdictions your stuck cases sit in; and whether you can share your policy pack — the ten to twenty signed PDFs your requirements actually live in. Nothing else is needed to prepare a live run.
What you get.
A live run against your own policy: we assemble the requirements map in front of you, element by element, each with the clause it came from, and run a case against it — showing every source, what can be established, and what cannot. You keep the map and the decision file either way, whether or not we ever speak again.
Security questionnaires.
Welcome at the same address. We answer them as written, and we mark every control that is planned rather than in place. If an answer would need a footnote to be true, you get the footnote.
Then read the file instead. A live decision file is a whole case, open to the last event in its journal, with nothing asked of you — including the two elements that could not be established and what stands in their place.
onboarding is by hand. that is why the first case is done with you, and why this page says “write”, not “get started”.