Priya Raman

Fenmoor Specialty Underwriting / BB-Demo – Demo

Callcompleted

Fenmoor Specialty Underwriting: documents logo Fenmoor Specialty Underwriting: documents · 2024-04-11 14:15

Callum Reid saw the brain answer a live submissions question and flag a source conflict. He wants the 07:00 refresh written into the order form and is unhappy that scheduled packs are not committed. Security goes to IT.

What was said

What this says

Current to 10 Oct 26

Callum Reid saw the brain answer a live submissions question and flag a source conflict. He wants the 07:00 refresh written into the order form and is unhappy that scheduled packs are not committed. Security goes to IT.

What happened: Tobias Renwick demoed the brain on Fenmoor's sample extracts, covering submissions, bordereaux queries, search and a live dashboard. The brain found two submissions marked awaiting quote that the emails showed as quoted.

Customer view: Callum said the mismatch is the problem he has every week. He wants the 07:00 refresh in writing: "What I need is that it's written, not promised."

Commercial: Priya Raman will prepare the proposal. The decision sits with Richard, who was absent, and the target date is 17 Jun 2024. Callum will take the architecture page to IT.

Watch: Tobias would not commit to an automatic scheduled pack to a capacity provider, and Callum said he is not happy about it. Callum also expects to be the main asker at first, a key-person risk.

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

Themes

Current to 9 Oct 26
Theme
Demo, security and refresh SLA
Importance
upsell
Sentiment
mixed
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tobias Renwick to send a one-page architecture note to Callum's IT team the day after the call.
  • Priya Raman to send call options for Richard and prepare the proposal ahead of 17 Jun 2024.
  • Priya Raman to include the 07:00 refresh service level in the order form.

Risks

Current to 9 Oct 26
  • Scheduled automatic packs to capacity providers were not committed, and Callum said he is not happy about it.
  • Callum is likely the main asker at first, which is a key-person risk until underwriters adopt it.
  • Richard, who owns the number, was absent and has not seen the demo.

Opportunities

Current to 9 Oct 26
  • The brain flagged a real source mismatch, which Callum called a weekly problem.
  • Dashboards builder and four connectors fit the Growth tier, and the 07:00 refresh can be written into the order form.

