Tom Ashdown

Lindqvarn Retail / BB-Demo – Demo

Callcompleted

Lindqvarn Retail: documents logo Lindqvarn Retail: documents · 2025-02-19 08:30

Hannah Lowe demoed the brain on sample exports for Karin Sjöberg and Johan Berglund. They want one segment view that store managers can use, and returns with reasons. No tier or price was discussed; a decision was still targeted for 18 Mar 2025.

What was said

What this says

Current to 11 Oct 26

Hannah Lowe demoed the brain on sample exports for Karin Sjöberg and Johan Berglund. They want one segment view that store managers can use, and returns with reasons. No tier or price was discussed; a decision was still targeted for 18 Mar 2025.

What happened: Hannah ran the 19 Feb 2025 demo on sample exports from customer service, e-commerce and store feedback. Johan had to leave early and had nothing to decide.

Customer view: Karin wants one segment view that store managers can use, and pages her team owns. Johan wants returns and complaints by product without building a report each time.

Commercial: No tier or price was named. Hannah mentioned the Enterprise security review, and Tom Ashdown said a decision was still targeted for 18 Mar 2025.

Watch: Return reasons are often blank at source, which limits the returns answer. Karin said Mats will want to know the control is the customer's, so a written architecture note is owed.

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

Themes

Current to 9 Oct 26
Theme
Segment view demo
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hannah Lowe to send the written architecture note and the list of what is needed from IT.
  • Tom Ashdown to diarise the security conversation and prepare the numbers for Mats.
  • Johan Berglund to send his questions for use in the next demo session.

Risks

Current to 9 Oct 26
  • Return reasons are often blank in the customer's own data, so the returns answer may look thin.
  • Mats needs written assurance that control stays with the customer inside their own Snowflake account.

Opportunities

Current to 9 Oct 26
  • Store-manager pages and a dashboards builder could justify Growth or Enterprise.
  • Johan's returns-by-channel question gives a concrete test for the next session.

