Hannah Lowe

Fenmoor Specialty Underwriting / BB-Demo – Security Review

Callcompleted

Fenmoor Specialty Underwriting: documents logo Fenmoor Specialty Underwriting: documents · 2025-10-24 15:30

First of five security review sessions on 24 Oct 2025 for the open Enterprise proposal of £125,000. Nadia Osei wants written evidence for her capacity providers and will set no sign-off date until they have seen it.

What was said

What this says

Current to 10 Oct 26

First of five security review sessions on 24 Oct 2025 for the open Enterprise proposal of £125,000. Nadia Osei wants written evidence for her capacity providers and will set no sign-off date until they have seen it.

What happened: Hannah Lowe held session one of five on 24 Oct 2025, covering architecture and data residency. Nadia Osei listed her open items, and Hannah committed to written answers, an annotated diagram and connector permission scopes.

Customer view: Nadia needs evidence her capacity providers can audit, and pressed on where the AI model processes data. Hannah did not give a firm answer and left it for the security side to confirm.

Commercial: The review supports the open Enterprise proposal, total deal value £125,000, against Growth at £44,000 today. The expected close of 31 Dec 2025 is BB-Demo's own estimate, and Nadia will not set a date.

Watch: Staff access mechanism, model processing location and encryption are all pending in writing. The EU or US residency add-on may be unnecessary if the Snowflake region suffices.

AI · claude-sonnet-5-5 · 10 Oct 2026

Themes

Current to 9 Oct 26
Theme
Enterprise security review
Importance
upsell
Sentiment
neutral
Voice
unknown

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hannah Lowe to send the annotated architecture diagram and a short summary of what was asked and answered.
  • Hannah to deliver written answers on model processing, staff access (marked pending), encryption with document version, and the nightly refresh region.
  • Nadia Osei to confirm Fenmoor's Snowflake region from the customer side.

Risks

Current to 9 Oct 26
  • Nadia will set no sign-off date until the capacity providers have seen the evidence, so the expected close of 31 Dec 2025 may slip.
  • Where the AI model processes data is unanswered and is the point Nadia most wants in full.
  • Several written answers are still pending, and a slow or vague reply could stall the Enterprise proposal.

Opportunities

Current to 9 Oct 26
  • The Enterprise proposal of £125,000 is open and moving through security review at the customer's pace.
  • A dedicated EU or US data residency add-on could apply if Fenmoor's requirement is stricter than its Snowflake region.

