Hannah Lowe

Fenmoor Specialty Underwriting / BB-Demo – Security Review

Callcompleted

Fenmoor Specialty Underwriting: documents logo Fenmoor Specialty Underwriting: documents · 2025-11-28 11:30

Nadia Osei walked through eleven open items with Hannah Lowe: most received, two partial, none refused. Her capacity providers must review the pack first, so she will set no sign-off date. The review concerns the expansion only.

What was said

What this says

Current to 10 Oct 26

Nadia Osei walked through eleven open items with Hannah Lowe: most received, two partial, none refused. Her capacity providers must review the pack first, so she will set no sign-off date. The review concerns the expansion only.

What happened: Nadia worked through a numbered register of eleven items. Most are received, the access review is partial, and the incident procedure can be shared under a confidentiality agreement.

Customer view: Nadia called it the most orderly supplier review she had run this year. She will not close anything on a verbal answer and asked that nobody implies a sign-off date.

Commercial: Hannah said the commercial side hoped to land the Enterprise paperwork by 31 Dec 2025, but the review has its own sequence. SSO and SCIM evidence is a recorded future item if Fenmoor moves from Growth to Enterprise.

Watch: Nadia expects her providers to press on the model provider retention point. A Fenmoor-specific written statement may be requested, and legal should be ready.

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

Themes

Current to 9 Oct 26
Theme
Enterprise security review
Importance
upsell
Sentiment
positive
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hannah Lowe sends the written access review confirmation within the next few days.
  • Hannah Lowe drafts a one-page architecture summary for the capacity providers.
  • Hannah Lowe tells Priya and Daniel that no sign-off date should be implied.

Risks

Current to 9 Oct 26
  • The capacity providers review on their own timetable, so the hoped-for 31 Dec 2025 Enterprise paperwork date may slip.
  • The model provider retention point may draw a request for a Fenmoor-specific written statement needing legal review.
  • The access review confirmation from a second reviewer is still outstanding.

Opportunities

Current to 9 Oct 26
  • A successful review supports moving Fenmoor from Growth to Enterprise.
  • SSO and SCIM evidence is a recorded follow-on if the Enterprise move proceeds.

