What was said
What this says
As at Fri 9 Oct 2026Hannah Lowe demoed ticket and usage data on one timeline in a test space. Alyssa Greenberg was positive. She wants written answers on data and access controls, then a proposal to take to Howard.
What happened: On 31 Mar 2026 Hannah showed a sample of Assunpink tickets and usage in a test space inside the customer's Snowflake account. Alyssa said the side-by-side timeline was exactly what she needed.
Customer view: She did not know the company had a Snowflake account, so data location and access need a clear written answer. She said the demo was much better than she expected.
Commercial: Hannah would only confirm the access controls for the tier in writing. Alyssa's conditions for moving forward are a written note and a proposal, which Jordan will send after Hannah's notes.
Watch: Ticket categories are a mess, with three tagging methods, so fix them before go-live. Howard, the CFO, has not been on a call, and his view is not shown.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Hannah sends written answers on the data and the access controls for the tier.
- Jordan follows up with a proposal once Hannah's notes are in.
- Jordan checks in with Alyssa at the end of the following week.
Risks
As at Fri 9 Oct 2026- Alyssa did not know the company had a Snowflake account, so IT involvement and the security questions are still open.
- Inconsistent ticket categories could weaken early results unless fixed before go-live.
- Howard has still not been involved and decides on spend.
Opportunities
As at Fri 9 Oct 2026- A proposal for a first team, with the access controls (leads see all, newer staff see their own tickets) as a selling point.
- A chance to tie the proposal to the Monday reconciliation problem Alyssa described.
Transcript
- Jordan PikeHi everyone, Jordan. Alyssa, good to see you again. Hannah's joining too, she's our solutions engineer and she's going to do the demo properly. Agenda's simple: we show it on your kind of data, then questions.
- Hannah LoweHi Alyssa, hi. Before I start, what's the one thing you most need to see today? I'd rather spend the time on that than on everything.
- Alyssa GreenbergHonestly, I need to see a ticket next to the usage for the same customer, with the dates lined up. That's the thing that takes my team all Monday.
- Hannah LowePerfect, that's a good place to start. I've loaded a sample of your tickets and usage into a test space in your Snowflake account, so we're working on data that looks like yours.
- Alyssa GreenbergOkay. Wait, that's our Snowflake? I didn't know we had one.
- Hannah LoweYou do, or your IT team does. We build inside your own account, so the data stays in your tenancy. I'll show you where that's set up in a minute.
- Jordan PikeTo be transparent, that's one of the first questions a security team asks, so it's good to have it up front.
- Hannah LoweRight. Let me share the screen. So this is the search. Type a customer name and it pulls the tickets, the usage and the last few calls in one list.
- Alyssa GreenbergOh. Okay. Can you do one of ours? Pick one that went quiet.
- Hannah LoweSure. Let's take a landlord account that had a lot of tickets last spring and then almost no logins. The short answer is you can see the drop straight away. The longer answer is that the tickets and usage are on the same timeline, so you can see which came first.
- Alyssa GreenbergYes. That's exactly it. We'd never know which came first, we'd argue about it.
- Hannah LoweMm. So for the team it's a question they can ask in plain English. Like, which customers had more than a few tickets and then dropped in usage?
- Alyssa GreenbergCan it do that? Try it.
- Hannah LoweTyping now. It gives you a list, but I'd check it with you before you trust it, because the answer depends on how your tickets are categorised.
- Alyssa GreenbergYeah, the categories are a mess. We've got three different ways of tagging a ticket.
- Hannah LoweThat's a very common thing, and it's worth fixing before go-live. I'll put a note on that in writing so we don't forget it.
- Jordan PikeHannah, can I ask what the demo looks like for your sales team, the team that would actually use it?
- Hannah LoweGood question. Each person gets a view they can build themselves, and the team lead sets what's shared. I'll show you the share settings in a second.
- Alyssa GreenbergWe'd want the leads to see everything and the newer people to see just their own tickets. Can it do that?
- Hannah LoweIt can, and I'll show you that. But I want to be precise about it. I can show you the controls today, and I'll confirm exactly how they work for your tier in writing. I don't want to overstate it.
- Alyssa GreenbergFine, I appreciate that. Okay, show me the controls.
- Hannah LoweRight. Here's the admin page. You can see who has access and to which views. It's simple enough that you could set it up on a Monday.
- Alyssa GreenbergThat's a relief. Our current tool takes a week of tickets to change anything.
- Jordan PikeHere's where we are on the timing. Alyssa, what would you need to see next to move this forward?
- Alyssa GreenbergProbably a written answer on the data and the access controls, and a proposal. Then I can take it to Howard.
- Hannah LoweI'll send the written answers after this. I'd rather send a precise note than a fast one.
- Jordan PikePerfect. I'll follow up with the proposal once Hannah's notes are in. What's the best time to come back to you?
- Alyssa GreenbergEnd of next week, probably. I'll check my diary.
- Hannah LoweOkay, I'll put the notes in the shared folder today. Thanks Alyssa.
- Alyssa GreenbergThanks, both of you. This was much better than I expected.
- Jordan PikeThanks Alyssa. Speak soon.