Quabbin Clinical Research / BG-Demo – Demo
Callcompleted
Quabbin Clinical Research · 29 Jan 2026 16:30
Demo on the customer's sample extract. Interest is strong, but sponsor separation, the quality of study and sponsor matching and the study system export must be resolved. The 23 Mar 2026 target close still depends on the reviews.
What was said
What this says
As at Fri 9 Oct 2026Demo on the customer's sample extract. Interest is strong, but sponsor separation, the quality of study and sponsor matching and the study system export must be resolved. The 23 Mar 2026 target close still depends on the reviews.
What happened: Hannah Lowe showed a sponsor page, a chat question and a finance invoice view on the extract. Rachel Feldman asked about connectors, freshness and access by sponsor.
Customer view: Meredith said the access answer was "the answer I needed" and left the number to Gregory. Rachel said the finance view would save real time at month end.
Commercial: Hannah explained that Enterprise allows up to twenty connectors and covers freshness misses with service credits. The target close of 23 Mar 2026 still stands but depends on the reviews.
Watch: Rachel's worries are matching quality, since older studies are patchy and finance uses a separate sponsor code, and the clunky study system export. Gregory was not on this call.
Themes
As at Fri 9 Oct 2026Theme
Demo, matching, access
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 sends written notes on matching, the export and access early next week.
- Rachel sends the cleaned-up lookup table.
- Jordan sends Gregory the proposal detail.
Risks
As at Fri 9 Oct 2026- Poor study and sponsor code matching would show up as bad links and could lengthen implementation.
- The study management system export is clunky and its connector is not yet scoped.
- Sponsor separation and the security review must hold before Gregory decides.
Opportunities
As at Fri 9 Oct 2026- A finance invoice view beside study issues answered a pain Gregory raised in discovery.
- Enterprise freshness cover and up to twenty connectors fit the sources described.
Transcript
Jordan PikeHi all, afternoon. Can everyone hear me? Meredith, Rachel, welcome.
Rachel FeldmanHear you fine. Rachel Feldman, clinical operations data. Nice to meet you, Hannah.
Hannah LoweAnd you, Rachel. Hello Meredith. Thanks for making time, I know it's late in the day for me in London but it's a good hour for you.
Meredith SullivanIt's a good hour for us too. I'll start with a quick sponsor update, if I may. One of our biotech sponsors asked this morning whether two of their studies were affected by the same site problem, and it took us most of the day to answer. That's exactly why we're here.- Jordan PikeThat's a perfect lead-in. Quick agenda and time check: we have until about 17:25. Hannah will show B-Viz on the sample extract Rachel's team shared, then we leave time for questions on access and connectors. Hannah, over to you.
- Hannah LoweThanks, Jordan. Before I share anything, what do you most need to know from today? I'd rather aim at that than walk through every screen.
- Rachel FeldmanFor me, three things. Which sources connect, how fresh the data is each morning, and how access is separated by sponsor. The rest I can work out.
- Meredith SullivanAnd for me, one view per sponsor. If I search a sponsor, I want their studies, issues, calls and invoices in one place.
- Hannah LoweGood, that's a clear brief. I'll start with Meredith's and work towards Rachel's. Can you see my screen?
- Rachel FeldmanYes, clear.
- Hannah LoweSo this is a sponsor page. I've picked a sample sponsor from the extract. At the top you have the summary, then the studies underneath. Each study lists its open issues, drawn from the study records. Next to that, the recent calls with that sponsor, and below, the invoices. All of this is one page, built from the connected sources inside your Snowflake account.
- Meredith SullivanOkay, that's the thing. So I click on an issue and I see what was said about it?
- Hannah LoweYes. Let me open one. This issue links to a call where it was discussed, and the call shows its transcript and summary. To be precise, the link exists because the extract has a shared study identifier across the sources. If your sources don't share one, we'd need to design a mapping. That's a connector design question, and Rachel will know the answer better than I do.
- Rachel FeldmanWe have a study code in most places. Not all. Older studies are patchy. The finance side uses its own sponsor code and we've got a lookup table, but it's not perfect.
- Hannah LoweThe short answer is that a lookup table is workable. The longer answer is that I'd want to see how often it's wrong, because every bad match shows up as a bad link on a page like this. I'll put that in writing as something to check before we promise anything.
- Jordan PikeAnd to be transparent for the record, that's the kind of thing that decides how long implementation takes. Better we find it now.
- Meredith SullivanAgreed. Show me the question side. That's what my team will do all day.
- Hannah LoweSure. I'll use the chat. I'll ask: which studies for this sponsor have an open issue and an invoice due soon? Give it a moment.
- Hannah LoweThere. It names two studies, lists the open issues, and shows the invoices with their dates. Each statement has a source underneath it, so you can click through and check. I'd encourage your people to do that at first, because it builds trust.
- Rachel FeldmanWhat happens if the answer is wrong? Say the issue was closed in the study system but the tracker still shows it open.
- Hannah LoweThen it reflects whatever the sources say, and may show a conflict. It can't know which of your sources is right. What it does is show you both, with where each came from. That's useful, but it's not magic, and I won't pretend it is.
- Rachel FeldmanFair enough. Now freshness. When do I know the data is current?
- Hannah LoweThe nightly refresh is meant to be complete by 07:00 your local time on business days, on every tier. Each source also shows when it last loaded, and if one stops loading you'll see the record count stay flat. In Enterprise, a miss on freshness is covered by service credits, not only availability.
- Meredith SullivanGood to know. I'm not going to talk about money today, that's Gregory's side, but I'm glad it's in there.
- Rachel FeldmanNow access. If someone in sponsor relations looks after one sponsor, can they see only that sponsor?
- Hannah LoweLet me be careful, because this is where precision matters. Access follows the permissions in your Snowflake account. So separation by sponsor is something we configure with your team, using roles and row-level rules, and Enterprise adds single sign-on and user provisioning. What I can show today is the principle on the sample. What I won't do is tell you your exact setup is airtight before your security team has reviewed it.
- Meredith SullivanThat's the answer I needed, honestly. One sponsor's information can never be visible to another. If it needs a longer review, fine.
- Jordan PikeAnd I'll say it plainly: your security team will get the full picture from Hannah, including anything we can't do. No surprises.
- Rachel FeldmanConnectors, then. How many can we have, and which ones do you already support?
- Hannah LoweEnterprise allows up to twenty connectors, which is well beyond what you've described. The common ones are the CRM, the helpdesk, the call recorder, Microsoft 365 or Google Workspace for email, and the accounting system. For the study management system, I'll need to look at what it exposes. The short answer is it depends on its export options. I'll check and put it in writing.
- Rachel FeldmanIt does have an export, but it's clunky. I'd rather we scope it than guess.
- Hannah LoweAgreed. Let's put it on the design list.
- Meredith SullivanOne more demo ask. Can you show how a finance person would see it? Gregory won't be in the room for product, but his team will.
- Hannah LoweYes. This is an invoice view for the same sponsor. Each invoice sits beside its study and any open issue, so someone in finance can see why a milestone invoice might be queried before it goes out. That's the link Gregory described to Jordan.
- Rachel FeldmanThat would save us real time at month end.
- Jordan PikeLet me pause on what would make this a yes. Meredith, Rachel, is there anything you've seen that worries you?
- Rachel FeldmanOnly the matching quality and the study system export. If those work, I'm comfortable.
- Meredith SullivanMine is the sponsor separation, and the security review. If that holds, the rest is Gregory's call, and I'm not putting a number to him.
- Jordan PikeUnderstood. Here's where we are. The deal is still pencilled for 23 Mar 2026 as a target, and it depends on the reviews. Next steps: Hannah sends the written notes on matching, the export and access. Rachel, a bit more of the lookup table if you can share it. I'll send Gregory the proposal detail.
- Hannah LoweI'll have the notes to you early next week, and I'll flag anything I want to check before I commit to it.
- Rachel FeldmanI'll send the lookup table once I've cleaned it up.
- Meredith SullivanThanks, everyone. This was useful. One portfolio, one story, we're getting closer.
- Jordan PikeThanks, all. Speak soon.
Callsmade from