Transcript

  1. Nadia Osei
    Nadia Osei None
    Hello, Hannah. Can you see my screen? I've put the open items register up so we're looking at the same thing.
  2. Hannah Lowe
    Hannah Lowe None
    I can, yes. Morning, Nadia. Lovely, that's much easier than me trying to recall which number is which. How was your week after last Friday?
  3. Nadia Osei
    Nadia Osei None
    Long, but fine. The audit call went as expected. Shall I begin with the list, since that's what we're here for?
  4. Hannah Lowe
    Hannah Lowe None
    Please do. Though before you do, can I ask what you most need out of today? I have the written note ready and I'd like to focus on whatever is actually blocking you.
  5. Nadia Osei
    Nadia Osei None
    Good question. What I most need is to know exactly what is closed, what is open and who owns each open item, so that I can put a pack in front of our capacity providers. I'll open with the register. There were eleven items after last week's session.
  6. Hannah Lowe
    Hannah Lowe None
    Eleven, yes. I've closed eight of them in the note I sent on Monday, to be precise, and the other three are the ones where I wanted to give you something exact rather than something quick.
  7. Nadia Osei
    Nadia Osei None
    Let's take the closed ones briefly, then. One, the incident roles. I have your role definitions. They're clear. I'm marking that as received.
  8. Hannah Lowe
    Hannah Lowe None
    Good. Received, not signed off, if I'm reading your column correctly.
  9. Nadia Osei
    Nadia Osei None
    Correct. Received means I have the evidence and I'm content with it. Closed for my purposes means my providers have seen it too. I don't close anything on a verbal answer, and I don't close it before they've looked.
  10. Hannah Lowe
    Hannah Lowe None
    That's absolutely fine, and it's how I'd want it. Carry on.
  11. Nadia Osei
    Nadia Osei None
    Two, notification wording. Your note quotes the procedure and the order form language side by side. That's helpful. I'd have liked a stronger commitment, but I can see what it says and I can evidence it. I'll flag the wording to my providers as it stands.
  12. Hannah Lowe
    Hannah Lowe None
    Understood. I didn't want to dress it up. If your providers want something firmer, that becomes a commercial conversation with Priya and it would be written into the Enterprise order form. It wouldn't be something I'd agree on a call.
  13. Nadia Osei
    Nadia Osei None
    Noted. Three, the last exercise date. You've given me the date from the record. Thank you. Four, report delivery. You confirmed it is in the procedure, with the reference.
  14. Hannah Lowe
    Hannah Lowe None
    Yes. I checked that one twice, since I'd said on the last call I believed it was there, and I wanted to be sure rather than lucky.
  15. Nadia Osei
    Nadia Osei None
    Appreciated. Five, the register extract. I have it. I looked at the fields and I'm satisfied with the structure. Six, subprocessor change notice. Seven, the retention position with the model provider.
  16. Hannah Lowe
    Hannah Lowe None
    Seven is the one I'd like to say a word about, if that's all right, because the answer is a bit more nuanced than a tick.
  17. Nadia Osei
    Nadia Osei None
    Please.
  18. Hannah Lowe
    Hannah Lowe None
    The short answer is that the retention position is a contract term, not only a setting. The longer answer is that there is also a configuration that enforces it, and the two are consistent today. If the configuration were ever changed, the contract would still stand, but I'd expect us to treat that as an incident. I've put the contract extract in the note, and I've been clear about which is which.
  19. Nadia Osei
    Nadia Osei None
    That is much better than I expected. Can you evidence that the contract term applies to Fenmoor's usage specifically, and not only to a generic arrangement?
  20. Hannah Lowe
    Hannah Lowe None
    It's an arrangement that applies to the service as a whole, so it covers Fenmoor's usage by being part of how the service operates. I don't have a Fenmoor-specific clause and I won't pretend there's one. If your providers want a Fenmoor-specific statement, we could give a written statement from our side confirming applicability. I'd want legal to look at the wording.
  21. Nadia Osei
    Nadia Osei None
    I'll add that as an option, not a requirement, and let my providers say whether it's needed. I don't want to create work that nobody asked for.
  22. Hannah Lowe
    Hannah Lowe None
    Sensible.
  23. Nadia Osei
    Nadia Osei None
    Eight, the access review extract with the matching sample. Nine, whether the incident procedure can be shared with our providers. Those two are the ones I believe are still open.
  24. Hannah Lowe
    Hannah Lowe None
    Right. Eight, I did send the extract and the sample, and you've got them. What I wasn't able to give you was the second person's review of the extract. It has been reviewed, but the written confirmation of that wasn't back in time for Monday. So I'd classify eight as sent but with one piece outstanding.
  25. Nadia Osei
    Nadia Osei None
    Understood. I'll mark it as partial. Could you say when the confirmation will arrive? I'm not asking for a promise, only your best estimate.
  26. Hannah Lowe
    Hannah Lowe None
    I'd say within the next few days. I'd rather say that and be early than name a day and miss it. I'll write to you the moment it's in.
  27. Nadia Osei
    Nadia Osei None
    That's fine. And nine?
  28. Hannah Lowe
    Hannah Lowe None
    Nine, I asked, as I said I would. The answer from our legal side is that the procedure can be shared with a customer's capacity providers under a confidentiality agreement. So it's a yes, but with a condition, and the condition is the agreement. I can't tell you more about the form of it. They'd need to be in touch with us, or you'd route it through Priya.
  29. Nadia Osei
    Nadia Osei None
    That works. I'll tell my providers that it's available subject to confidentiality and let them decide whether they want it. Ten, the subprocessor incident chain. And eleven, the data flow diagram labels.
  30. Hannah Lowe
    Hannah Lowe None
    Ten, I've set out what the terms with each one say, and I've stated the limit that we can only pass on what we're told, as we agreed. Eleven, the revised diagram is attached. I changed the service side labels and added a short key. Please look at it with fresh eyes, because I've been staring at it for days.
  31. Nadia Osei
    Nadia Osei None
    I will. I looked at it this morning, as it happens, and I think it reads better. The key helps. Let me say that I'm quite pleased with the position overall. Most of this is received, two items are partial, and none is a refusal.
  32. Hannah Lowe
    Hannah Lowe None
    That's a fair summary and I'm glad it reads that way. So where does that leave us? I think the question you and I haven't said out loud is what happens next with your providers.
  33. Nadia Osei
    Nadia Osei None
    Yes. Let me be careful here. The sign-off isn't mine alone. Fenmoor's supplier security reviews are audited by our capacity providers, and the pack has to go to them. They'll review it on their own timetable. Until they have seen it, I'm not going to set a sign-off date, and I'd ask that nobody on your side or ours implies one.
  34. Hannah Lowe
    Hannah Lowe None
    Understood, and I'll make sure Priya and Daniel know that. I think there's been a hope on the commercial side to land the Enterprise paperwork by 31 Dec 2025, but that's a hope on our side. It isn't something your review has to bend to.
  35. Nadia Osei
    Nadia Osei None
    I appreciate you saying that. I'm aware of the timetable. I'd simply rather it was clear that the review has its own sequence. If my providers have questions, those questions come first.
  36. Hannah Lowe
    Hannah Lowe None
    Of course. Is there anything we can do to make their review easier? A cover note, a single summary page, a contact on our side they can call directly?
  37. Nadia Osei
    Nadia Osei None
    A one-page summary of the architecture would help, I think, written for someone who hasn't heard any of these calls. And a named contact on your side for technical questions, which I assume would be you.
  38. Hannah Lowe
    Hannah Lowe None
    It would be me for technical questions, yes. If it's something outside my area I'll route it to our security lead rather than guess. The one-page summary I can do. I'll draft it and you tell me whether it's pitched right for them.
  39. Nadia Osei
    Nadia Osei None
    Good. I'll also put the summary alongside the evidence list in the pack, with a cross-reference, so each claim points to a document. For the audit trail, I want every statement traceable.
  40. Hannah Lowe
    Hannah Lowe None
    That's how I'd structure it too. One question from me, if I may. Is there anything in the pack that you personally still feel uncomfortable about? I'd rather hear it now than learn it from your providers.
  41. Nadia Osei
    Nadia Osei None
    That's a fair question. Honestly, the one I'd watch is the model provider retention point. I'm content with what you've written, but it is the one I expect them to press on. If they want the Fenmoor-specific statement, we'll come back to you quickly.
  42. Hannah Lowe
    Hannah Lowe None
    Then I'll have legal ready to look at it as soon as you ask, so it doesn't sit in a queue. That's a reasonable thing to prepare for.
  43. Nadia Osei
    Nadia Osei None
    Thank you. I also want to mention, because it's on my list, that for the Enterprise tier the SSO and SCIM configuration would need to be evidenced as well. That's a later stage, but I'd like it recorded as a future item so it doesn't surprise anyone.
  44. Hannah Lowe
    Hannah Lowe None
    Recorded. That would come into scope if Fenmoor moves from Growth to Enterprise. I'll note it as a follow-on, with a configuration walkthrough, and I'd put it in writing when we get there.
  45. Nadia Osei
    Nadia Osei None
    Perfect. Then I think we're done with the list. To confirm what happens now. You send the written confirmation for the access review, the one-page summary, and anything else that changes. I assemble the pack, send it to our capacity providers, and tell you when they've responded.
  46. Hannah Lowe
    Hannah Lowe None
    Yes. And I'll let Priya and Daniel know the position so the commercial side isn't guessing. I'll also make clear that the contract you have today runs to 30 Jun 2026 and that nothing in the review changes it. The review is about the expansion only.
  47. Nadia Osei
    Nadia Osei None
    Yes, that's my understanding as well. Thank you, Hannah. I'll say, for the record, that this has been the most orderly supplier review I've run this year, and I don't say that lightly.
  48. Hannah Lowe
    Hannah Lowe None
    That's very kind. The credit goes to you for the numbered questions, honestly. They made it easy to be exact. Right, I'll get the confirmation and the summary to you as soon as they're ready.
  49. Nadia Osei
    Nadia Osei None
    Thank you. Kind regards, Hannah. Have a good weekend.
  50. Hannah Lowe
    Hannah Lowe None
    And you, Nadia. Thanks, Hannah. Bye for now.

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