Transcript

  1. Priya Raman
    Priya Raman None
    Afternoon, Callum. Tobias is just dialling in, I think he's on the screen now.
  2. Tobias Renwick
    Tobias Renwick None
    I'm here. Afternoon. Is the sound all right? I've changed headset.
  3. Callum Reid
    Callum Reid None
    Fine. Afternoon. I've got about forty minutes before I'm pulled off, so let's use it.
  4. Priya Raman
    Priya Raman None
    Perfect. Quick recap so we're all on the same page. Last time was discovery, with Richard. He sends his apologies for today, he's tied up with capacity providers. Callum was going to pick real oversight questions and check with IT what's set up in the warehouse. Today is the brain on the extracts you sent, to keep momentum, and the date we're working towards is Monday 17 June 2024.
  5. Callum Reid
    Callum Reid None
    What I need is to see whether it gets the answers right. Not the slides.
  6. Tobias Renwick
    Tobias Renwick None
    Understood. Before I share anything, may I ask what your security team will need to see? I'd rather aim the second half of the call at that than guess.
  7. Callum Reid
    Callum Reid None
    Where the data lives, who can see what, and whether anything leaves our environment. That's the first thing IT will ask me. I did speak to them, by the way. We do have a warehouse account, they were fine with the idea in principle.
  8. Tobias Renwick
    Tobias Renwick None
    Good. Then to be precise about the architecture: the brain is built and run inside your own Snowflake account. We don't take a copy of your data into our systems. Access follows the controls you already set there, so your IT team decides who can reach what. The trade-off is that your side owns those permissions, which most security teams prefer, but it does mean they have to be involved in setup.
  9. Callum Reid
    Callum Reid None
    That I can sell to them. Go on.
  10. Tobias Renwick
    Tobias Renwick None
    Let me share my screen. Give me a second.
  11. Priya Raman
    Priya Raman None
    Take your time. Callum, you should see it in a moment.
  12. Callum Reid
    Callum Reid None
    Got it. That's bordereaux data. I recognise the column headers.
  13. Tobias Renwick
    Tobias Renwick None
    It is the sample you sent, indexed overnight. Here's the home view. On the left, the sources that have been connected for this demo: submissions, the bordereaux sheets, claims tickets, CRM activity. Four sources, which is comfortably inside what the Growth tier carries.
  14. Callum Reid
    Callum Reid None
    Start with the first of my questions. The one about submissions waiting on a quote.
  15. Tobias Renwick
    Tobias Renwick None
    Right. I'll type it as you phrased it in your note. Which marine cargo submissions are still waiting on a quote?
  16. Tobias Renwick
    Tobias Renwick None
    And there's the answer. A short list, each with the broker and the date received. If I open the first, the page shows where each field came from.
  17. Callum Reid
    Callum Reid None
    Hang on. Those two at the bottom. They look quoted to me.
  18. Tobias Renwick
    Tobias Renwick None
    Let me look. Mm. Yes, in the submissions source they're marked as awaiting quote, but there is an email in the activity that says the quote went out. The honest answer is that the two sources disagree, and the brain is showing you both rather than choosing for you.
  19. Callum Reid
    Callum Reid None
    That's actually the problem I have every week. So it flags the disagreement.
  20. Tobias Renwick
    Tobias Renwick None
    It shows the conflict and the source of each side. Whether the workflow should be corrected is your team's decision, but you'd see it in seconds rather than in a Friday pack.
  21. Priya Raman
    Priya Raman None
    That's the bit I'd underline, Callum. It's not that it's smarter than your people. It's that nobody has to do the joining.
  22. Callum Reid
    Callum Reid None
    Fine. Next one. Open bordereaux queries by capacity provider. What's outstanding for longer than normal?
  23. Tobias Renwick
    Tobias Renwick None
    Longer than normal needs a definition, so let me ask it more narrowly. Which bordereaux queries have been open longer than the other queries in the same period?
  24. Callum Reid
    Callum Reid None
    Better. Or just give me the oldest ten. No, sorry, the oldest few. I don't want to lock in a number.
  25. Tobias Renwick
    Tobias Renwick None
    Of course. The oldest few it is. There they are, sorted by age, with the syndicate where the sheet records one.
  26. Callum Reid
    Callum Reid None
    Can I filter by syndicate?
  27. Tobias Renwick
    Tobias Renwick None
    To be precise, it depends on whether syndicate is a field in a source. In your extract it's a column, so yes, here, I'll filter. If a source only had it in free text, we'd get it by search but it would be less tidy.
  28. Callum Reid
    Callum Reid None
    It's a column in the market sheets. In the emails it's in the subject line half the time.
  29. Tobias Renwick
    Tobias Renwick None
    Then the sheets give you the clean answer and the emails give you the context. That's how I'd expect it to behave.
  30. Priya Raman
    Priya Raman None
    Tobias, can you show Callum search across the claims tickets? That was the other thing Richard cared about, the capacity providers asking what's open.
  31. Tobias Renwick
    Tobias Renwick None
    Yes. Search, here. If I type a vessel-related term from one of your claims tickets, it returns the ticket, the related broker emails, and the CRM note from the same account. One view of one story.
  32. Callum Reid
    Callum Reid None
    That's useful for the claims team. They'd be asking exactly that. Who else can see that view? Everyone?
  33. Tobias Renwick
    Tobias Renwick None
    Only those you permit. Visibility follows the permissions on the underlying data in your Snowflake account, so the person who isn't meant to see a claim doesn't see it here either. I wouldn't want you to have to maintain a second set of rules.
  34. Callum Reid
    Callum Reid None
    Good. Next. Dashboards. That's where I get hurt.
  35. Tobias Renwick
    Tobias Renwick None
    Right. This is the dashboards builder, which is part of Growth. I'll build one live. Submissions received, quoted, declined, by month, by class.
  36. Callum Reid
    Callum Reid None
    It's quick.
  37. Tobias Renwick
    Tobias Renwick None
    It's building on data that's already indexed, so it's mostly configuration. The important thing for your question is timing. The nightly refresh completes by 07:00 your time on business days, so this view is current when your day starts.
  38. Callum Reid
    Callum Reid None
    By when exactly, though. 07:00 isn't a rough target.
  39. Priya Raman
    Priya Raman None
    It's a service level, Callum, and it can sit in the order form. Same as I said with Richard.
  40. Callum Reid
    Callum Reid None
    Then I want it in there. What I need is that it's written, not promised.
  41. Callum Reid
    Callum Reid None
    Different question. Could this send a scheduled pack to a capacity provider? Same report, same day each month, no one touching it.
  42. Tobias Renwick
    Tobias Renwick None
    The honest answer is that isn't something I'll commit to today. You can build the dashboard and export what it shows, and your team can send it. A fully automatic pack to an external party is a different question, and I won't give you a date for it when I'm not certain.
  43. Callum Reid
    Callum Reid None
    Fair. I'd rather hear that than a maybe.
  44. Priya Raman
    Priya Raman None
    And I'd say, to be fair to the demo, the win is the two people not spending their week assembling it. Sending it is the easy part.
  45. Callum Reid
    Callum Reid None
    Sending it isn't easy if it's wrong. But I take the point.
  46. Tobias Renwick
    Tobias Renwick None
    May I show one more thing, since you mentioned who asks the questions? There's a view of what's been asked in the brain and by whom. It matters for adoption. If one person is asking most of the questions, that's a key-person risk, and you'd want to know.
  47. Callum Reid
    Callum Reid None
    That'd be me, at first. Then I'd want the underwriters on it, otherwise it's my toy.
  48. Tobias Renwick
    Tobias Renwick None
    Which is the usual pattern. The champion starts, and the value shows when a second and third team ask their own. It's one of the things your customer success manager would watch with you.
  49. Callum Reid
    Callum Reid None
    Right. I've seen what I needed. Let me tell you where I am. The submissions answer was right and, more to the point, it found the mismatch. The bordereaux view works. I'm not happy about the scheduled pack, but I'd rather know now. Security, I can take to IT.
  50. Priya Raman
    Priya Raman None
    That's a good place to be. So, next steps. Tobias, could you write the architecture on one page for Callum's IT team?
  51. Tobias Renwick
    Tobias Renwick None
    Yes. I'll keep it to one page, covering where the data sits, how permissions follow your warehouse, and what we need from them at setup. I'll send it tomorrow.
  52. Priya Raman
    Priya Raman None
    And I'll put together the proposal. Callum, you know the number Richard saw, fifty-six all in, implementation included. Do you want me to walk him through it, or would you rather bring it to him?
  53. Callum Reid
    Callum Reid None
    That's Richard's. I'll get the demo points to him and you take it from there. But book him a call. By when?
  54. Priya Raman
    Priya Raman None
    If we can get it over the line by Monday 17 June 2024, I'd want him on a call well before then. I'll send options to you both today, happy to make this easy.
  55. Callum Reid
    Callum Reid None
    Fine. Send them. I'm off, I'm late already.
  56. Tobias Renwick
    Tobias Renwick None
    Thank you, Callum. Best of luck with the rest of the day.
  57. Priya Raman
    Priya Raman None
    Thanks both. Speak soon.

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