Mossbrook Data Partners / BG-Demo – Training
Callcompleted
Mossbrook Data Partners · 16 Dec 2025 10:45
Hannah Lowe trained two Mossbrook consultants on the Snowflake connector, entity mapping and chat, ahead of a client demo. They left confident to run the next set-up themselves, and asked early about Starter limits.
What was said
What this says
As at Fri 9 Oct 2026Hannah Lowe trained two Mossbrook consultants on the Snowflake connector, entity mapping and chat, ahead of a client demo. They left confident to run the next set-up themselves, and asked early about Starter limits.
What happened: On 16 Dec 2025 Hannah walked Lauren Bickerstaff and Ciaran Doherty through a live connector set-up on a test schema. Ciaran's failed connection tests came from a role missing schema usage, which he called his own mistake.
Customer view: Both said it was clearer than expected, and Lauren said she would run the next one herself with Ciaran on the Snowflake side. They liked that everything stays in the client's own account.
Commercial: Lauren asked where the Starter limits sit, saying she was not asking for anything yet. Hannah named fifteen users as a soft limit and four connectors as a hard limit, and said she would route any need for more to Sophie and Marcus.
Watch: Ciaran called silent staleness his biggest worry. Table-level hiding between users on Starter is unconfirmed until Ewan answers.
Themes
As at Fri 9 Oct 2026Theme
Partner connector and mapping training
Importance
upsell
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Hannah Lowe to send the table approval template, the one page diagram and Ewan's answer on hiding tables.
- Hannah to tell Sophie Ling and Marcus Bell that a capacity conversation on connectors and users is coming.
- Ciaran Doherty to write up the role and grants and the freshness check, after a dry run.
Risks
As at Fri 9 Oct 2026- Four connectors is a hard limit on Starter, so serving several clients through it could hit the ceiling quickly.
- Whether Starter can hide tables between users is unconfirmed, and the client's IT person is expected to ask.
- A blank or unchanged updated column would leave a mapped source quietly stale.
Opportunities
As at Fri 9 Oct 2026- Lauren said more than one client may use B-Viz if the Astley Brook demo goes well, which could mean more connectors or a higher tier.
- The partner is preparing a demo on a client's own data, which could bring a new B-Viz customer.
Transcript
Hannah LoweHello, hello. Can you both hear me all right?
Lauren BickerstaffLoud and clear. Morning, Hannah. I think Ciaran's just unmuting.
Ciaran DohertyHere. Morning. Sorry, wrong headset.- Hannah LoweNo problem at all. How's the week treating you?
- Lauren BickerstaffBusy, which is the good kind. It's the run up to Christmas, so every client wants everything signed off before the break. And it's raining sideways in Manchester, so nobody's in the mood.
- Hannah LoweSame in London, honestly. Right, before I share anything, what do you most need to know by the end of today? I'd rather aim at that than march you through slides.
- Lauren BickerstaffOkay, so the plan from our side. Astley Brook is going to see a demo on their own data, and we want to be the ones who've set the Snowflake side up properly before you come in. What's left on the list is really three things: the connector, the entity mapping, and being able to answer their questions without ringing you every time.
- Ciaran DohertyCan I start with what I found in the logs?
- Hannah LowePlease do.
- Ciaran DohertyTest connection failed twice last week. Not the network. I checked the role grants. The role I made had usage on the database but nothing on the schema. So it could see the door and not the room.
- Hannah LoweThat's the most common one, and it's a good place to start because it leads straight into how the connector works. To be precise, the role needs usage on a warehouse, usage on the database and the schema, and select on the tables you've chosen. It never needs to write to your source tables.
- Ciaran DohertyGood. Least privilege. I'd rather grant per table than select on all tables in the schema.
- Hannah LoweI'd agree, and that's what I'd recommend for a client like Astley Brook. The short answer is that either works. The longer answer is that future grants on a whole schema mean a new table appears in B-Viz the moment someone creates it, and most clients are not expecting that.
- Lauren BickerstaffYeah, that would be a surprise at sign-off. Has the client seen it yet, I mean the list of what we'll expose? Because I'd want them to approve that list in writing.
- Hannah LoweI'll put that in writing for you, a one page template: tables in, tables out, who approved. Mm. And it makes the later conversation about what B-Viz can see much easier.
- Ciaran DohertyWhich warehouse does the refresh run on?
- Hannah LoweGood question. B-Viz runs inside the customer's Snowflake account, so it's whichever warehouse you point it at. I'd suggest a dedicated extra-small one with auto-suspend, so you can see exactly what it costs the client and nothing else is competing with it.
- Ciaran DohertyDedicated. Fine. Easier to explain on the bill too.
- Lauren BickerstaffThat's a real selling point with our clients, actually. Everything stays in their account. Okay, I'm writing that down. Dedicated warehouse, per table grants.
- Hannah LoweRight. Let me share my screen and we'll do it properly rather than talk about it. Can you see the admin page?
- Lauren BickerstaffYes, connectors list, and there's an empty slot.
- Hannah LoweThat's the one. Starter has four connectors, and that's a hard limit, so each slot is worth thinking about. For today we'll use one for the Snowflake connector on a test schema, not a client's production one.
- Ciaran DohertyGood. I don't touch a client's production account on a Friday anyway, and I'd want a dry run first.
- Hannah LoweHa, sensible. So, add connector, choose Snowflake. First field is the account identifier, then the user, then authentication. I'd use key pair rather than a password, because it can be rotated without anyone typing a secret into a form.
- Ciaran DohertyKey pair. I've got one generated. Give me a minute to paste the public key against the service user.
- Ciaran DohertyDone. Service user has the role, role has the warehouse, database, schema usage, select on three tables.
- Hannah LoweLovely. Now fill in the account, the user, the role and the warehouse, then paste the private key. Don't test yet, I want you to look at the schema picker first.
- Lauren BickerstaffOkay, I've got the form filled. The picker is showing the test schema and nothing else. Is that because of the role?
- Hannah LoweExactly because of the role. It only lists what the role can see. That's a nice check for a client, honestly: if a table is missing from the picker, it's a grant question, not a B-Viz question.
- Ciaran DohertyThat's a schema question. Or a grant question. Same thing mostly.
- Hannah LowePretty much. Go on, run the test.
- Ciaran DohertyGreen. Connected, three tables found.
- Lauren BickerstaffOh, that's so much nicer than last week. What's left on the list? Mapping, I think.
- Hannah LoweMapping, yes. Let me give you the idea first, then we do it. B-Viz doesn't think in tables, it thinks in entities: organisations, people, deals, tickets, calls. Your job when you map is to tell it which table is which entity, and which column is the identifier.
- Lauren BickerstaffSo a client's customer table becomes organisations.
- Hannah LoweIn the simple case, yes. The short answer is it's a drag and a dropdown. The longer answer is that the identifier is where people get caught. If your key column isn't stable, say it gets reused or regenerated on a reload, then B-Viz sees the same company as two different companies.
- Ciaran DohertySurrogate keys regenerate on full reload in about half the warehouses I've inherited. I'd map to the natural key where there is one. Company number, domain.
- Hannah LoweThat's a better answer than mine, to be fair. Domain is especially useful, because it lets B-Viz join the same organisation across the CRM, the helpdesk and your warehouse without anyone doing it by hand.
- Lauren BickerstaffAnd if there are two records with the same domain? Because Astley Brook will have those. Everyone does.
- Hannah LoweTreat them as one company unless there's a reason not to. B-Viz will flag the pair for review rather than quietly merging them, and you decide. I'd have that conversation with the client before the demo, so nobody is surprised on the day.
- Lauren BickerstaffRight, I like that. No surprises. Let's do it.
- Hannah LoweOpen the mapping tab. Pick the first table. What's it called?
- Ciaran Dohertyclient_accounts. Name, domain, created, updated, owner, status.
- Hannah LoweMap that to organisation. Identifier is domain. Name is name. Now the important one, the updated column. That's your change marker.
- Lauren BickerstaffWhy is that one important? Sorry, I know I should know this.
- Hannah LoweNo, it's the right question. The nightly refresh only reads rows that have changed since the last run, and it uses that column to decide. If it's blank or never updated, B-Viz will read the table once and then think nothing has changed. The data goes stale and nobody complains for weeks.
- Ciaran DohertyThat would be my biggest worry. Silent staleness. I'd add a check on the max updated value in the source.
- Hannah LowePlease do, and I'd love to see it. Our refresh should be complete by 07:00 on business days, so if your check runs a bit before that you'll catch a stuck source first.
- Lauren BickerstaffI'll add that to the hand-over checklist. Item: freshness check, owner Ciaran.
- Ciaran DohertyFine.
- Hannah LoweNext table, then. What's the second one?
- Ciaran Dohertycontacts. Name, email, account id, job title, last seen. Account id points at client_accounts.
- Hannah LoweMap it to person. Identifier is email, and then there's a relationship field, set it to organisation and choose the account id. That's the link that lets someone ask who the contacts are at a company and get a sensible answer.
- Lauren BickerstaffDone. Oh, it's warning me about some blank emails.
- Hannah LoweThat's it being honest with you. Rows with no email can't be identified, so they're skipped and counted. You can fix them at source or leave them. I'd leave them for the demo and mention it, rather than hide it.
- Ciaran DohertyAgreed. Clean up later. I don't change source data to suit a demo.
- Lauren BickerstaffHa, no. Third table is projects, I think? That's the one the Astley Brook people care about.
- Hannah LoweThere isn't a project entity out of the box, so that's an interesting one. We can map it as a custom entity. Give it a name, choose the identifier, and describe in a sentence what it is. That sentence matters more than people think, because it's what the chat uses to understand the question.
- Lauren BickerstaffSo a plain English description. Like, a piece of work we deliver for a client, with a start, an end and a lead.
- Hannah LowePerfect. That's exactly the sort of thing. Fewer jargon words than you'd write for a colleague.
- Ciaran DohertyMapped. Identifier is project code. Lead is a user column, not a contact.
- Hannah LoweThen leave the lead as plain text for now, don't force a relationship that isn't true. Right, save, and run the first load.
- Lauren BickerstaffIt's saying in progress. Should it take this long?
- Hannah LoweFor a test schema, a couple of minutes is normal, because it's building the index as well as copying. For a real client the first load is the longest one, and I'd say so up front so nobody thinks it's stuck.
- Ciaran DohertyWarehouse is running. I can see the queries. Small, as expected. Nothing odd.
- Ciaran DohertyFinished. Records indexed matches the row counts, minus the blank emails.
- Hannah LoweThat's what I like to see. The records indexed figure on the connector page is the one to watch over time. If it goes flat for weeks while the client is still adding rows, something upstream has changed.
- Lauren BickerstaffLike if they rename a column. Which clients do. Constantly.
- Hannah LoweYes, usually after they've changed a system and nobody told you. So it's worth asking the client to tell you before they change a schema, and that's a hand-over item too.
- Lauren BickerstaffAdded. Right, now can we ask it something? I want to see whether it answers the way a client would ask.
- Hannah LoweGo to chat and ask it as if you were the client. Don't be kind to it.
- Lauren BickerstaffOkay. Which projects are overrunning for companies in the North West? Hm. It's answered, but it's asked me what I mean by overrunning.
- Hannah LoweGood. That's it telling you the data doesn't define it. If you've got an end date and an expected end date, you can add a sentence to the project description saying overrunning means actual is later than expected. Then it stops guessing.
- Ciaran DohertyI'd rather it asked than guessed. Never guess.
- Hannah LoweWe're aligned there. It will say when it can't tell, and it shows the records it used, so you can check the answer against the table. That's how you build trust with a sceptical client.
- Lauren BickerstaffLet me try another. Who are the contacts at the biggest client we have on this schema? Oh, nice, it gave a list and the company. And I can click through to the source row?
- Hannah LoweYou can. Mm, that's the bit people like most, honestly. Every answer points back to where it came from.
- Ciaran DohertyQuestion about roles inside B-Viz. Who sees what? If a client has sensitive projects, can I hide a table from some users?
- Hannah LoweThe short answer is that you control it at the connector, by what you grant in Snowflake. The longer answer is that inside B-Viz you manage who the users are and what admin rights they have, but I wouldn't promise table-level hiding between users on Starter. I'm not certain of the exact behaviour for every case, so I'll check with Ewan and put the answer in writing rather than guess.
- Ciaran DohertyFair. Good that you said so. Send me what he says.
- Lauren BickerstaffAnd that's the sort of thing the client's IT person will ask, so I want it in the pack.
- Hannah LoweUnderstood. Now, on the plan for Astley Brook. When we come in for the demo, I'd like it to run on their own data with the mapping you've done, so what we've practised today is the real preparation. What do you want me to do, and what do you want to own?
- Lauren BickerstaffI'd like to own the walkthrough of the mapping, so the client sees it's us who understands their data. You do the architecture and the questions on security. Ciaran does the Snowflake side.
- Ciaran DohertyYes. I'll write up the role and grants as a document the client can keep. Plain, with the statements in it.
- Hannah LoweLovely. And I'd put a diagram on one page: their Snowflake account, the dedicated warehouse, the role, the connector, nothing leaving. I'll draw it and you can edit it.
- Lauren BickerstaffCan I ask about capacity? We use Starter for our own client base, and obviously if this goes well we'll want more than one client in it. Where are the limits?
- Hannah LoweSure. Starter is fifteen users as a soft limit and four connectors as a hard limit. So you can go over on users with a conversation, but not on connectors. If you find you need more, that's a commercial conversation, and I'd rather route it to Sophie and Marcus than improvise it myself. I'll let them know it's coming up.
- Lauren BickerstaffThat's helpful, thanks. I'm not asking for anything yet, just don't want to be surprised later. Never take a scope change without Joanna anyway.
- Ciaran DohertyOne practical point. Each client in its own schema, or each in its own connector? Because four runs out fast.
- Hannah LoweGood one. A connector can read several schemas if the role can see them, so one connector doesn't have to mean one client. But I'd think about isolation. Keep it clean per client where the client's own contract requires it. We can sketch it on the next call once you know how many clients are actually going to use it.
- Ciaran DohertyOkay. That's a design decision, not a today decision.
- Lauren BickerstaffAgreed. Right, let me read back the actions, because I never leave a call without them. Hannah, you send the table approval template, the one page diagram, and an answer from Ewan on hiding tables.
- Hannah LoweYes. And I'll send a short written summary of today's steps in order, so either of you can repeat it for a client without me.
- Lauren BickerstaffLovely. Ciaran, you write up the role and grants and the freshness check.
- Ciaran DohertyYes. Not on a Friday, mind. I'll do the dry run before anything touches the client's account.
- Lauren BickerstaffAnd me, I write the project description sentences, the overrunning definition, and the hand-over checklist. I'll show the client the list of tables before we connect anything. Has the client seen it yet? No. So that's mine, first.
- Hannah LoweThat's a good list. Anything I haven't covered that you'd want before we finish? Anything that's still bothering you?
- Ciaran DohertyNo. It was clearer than I expected. The grants thing was my mistake, not the product's.
- Hannah LoweEasily done, and now you know what to look for. Honestly, you've both picked this up quickly.
- Lauren BickerstaffI'd feel comfortable running the next one myself, with Ciaran on the Snowflake side. We'll pair on the Astley Brook set-up and ring you if we get stuck.
- Hannah LoweThat's exactly where I'd like you. Ring me whenever, or put the question in a ticket if it's not urgent. I'll check the diagram and the template go out today.
- Lauren BickerstaffBrilliant. Thanks so much, Hannah. Have a good rest of the week, and stay dry.
- Ciaran DohertyThanks. Bye.
- Hannah LoweThanks both, speak soon.
Callsmade from