Transcript

  1. Hannah Lowe
    Hannah Lowe None
    Hello Nadia, can you hear me? Good. Thanks for joining, and good afternoon. Before we start – is there anything you most need to know from today, so I can make sure we cover it?
  2. Nadia Osei
    Nadia Osei None
    Hello Hannah, yes, I can hear you well. Thank you. Since this is the first of the sessions, I would like to list what I have as open items, so that we agree the scope. One, the architecture and where the data lives. Two, data residency. Three, access control and how it is administered. Four, logging and what I can show an auditor. I understand we will not get to all of them today.
  3. Hannah Lowe
    Hannah Lowe None
    That matches my understanding. Session one of five is architecture and data residency, so numbers one and two properly today. Access control and logging are in the later sessions, but I'll note anything you want to flag early so it doesn't get lost.
  4. Nadia Osei
    Nadia Osei None
    That is fine. For the audit trail, I should say I am taking notes and I will send you my version of the record afterwards. Could you confirm that you are happy for the notes to go into the questionnaire?
  5. Hannah Lowe
    Hannah Lowe None
    Yes, of course. And I'll put anything I say in writing as well, so you're not relying on a verbal answer. That's how I'd prefer it.
  6. Nadia Osei
    Nadia Osei None
    Good. Then let us begin with architecture. In plain terms, where does BB-Demo sit in relation to our systems?
  7. Hannah Lowe
    Hannah Lowe None
    The short answer is: inside your own Snowflake account. The longer answer is this. The brain isn't a separate service that you send your data to. It's built and run inside your Snowflake account, so the data you already hold there is where the brain's data sits as well. We don't hold a copy of your data in an environment of ours.
  8. Nadia Osei
    Nadia Osei None
    Can you evidence that? I would like to see a diagram, and not only a description.
  9. Hannah Lowe
    Hannah Lowe None
    Yes. I have an architecture diagram that shows the boundary – your Snowflake account on one side, the source systems on the other, and the connectors between them. I'll share it after this call, and I'll annotate where each type of data goes and which side of the boundary it's on. To be precise, I'd rather you had it labelled than have to infer it.
  10. Nadia Osei
    Nadia Osei None
    Thank you. Now the sources. Which of our systems does it read from?
  11. Hannah Lowe
    Hannah Lowe None
    For Fenmoor it reads from the sources that were agreed in your order form – broadly your CRM, the helpdesk for claims tickets, and the submissions and bordereaux data. I'd rather not recite a list from memory, because I don't want to say something that's out of date. I'll take the connector list from the order form and put it in the pack with the exact source for each one.
  12. Nadia Osei
    Nadia Osei None
    I appreciate that. Is access to those source systems read-only?
  13. Hannah Lowe
    Hannah Lowe None
    That's one I want to answer carefully. The connectors are designed to read from the source and write into your Snowflake account. But whether it's strictly read-only depends on the permissions that the connector is granted by your admin in each source system. So the control is partly ours and partly yours, and I'd like to document exactly which scopes each connector requests, rather than say 'read-only' as a blanket statement.
  14. Nadia Osei
    Nadia Osei None
    That is a better answer than the one I usually receive. Please add the permission scopes per connector to the questionnaire.
  15. Hannah Lowe
    Hannah Lowe None
    Will do. I'll make a note of that now – scopes, per connector, in the questionnaire.
  16. Nadia Osei
    Nadia Osei None
    Now, I will ask about the people at BB-Demo. Who on your side can see our data?
  17. Hannah Lowe
    Hannah Lowe None
    Right, and this one belongs partly to the next session on access control, but let me give you the outline. Because the brain runs in your account, access by anyone at BB-Demo depends on what your account administrators grant to us. Nobody at BB-Demo has standing access to your data by default. When we need to support something, it's through access that you grant.
  18. Nadia Osei
    Nadia Osei None
    By default. And in practice? When an incident is raised?
  19. Hannah Lowe
    Hannah Lowe None
    In practice, for an incident, we'd ask for access, and you'd grant it for the duration. What I don't want to do is describe the mechanism in detail today without checking it, because I'd want to be sure of the exact steps. I'll confirm that with a colleague on our security side and include it in the written answer for session three.
  20. Nadia Osei
    Nadia Osei None
    That is acceptable. Please mark it clearly as pending, so I do not record it as confirmed.
  21. Hannah Lowe
    Hannah Lowe None
    Yes. Pending, with an owner and a date. I'll send you that with the diagram.
  22. Nadia Osei
    Nadia Osei None
    Now data residency. This is the item our capacity providers care about most. Where is our data held, geographically?
  23. Hannah Lowe
    Hannah Lowe None
    Because the brain sits inside your Snowflake account, the data lives wherever that account is hosted. So residency follows your Snowflake region. I don't want to guess what that region is for Fenmoor – you'll know it better than I do, or your account administrators will.
  24. Nadia Osei
    Nadia Osei None
    I will confirm the region from our side. But I would like to hear from you that nothing leaves it.
  25. Hannah Lowe
    Hannah Lowe None
    Understood. So to be precise: the brain's storage and processing run inside your account, so they're in your region. The part I'd want to qualify is anything involving the AI model that answers the questions. Where that processing happens, and what's sent to it, is a separate question from where the data is stored, and I don't want to blur the two.
  26. Nadia Osei
    Nadia Osei None
    Yes. That is exactly the part I was going to ask. Please answer that one in the questionnaire, in full, not in summary.
  27. Hannah Lowe
    Hannah Lowe None
    I'll do that, and I'll check the wording with the security side first, so it's right the first time. Can I ask – is that question coming from your capacity providers specifically, or is it your own requirement?
  28. Nadia Osei
    Nadia Osei None
    Both. The capacity providers audit our supplier reviews. They will want to see that I asked the question and what evidence I received. I will not set a sign-off date until they have seen the pack.
  29. Hannah Lowe
    Hannah Lowe None
    That's completely reasonable, and I'd rather we didn't put a date on it either. We'll take the sessions at your pace.
  30. Nadia Osei
    Nadia Osei None
    Good. Is there a different arrangement available for residency, if our requirement is stricter than the default?
  31. Hannah Lowe
    Hannah Lowe None
    There is. There's a dedicated EU or US data residency add-on, which is for customers who need the data in a specific region. For a UK customer whose own Snowflake account is already where you want it, you may not need it, but I'll say that in writing once you've confirmed the region. I wouldn't want to recommend something you don't need.
  32. Nadia Osei
    Nadia Osei None
    Understood. Can I ask – this review is for the larger arrangement, not the current one?
  33. Hannah Lowe
    Hannah Lowe None
    Correct. You're on Growth today at forty-four thousand a year. The security review is part of the proposal for Enterprise, which is the expansion that's open at the moment. The total deal value on that proposal is one hundred and twenty-five thousand pounds. I'm not the commercial owner of it – Priya is – but I wanted to be clear about why we're doing this review.
  34. Nadia Osei
    Nadia Osei None
    Thank you. And the timeline on your side? I have seen a reference to the end of the year.
  35. Hannah Lowe
    Hannah Lowe None
    The expected close in our system is Wednesday 31 December 2025. But that's an expected date on our side, not a commitment, and it's very much subject to your review. If your review needs longer, the date moves, not the review.
  36. Nadia Osei
    Nadia Osei None
    That is the right way round. Thank you.
  37. Nadia Osei
    Nadia Osei None
    Last item for today from my list. Encryption. At rest and in transit.
  38. Hannah Lowe
    Hannah Lowe None
    I'll be careful here, because I don't want to overstate a control. What I can say confidently is that the data sits inside your Snowflake account, so the storage controls are the ones that account has. In transit, between the connectors and your account, I'd want to give you the exact configuration rather than a general statement. I'll include it in the questionnaire with the source for it, and you can compare it with what you need.
  39. Nadia Osei
    Nadia Osei None
    Please. I will need that in the questionnaire, with the version of the document it comes from.
  40. Hannah Lowe
    Hannah Lowe None
    Yes – document and version. Let me read back what I've got, so we both agree. One: the architecture diagram, annotated with the boundary and the data types. Two: the connector list from the order form, with permission scopes per connector. Three: the answer on BB-Demo staff access, marked pending until I've confirmed it. Four: the written answer on where the model's processing happens. Five: the encryption configuration with sources. Anything missing?
  41. Nadia Osei
    Nadia Osei None
    One addition. Please include the region for the nightly refresh, as in, where that job runs. And I will send you the Snowflake region from our side.
  42. Hannah Lowe
    Hannah Lowe None
    Good, I'll add that as number six. Anything for the audit trail from today that you'd like me to send in a separate note?
  43. Nadia Osei
    Nadia Osei None
    A short summary of what was asked and answered would be enough. I will attach it to my own record.
  44. Hannah Lowe
    Hannah Lowe None
    I'll send that this afternoon, with the diagram to follow when I've annotated it. Thank you for the clear list – it makes this much easier.
  45. Nadia Osei
    Nadia Osei None
    Thank you, Hannah. That was a useful first session. Kind regards, Nadia.
  46. Hannah Lowe
    Hannah Lowe None
    Thanks, Nadia. Speak at the next session. Goodbye.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Ask B

Ask B

B-Brain · read-only