Callie Brennan

Delancey Haig / BB-Demo – Onboarding

Callcompleted

Delancey Haig: documents logo Delancey Haig: documents · 2024-07-16 16:30

Onboarding call with Delancey Haig on Growth. Adoption is thin, four sources are planned for the first wave, access depends on IT and finance, and the mailbox is deferred. Saskia Mendes left feeling better about it.

What was said

What this says

Current to 11 Oct 26

Onboarding call with Delancey Haig on Growth. Adoption is thin, four sources are planned for the first wave, access depends on IT and finance, and the mailbox is deferred. Saskia Mendes left feeling better about it.

What happened: Callie Brennan set the connector order for the first wave: CRM, placements system, accounting system and helpdesk. SharePoint is planned for a second wave.

Customer view: Saskia Mendes said adoption is thin and the directors have not logged in. She also noted that the helpdesk alone will miss complaints that arrive by email.

Commercial: Callie confirmed Growth at £41,800 a year with forty users and eight connectors. Single sign-on was named as an Enterprise feature, which Holly Tranter will flag to IT.

Watch: Holly is the only admin, and the Snowflake role depends on an IT colleague. Callie advised two admins, and the colleague is the proposed second.

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

Themes

Current to 9 Oct 26
Theme
Growth onboarding and access
Importance
neutral
Sentiment
mixed
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Callie Brennan sends the written access request for IT and the field-list note for finance the day after the call.
  • Saskia Mendes arranges placements system access by Friday and picks two or three test clients.
  • Holly Tranter forwards the Snowflake request to IT and asks a colleague to be second admin.

Risks

Current to 9 Oct 26
  • Adoption is thin and the directors have not yet logged in.
  • Access depends on IT and finance teams that Holly Tranter does not control.
  • Complaints sent by email will be missed until the mailbox is connected.

Opportunities

Current to 9 Oct 26
  • Single sign-on is an Enterprise feature if IT makes it a requirement.
  • A second-phase mailbox connector and SharePoint would deepen use of the eight connectors on Growth.

