Home / Briefs / RiskMandate interview page
For RiskMandate.ai: an interview page, and a ChatGPT voice prompt to run it
A build brief from the sgit.ai site team to the RiskMandate.ai team. Status: open. Written 24 September 2026.
The founder wants expert feedback on RiskMandate from people whose time is scarce and whose knowledge is mostly in their heads. The first is a startup founder who has been unusually good at getting into UK events, at marketing and promotion, at content that spreads, and at making things happen. Asking such a person to read a site and write feedback rarely works. Asking them to talk for twenty minutes usually does.
So the ask is a page on riskmandate.ai that a person can be sent a link to. The page carries a prompt they copy into ChatGPT. ChatGPT then interviews them in voice mode, and at the end writes up their ideas, an action plan and their candid feedback, which they send back.
This will not be the last one. The same shape will be wanted for investors, for security leaders, for insurers and for GRC practitioners. So the brief asks for a reusable page pattern, and then for the first page built on it.
The prompt is written out in full below and is ready to use today. The founder can send it directly while the page is being built.
What to read first
- riskmandate.ai's home page: the value proposition the interview will test, in the site's own words: "Know what your agents can do. Not what they did. What they can."
- For corporate and Licence to operate: the two framings the interviewee is most likely to react to.
- The published behaviour policies: the sixteen free examples, which are the most shareable thing RiskMandate has.
- The earlier brief from sgit.ai to RiskMandate, for the house rules on facts and claims.
Part A: the interview page pattern
A page that exists to be sent to one kind of person, and that turns twenty minutes of their talking into written, usable feedback. Every page built on the pattern has the same six parts, in this order:
- Who this is for, and why you. Two sentences. Written to the reader, generic enough to send to anyone in that group, specific enough that they know why they were chosen.
- What we want to learn. Three to six bullets. The reader should know the questions before agreeing to answer them.
- How it works, in three steps. Copy the prompt. Paste it into a new ChatGPT chat and switch to voice. Talk for about twenty minutes, then send us the summary it writes.
- The prompt, in a box with a copy button, and a note that it also works typed, or in another assistant.
- What happens to your answers. Nothing is sent anywhere by the page. The conversation stays in the reader's own ChatGPT account until they choose to send the summary. Ask them not to share anything confidential about their own company or clients.
- Send it back. One clear route: an email address, or a form. See "Later" for a better one.
Rules for every interview page:
- No tracking of what people paste. The page is static. The prompt runs in the reader's own assistant.
- The prompt tells the assistant what RiskMandate is, in a few plain sentences, because the interviewee may never have seen the site.
- One question at a time, short turns, in plain speech. Voice mode reads everything aloud, so no lists, tables or long preambles during the interview.
- The reader controls the length. About twenty minutes, and "skip" or "wrap up" work at any time.
- The write-up is the product. The final summary must be structured, specific and attributed to the interviewee's own words where it matters.
- Candour is asked for explicitly. The most useful feedback is the unflattering kind, and the prompt says so.
Part B: the first page, for a founder who knows events, marketing and content
Proposed path: riskmandate.ai/interview/founder-marketing.html, or wherever the site keeps pages of this kind.
Who it is for: founders and operators who are good at getting into events, at marketing and promotion, at content that spreads, and at making things happen, particularly in the UK.
What we want to learn:
- Whether the value proposition lands, and how they would say it instead.
- Whether the name RiskMandate works.
- Who RiskMandate should reach first, and where those people gather.
- Which UK events to be at, and how to get on stage or in the room.
- Which content angles and formats would spread.
- What they would do in the first thirty, sixty and ninety days.
The prompt
Paste everything between the lines as the first message in a new ChatGPT chat, then switch to voice mode.
You are going to interview me, by voice, to help a startup called RiskMandate. Be a warm, curious, efficient interviewer. I have about twenty minutes.
What RiskMandate is. RiskMandate.ai helps organisations know what their AI agents can do. Its line is: "Know what your agents can do. Not what they did. What they can." Its main product is an Agent Behaviour Policy: a short record, for one AI agent in one deployment, of everything the agent can actually reach, what the business authorised it to do, and the gap between the two, written so that a CEO, a CTO, a CISO and an insurer can all stand behind the same document. It builds towards a "licence to operate" for each agent: the business as the authority, the policy as the evidence, and the agent operating on stated terms for a stated period. Sixteen example policies are published free, for tools such as Claude Code, ChatGPT and Gmail connectors. The context: insurers are starting to exclude AI from cover, and businesses answer for what their agents do. RiskMandate is UK-based, early-stage and founder-led, and it is not an insurer.
Who I am. I am a founder who is good at events, marketing, promotion, content that spreads and making things happen. Treat me as the expert. You do not need to explain marketing to me.
What RiskMandate wants from me:
- Whether the value proposition lands, and how I would say it.
- Whether the name "RiskMandate" works.
- Who to reach first, and where they gather.
- Which UK events matter, and how to get on stage or into the room.
- Content angles and formats that would spread.
- A practical action plan for the next thirty, sixty and ninety days.
- My most candid criticism.
How to run the interview:
- Start by asking my name, what I do now, and one thing I have promoted that went well. Keep that part to two minutes.
- Then give me the one-paragraph description of RiskMandate above, in your own words, and ask for my first reaction before anything else.
- Then work through the seven topics. Ask one question at a time. Keep your turns short: this is voice, so no lists, no headings, and no long summaries while we talk.
- Follow up when I say something interesting. Ask for specifics: names of events, formats, examples, numbers, people or types of people.
- Ask me to be blunt, and do not argue with criticism. If I am vague, ask for an example.
- About every five minutes, tell me in one sentence how far through we are.
- If I say "skip", move on. If I say "wrap up", go straight to the summary.
- Do not invent facts about RiskMandate. If I ask something you do not know, say so and note it as a question for the founder.
When we finish, write a summary in text, not read aloud, with these sections:
- First reaction, in my words.
- The value proposition: what landed, what did not, and up to three one-line rewrites I suggested or agreed with.
- The name: my verdict, my reasons, and any alternatives or taglines I liked.
- Who to reach first, and where they gather.
- Events: a list of named UK events or kinds of event, with how to get in for each.
- Content angles: the hooks and formats I suggested, each with one example post, talk title or headline.
- Action plan: a table with next 30 days, 60 days and 90 days, and for each item who does it and what "done" looks like.
- Candid criticism: the hardest points I made, in my words.
- Introductions I offered, if any.
- Open questions for the founder.
Then ask me whether I am happy for this summary to be shared with RiskMandate's founder, and remind me to copy it and send it back.
Why the prompt is built this way
- The description of RiskMandate is inside the prompt, because the interviewee may never open the site. It uses the site's own words and claims only what the site claims, including that RiskMandate is not an insurer.
- The interviewee is treated as the expert. People who are good at promotion lose patience with being explained to.
- Voice rules are explicit, because voice mode will otherwise read out long structured answers.
- The summary is the deliverable, with fixed sections, so answers from several interviewees can be compared side by side.
- Consent is asked at the end, before anything is shared.
Later: sending the summary back without email
An sgit vault can receive messages through a write-only append lane. A token that can only write is safe to publish, as the telemetry brief explains. A "send it back" box on the page could append the pasted summary straight into a RiskMandate vault, encrypted, with nothing stored anywhere else. Worth doing once there are several interviews to compare. Not needed for the first.
Before you call it done
- The page has the six parts, in order, and reads well on a phone.
- The copy button copies the prompt exactly, including the line breaks.
- The prompt has been run once, end to end, in ChatGPT voice mode, and the summary came back with all ten sections.
- Nothing on the page or in the prompt claims more than riskmandate.ai already claims.
- The pattern is written down as a template, so the next interview page takes an hour, not a day.
Likely next pages on the same pattern
- An investor, on the fundraising story.
- A CISO, on whether they would buy a behaviour policy, and at what price.
- An insurer or broker, on what evidence would change a decision about cover.
- A GRC practitioner, on the acceptance loop described in "Every risk is already accepted" on sgit.ai.
The prompt to hand the builder agent
You are working on riskmandate.ai. Read this brief in full. Part A. Create a reusable "interview page" template with six parts in this order: who this is for and why you; what we want to learn; how it works in three steps (copy, paste into a new ChatGPT chat and switch to voice, talk about twenty minutes and send the summary back); the prompt in a box with a copy button; what happens to your answers (nothing is sent by the page; do not share confidential information); and how to send it back. The page is static, with no tracking. Part B. Build the first page on the template, for founders who are good at UK events, marketing, promotion and content that spreads, at /interview/founder-marketing.html or the site's equivalent. Use the prompt in this brief exactly, and only change it to correct a fact about RiskMandate that the site states differently. Run the prompt once in ChatGPT voice mode and check that the summary has all ten sections. Finish with the checklist under "Before you call it done".
The canonical markdown copy of this brief lives in the SGit-AI__CLI repository, under team/humans/dinis_cruz/claude-code-web/09/24/.