Transcript

  1. Tom Ashdown
    Tom Ashdown None
    Morning, all. Early one, this. Karin, how are you? Johan, good to have you.
  2. Karin Sjöberg
    Karin Sjöberg None
    Good morning, Tom. I am well, thank you. Johan has joined, he is just sharing his camera.
  3. Johan Berglund
    Johan Berglund None
    Morning. Can you hear me? Good. Apologies, I have a call with the web team straight after, so I may need to leave a little early.
  4. Tom Ashdown
    Tom Ashdown None
    No problem at all. Hannah's going to run the demo, and I'll keep out of her way. Hannah, over to you.
  5. Hannah Lowe
    Hannah Lowe None
    Thanks, Tom. Good morning. Before I share anything, what do you most need to know from the next hour? I can shape it around that.
  6. Karin Sjöberg
    Karin Sjöberg None
    We should anchor this. I would like to see one customer segment across customer service, the web shop and the store feedback, and I would like the store managers to be able to use it.
  7. Johan Berglund
    Johan Berglund None
    From e-commerce I care about whether it can answer questions about returns and complaints by product without my team building a report each time.
  8. Hannah Lowe
    Hannah Lowe None
    Good, that's clear. The short answer is yes to both. The longer answer is that it depends on how clean the sources are, and I'll show you where that bites. I've loaded sample exports from the three areas into a demo set, so you'll see your own shape of data rather than something polished.
  9. Hannah Lowe
    Hannah Lowe None
    Sharing my screen now. This is the front page. Think of it as one search box over everything connected. Let me ask something plain: which products attract the most complaints in customer service.
  10. Hannah Lowe
    Hannah Lowe None
    It comes back with an answer, and, importantly, it shows where each part came from. Here are the helpdesk tickets, and here is the link back to the original record.
  11. Karin Sjöberg
    Karin Sjöberg None
    That is the part I like. The source is visible. What do the stores say, though? Can I add the store feedback to the same question?
  12. Hannah Lowe
    Hannah Lowe None
    Yes. Same question, now with the store forms included. You can see the store feedback speaks about the same products, with a slightly different emphasis. Stores mention delivery and assembly more than the helpdesk does.
  13. Johan Berglund
    Johan Berglund None
    That is interesting. In e-commerce we see returns, but not the reason. Can you show returns next to that?
  14. Hannah Lowe
    Hannah Lowe None
    Let me do it. I'll ask for returns by product alongside the complaint themes. There. The caveat, to be precise, is that this is only as good as the field that records the return reason. In the sample, about a fair share of them are blank, so the brain says so rather than guessing.
  15. Johan Berglund
    Johan Berglund None
    That is honest. Our return reasons are not always filled in. We know that.
  16. Hannah Lowe
    Hannah Lowe None
    It's worth knowing early. It's fixable at the source, and the brain will show you where the gaps are, which most people find useful in itself.
  17. Tom Ashdown
    Tom Ashdown None
    Can I come in? This is the bit customers tell me they like, Karin. Not the clever answer, but being told what it can't answer.
  18. Karin Sjöberg
    Karin Sjöberg None
    Yes. I would rather be told. Hannah, can you show how a store manager would use it? She does not want a dashboard with twenty filters.
  19. Hannah Lowe
    Hannah Lowe None
    Right. Here's a page built for a regional store manager. It's a saved view with three questions already on it, and she can type her own underneath. Pages like this are part of every tier. The dashboards builder is a Growth and above feature, which Enterprise includes.
  20. Johan Berglund
    Johan Berglund None
    Who builds the pages? My team, or yours?
  21. Hannah Lowe
    Hannah Lowe None
    Yours, once we've set it up. We'd build the first ones with you during implementation so your team knows how, and then you own them.
  22. Karin Sjöberg
    Karin Sjöberg None
    That matters. We do not want to depend on you for every change.
  23. Hannah Lowe
    Hannah Lowe None
    Understood. Let me come to the architecture, because I know your IT colleagues will ask. The brain is built and run inside your own Snowflake account. Your data stays there, and we work within the permissions you give us.
  24. Karin Sjöberg
    Karin Sjöberg None
    Mats will ask about that. He wants to know the control is ours.
  25. Hannah Lowe
    Hannah Lowe None
    Then I'll put it in writing: what we can see, what we can't, and how access is granted and removed. For the Enterprise tier there's also a security review, and I'd do that with your IT team. I won't answer anything about a specific control until I've checked it properly, so you'll get a written answer, not a guess on a call.
  26. Johan Berglund
    Johan Berglund None
    Good. That is what I would want. I must go in a few minutes. Is there anything I should decide today?
  27. Tom Ashdown
    Tom Ashdown None
    Nothing at all, Johan, no drama. Just tell us what question you'd most like to see answered, and Hannah can use it in the next session.
  28. Johan Berglund
    Johan Berglund None
    Returns by product and by channel, with the reason. And whether campaigns change the complaints. I will send a short note.
  29. Hannah Lowe
    Hannah Lowe None
    Perfect, that's a good test. Thanks, Johan.
  30. Karin Sjöberg
    Karin Sjöberg None
    Thank you, Johan. We will think about it together afterwards, with Mats.
  31. Tom Ashdown
    Tom Ashdown None
    Right, so, next steps. Hannah sends the written architecture note and a list of what we'd need from your IT. Johan sends his questions. I'll get something in the diary for the security conversation and the numbers for Mats. We're still working towards Tuesday 18 March 2025 for a decision, but only if it feels right to you.
  32. Karin Sjöberg
    Karin Sjöberg None
    That is acceptable. Thank you both. It was clearer than I expected.
  33. Hannah Lowe
    Hannah Lowe None
    Thanks, Karin, thanks, all. Thanks, Hannah, as they say. Speak soon.
  34. Tom Ashdown
    Tom Ashdown None
    Cheers, everyone.

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