Transcript

  1. Callie Brennan
    Callie Brennan None
    Hello, hello. Can you hear me alright? I've got the recording going, just so you know.
  2. Saskia Mendes
    Saskia Mendes None
    Loud and clear. Hi Callie. Holly's just joining, I think she's on mute.
  3. Holly Tranter
    Holly Tranter None
    Hi, sorry, yes. The meeting room screen fought me for a minute. Can you both hear me?
  4. Callie Brennan
    Callie Brennan None
    Perfect. Good afternoon, both. Thanks for making time at this end of the day, I know Tuesdays get away from people.
  5. Saskia Mendes
    Saskia Mendes None
    Oh, you have no idea. Quick story from this week, actually, and it's why I'm keen on all this. One of our client-account directors went into a review on Monday and the client opened with a complaint she'd never heard about. It had been sitting with someone in billing for days. She had the vacancies, she had the placements, and she was blindsided by an invoice query.
  6. Holly Tranter
    Holly Tranter None
    Mm. That's the one about the contractor timesheets, isn't it?
  7. Saskia Mendes
    Saskia Mendes None
    That's the one. So, the directors need this, and I'd like them to have it sooner rather than later. Sorry, I've launched straight in.
  8. Callie Brennan
    Callie Brennan None
    No, that's a good place to start, honestly, because that's the picture we're building towards. So let me give you the plan for the next forty minutes or so. First, a quick look at where we are and who owns what on your side. Second, the connectors: which sources we connect, in what order, and what I need from your side for each. Third, what happens at the first refresh. And last, how we hand the day to day over to Holly so you're not relying on me.
  9. Holly Tranter
    Holly Tranter None
    That sounds sensible. I should say up front, I'm the person who'll be doing most of the clicking, and I've not seen the product beyond the demo recording Saskia sent round.
  10. Callie Brennan
    Callie Brennan None
    That's fine, that's exactly what today is for. Saskia, just to set the frame, you're on Growth, so forty users and eight connectors. The contract is for £41,800 a year, and the implementation runs over about eight weeks. We're at the start of that now.
  11. Saskia Mendes
    Saskia Mendes None
    Right. And I'll be straight with you, adoption is thin at the moment. A handful of us have logged in and had a poke around. The directors haven't. I'm not going to pretend otherwise.
  12. Callie Brennan
    Callie Brennan None
    Which is normal before a first refresh, there's nothing in there worth looking at yet. So our job is to get the data landing cleanly, and then the directors will have a reason to come in. Can we start with the sources? Holly, did you get the checklist I sent over last week?
  13. Holly Tranter
    Holly Tranter None
    I did. I've got it open. I haven't done all of it, so bear with me.
  14. Callie Brennan
    Callie Brennan None
    No problem. Let me share my screen so we're looking at the same list. Give me a second.
  15. Callie Brennan
    Callie Brennan None
    Okay, can you see it? That's the connector plan. There's a column for the system, a column for the access I need, a column for who gives it, and a date against each one.
  16. Holly Tranter
    Holly Tranter None
    Yes, I can see that. It's a bit small but I've got my own copy.
  17. Callie Brennan
    Callie Brennan None
    Good. So, first things first. Everything lands in your Snowflake account, so before anything else I need to know the Snowflake side is ready. Holly, you're the admin there?
  18. Holly Tranter
    Holly Tranter None
    I'm the admin for the business systems, yes. For Snowflake itself it's me and a colleague in IT. He's the one who created the account, so I'd want him on a call before anything gets switched on.
  19. Callie Brennan
    Callie Brennan None
    That's useful. What I need from your side is a dedicated role and warehouse for the brain, created by whoever holds that, and the details sent to me in writing. I don't start a connector without written access, it saves everyone grief later.
  20. Saskia Mendes
    Saskia Mendes None
    Can we make it simpler? Is it a case of Holly emailing IT and IT sending you something?
  21. Callie Brennan
    Callie Brennan None
    Pretty much. I'll write the exact request so Holly can forward it as it is, and IT only has to tick through it. Nobody has to translate.
  22. Holly Tranter
    Holly Tranter None
    That would help. He's lovely but he's got a queue as long as my arm.
  23. Callie Brennan
    Callie Brennan None
    Understood. I'll send that tomorrow, so you've got the rest of the week to get it done. Right, the sources. Top of the list is the CRM, because that's where your clients and your vacancies live. Which one are you using for the client relationships, Holly, and who owns it?
  24. Holly Tranter
    Holly Tranter None
    The CRM is ours, I look after it. I can create a service user with read access. The vacancies and placements sit in a separate placements system though, which is a different team's. So that's two.
  25. Callie Brennan
    Callie Brennan None
    Good, I'm glad you said that, because it changes the order. So the CRM first, then the placements system. Does the placements system give us a read-only way in, do you know?
  26. Holly Tranter
    Holly Tranter None
    I think so. There's a reporting login the operations team use. I'd have to check whether that's what you'd want, or whether we ought to ask for something properly set up.
  27. Callie Brennan
    Callie Brennan None
    A proper one, please. A shared reporting login tends to get its password changed and then the refresh fails at three in the morning and nobody knows why. A named service account is much cleaner.
  28. Saskia Mendes
    Saskia Mendes None
    I'll chase that one. The placements system belongs to my team's side of things, so that's on me. Put my name against it.
  29. Callie Brennan
    Callie Brennan None
    Lovely. Saskia against the placements system. And I'll put a date next to it so it doesn't float. Would end of this week be fair?
  30. Saskia Mendes
    Saskia Mendes None
    Friday. Yes. If it slips I'll tell you on Friday, not the week after.
  31. Callie Brennan
    Callie Brennan None
    Great, thank you. That's a habit I like. Now, invoices. You mentioned in the order discussions that the invoices matter, and the contractor-invoice disputes especially. Where do those sit?
  32. Holly Tranter
    Holly Tranter None
    In the accounting system, which finance own. I don't have admin on it at all. I'd be asking our finance team, and they're quite careful about it, understandably.
  33. Callie Brennan
    Callie Brennan None
    Understandably, yes. What I'd ask is a read-only user, and nothing that can write back. We never write to the accounting system, we only read. If it helps I can put that in a short note for finance, so they can see exactly what is and isn't touched.
  34. Saskia Mendes
    Saskia Mendes None
    Please do. What did the finance team actually say when you spoke to them in the sales stage? I wasn't in that conversation.
  35. Holly Tranter
    Holly Tranter None
    I wasn't either, but I gather they were fine with the idea, as long as it's read-only and they can see the list of fields in advance.
  36. Callie Brennan
    Callie Brennan None
    That's easy, I'll put the field list in the note. So that's the accounting system, owner on your side is finance, and Holly is the go-between. Holly, are you comfortable being that?
  37. Holly Tranter
    Holly Tranter None
    Yes. I'd rather be the one in the middle than have three people emailing you separately.
  38. Callie Brennan
    Callie Brennan None
    That makes my life a lot easier, thank you.
  39. Callie Brennan
    Callie Brennan None
    Right, complaints. This is the one I'm most interested in for Saskia's story. Where do client complaints get logged at the moment?
  40. Saskia Mendes
    Saskia Mendes None
    Honestly, in a few places. Some go in the helpdesk, which is the formal route. A lot arrive by email to the account director and never get logged at all. That's half the problem.
  41. Callie Brennan
    Callie Brennan None
    Okay, so I want to be careful here, because the brain can only show what's been recorded. If the complaint only lives in somebody's inbox, we'll only see it if the mailbox is connected, and that's a bigger conversation about privacy and who agrees to it.
  42. Holly Tranter
    Holly Tranter None
    Right. That's something I'd need to take to our compliance people, I think. Not today.
  43. Callie Brennan
    Callie Brennan None
    Not today, agreed. Let's start with the helpdesk, because that's already structured and it maps cleanly. We can come back to email once you've seen what the brain does with the first sources. Is that fair, Saskia?
  44. Saskia Mendes
    Saskia Mendes None
    Fair. Though I'll say this, if we only get the helpdesk we'll still miss the Monday story. I'd like to come back to that in a few weeks.
  45. Callie Brennan
    Callie Brennan None
    Noted, and I'll put it on the list as a second phase so it doesn't get lost. Daniel, your customer success manager, will be the one to pick that up with you once we're live, because it's more about how you use it than the plumbing.
  46. Saskia Mendes
    Saskia Mendes None
    Daniel Okafor. Yes, we've met. Good.
  47. Callie Brennan
    Callie Brennan None
    So that's four sources for the first wave: CRM, placements system, accounting system and helpdesk. You've got eight connectors in the plan, so plenty of room for later. Any I've missed that matter in the first month?
  48. Holly Tranter
    Holly Tranter None
    Documents, maybe. We have a shared drive with the client contracts and the terms of business, and the directors are always hunting for those.
  49. Callie Brennan
    Callie Brennan None
    Yes, that's a sensible fifth. Is that in Microsoft 365 or somewhere else?
  50. Holly Tranter
    Holly Tranter None
    SharePoint, yes. It's in Microsoft 365.
  51. Callie Brennan
    Callie Brennan None
    Great. SharePoint goes in as the fifth, but I'd put it in the second wave, because document folders are where permissions get untidy. I'd want you to tell me which sites are fair game before I touch any of it.
  52. Holly Tranter
    Holly Tranter None
    Yes, that's definitely a conversation. There are some folders that nobody outside HR should ever see.
  53. Callie Brennan
    Callie Brennan None
    Exactly. And that's a good habit for the whole thing: we only bring in what you've said yes to, in writing, and Holly can see the list at any time.
  54. Saskia Mendes
    Saskia Mendes None
    Can I ask a practical one? When the directors do finally open this, what will they actually see on day one? I don't want to over-promise to them and then have a blank page.
  55. Callie Brennan
    Callie Brennan None
    Good question, and the honest answer is: after the first refresh, you'll have a page per client with the vacancies, placements, invoices and any helpdesk tickets together, and you can ask it questions in plain English. What it won't have on day one is history from sources we haven't connected, and it won't be right until we've checked the mapping with you.
  56. Saskia Mendes
    Saskia Mendes None
    Okay. That I can tell them. A page per client, built from four sources, and we'll check it together.
  57. Callie Brennan
    Callie Brennan None
    Yes. And I'd actually suggest you pick two or three clients as test cases. Ones you know really well. Then when the first refresh lands, you can check the page against what you know to be true.
  58. Saskia Mendes
    Saskia Mendes None
    I like that. I'd pick the one with the contractor dispute, because I know exactly what that page ought to say.
  59. Holly Tranter
    Holly Tranter None
    And maybe a boring one, as a control. A client where nothing has gone wrong.
  60. Callie Brennan
    Callie Brennan None
    Oh, that's a really good idea. A quiet one and a noisy one. Holly, you've done this before, haven't you?
  61. Holly Tranter
    Holly Tranter None
    Only with reports. Same principle, really. If it's wrong on the dull one, it's wrong everywhere.
  62. Callie Brennan
    Callie Brennan None
    Right, let me go through the mapping side, because this is where the time goes. When we pull the CRM in, your client names need to match across systems. If a client is spelled one way in the CRM and another way in accounting, the brain will treat them as two clients.
  63. Holly Tranter
    Holly Tranter None
    Ah. We have that. It's quite common, actually, with the old group companies. Same client, three names.
  64. Callie Brennan
    Callie Brennan None
    Okay, so that's a real thing to plan for. What I'd do is take a sample from each system before we switch anything on, and look at how the names line up. Then we agree a rule, and I write it down in the setup note, so there's no guessing later.
  65. Saskia Mendes
    Saskia Mendes None
    Is that something Holly needs to do, or is that you?
  66. Callie Brennan
    Callie Brennan None
    Mostly me. What I need from Holly is an export of the client list from each system, just the names and whatever reference each system uses. Nothing sensitive, no money, no personal details. I'll tell her exactly which columns.
  67. Holly Tranter
    Holly Tranter None
    That I can do quickly. Is there a format you'd prefer?
  68. Callie Brennan
    Callie Brennan None
    A spreadsheet is perfect. One tab per system if you like.
  69. Holly Tranter
    Holly Tranter None
    Sorry, one more thing on that. If the same client is under three names, who decides which is the right one? Because I can guess, but the account directors may disagree.
  70. Saskia Mendes
    Saskia Mendes None
    That's me, then. If it's a naming argument, bring it to me and I'll rule on it. I'd rather have one person decide than a committee.
  71. Callie Brennan
    Callie Brennan None
    Brilliant. That's a decision owner, so I'll write that down. Saskia decides on client naming, Holly prepares the lists, I propose the matching rule.
  72. Saskia Mendes
    Saskia Mendes None
    Don't tell Rupert I've given myself more power.
  73. Callie Brennan
    Callie Brennan None
    Ha. My lips are sealed. Mind you, he's on the list as a stakeholder, so he'll see it in the plan.
  74. Saskia Mendes
    Saskia Mendes None
    Well. That's fair.
  75. Callie Brennan
    Callie Brennan None
    Let's talk about the first refresh itself, because I want you both to know what to expect. Before we switch on the refresh, I do a dry run on a small slice of data. Nothing is visible to your users. I check that records are arriving, counts look sensible, and nothing is failing quietly.
  76. Holly Tranter
    Holly Tranter None
    And how will I know it's gone right? Is there something I can look at?
  77. Callie Brennan
    Callie Brennan None
    Yes. There's an admin view with each connector, its last run, and how many records it indexed. I'll walk you through it in a moment. The thing to watch is whether the record count keeps climbing after the first load. If it goes flat for a while, that usually means a source has stopped loading, often because somebody changed something in that system.
  78. Holly Tranter
    Holly Tranter None
    Which will happen. We change the CRM all the time.
  79. Callie Brennan
    Callie Brennan None
    It does, and that's nobody's fault. The ask is just: if you're changing fields or permissions on a connected system, drop a line to the support desk or to me while I'm on the project, and we'll check the mapping still holds.
  80. Holly Tranter
    Holly Tranter None
    Okay. I'll add it to our change checklist, so it doesn't rely on my memory.
  81. Callie Brennan
    Callie Brennan None
    That's exactly the right instinct.
  82. Callie Brennan
    Callie Brennan None
    Okay, I'm going to flip to the admin view so you can see it. One moment while I load it up.
  83. Callie Brennan
    Callie Brennan None
    There we are. This is a demo workspace, not yours, so ignore the names. Down the left you've got the connectors, each with a status. Green is running, amber is a warning, red is failed. In the middle, the last run time and the number of records. And over here, the users and who's an admin.
  84. Holly Tranter
    Holly Tranter None
    Right. So I'd be looking at the amber ones first thing in the morning?
  85. Callie Brennan
    Callie Brennan None
    Yes. The nightly refresh should be complete by seven in the morning, your time, on business days. So a quick look at about that time tells you whether you've got a clean start to the day.
  86. Saskia Mendes
    Saskia Mendes None
    Can I ask, how many admins should we have? I'd rather not have only Holly. She goes on holiday.
  87. Holly Tranter
    Holly Tranter None
    I do. Occasionally. Fair point.
  88. Callie Brennan
    Callie Brennan None
    Strong point, actually. I'd always say two. One main, one cover. Does anyone come to mind, Holly, someone who understands the systems?
  89. Holly Tranter
    Holly Tranter None
    My colleague in IT would be the natural one, since he's in Snowflake anyway. I'd have to ask him.
  90. Callie Brennan
    Callie Brennan None
    That sounds ideal. If you can ask him this week, I'll add him as the second admin when we do the user set up.
  91. Saskia Mendes
    Saskia Mendes None
    Right, users. We've got forty seats. I won't need forty for a while. The directors, a few people from operations, finance for the invoice side. What's sensible for the start?
  92. Callie Brennan
    Callie Brennan None
    I'd start small and deliberate. Directors who will actually use it, plus whoever can sanity check the data. A group of fifteen is a nice size, but you decide. People who are given access without a reason tend not to come back.
  93. Saskia Mendes
    Saskia Mendes None
    Yes. I've seen that with other tools. Everyone gets a login, nobody uses it, and then we're asked why we're paying for it.
  94. Callie Brennan
    Callie Brennan None
    So you'd rather have a smaller group who ask questions every week. And you can add the rest whenever you want, there's no penalty for starting small.
  95. Saskia Mendes
    Saskia Mendes None
    Good. Then it's the directors and a few of us. I'll draft a list and send it to Holly.
  96. Holly Tranter
    Holly Tranter None
    On sign-in, will people use their normal work login? Because if they have to remember another password, it won't get used.
  97. Callie Brennan
    Callie Brennan None
    Good one. On Growth, people sign in with an email and password, or a link to their email. Single sign-on is an Enterprise feature, so it's not part of your plan. If that becomes a requirement we can talk about it, but for forty users it's usually fine.
  98. Holly Tranter
    Holly Tranter None
    Okay. That's fine for now. I'll flag it to our IT lead, in case he has a view.
  99. Callie Brennan
    Callie Brennan None
    Please do. Better to know early.
  100. Callie Brennan
    Callie Brennan None
    Let me recap the actions, because we've covered a fair bit and I'd hate for any of it to drop. Tell me if I've got any of this wrong. Holly, you'll forward the Snowflake request to IT, and ask your colleague about being second admin. That's this week.
  101. Holly Tranter
    Holly Tranter None
    Yes. And I'll set up the CRM service user, and send the client name lists, one tab per system.
  102. Callie Brennan
    Callie Brennan None
    Lovely. Saskia, the placements system access by Friday, and you'll rule on client naming when it comes up. And you'll pick two or three test clients, a noisy one and a quiet one.
  103. Saskia Mendes
    Saskia Mendes None
    Yes. The contractor dispute one, and a dull one. I'll send Holly the names tomorrow.
  104. Callie Brennan
    Callie Brennan None
    And from me: tomorrow I send the written access request for IT, the short note for finance with the field list, and the setup checklist, updated with the dates we've agreed today. I'll also write up the plan so the order of the connectors is in one place.
  105. Holly Tranter
    Holly Tranter None
    That would be great. I'll keep everything in one folder so I don't lose track.
  106. Saskia Mendes
    Saskia Mendes None
    Can I ask about timing? When can I tell the directors they'll see something? I'd like to give them a date, even a rough one.
  107. Callie Brennan
    Callie Brennan None
    I'd rather not promise a date until the access has come through, because that's what drives it. Realistically, if the access arrives by the end of next week, then the first refresh on the first sources is a matter of days after that. Then we check it with you, and then it's something the directors can have a look at.
  108. Saskia Mendes
    Saskia Mendes None
    So, tell them a few weeks, and promise nothing else.
  109. Callie Brennan
    Callie Brennan None
    Yes, that's honest, and it's what I'd say. And I'd rather you under-promise and it turns up early.
  110. Saskia Mendes
    Saskia Mendes None
    Ha, fine by me.
  111. Holly Tranter
    Holly Tranter None
    One more question, if there's time. When you've finished, when the project is over, what do I have? Is there a document I can pass on if I'm off or I move on?
  112. Callie Brennan
    Callie Brennan None
    Yes, and that's important to me. I never hand over without a setup note. It lists every connector, what it reads, the account it uses, who owns it on your side, the naming rules we agreed, and what to do when something turns amber. It's written so that someone who wasn't on this call could pick it up.
  113. Holly Tranter
    Holly Tranter None
    That's exactly what I'd want. Last place I worked, the person who built the reports left and nobody knew how any of it worked.
  114. Saskia Mendes
    Saskia Mendes None
    We've had that here too. More than once. That's partly why I pushed for this.
  115. Callie Brennan
    Callie Brennan None
    Then we're pointing at the same thing. The aim is that Holly can run it without me, and that if she's away, the second admin can too.
  116. Saskia Mendes
    Saskia Mendes None
    Right, anything else from you, Callie? Because I've got a call at the top of the hour, and I want to make sure I haven't skipped something.
  117. Callie Brennan
    Callie Brennan None
    Just one. Is there anyone else who should be on the next call? Somebody from finance, or IT, perhaps? It might save a round of emails.
  118. Holly Tranter
    Holly Tranter None
    Probably yes. Both, actually. I'll ask them for a slot, and I'll tell you who's coming. Would a short call be okay? Half an hour?
  119. Callie Brennan
    Callie Brennan None
    Half an hour is plenty. Ideally in the middle of next week, once you've forwarded the requests. I'll send you a couple of times that work for me.
  120. Holly Tranter
    Holly Tranter None
    Perfect.
  121. Saskia Mendes
    Saskia Mendes None
    Good. I feel better about this than I did an hour ago. Which is saying something, because I was quite wound up about Monday.
  122. Callie Brennan
    Callie Brennan None
    That's understandable, and it's a very good example for us to build around. We'll make sure the first test page answers that exact question: what did the client actually say, and has anyone replied?
  123. Saskia Mendes
    Saskia Mendes None
    Yes. That's it exactly. Thank you.
  124. Holly Tranter
    Holly Tranter None
    Thanks, Callie. I'll get the forward off to IT as soon as I'm off this call, so it's not sitting on my list overnight.
  125. Callie Brennan
    Callie Brennan None
    Brilliant. If anything's unclear in what I send tomorrow, just ask. It's much quicker to ask than to guess, and I'd rather get a question than a surprise.
  126. Saskia Mendes
    Saskia Mendes None
    Will do. Right, I'll let you both go. Thanks, Callie, this was really useful.
  127. Callie Brennan
    Callie Brennan None
    My pleasure. Thanks, both. Speak soon, and good luck with the rest of the day.
  128. Holly Tranter
    Holly Tranter None
    Bye, both.
  129. Saskia Mendes
    Saskia Mendes None
    Bye, bye.

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
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

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.

HelpAsk B

Ask B

B-Brain · read-only